Saturday, September 11, 2004, 7:04:55 AM, Darin Cox wrote: > Yes. One of the flaws of SPF. However, you can also use a weaker SPF > record that says basically that you don't know what mail server it is coming > from. Not much point in that except to say that you're using SPF, though I > suppose it might be possible that a particular mail admin might penalize > sites that haven't implemented SPF in spam weighting.
This is not good ... I don't see SPF becoming a useful tool, since I have a few customers in this particular situation, and without widespread SPF implementation I don't see it particularly helpful. > A caveat on the above flaw: SPF does have the ability to reference another > domains SPF records, so if the ISP in question has implemented SPF you > should be able to "inherit" their SPF implementation by referencing it in > your own. I haven't had an occasion to try that out yet, though. But this requires me to keep up each customers ISP ... what a pain. And what happens when one travels? I was traveling a few weeks ago, and the hotel's IP connection had port 25 blocked ... so I couldn't use my own SMTP server remotely using SMTP AUTH. I called the hotel's ISP and they opened up port 25 for my room's IP for my stay since I was going to be there for a week, but the average person is not going to do this. --- [This E-mail was scanned for viruses by Declude Virus (http://www.declude.com)] --- This E-mail came from the Declude.JunkMail mailing list. To unsubscribe, just send an E-mail to [EMAIL PROTECTED], and type "unsubscribe Declude.JunkMail". The archives can be found at http://www.mail-archive.com.
