On 2/19/2009, post...@corwyn.net (post...@corwyn.net) wrote: >>> When mail is inbound and is spam, it gets flagged as spam by spam >>> assassin, and becomes addressed to, with recipient_delimiter, >>> user+s...@example.com
>> Right... so just configure spamassassin to add the x-spam header (I >> can't help you with particulars for that) IN ADDITION TO adding >> the recipient delimeter, and it will 'just work'. > Spam assassin sets the x-spam header on the way in. When it gets sent > back out, it doesn't get spam headers added. And since it's a reply, > the fact that spam headers were set set on the way in doesn't matter > since those headers, are no longer the headers. It's a new message, > with new headers. That doesn't make sense. I've never used spamassassin, so this just may be the way it works, and I really want to understand what I'm missing here, so... My understanding is that even though spamassassin is involved, and may even rewrite the recipient with the recipient delimeter, it should STILL be the same message (messageID, PREVIOUS HEADERS and so forth) - it just doesn't make sense that it is a NEW message and LOSES all of the previous header information. It sounds TO ME like you are simply doing it wrong. I would appreciate it if someone more knowledgable would chime in here. -- Best regards, Charles
