Matt
11-09-2007, 01:41 PM
I haven't been involved in the recent and numerous discussions regarding bounced/ forwarded e-mails. However, my general understanding is that bouncing non-deliverable messages (i.e. addessed to non-existent address) and forwarding messages to a non-FQ account are now frowned upon. If this is the case, then spammers have successfully broken two very common features of e-mail.
I do not think that only forwarding e-mail on accounts with SpamAssassin in place is going to address the problem of an ISP thinking that FQ is forwarding spam. SpamAssassin isn't perfect and some spam does get past. One idea, would be a conditional forwarder: only e-mails from specific senders would be forwarded. But how can you be sure that a 3rd party network will not improperly flag a valid e-mail as spam? The other issue is the sheer volume of forwarded messages appearing to be spam-like behavior.
Maybe it is time to investigate forging headers on a network level. Basically, FQ would forge the headers of the original sender, rather than appending its own headers.
I am really starting to think that for reliable e-mail it is necessary to use a company that specializes in e-mail. It is really becoming a challenge in the same way that hosting is. The problem with such a solution, is that I would be paying FQ for every account that I want to implement this for. This is particularly irksome, since even if I use a third party DNS to handle these issues, I still have to pay FQ to change its own internal settings, otherwise I will never see e-mails sent from a user on the FQ network. As an aside, has FQ given any thought to partnering with a company that specializes in e-mail?
-Matt
I do not think that only forwarding e-mail on accounts with SpamAssassin in place is going to address the problem of an ISP thinking that FQ is forwarding spam. SpamAssassin isn't perfect and some spam does get past. One idea, would be a conditional forwarder: only e-mails from specific senders would be forwarded. But how can you be sure that a 3rd party network will not improperly flag a valid e-mail as spam? The other issue is the sheer volume of forwarded messages appearing to be spam-like behavior.
Maybe it is time to investigate forging headers on a network level. Basically, FQ would forge the headers of the original sender, rather than appending its own headers.
I am really starting to think that for reliable e-mail it is necessary to use a company that specializes in e-mail. It is really becoming a challenge in the same way that hosting is. The problem with such a solution, is that I would be paying FQ for every account that I want to implement this for. This is particularly irksome, since even if I use a third party DNS to handle these issues, I still have to pay FQ to change its own internal settings, otherwise I will never see e-mails sent from a user on the FQ network. As an aside, has FQ given any thought to partnering with a company that specializes in e-mail?
-Matt