SPF wouldn't add you to a blacklist since it operates realtime (at the SMTP level). But just because you log in to your home ISP doesn't mean you can't send mail through your work ISP if you have SMTP authentication of course.

In that instance you'll know immediately that your SMTP fails and that you've got an incorrect configuration. You then correct the SMTP sender for any particular work email and resend.

FWIW, all of our clients use their boxes remotely since we don't offer dialup service. They have to do the same thing.

On Sep 13, 2004, at 3:19 PM, Steve Bertrand wrote:

But still, my recommendation is to use an SPF pass to decrease the
spam
score and to not use SFP fails to blacklist.

This is really the first post I've looked at on this thread, but I see your point...correct me if I am wrong with this situation:

I work for an ISP. My laptop, seldomly moved from the office is
configured to send out my [EMAIL PROTECTED] email through this ISP
SMTP server. I take my laptop home, which is connected to a different
SMTP server. Unwittingly, I change the SMTP server to the home ISP's
server and send out mail (which was always a common practice).

AFAICT, this instance would blacklist me and/or my entire domain
because of a user mistake...correct? (As it would send my
[EMAIL PROTECTED] email through a server not listed in our SPF
records).

Steve

Kindest regards,

Ron

"What shall we do? What shall we do?" he cried, "Escaping goblins to be caught by wolves!" - Bilbo Baggins

The Hobbit by J. R. R. Tolkein
http://www.apple.com/trailers/newline/returnoftheking/trailer_large.html



Reply via email to