I'm missing comprehension pieces also; however, I understand that if a message is sourced from a dynamic IP, it is expected to route it's mail thru "the correct" smtp server.

How the correctness of the smtp server is a mystery to me; however, I suspect it is any server with an IP which at least 2 (3?) octets in common with the dialup IP.

In other words, the DYN RBL lists will score against you even if you are using a "legitimate" smtp if that smtp server is not some how associated with the dynamic IP.

This is a problem for me. We have a number of customers who use Verizon DSL. The Verizon DSL has been refusing (I haven't tested this in the last month or 2) to transfer any mail originating from their DSL lines which does not conform to "[EMAIL PROTECTED]". This means that folks trying to use their own domains cannot use Verizon's smtp for out going mail. I provide an authenticated smtp server for them to use; but they always get tagged by the DYN RBL rules.

Andy Spiegl wrote:

Hi, out there.
I thought I finally understood the concept SA is using with dialup IPs,
but today I noticed that apparently I didn't.

Please, I need help understanding why a message get's tagged with
 RCVD_IN_DYNABLOCK, RCVD_IN_NJABL, RCVD_IN_NJABL_DIALUP, RCVD_IN_SORBS

It was sent from a machine (by sendmail) using this dialup IP
But it was sent to the smarthost (which has a fixed public IP).
From there it was relayed to the mailserver of the receiver machine.

I thought SA only uses these tags if the message was sent directly from the dialup IP to the receiver's mailserver, right?

What could have gone wrong?  I can provide examples if necessary.
I'd include it but would like to avoid to feed harvesters.
Oh, wait, idea: I'll put it on my website:
 http://andy.spiegl.de/sa-dialupip-example.txt

Thanks and have a nice weekend!
 Andy.

Reply via email to