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.
Your DNS TXT record is:
junc.org TXT "v=spf1 ip4:80.166.47.252/30 ip4:80.166.75.16/29 -all"
But your message here is okay:
Received-SPF: pass (athena.apache.org: domain of [EMAIL PROTECTED] designates
80.166.75.17 as permitted sender)
Received: from [80.166.75.17] (HELO gate.junc.org) (80.166.75.17)
by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 25 Jun 2008 20:34:45 +0000
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.
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.
Bob
