SpamFilter rejecting store & forward mail |
Post Reply ![]() |
Author | |
jacksun ![]() Newbie ![]() Joined: 24 February 2005 Status: Offline Points: 31 |
![]() ![]() ![]() ![]() ![]() Posted: 25 January 2006 at 8:23pm |
Hi everyone, I have a little problem I need to resolve and I hope you can help. Here is the situation: We use Frontbridge for store & forward service. Basically if our mail servers are offline our mail is redirected to them, they store it and when our servers come back online they forward it through to us. So, to test this service we took our mail servers offline for scheduled maintenance. Everything worked fine, notifications, reports, stats etc until we turned our servers back online. I need to prevent their servers from ever being blocked, except for emails that are spam that would be blocked if the original senders server was seen by spamfilter. Any ideas? Thanks, Edited by jacksun |
|
![]() |
|
Desperado ![]() Senior Member ![]() ![]() Joined: 27 January 2005 Location: United States Status: Offline Points: 1143 |
![]() ![]() ![]() ![]() ![]() |
Wayne, Tough one ... one that I resolved only by running my own backup servers at our 2nd facility and using SpamFilter. Once a server is allowed to receive its mail for you, any blocking due to connection stuff, rDNS, MX, even dnsbl's will no longer work (as you saw) and you are now down to filtering by the more subjective keywords, froms, to's ETC. No help from me. |
|
The Desperado
Dan Seligmann. Work: http://www.mags.net Personal: http://www.desperado.com |
|
![]() |
|
LogSat ![]() Admin Group ![]() ![]() Joined: 25 January 2005 Location: United States Status: Offline Points: 4104 |
![]() ![]() ![]() ![]() ![]() |
Wayne,
That is a bit problematic... In your scenario, as Dan said, many of the IP-based filter will fail to detect spam as the IP address of the sender is masked by the mail holding service. Furthermore, other tests, like the SPF filter, will actually cause emails to be rejected as the sender (Frontbridge) is not going to be an approved IP for the sender's email domain (SPF verifies that the IP used to send an email has been authorized by the domain administrators to send emails on their behalf). That said, you should be able to prevent Frontbridge to be permanently blocked by adding their IP in the "DoNotAddIPtoHoneypot" settings. That setting is used not only by the honeypot, but also by the new IP blacklist cache, so that neither filter will permanently block them. If you're using the antivirus plugin, you'll need to disable the option to "Autoblock virus sender's IP" as well. From then on, unless Frontbridge's IP address appears on the various MAPS RBL lists, they should not be blocked (please note the SPF comment above, as those emails *will* be blocked...) |
|
![]() |
|
jacksun ![]() Newbie ![]() Joined: 24 February 2005 Status: Offline Points: 31 |
![]() ![]() ![]() ![]() ![]() |
Hi Guys, thanks for the feedback. One key piece of information from Roberto is that the "DoNotAddIPtoHoneypot" setting works on the Blacklist IP cache as well. I am not sure that SPF is an issue, here is a header from one of the inbound mails: Received: from 63.161.60.29 by ccsmail1.ccs.corp (LogSat Software SMTP Server) Tue, 24 Jan 2006 10:51:32 -0700 The originators IP is the [84.114.139.28] Bigfish.com is the domain frontbridge uses for all its mail servers so this is legitimate. My biggest issue is making certain they are filtered to the largest degree possible and not blocked from delivery. Some false positives are acceptable as this situation will not occur often and users can us their quarantine web access to grab what they didn't get and needed. Thanks, |
|
![]() |
Post Reply ![]() |
|
Tweet
|
Forum Jump | Forum Permissions ![]() You cannot post new topics in this forum You cannot reply to topics in this forum You cannot delete your posts in this forum You cannot edit your posts in this forum You cannot create polls in this forum You cannot vote in polls in this forum |
This page was generated in 0.203 seconds.