I would like to start some discussion about the current e-mail forwarding policy and problems that arise from it.
Current situation
Forwarding is done by postfix and the mail_virtual table. There is a mapping from local-address -> destination.
mysql> select id,email,destination from mail_virtual where destination like '%t-online.de';
+----+--------------------------+-----------------------------------------------------+
| id | email | destination |
+----+--------------------------+-----------------------------------------------------+
| 5 | some@domain.com | some@t-online.de |
Problem
The problem with that is, that e-mail is forwarded, regardless of any other filter rules that might exist in Sieve. Especially SPAM is forwarded regardless of the spamassassin scoring.
spamd: result: Y 16 - RCVD_IN_BL_SPAMCOP_NET,RCVD_IN_PBL,RCVD_IN_SORBS_DUL,RCVD_IN_XBL,RDNS_DYNAMIC,SPF_HELO_NEUTRAL,TRACKER_ID,URIBL_JP_SURBL,URIBL_WS_SURBL scantime=0.2,size=912,user=spamd,uid=10009,required_score=5.0,rhost=localhost,raddr=127.0.0.1,rport=55632,mid=<FB42B745.860CF341@gmail.com>,autolearn=spam
[...]
postfix/smtp[4856]: *********: to=<some@t-online.de>, orig_to=<some@domain.com>, relay=mx01.t-online.de[194.25.134.72]:25, delay=0.14, delays=0.02/0.01/0.04/0.07, dsn=5.7.0, status=bounced (host mx01.t-online.de[194.25.134.72] said:
550-5.7.0 Message considered as spam or virus, rejected 550-5.7.0 Your IP: ********* 550-5.7.0 Mailhost: mailin06.aul.t-online.de 550-5.7.0
[...]
Proposal
I would suggest to use Sieve even for Froxlor-controlled forwarding. That would give you the option to not forward SPAM by putting a blocking-rule on top of the rule-list.
Question
Simon Niechzial
I would like to start some discussion about the current e-mail forwarding policy and problems that arise from it.
Current situation
Forwarding is done by postfix and the mail_virtual table. There is a mapping from local-address -> destination.
Problem
The problem with that is, that e-mail is forwarded, regardless of any other filter rules that might exist in Sieve. Especially SPAM is forwarded regardless of the spamassassin scoring.
Proposal
I would suggest to use Sieve even for Froxlor-controlled forwarding. That would give you the option to not forward SPAM by putting a blocking-rule on top of the rule-list.
What do you think about this? What could be pitfalls?
5 answers to this question
Recommended Posts
Archived
This topic is now archived and is closed to further replies.