[Raw Msg Headers][Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Another test of 2.99.49p6 ..
I had problems at nic.funet.fi in form of somebody using
it as a spam-relay, and thus I fortified policy processing
somewhat -- although now it definitely will slow down..
My main problem of using the original policytest stuff is
that I don't know who all are using nic.funet.fi as their
MX server, thus I can't quite easily just write a list of
who are accepted targets (smtp-policy.mx in the policy-builder.sh
Also I saw vast number of invalid domains being used in the
MAIL FROM:<..>s, and for that I added another policy flag:
which does a lookup of MX and A (and AAAA) records, and if
it finds any, the sender is acceptable.
I am have a hope that this would be 'final' test for 2.99.49p6,
and as usual, feedback is appreciated.
Next week (Aug 11-15) I will be at Munich at IETF, but it
will be a networking confrence with GOOD network connectivity :)
/Matti Aarnio <email@example.com>
Thu Aug 7 23:00:52 1997 Matti Aarnio <firstname.lastname@example.org>
* SiteConfig.in, scheduler/scheduler.c, scheduler/update.c:
Eugene Crosser's SYSLOGFLGs for the scheduler.
* scheduler/threads.c, scheduler/update.c:
A weird null-pointer derefferrence problem with gcc 18.104.22.168
at DEC UNIX 4.0 -- perhaps it is about gcc bug...
* include/policy.h, proto/db/smtp-policy.src,
Understand new policy parameters:
of which the first (when existing) uses DNS lookup to
verify that the source address is acceptable, and the
second uses DNS to check that we are MX for the given
target domain. '+' means 'yield SOFT (4XX) error', and
'-' means 'yield HARD (5XX) error'...
Eugene Crosser's syslog fix
* smtpserver/smtpserver.c, util/policy-builder.sh:
If policy database is defined, but can't be opened,
smtp-server responds "400 Policy database problem, code=NN"
to every command (except 'help' and 'quit').
The codes mean: 1: Unknown db format, 2: db open failed
A mistake in character counting in RFC821_822QUOTE macro.
Detect if scheduler job-description file writing has
a fault, and give up. The job will go into deferred
directory, from whence it should be (via cron?) moved
back into the router.
Removed various +XXXX targets, and touches of them..
When the transport-agent receives 'SIGTERM', it sees if
it can die immediately, or if it should take a delayed
action on the death issue. The delayed action is done
when the smtp transport is doing '.' write operation,
and waiting for the acknowledgement, plus doing diagnostics.
At Alpha, storing LONG_MAX into time_t doesn't work, use INT_MAX.