Hello fellow Courier users ... The question is: Is there a limit regarding the number of lines of a multiline SMTP response as it is propagated from filtering host back to sender ???
To be more specific I have the following setup: Thunderbird client uses a Courier SMTP server (lets call it Host1) as an outgoing mail server. Host1 forwards all messages to another Courier SMTP server (lets call it Host2) using a simple esmtproute. Host2 runs a perl filter to check the message through spamassassin. if the message is clean it issent to the recipient(s). If the message is considered spam by spamassassin it is rejected and the perlfilter returns the spamassassin report in the form of a multiline SMTP error message. This SMTP error message is correctly logged in syslog at Host2 ---- Log Host2 -------------------------------------- Mar 21 11:56:24 blade-b3-vm7-relay courieresmtpd: started,ip=[::ffff:xxx.xxx.xxx.xxx] Mar 21 11:56:36 blade-b3-vm7-relay courieresmtpd: error,relay=::ffff:xxx.xxx.xxx.xxx,from=<[email protected]>: 571-Spam detection software, running on the system "blade-b3-vm6-antispam.servers.yyy.zzz", has Mar 21 11:56:36 blade-b3-vm7-relay courieresmtpd: error,relay=::ffff:xxx.xxx.xxx.xxx,from=<[email protected]>: 571-identified this incoming email as possible spam. The original message Mar 21 11:56:36 blade-b3-vm7-relay courieresmtpd: error,relay=::ffff:xxx.xxx.xxx.xxx,from=<[email protected]>: 571-has been attached to this so you can view it (if it isn't spam) or label Mar 21 11:56:36 blade-b3-vm7-relay courieresmtpd: error,relay=::ffff:xxx.xxx.xxx.xxx,from=<[email protected]>: 571-similar future email. If you have any questions, see Mar 21 11:56:36 blade-b3-vm7-relay courieresmtpd: error,relay=::ffff:xxx.xxx.xxx.xxx,from=<[email protected]>: [email protected] for details. Mar 21 11:56:36 blade-b3-vm7-relay courieresmtpd: error,relay=::ffff:xxx.xxx.xxx.xxx,from=<[email protected]>: 571- Mar 21 11:56:36 blade-b3-vm7-relay courieresmtpd: error,relay=::ffff:xxx.xxx.xxx.xxx,from=<[email protected]>: 571-Content preview: XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX Mar 21 11:56:36 blade-b3-vm7-relay courieresmtpd: error,relay=::ffff:xxx.xxx.xxx.xxx,from=<[email protected]>: 571- XXXXXXXXXXXXXXXX [...] Mar 21 11:56:36 blade-b3-vm7-relay courieresmtpd: error,relay=::ffff:xxx.xxx.xxx.xxx,from=<[email protected]>: 571- Mar 21 11:56:36 blade-b3-vm7-relay courieresmtpd: error,relay=::ffff:xxx.xxx.xxx.xxx,from=<[email protected]>: 571-Content analysis details: (9.1 points, 5.0 required) Mar 21 11:56:36 blade-b3-vm7-relay courieresmtpd: error,relay=::ffff:xxx.xxx.xxx.xxx,from=<[email protected]>: 571- Mar 21 11:56:36 blade-b3-vm7-relay courieresmtpd: error,relay=::ffff:xxx.xxx.xxx.xxx,from=<[email protected]>: 571- pts rule name description Mar 21 11:56:36 blade-b3-vm7-relay courieresmtpd: error,relay=::ffff:xxx.xxx.xxx.xxx,from=<[email protected]>: 571----- ---------------------- -------------------------------------------------- Mar 21 11:56:36 blade-b3-vm7-relay courieresmtpd: error,relay=::ffff:xxx.xxx.xxx.xxx,from=<[email protected]>: 571- 0.5 URI_NOVOWEL URI: URI hostname has long non-vowel sequence Mar 21 11:56:36 blade-b3-vm7-relay courieresmtpd: error,relay=::ffff:xxx.xxx.xxx.xxx,from=<[email protected]>: 571--1.9 BAYES_00 BODY: Bayes spam probability is 0 to 1% Mar 21 11:56:36 blade-b3-vm7-relay courieresmtpd: error,relay=::ffff:xxx.xxx.xxx.xxx,from=<[email protected]>: 571- [score: 0.0000] Mar 21 11:56:36 blade-b3-vm7-relay courieresmtpd: error,relay=::ffff:xxx.xxx.xxx.xxx,from=<[email protected]>: 571- 1.7 URIBL_BLACK Contains an URL listed in the URIBL blacklist Mar 21 11:56:36 blade-b3-vm7-relay courieresmtpd: error,relay=::ffff:xxx.xxx.xxx.xxx,from=<[email protected]>: 571- [URIs: XXXXXXXXXXX] Mar 21 11:56:36 blade-b3-vm7-relay courieresmtpd: error,relay=::ffff:xxx.xxx.xxx.xxx,from=<[email protected]>: 571- 2.5 URIBL_DBL_SPAM Contains an URL listed in the DBL blocklist Mar 21 11:56:36 blade-b3-vm7-relay courieresmtpd: error,relay=::ffff:xxx.xxx.xxx.xxx,from=<[email protected]>: 571- [URIs: XXXXXXXXXXX] Mar 21 11:56:36 blade-b3-vm7-relay courieresmtpd: error,relay=::ffff:xxx.xxx.xxx.xxx,from=<[email protected]>: 571- 1.6 URIBL_WS_SURBL Contains an URL listed in the WS SURBL blocklist Mar 21 11:56:36 blade-b3-vm7-relay courieresmtpd: error,relay=::ffff:xxx.xxx.xxx.xxx,from=<[email protected]>: 571- [URIs: XXXXXXXXXXX] Mar 21 11:56:36 blade-b3-vm7-relay courieresmtpd: error,relay=::ffff:xxx.xxx.xxx.xxx,from=<[email protected]>: 571- 1.2 URIBL_JP_SURBL Contains an URL listed in the JP SURBL blocklist Mar 21 11:56:36 blade-b3-vm7-relay courieresmtpd: error,relay=::ffff:xxx.xxx.xxx.xxx,from=<[email protected]>: 571- [URIs: XXXXXXXXXXX] Mar 21 11:56:36 blade-b3-vm7-relay courieresmtpd: error,relay=::ffff:xxx.xxx.xxx.xxx,from=<[email protected]>: 571- 1.3 URIBL_MW_SURBL Contains a Malware Domain or IP listed in the MW SURBL Mar 21 11:56:36 blade-b3-vm7-relay courieresmtpd: error,relay=::ffff:xxx.xxx.xxx.xxx,from=<[email protected]>: 571- blocklist Mar 21 11:56:36 blade-b3-vm7-relay courieresmtpd: error,relay=::ffff:xxx.xxx.xxx.xxx,from=<[email protected]>: 571- [URIs: XXXXXXXXXXX] Mar 21 11:56:36 blade-b3-vm7-relay courieresmtpd: error,relay=::ffff:xxx.xxx.xxx.xxx,from=<[email protected]>: 571- 0.6 URIBL_SC_SURBL Contains an URL listed in the SC SURBL blocklist Mar 21 11:56:36 blade-b3-vm7-relay courieresmtpd: error,relay=::ffff:xxx.xxx.xxx.xxx,from=<[email protected]>: 571- [URIs: XXXXXXXXXXX] Mar 21 11:56:36 blade-b3-vm7-relay courieresmtpd: error,relay=::ffff:xxx.xxx.xxx.xxx,from=<[email protected]>: 571- 1.6 URIBL_SBL Contains an URL's NS IP listed in the SBL blocklist Mar 21 11:56:36 blade-b3-vm7-relay courieresmtpd: error,relay=::ffff:xxx.xxx.xxx.xxx,from=<[email protected]>: 571- [URIs: XXXXXXXXXXX] Mar 21 11:56:36 blade-b3-vm7-relay courieresmtpd: error,relay=::ffff:xxx.xxx.xxx.xxx,from=<[email protected]>: 571- Mar 21 11:56:36 blade-b3-vm7-relay courieresmtpd: error,relay=::ffff:xxx.xxx.xxx.xxx,from=<[email protected]>: 571 End of response ----------- END of log Host2 ------------------------------------------------- The problem is that back to Host1 a truncated (to first 10 lines) SMTP error message is logged and also included in the dsn message sent back to the sender of the message. ---------------- Log in Host1 ---------------- Mar 21 11:56:36 blade-b3-vm2-smtp courieresmtp: id=000...06F1F,from=<[email protected]>,addr=<[email protected]>: 571-Spam detection software, running on the system "blade-b3-vm6-antispam.servers.yyy.zzz", has Mar 21 11:56:36 blade-b3-vm2-smtp courieresmtp: id=000...06F1F,from=<[email protected]>,addr=<[email protected]>: 571-identified this incoming email as possible spam. The original message Mar 21 11:56:36 blade-b3-vm2-smtp courieresmtp: id=000...06F1F,from=<[email protected]>,addr=<[email protected]>: 571-has been attached to this so you can view it (if it isn't spam) or label Mar 21 11:56:36 blade-b3-vm2-smtp courieresmtp: id=000...06F1F,from=<[email protected]>,addr=<[email protected]>: 571-similar future email. If you have any questions, see Mar 21 11:56:36 blade-b3-vm2-smtp courieresmtp: id=000...06F1F,from=<[email protected]>,addr=<[email protected]>: [email protected] for details. Mar 21 11:56:36 blade-b3-vm2-smtp courieresmtp: id=000...06F1F,from=<[email protected]>,addr=<[email protected]>: 571- Mar 21 11:56:36 blade-b3-vm2-smtp courieresmtp: id=000...06F1F,from=<[email protected]>,addr=<[email protected]>: 571-XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX Mar 21 11:56:36 blade-b3-vm2-smtp courieresmtp: id=000...06F1F,from=<[email protected]>,addr=<[email protected]>: 571- XXXXXXXXXXXXX [...] Mar 21 11:56:36 blade-b3-vm2-smtp courieresmtp: id=000...06F1F,from=<[email protected]>,addr=<[email protected]>: 571- Mar 21 11:56:36 blade-b3-vm2-smtp courieresmtp: id=000...06F1F,from=<[email protected]>,addr=<[email protected]>: 571-Content analysis details: (9.1 points, 5.0 required) Mar 21 11:56:36 blade-b3-vm2-smtp courieresmtp: id=000...06F1F,from=<[email protected]>,addr=<[email protected]>,status: failure ------------------------ END of log in Host1 Obviously i need the full spamassassin report to be received by the sender of the message so that she knows why her message is rejected. Additional info: Both Hosts are Debian 6.0.7 Courier version at both hosts as follows dpkg -l | grep courier ii courier-authdaemon 0.63.0-3 Courier authentication daemon ii courier-authlib 0.63.0-3 Courier authentication library ii courier-authlib-ldap 0.63.0-3 LDAP support for the Courier authentication library ii courier-authlib-userdb 0.63.0-3 userdb support for the Courier authentication library ii courier-base 0.65.0-3 Courier mail server - base system ii courier-mta 0.65.0-3 Courier mail server - ESMTP daemon Any suggestion would be most welcome Thank you in advance Constantine Kousouris ------------------------------------------------------------------------------ Learn Graph Databases - Download FREE O'Reilly Book "Graph Databases" is the definitive new guide to graph databases and their applications. Written by three acclaimed leaders in the field, this first edition is now available. Download your free book today! http://p.sf.net/sfu/13534_NeoTech _______________________________________________ courier-users mailing list [email protected] Unsubscribe: https://lists.sourceforge.net/lists/listinfo/courier-users
