10 messages in net.sourceforge.lists.courier-maildropRe: [maildropl] segregate non-whiteli...
FromSent OnAttachments
email builderSep 4, 2008 2:52 pm 
email builderSep 4, 2008 3:32 pm 
Sam VarshavchikSep 4, 2008 3:32 pm 
email builderSep 4, 2008 4:46 pm 
moussSep 5, 2008 2:38 pm 
email builderSep 7, 2008 2:51 pm 
email builderSep 7, 2008 2:59 pm 
Sam VarshavchikSep 7, 2008 3:12 pm 
email builderSep 7, 2008 5:28 pm 
Devin RubiaSep 8, 2008 8:01 am 
Actions with this message:
Paste this link in email or IM:
Paste this link in email or IM:
Atom feed for this thread
Paste this URL into your reader:
Subject:Re: [maildropl] segregate non-whitelisted mails?Actions...
From:Devin Rubia (dev@thezone.net)
Date:Sep 8, 2008 8:01:54 am
List:net.sourceforge.lists.courier-maildrop

On Sun, Sep 07, 2008 at 02:52:06PM -0700, email builder wrote:

Exactly. So is there anything you can think of to thwart someone who uses a technique like that to learn a user's whitelist contents? It seems like most
spambots can't usually be bothered to have a list of acceptable FROM addresses for each destination address, so I think it'd have to be a situation where it'd be more
like a harrasement case than just spam. But aside from guessing about intent, what are the good measures to take against forged FROM addresses that happen to be on a user's whitelist?

Well, you could implement SPF, et al, in your MTA but that's not a job for maildrop and that would only work for those domains publishing SPF (or whatever) records.