McDonald, Dan wrote:
From: Bob Proulx [mailto:[EMAIL PROTECTED]
Benny Pedersen wrote:
http://www.openspf.org/Why?id=me%40junc.org&ip=194.116.240.69&receiver=athena.apache.org
On that page it says:
athena.apache.org received a message from mx.grupointercom.com
(194.116.240.69) that claimed an envelope sender address of [EMAIL PROTECTED]
However, the domain junc.org has declared using SPF that it does not
send mail through mx.grupointercom.com (194.116.240.69). That is why
the message was rejected.
What did you do differently between this message and the one that was
rejected? Somehow you routed the other message through an
unauthorized route. It is specifically configured to be rejected by
your own domain configuration. Routine mail through grupointercom.com
makes it look like a forgery.
I got similar messages (and will probably get another one soon).
This doesn't really have anything to do with SpamAssassin and
therefore is off-topic for this mailing list. Consider conversing
directly with the mailing list owner.
I beg to differ. Misconfigured mailing lists are always on topic for a mailing list.
what is misconfigured in this list?
If even the sa list doesn't follow the recommendations that we talk about on
this list (changing the envelope-from to [EMAIL PROTECTED]) then how can we
complain about other noobs who make the same mistake?
the envelope from of the list is something like
<[EMAIL PROTECTED]>
so it's using VERP with an apache domain. is that a problem?
