Hi Sam,

I'm currently experimenting with writing a custom courierfilter.  It works
fine, except for one thing.  When mails get rejected due to the sending
host being listed in a DNS blacklist (via the "BLACKLISTS" option in
/etc/courier/esmtpd), I get log entries of this format:

  Oct  9 03:37:30 io courieresmtpd:
error,relay=::ffff:68.35.83.35,from=<[EMAIL PROTECTED]>,to=<[EMAIL PROTECTED]
.net>: 511 Blocked - see http://www.spamcop.net/bl.shtml?68.35.83.35

But when a mail gets rejected due to my custom filter, I get log entries
of this format:

  Oct  9 03:59:00 io courieresmtpd:
error,relay=::ffff:217.88.243.27,from=<[EMAIL PROTECTED]>: 511 Just
testing...

The "to=<...>" part is missing.  I need this because I parse the log files
for rejection messages and create records in a PostgreSQL database, so my
users can use a web front-end to look up whether mails directed to them
have been rejected by the mail server.  Without the "to=<...>" part, I'm
unable to assign the rejection records to users.

Why is the "to=<...>" part missing in rejection log messages caused by a
courierfilter?



-------------------------------------------------------
This SF.net email is sponsored by: SF.net Giveback Program.
SourceForge.net hosts over 70,000 Open Source Projects.
See the people who have HELPED US provide better services:
Click here: http://sourceforge.net/supporters.php
_______________________________________________
courier-users mailing list
[EMAIL PROTECTED]
Unsubscribe: https://lists.sourceforge.net/lists/listinfo/courier-users

Reply via email to