> 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
I have no idea how this dynablock RBL is working. There shouldn't be any way that it is flagging the receiver's system...what good would that do? It wouldn't surprise me that it isn't working correctly. I have little confidence in RBL's at the best of times. I was stunned when I saw that SA was scoring a dynablock hit at 2.6! Gerry ------------------------------------------------------- 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
