> John Hardin wrote: > > What's odd here is it sounds like you're describing messages that have > > been received from a third-party MTA rather than an external MUA, so > > they _should_ have a Received: header added by that MTA.
On 01.12.09 08:50, Per Jessen wrote: > Yes, most would be coming from a third-party MTA - except for most of > the spam :-) so, is it the spam which you want prevent from checking by SA? :) > > Seeing the headers from one of these would be helpful, can you post a > > sample? Body not needed. What I'm looking for is the presence of any > > Received: header not added by _your_ MTA. I would wager that the > > problematic messages when examined in your queue will only have one > > Received: header. > > Here is one example: http://jessen.ch/files/email77 I see headers here byt they all seem to be added by inbound.spamchek.net which is I guess your machine. It is message generated by mail2.emirates.net.ae and the generating host did not create any Received: header (apparently since it did not receive the message - it only created it and sent it to you). > The really weird thing is that when I run that through SA manually > with "spamassassin -t -x ", there is no problem. It's because at time you scan the message, the headers were already added by your MTA. > That's why I'd like to have something like "score NO_RELAYS die" to make > spamd quit processing it. well, you can shortcircuit on NO_RELAYS but I think you should either fake Received: headeror use a program that does it (like milter) -- Matus UHLAR - fantomas, uh...@fantomas.sk ; http://www.fantomas.sk/ Warning: I wish NOT to receive e-mail advertising to this address. Varovanie: na tuto adresu chcem NEDOSTAVAT akukolvek reklamnu postu. Spam = (S)tupid (P)eople's (A)dvertising (M)ethod
