On Friday 26 January 2007 06:24, Matt Kettler wrote: > Eddie wrote: > > I've set up DCC within Spamassassin, and enabled greylisting. At first, > > I couldn't see any mails being "bounced", pending a re-tramsmission, > > until I realised that all the e-mails I was looking at were maked as spam > > by SA, in which case, my understanding is that it's a waste of time > > asking for a re-transmission, as they're already identified as spam. > > > > However, the first "genuine" e-mail that i received, also was passed > > though immediately, instead of being "bounced", for a re-send. > > > > When I checked the DCC log for that particular message, it stated: > > "result: temporary greylist embargo". However, it was immediately passed > > though to the destination mailbox. > > > > So, why was it then that this message wasn't "held", to prove it wasn't > > spam. > > > > Or, have I still got problems with my configuration. > > > > Cheers. > > DCC's greylisting feature only works when you integrate DCC directly > into your MTA. > > When you call DCC from SpamAssassin, the only thing SA will ever do with > it is use it for scoring. > > SpamAssassin, being a simple mail filter, has absolutely no way to > directly cause a message to be greylisted. SA cannot delete, bounce, > redirect, greylist, or do anything at all that would alter message > delivery. Now, any other tool in your mail chain can examine SA's > results and take such actions, provided they are within that tools > power. (ie: procmail could delete or redirect, but it could not > greylist. Procmail is called after the message has already been > accepted, therefore the time to greylist has already passed.)
Thanks. I'd kinda guessed that, after sleeping on it. I'm also guessing that if I'm pulling down mail, from a POP mailbox at my ISP, there's really no way to use greylisting at all. Because the mail has already been accepted by my ISP. Cheers.
