On 5/22/2006 12:16 PM, Kenneth Porter wrote:
--On Saturday, May 20, 2006 4:54 PM -0700 jdow <[EMAIL PROTECTED]> wrote:
Looking at your own email it comes from a COMCAST cable connection
in Palmer Ranch Florida through the WFGB mailer. The WFGB mailer is
not in SORBS anywhere. YOUR address most certainly is a dialup. So
it WILL get tagged unless your mail goes through a machine that
properly vouches for it. 68.32.0.0/11 (68.32.0.0-68.63.255.255) is
a dynamic IP netblock.
How does another machine "properly vouch for it"? If I route my mail to
a colocated host under my control, how do I make that host vouch for the
mail from my house?
There's no vouching. SpamAssassin simply looks for one relay between
your network and the sender. If there isn't a relay between the two
(that is the sender sent mail directly to your MX) the mail is treated
as direct-to-MX and its IP is looked up in various blacklists.
Normally a sender would relay through their own mail server which would
then relay the mail to your MX, thus avoiding having the sender's
(end-user's MUA) IP looked up... their mail relay would be looked up though.
When your sending mail to your own domain which uses the same mail
server for everything this relay between the client and your MX doesn't
exists and you run in to the problem described. As previously noted in
this thread, it is explained here:
http://wiki.apache.org/spamassassin/DynablockIssues
Daryl
