Hello!
I believe there's no need to elaborate on the problems recently introduced by
Yahoo, changing their
DMARC DNS record and rendering many mailman lists unusable for Yahoo mail users.
I see the solution to this problem in changing the From: field to mailing
list's address, but
keeping the
They're breaking RFC 822 / 5322.
The From: field specifies the author(s) of the message,
that is, the mailbox(es) of the person(s) or system(s) responsible
for the writing of the message. [...]
In all cases, the From: field SHOULD NOT contain any mailbox that
does not belong to the
On 10/04/14 16:25, Joseph Brennan wrote:
They're breaking RFC 822 / 5322.
The From: field specifies the author(s) of the message,
that is, the mailbox(es) of the person(s) or system(s) responsible
for the writing of the message. [...]
In all cases, the From: field SHOULD NOT
I hate to say it, but the days of the kinder, gentler internet when
everyone played strictly by the RFCs are passing as operational control
of internet services comes increasingly under the control of fewer,
bigger players who can do as they wish.
This isn't to say that Mailman should break RFCs
Lindsay Haisley fmo...@fmp.com wrote:
SPF inherently breaks mailing lists
No, it doesn't. SPF checks the envelope sender, and when the list host is,
say, lists.example.com, the envelope sender is something like
listname-boun...@lists.example.com, and that can pass SPF. Mailman,
Listserv,
On 10/04/14 17:18, Lindsay Haisley wrote:
This is the first I've heard of this issue, but it doesn't surprise me
at all.
Basically, Yahoo insists that their own mail servers are the only ones that can
originate the
message with @yahoo.com domain in the From header. Not Return-Path, Not the
On Apr 10, 2014, at 03:09 PM, Siniša Burina wrote:
I believe there's no need to elaborate on the problems recently introduced by
Yahoo, changing their DMARC DNS record and rendering many mailman lists
unusable for Yahoo mail users.
It *is* a shame that these anti-spam defenses knowingly break
On Thu, Apr 10, 2014 at 10:18:33AM -0500, Lindsay Haisley wrote:
I hate to say it, but the days of the kinder, gentler internet when
everyone played strictly by the RFCs are passing as operational control
of internet services comes increasingly under the control of fewer,
bigger players who
On Thu, Apr 10, 2014 at 12:04 PM, Adam McGreggor
adam-mail...@amyl.org.uk wrote:
On Thu, Apr 10, 2014 at 10:18:33AM -0500, Lindsay Haisley wrote:
I hate to say it, but the days of the kinder, gentler internet when
everyone played strictly by the RFCs are passing as operational control
of
Siniša Burina writes:
Basically, Yahoo insists that their own mail servers are the only
ones that can originate the message with @yahoo.com domain in the
From header. Not Return-Path, Not the envelope sender, but exactly
the From header in the message itself. If this practice gets
On 10/04/14 19:57, Stephen J. Turnbull wrote:
Or just bounce them with a message stating that Yahoo no longer
permits its users to post to mailing lists, so please use a different
posting address. I realize that most sites can't do that, but mine
can (and will if I get any complaints about
On Thu, Apr 10, 2014 at 2:34 PM, Siniša Burina s...@burina.net wrote:
On 10/04/14 19:57, Stephen J. Turnbull wrote:
Or just bounce them with a message stating that Yahoo no longer
permits its users to post to mailing lists, so please use a different
posting address. I realize that most sites
On Apr 11, 2014, at 02:57 AM, Stephen J. Turnbull wrote:
The straightforward thing for Mailman to do is to wrap mail from yahoo
addresses in a multipart/mixed with a text part explaining that Yahoo
is knowingly interfering with the mail service of their users, and
the mail itself in a
On 04/10/2014 07:25 AM, Joseph Brennan wrote:
They're breaking RFC 822 / 5322.
The From: field specifies the author(s) of the message,
that is, the mailbox(es) of the person(s) or system(s) responsible
for the writing of the message. [...]
In all cases, the From: field SHOULD NOT
I have tentatively scheduled an open space for Friday, 11 April at 18:00
in room 523B at Pycon to talk about DMARC and mail lists. All available
interested parties are invited. If the time doesn't work, we can reschedule.
--
Mark Sapiro m...@msapiro.netThe highway is for gamblers,
San
On Apr 10, 2014, at 20:25, Mark Sapiro m...@msapiro.net wrote:
On 04/10/2014 07:25 AM, Joseph Brennan wrote:
They're breaking RFC 822 / 5322.
The From: field specifies the author(s) of the message,
that is, the mailbox(es) of the person(s) or system(s) responsible
for the writing of
On 04/10/2014 06:09 AM, Siniša Burina wrote:
I see the solution to this problem in changing the From: field to mailing
list's address, but
keeping the poster's name or address in the description part of the same
field. For example:
...
I'm using Mailman 2.1.13, and can not upgrade to
On 04/10/2014 05:35 PM, mail.ulticom.com wrote:
At least as of iOS 7 it can show messages inside messages.
Thanks for the tip. I'll check with my users and see what they're using.
--
Mark Sapiro m...@msapiro.netThe highway is for gamblers,
San Francisco Bay Area, California
Mark Sapiro writes:
Unfortunately, when I actually turned this on in response to
Yahoo's change in DMARC policy, I got complaints from users of
Apple iOS iThings that their mail clients do not deal well with
this message,
The iOS 6 mail client was just plain unusable, and in very limited
19 matches
Mail list logo
