[Mimedefang] Notify sender: need to check for empty sender (postmaster notify)

Martin Bene martin.bene at icomedias.com
Sun Mar 3 09:08:22 EST 2002


I just saw a few strange error messages in my maillog; turns out that mimedefang objected to a postmaster notification with empty sender (<>) and obviously failed miserably in notify_sender.

mimedefang[15535]: Error from multiplexor: <>... User unknown
sendmail[15534]: g23DKjC9015534: Milter: data, reject=451 4.7.1 Please try again later
sendmail[15549]: g23DKrsn015549: <>... User unknown
sendmail[15549]: g23DKrsn015549: to=<>, delay=00:00:00, mailer=local, pri=0, dsn=5.1.1, stat=User unknown
sendmail[15549]: g23DKrsn015549: g23DKrso015549: DSN: User unknown
mimedefang-multiplexor: handleSlaveReceivedAnswer(0): Timeout or error: Flag = 3
mimedefang-multiplexor: Killing slave 0 (pid 15437): Busy timeout
mimedefang[15552]: Error from multiplexor: ERR Filter timed out
sendmail[15551]: g23DKrC9015551: Milter: from=<>, reject=451 4.7.1 Please try again later

Now im just not sure where/how to best check for this - Either action_notify_admin or signal_complete should be OK, I'll probably stick a fix in signal_complete:

    # Send notification to sender, if required
    if (-r "NOTIFICATION" && $Sender ne "<>") {

should do it.

Another thing I just noticed: in action_notify_administrator, the action flag notify_sender gets incremented:$Actions{'notify_sender'}++;
shouldn't this be 'notify_admin' so the right action gets sent to syslog at the end of signal_complete?

Bye, Martin

More information about the MIMEDefang mailing list