(Replying to the list this time...)
I removed my email address and IP address from the message, since
archived of this list are publicly available. If you put in an arbitrary
email and IP address you'll get the gist of the page - it just
customises the page with those details.
SPF (Sender Policy Framework) allows domains to specify in their DNS
records which servers are used to send email appearing to be from
addresses in their domain. spamgourmet.com (a service I use to avoid
exposing my real email address, particularly important on publicly
archived mailing lists) have set up such a record, so email sent through
any SMTP server other than theirs will fail the check. I send email
through my ISP's SMTP server, which does not match spamgourmet's SPF
records. The "correct" way to send email from a spamgourmet address is
to log in to www.spamgourmet.com, search for and select the address I
want to appear to send from, enter the address I want to send to, be
provided with an address, and send an email to that address - which will
then be forwarded to the address I specified, appearing to come from my
spamgourmet address rather than my actual address. A lot of effort to go
through, when sending through my ISP's SMTP server and setting the
"from" address to my spamgourmet address in my mail client usually works.
Usually, mail filters just assign a higher "spam score" to messages
failing the SPF check, increasing the chance that it will be rejected as
spam but not rejecting it outright just on that check - Apache are the
only ones I've come across so far which do that.
Another one of those systems put in place to block spam, but which can
end up making legitimate use very difficult! I use spamgourmet to avoid
spam to me, Apache reject mail failing SPF checks to avoid spam to them,
but the two systems don't play nicely.
Thanks,
Mark.
Dennis E. Hamilton wrote:
So many of these SPF arrangements are flakey.
This is off-track from getting you tied into bugzilla again, but I notice this
oddity.
If you go to openspf.org with the pasted-together URL they supply, it seems
that [my address]
is a problem!
Also, I have no idea when it says "bad destination address" when it is
apparently the sender
address that is a problem. But I regularly see that in messages like the one
you received.
Did you patch that "[my address]" into the message below?
Since there are apparently not a lot of problems about this, I would check with
your ISP first.
(I have trouble because I use a From: that is different from the Sender: and
the From: is the
address of a vanity forwarding (@acm.org) that I can't originate mail through.
But ooo-dev
was not a problem for me.)
-----Original Message-----
From: [email protected]
[mailto:[email protected]]
Sent: Friday, October 07, 2011 11:56
To: [email protected]
Subject: [users] Re: Re:
Dennis E. Hamilton wrote:
2. Was the bounce from ooo-dev itself or from someone on the list whose
e-mail system bounced your post? (I'm asking because I get these from various
individual users but not from the lists themselves.)
It was from my ISP's mail server (postmaster at anakin.london.02.net),
saying mx1.eu.apache.org didn't accept the message:
- These recipients of your message have been processed by the mail server:
ooo-dev at incubator.apache.org; Failed; 5.1.1 (bad destination mailbox
address)
Remote MTA mx1.eu.apache.org: SMTP diagnostic: 550 SPF forgery:
Please see http://www.openspf.org/why.html?sender=[my
address]&ip=87.194.255.134&receiver=nike.apache.org
[ ... ]
--
-----------------------------------------------------------------
To unsubscribe send email to [email protected]
For additional commands send email to [email protected]
with Subject: help
