I re-read the OP--I may have misunderstood. I wouldn't process (e.g. forward) anything without virus/spam-filtering it first. If you make yourself that front line, you'll have to handle it.
| Linode Forum https://forum.linode.com/ |
|
| delay in /etc/mail/aliases https://forum.linode.com/viewtopic.php?f=11&t=3878 |
Page 1 of 1 |
| Author: | holdOnCowboy [ Fri Feb 06, 2009 12:34 am ] |
| Post subject: | delay in /etc/mail/aliases |
I am running sendmail on my website so that I can offer "vanity emails" for a few users... i.e. john@mysite.com which automatically forwards to their "real" email using /etc/mail/aliases. To filter spam, I forward not directly to their "real" email, but to a gmail account, which in turn forwards to their "real" email (while leaving a copy in the gmail account) The problem I'm having is that users are still complaining about spam. When I check the gmail account, I can see that the messages they are complaining about are indeed in the Spam box. What I think is hapenning is that at the time the email is forwarded, Gmail does not yet know the mail is spam.... later on, based on gmail user feedback, it learns that it is spam. By that time, it's too late for my poor users... they've already got the forwarded spam. My idea is to set up sendmail to DELAY forwarding to gmail... hopefully that way, gmail will have a chance to learn that it's spam. Is there an easy way to do that? |
|
| Author: | pratfall [ Tue Feb 10, 2009 1:30 pm ] |
| Post subject: | |
Take a look at Greylisting; a greylisting system looks at each incoming email's to field, from field and sending server, and, if it hasn't see that combination in the last 24 hours (configurable), it has the mail server send a 451 "try again later" until some amount of time has passed (I use 20 minutes), and then allows the mail to pass through. I use Postfix+Postgrey, but there are Sendmail implementations, too: http://www.greylisting.org/implementati ... mail.shtml |
|
| Author: | phvt [ Tue Feb 10, 2009 3:16 pm ] |
| Post subject: | |
Actually, I think the problem may be that when you forward, you cause the message to originate from an unauthorized server. For example, a message from joeuser@yahoo will seem to be originating from your server instead of Yahoo!, which Gmail might see as a forgery and flag as spam. This problem is perhaps most closely associated with SPF: http://www.openspf.org/FAQ/Forwarding (see the note about "remailing"). |
|
| Author: | Xan [ Tue Feb 10, 2009 10:08 pm ] |
| Post subject: | |
Or it could even be the inverse problem. If the spam originates from a known bad IP, and then he resends it from a nominally trusted IP (Gmail's), then it could be less likely to be flagged. |
|
| Author: | phvt [ Tue Feb 10, 2009 10:23 pm ] |
| Post subject: | |
I re-read the OP--I may have misunderstood. I wouldn't process (e.g. forward) anything without virus/spam-filtering it first. If you make yourself that front line, you'll have to handle it.
|
|
| Page 1 of 1 | All times are UTC-04:00 |
| Powered by phpBB® Forum Software © phpBB Group http://www.phpbb.com/ |
|