Peter Shute writes:
I don't know if we are doing SPF/DKIM ( or what they are).
You should ask the people responsible for your mailserver. SPF and
DKIM in themselves are good things because they prevent rejections of
mail that you send directly to another domain that implements them,
and
* Mark Sapiro m...@msapiro.net:
On April 11, 2014 3:18:13 PM EDT, Mark Sapiro m...@msapiro.net wrote:
On 04/11/2014 05:25 AM, Mark Sapiro wrote:
Tentatively rescheduled to 17:00 EDT (21:00 GMT) on Friday, 11 Apr in
room 525.
I will attempt to post realtime summaries on #mailman.
On 04/11/2014 02:06 PM, Mark Sapiro wrote:
Development question, is there a way to test the handler against a mail
content, outside of the full mailman context?
Something like:
$ python -some-useful-switch-here MyHandler.py mymail_withheader.txt
withlist is the tool for this. When I
My native paranoia has caused me to take note of the fact that what can only be
described as a naked power grab by a collection of corporate Internet giants,
with blatant disregard for the principles of net neutrality, has occurred while
the attention of the national tech media is focused on
Hi - Starting this week, I've discovered that emails sent from yahoo members on my mailing lists, are not getting
delivered to other yahoo addresses on my mailing list, including the person who sent the message. My SMTP logs show
that the message is getting rejected (see below). I'm positive
On Sun, Apr 13, 2014 at 3:48 PM, Mark London m...@psfc.mit.edu wrote:
Hi - Starting this week, I've discovered that emails sent from yahoo members
on my mailing lists, are not getting delivered to other yahoo addresses on
my mailing list, including the person who sent the message. My SMTP logs
On 4/13/14, 3:48 PM, Mark London wrote:
Hi - Starting this week, I've discovered that emails sent from yahoo
members on my mailing lists, are not getting delivered to other yahoo
addresses on my mailing list, including the person who sent the
message. My SMTP logs show that the message is
On Sun, Apr 13, 2014 at 4:01 PM, Richard Damon rich...@damon-family.org wrote:
If you list modifies the message, in particularly either the subject
line or body, then the signature won't match and the message is supposed
to not be delivered.
It's worse than just modification of the
Thanks for the replies to my other post, and sorry that I didn't search the
archives first, before posting.
In any event, I'm a unclear about the best solution (if there is one).
Is there a solution, that will only modify messages from domains that are like yahoo? I.e., only yahoo posts will
Thanks for the replies to my other post, and sorry that I didn't search the
archives first, before posting.
In any event, I'm a unclear about the best solution (if there is one).
Is there a solution, that will only modify messages from domains that are like yahoo? I.e., only yahoo posts will
Hi gang,
I'm getting a little tired of going through the mail logs just to get an idea
of how are the damn dmarc bounces doing today.
Has anybody written a little script to sort through and count the bounces?
Ideally, it would mail me the results, though part of me thinks it would be
more
In any event, I'm a unclear about the best solution (if there is one).
My inclination is to refuse postings from addresses @yahoo.com, since
accepting them will interfere with everyone's use of our list system.
The only issue for me is precisely how to implement it.
Joseph Brennan
Jim Popovitch jim...@gmail.com wrote:
DMARC works off of SPF as well.
Not really. SPF does not check the From: header line, and that's where
the troubles begin with DMARC.
Joseph Brennan
Columbia University IT
--
Mailman-Users mailing
On 4/13/2014 3:34 PM, Al Black wrote:
Hi gang,
I'm getting a little tired of going through the mail logs just to get an idea of
how are the damn dmarc bounces doing today.
Has anybody written a little script to sort through and count the bounces?
Ideally, it would mail me the results,
On 04/13/2014 01:59 PM, Joseph Brennan wrote:
In any event, I'm a unclear about the best solution (if there is one).
Mailman 2.1.16 and up already has the ability to either mung the From:
header or wrap the original post in an outer message From: the list.
There is a minor bug in that this
On 04/13/2014 01:34 PM, Al Black wrote:
Has anybody written a little script to sort through and count the bounces?
Ideally, it would mail me the results, though part of me thinks it would be
more ideal to mail to results to me and yahoo abuse.
Yahoo is presumably already getting reports.
Mitra IMAP wrote:
My native paranoia has caused me to take note of the fact
that what can only be described as a naked power grab by a
collection of corporate Internet giants, with blatant
disregard for the principles of net neutrality, has occurred
while the attention of the national
On Sun, Apr 13, 2014 at 4:54 PM, Joseph Brennan bren...@columbia.edu wrote:
Jim Popovitch jim...@gmail.com wrote:
DMARC works off of SPF as well.
Not really.
DMARC checks alignment of *both* DKIM and SPF, if either is broken DMARC fails.
SPF does not check the From: header line, and
On 04/13/2014 03:03 PM, Jim Popovitch wrote:
DMARC checks alignment of *both* DKIM and SPF, if either is broken DMARC
fails.
SPF does not check the From: header line, and that's where the
troubles begin with DMARC.
SPF checks sending IPs (of which your IPs won't match Yahoo's, thus
Many sage responses elided... so back to the naive and foolish questions...
For an announce only list (viz. only very special people may post, and
those people aren't from yahoo accounts) will this DMARC issue be easily
avoided by not allowing any posts from yahoo members (they can read from
We just had a list member disabled. Is this likely to be caused by the DMARC
problem? Here's the header from the attachment in the bounce action
notification email:
x@gmail.com (expanded from xx...@x.com.au): host
gmail-smtp-in.l.google.com[2607:f8b0:400e:c03::1b] said:
On 4/13/14, 6:22 PM, Peter Shute wrote:
We just had a list member disabled. Is this likely to be caused by the DMARC
problem? Here's the header from the attachment in the bounce action
notification email:
x@gmail.com (expanded from xx...@x.com.au): host
On 4/13/14, 6:17 PM, Mark Sapiro wrote:
On 04/13/2014 03:03 PM, Jim Popovitch wrote:
DMARC checks alignment of *both* DKIM and SPF, if either is broken DMARC
fails.
SPF does not check the From: header line, and that's where the
troubles begin with DMARC.
SPF checks sending IPs (of which
On Thu, 2014-04-10 at 15:35 -0400, Jim Popovitch wrote:
Here's a tried and tested patch just awaiting more use:
https://code.launchpad.net/~jimpop/mailman/dmarc-reject
Jim, I note that what you reference here appears to be a complete branch
version of Mailman. Can you briefly outline exactly
On 04/13/2014 03:25 PM, Keith Bierman wrote:
For an announce only list (viz. only very special people may post, and
those people aren't from yahoo accounts) will this DMARC issue be easily
avoided by not allowing any posts from yahoo members (they can read from
others, correct?)
Yes, that
On 04/13/2014 03:17 PM, Mark Sapiro wrote:
There are weird issues though. It seems I can't post from my gmail
address to my yahoo group. I get a non-delivery notice from gmail. I'm
not sure why. The yahoo group exists and my gmail address is a member
with posting privileges.
My bad. I have
On Sun, Apr 13, 2014 at 8:25 PM, Lindsay Haisley fmo...@fmp.com wrote:
On Thu, 2014-04-10 at 15:35 -0400, Jim Popovitch wrote:
Here's a tried and tested patch just awaiting more use:
https://code.launchpad.net/~jimpop/mailman/dmarc-reject
Jim, I note that what you reference here appears to
On Sun, Apr 13, 2014 at 8:48 PM, Jim Popovitch jim...@gmail.com wrote:
On Sun, Apr 13, 2014 at 8:25 PM, Lindsay Haisley fmo...@fmp.com wrote:
On Thu, 2014-04-10 at 15:35 -0400, Jim Popovitch wrote:
Here's a tried and tested patch just awaiting more use:
Richard Damon wrote:
We just had a list member disabled. Is this likely to be
caused by the DMARC problem? Here's the header from the
attachment in the bounce action notification email:
x@gmail.com (expanded from xx...@x.com.au): host
On Apr 13, 2014, at 08:48 PM, Jim Popovitch wrote:
Launchpad is not my forte, so I'm not even sure how to push only my
modifications to LP without the upstream branch changes. And yes,
I'll be the first to say it's a bit confusing in it's current branch.
The best way to do it is to submit a
On Sun, Apr 13, 2014 at 9:06 PM, Barry Warsaw ba...@list.org wrote:
On Apr 13, 2014, at 08:48 PM, Jim Popovitch wrote:
Launchpad is not my forte, so I'm not even sure how to push only my
modifications to LP without the upstream branch changes. And yes,
I'll be the first to say it's a bit
On 04/13/2014 03:22 PM, Peter Shute wrote:
We just had a list member disabled. Is this likely to be caused by the DMARC
problem? Here's the header from the attachment in the bounce action
notification email:
x@gmail.com (expanded from xx...@x.com.au): host
On 4/13/14, 9:06 PM, Peter Shute wrote:
Richard Damon wrote:
My guess on how this works is that when you deliver to Gmail,
one message will actually have many recipients, and you will
get just a single rejection, which will be charged to the
first person on the list by mailman. How they
On 04/13/2014 06:48 PM, Richard Damon wrote:
When sending a large number of copies of identical emails to a single
server, you want to batch it into one message with multiple recipients
(this assumes you are not using VERP, which would cause the messages to
not be identical).
When the
Mark Sapiro writes:
Mailman 2.1.16 and up already has the ability to either mung the From:
header or wrap the original post in an outer message From: the list.
The major problem is it requires site configuration action to make this
option available to list owners.
Given that the whole
Keith Bierman writes:
For an announce only list (viz. only very special people may post, and
those people aren't from yahoo accounts) will this DMARC issue be easily
avoided by not allowing any posts from yahoo members (they can read from
others, correct?)
Yes.
BTW, hardly naive (the
On Apr 14, 2014, at 11:03 AM, Stephen J. Turnbull wrote:
Given that the whole site is at risk, should it be an option for list
owners at all?
This is a good point. It may make sense for the site admin to select whether
some general DMARC mitigation approach is enabled for their lists or not,
On Sun, Apr 13, 2014 at 10:12 PM, Barry Warsaw ba...@list.org wrote:
On Apr 14, 2014, at 11:03 AM, Stephen J. Turnbull wrote:
Given that the whole site is at risk, should it be an option for list
owners at all?
This is a good point. It may make sense for the site admin to select whether
some
On 04/13/2014 03:17 PM, Mark Sapiro wrote:
On 04/13/2014 03:03 PM, Jim Popovitch wrote:
DMARC checks alignment of *both* DKIM and SPF, if either is broken DMARC
fails.
SPF does not check the From: header line, and that's where the
troubles begin with DMARC.
SPF checks sending IPs (of
On Sun, Apr 13, 2014 at 10:47 PM, Mark Sapiro m...@msapiro.net wrote:
On 04/13/2014 03:17 PM, Mark Sapiro wrote:
On 04/13/2014 03:03 PM, Jim Popovitch wrote:
DMARC checks alignment of *both* DKIM and SPF, if either is broken DMARC
fails.
SPF does not check the From: header line, and that's
40 matches
Mail list logo
