On 15.06.2009, at 02:44, Sam Varshavchik wrote: > Lorenzo Perone writes: > >> Hello to all, >> I'm getting these really weird DSN messages and can't really >> figure out now if it's the client going nuts, the courier MTA >> finally starting to make funy jokes with crappy clients, or if >> it's some kind of hacking/spamming attempt over SqWebmail or over >> any other part of the package. Below there's such a message. >> ... >> X-Spam-Checker-Version: SpamAssassin 3.2.5 (2008-06-10) on >> mail.example.com >> X-Spam-Level: *** >> X-Spam-Status: No, score=3.5 required=4.0 tests=ALL_TRUSTED,BAYES_00, >> EMPTY_MESSAGE,MISSING_HB_SEP,MISSING_SUBJECT,TVD_SPACE_RATIO >> autolearn=no >> version=3.2.5 >> X-Maildrop: Processing >> X-Env-Sender: #...@[] >> Delivered-To: [email protected] >> Received: from localhost (localhost [127.0.0.1]) >> > The Received: header is the standard Received: header on Courier's > bounces. Everything else is probably due to a horribly broken mail > filtering recipe that chewed up the entire message.
Hi Sam! Thanx for this one, it definitively makes sense to look there... do You actually mean delivery filters (called over maildrop) or perlfilter (which is the only other one I use)? Note that, as suggested/discussed earlier, I do _not_ modify (at least not intentionally) the messages in the courierfilter phase. In fact, the spam assassin headers used to appear _after_ the maildrop ones... wonder if that's a hint too. Big thanx for taking time, and Regards, Lorenzo ------------------------------------------------------------------------------ Crystal Reports - New Free Runtime and 30 Day Trial Check out the new simplified licensing option that enables unlimited royalty-free distribution of the report engine for externally facing server and web deployment. http://p.sf.net/sfu/businessobjects _______________________________________________ courier-users mailing list [email protected] Unsubscribe: https://lists.sourceforge.net/lists/listinfo/courier-users
