On 12/19/2011 8:38 AM, welkinator wrote:
> My provider [ISP] is
austin.rr.com (RoadRunner).
>
> Recently all my posts to several Yahoo groups have been bounced
> with this message:
>
> /quote on
> Your email was not delivered due to a suspected guidelines violation.
> Please visit
http://groups.yahoo.com/local/guidelines.html
> /quote off
>
> If you go to the link provided it says:
>
> /quote on
> Most common cause - Using an external email client...
The quoted content does not come from the quoted link,
but something just like it appears here:
<
http://help.yahoo.com/kb/index?locale=en_US&page=content&y=PROD_GRPS&id=SLN3263&impressions=true>
Here is the explanation of SPF authentication,
as will be the first result of Googling "SPF":
<
http://en.wikipedia.org/wiki/Sender_Policy_Framework>
I'll now quote a key sentence from that article:
"SPF allows the _owner of an Internet domain_
to specify which computers are authorized to send mail
with _sender addresses in that domain_,
using special Domain Name System (DNS) records"
> But I _DO_ use "Allow Authentication"!!
Your "authentication" to RR permits you to use RR's outgoing servers to send mail,
but RR's outgoing servers are not those which OTHER domains publish in SPF records
as their self-provided outgoing servers; therefore, any time that you
use an RR server while your mail says "From: some_other_domain,"
an SPF test based on that OTHER domain in your "From" address will fail.
> I suspect it has something to do with using Road Runner to [send] my email
> with a Gmail return address, but I don't know how to overcome this.
Your suspicion is correct, and one way to overcome it,
_when the domain of your sending address publishes SPF records_
AND
_when a recipient's domain refuses to accept mail sent via other servers_
is to use the outgoing servers provided by the domain of your sending address.
A second way to overcome it is to NEVER USE YAHOO for anything related to email,
or to newsgroups, or for anything, given its management's miserable record
of bad decisions causing widespread customer disservice (more below about this).
> Note that in Blah, blah, blah I get this in the Yahoo Bounce:
> "Received-SPF: pass (
google.com: best guess record for domain of ng13-..."
>
> But when I get an email from my wife (yeah, yeah I know - she's just
> 20-feet away!) I get this:
> Received-SPF: fail (
google.com: domain of
wi...@gmx.com does not
> designate 71.74.56.123 as permitted sender) client-ip=71.74.56.123
You have just quoted Google's result of SPF testing,
rather than Yahoo's result, in case you didn't notice.
Google's declared SPF test results may parallel Yahoo's
SPF test results, but Google's policy re how severely to require
a positive confirmation is no doubt much more liberal than Yahoo's.
Yahoo is rather infamous for vastly over-reacting in a "vigilante" manner,
and for infuriating its own clientele by suddenly blocking a great deal of
perfectly legitimate mail that its subscribers expect, need, and depend upon,
as we observed a number of years ago when we (as well as legitimate sources
world-wide) became unable to email about 1/3 of all our students,
ever since which we have advised every student to use only Gmail
for academically important work, and let Yahoo screw itself instead,
by their ill-considered spastic killing of a high percentage of valid mail
instead of only spam, like a radical cancer treatment that destroys all of the
patients' organs and kills the patient along with the cancer.
For spammers, by the way, it is actually easy to circumvent the test,
leaving only ordinary mail clients like Outlook, Eudora, etc. failing it,
so once again, Yahoo is right about the fact that using a common email client
(even with your own ISP-provided, fully authenticated outgoing server)
will still leave your legitimate mail shot down by Yahoo,
while professional spammers have the last laugh.
The inherent flaw in using SPF tests to blindly and indiscriminately block mail
is the very reason why we _don't_ publish SPF records for our domain,
because we know that doing so would cause knee-jerk reactors like Yahoo
to refuse mail that _has_ to be set from elsewhere, such as by our
faculty and students in our locations in China, and elsewhere world-wide,
plus even from local faculty members' off-campus _homes_ (using other local ISPs).
We have a high quality graduate Computer Science masters degree program here,
and have placed many graduates at Microsoft, Google, and other top companies,
but I don't recall anyone ever seeking placement at Yahoo,
which perhaps would be a blight on their resume to even have worked at.
--