From: Christian Laursen <xi@borderworlds.dk>
To: mlmmj@mlmmj.org
Subject: Re: [mlmmj] mlmmj and spf
Date: Fri, 11 May 2012 12:43:02 +0000 [thread overview]
Message-ID: <4FAD0956.3040705@borderworlds.dk> (raw)
In-Reply-To: <4FACFAE7.60904@borm.org>
On 05/11/12 13:41, theo borm wrote:
>
> We operate a small, closed, moderated mailing list that recently stopped
> working for a large part of its subscribers. The organization of which
> these subscribers are a member maintains an SPF record which denies
> access to all servers except a named few, which seems to be the cause of
> these problems.
It sounds like their SPF implementation is broken.
> As a work-around I set mlmmj to use a different from address in the
> "From:" header. This solution is, however, plainly bad as it removes the
> original sender from the headers. I have seen other lists use "Sender:"
> header, but results are a mixed bag. With strict SPF checking of the
> "From:" header in place these mails also don't pass.
SPF checking should be done on the enevelope FROM address, not the From:
header contained inside the mail.
When mlmmj send out mails to the list subscribers the envelope from
looks something like this:
listname+bounces-XXXX-recipient=example.com@listowner.tld
So the SPF checking is done against the domain that the list is running on.
The correct cause of action would be to get the organization with broken
SPF checking to fix that.
--
Christian Laursen
next prev parent reply other threads:[~2012-05-11 12:43 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-05-11 11:41 [mlmmj] mlmmj and spf theo borm
2012-05-11 11:54 ` Franky Van Liedekerke
2012-05-11 12:42 ` theo borm
2012-05-11 12:43 ` Christian Laursen [this message]
2012-05-11 13:20 ` Ben Schmidt
2012-05-11 13:42 ` Franky Van Liedekerke
2012-05-11 13:51 ` theo borm
2012-05-11 13:55 ` theo borm
2012-05-11 13:56 ` Franky Van Liedekerke
2012-05-11 13:57 ` theo borm
2012-05-11 14:33 ` theo borm
2012-05-11 14:50 ` Ben Schmidt
2012-05-11 14:56 ` Ben Schmidt
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=4FAD0956.3040705@borderworlds.dk \
--to=xi@borderworlds.dk \
--cc=mlmmj@mlmmj.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox