

![]() | Start a set with this search |
![]() | Include this search in one of my sets |
![]() | Exclude this search from one of my sets |
![]() | Permalink to these results Paste this link in email or IM: |
| Atom feed for tracking future search results Paste this URL into your reader: |
10 messages in net.sourceforge.lists.courier-maildropRe: [maildropl] segregate non-whiteli...| From | Sent On | Attachments |
|---|---|---|
| email builder | Sep 4, 2008 2:52 pm | |
| email builder | Sep 4, 2008 3:32 pm | |
| Sam Varshavchik | Sep 4, 2008 3:32 pm | |
| email builder | Sep 4, 2008 4:46 pm | |
| mouss | Sep 5, 2008 2:38 pm | |
| email builder | Sep 7, 2008 2:51 pm | |
| email builder | Sep 7, 2008 2:59 pm | |
| Sam Varshavchik | Sep 7, 2008 3:12 pm | |
| email builder | Sep 7, 2008 5:28 pm | |
| Devin Rubia | Sep 8, 2008 8:01 am |

![]() | Permalink for this message Paste this link in email or IM: |
![]() | Permalink for this thread 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: | email builder (emai...@yahoo.com) | |
| Date: | Sep 4, 2008 3:32:45 pm | |
| List: | net.sourceforge.lists.courier-maildrop | |
1) I am attempting to implement a solution wherein I have a whitelist of senders whose mails go to the inbox (nothing new here). I don't know for sure yet, but I think it'd not be too hard to make maildrop work with my whitelist (?). (I know I can use whitelisting in SpamAssassin, for example, but what I am trying to do (see below) isn't necessarily related to spam scanning. So I figure the best placement for this is in the delivery agent. Am I wrong?)
2) The kicker is that I want all other (non-whitelisted senders) mail to be filtered elsewhere. I think if I can come up with a maildrop script that accomplishes #1 above, this may not be too hard, but I am concerned about two things:
a) Reading in a (possibly big) whitelist from a file or database during maildrop execution may not be efficient(?) and may be hard to code in maildrop script language
b) The FROM header is easily forged -- can I rely on typical postfix EHLO and client checks (such as requiring the client domain to match the sender domain or whatever) to catch those forgeries and safely be naive/trusting of what the FROM header says if I implement this in maildrop? Even if this kind of filtering was implemented elsewhere, it'd still have to be based on the FROM header, so maybe this question becomes irrelevant except to know how much postfix rules can help make the FROM header trustable....??
For example, I know in postfix you can reject mail where the EHLO does not match
the sender domain, but that some mailing lists resend mails on behalf of their
original sender, so if I turn that on, my FROM headers become more trustable,
but mailing list emails will all get blocked. Others that may get blocked are
users who send mail from their work address using gmail for example. Is there a
good way to work around this or is whitelisting FROM headers inherently flawed?
------------------------------------------------------------------------- This SF.Net email is sponsored by the Moblin Your Move Developer's challenge Build the coolest Linux based applications with Moblin SDK & win great prizes Grand prize is a trip for two to an Open Source event anywhere in the world http://moblin-contest.org/redirect.php?banner_id=100&url=/
_______________________________________________ Courier-maildrop mailing list Cour...@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/courier-maildrop







