If there are recieved-from headers from the recipient's mail system, then they may get checked in the rbl's depending on how deep they are. The recipient can use the 'trusted_networks' option that was added in 2.60 to get around that problem. I don't have the start of the thread on the machine I'm writing this from so hopefully I understood what was going on ;]


Ryan Moore ---------- Perigee.net Corporation 704-849-8355 (sales) 704-849-8017 (tech) www.perigee.net

Terry Milnes wrote:
But you are missing the point, mail is being identified as RCVD_IN_DYNABLOCK when it is the recipient who is in the dial up block, not the sender.

The sender is on the rogers network using aloak smtp/pop3 servers, sending a message to a domain that is in the dial up block.

The message should NOT be tagged as RCVD_IN_DYNABLOCK because the "received from" is from aloak.

I thought I might have a problem explaining this, take a look at the headers I supplied, a real close look and you should be able to see what I mean.

As for the Rogers Network, there is a problem there as well, they sell commercial accounts that did not have these restrictions you mention, yet over the last few weeks these commercial accounts are being treated the same as the residential. I am calling them tomorrow about this issue, it costs three times as much for the commercial services, hopefully their policies haven't changed.....

Thanks for the response btw.

Terry




------------------------------------------------------- This sf.net email is sponsored by:ThinkGeek Welcome to geek heaven. http://thinkgeek.com/sf _______________________________________________ Spamassassin-talk mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/spamassassin-talk

Reply via email to