On 11/4/19 7:42 AM, Andy Cravens wrote:
> Using mailman 2.1.26. I’m auditing the lists on my server for DMARC
> compliance I’ve found several list configs that do not have the DMARC action
> set to “munge_from.” It appears I need to edit all those list and fix that
> setting
is or should be :/
DMARC draft, sec. 15.2. This is discussion of matters outside the
scope of DMARC itself, not a normative specification, and the document
itself says there are legitimate uses of email addresses in display
names (or comments). But that hasn't stopped the spam-fighters in the
past
On 02/10/2017 05:31 PM, Adam Morris wrote:
>
> I have a user who is bounced periodically from one of my lists.
>
> He is on 4 of them but the bounce only happens for one of the lists.
...
> Any ideas on what I can do to fix this?
It would help to see the bounce m
> I'm really stumped... any pointers/ideas on where to look would be greatly
> appreciated!
>
> - Scott
I would also be interested if anyone has any answers or suggestions to this
as we have seen the same issue on our mailman servers. Enabling the DMARC
option on the general options page seems t
Last month a Mailman (v2.1.18-1) list on my server got hit with a bunch
of bounces based on DMARC rejections from Gmail, Yahoo and Hotmail
which honor "p=reject" in a DMARC record. The list had not previously
been configured to handle DMARC issues so at that time I
set dmarc_moderat
/rfc822 part. As far as I know, no
component of DMARC allows digging into a message and trying to DMARC
the MIME parts.
That's what I mean by we can fix it if we make the user experience
horrible. See all the complaints about the MIME-proper way we add footers in
some cases.
-Barry
On Mon, 2017-04-03 at 12:28 -0500, Lindsay Haisley wrote:
> Last month a Mailman (v2.1.18-1) list on my server got hit with a
> bunch of bounces based on DMARC rejections from Gmail, Yahoo and
> Hotmail which honor "p=reject" in a DMARC record.
Add comcast.net, msn.com
On 7/28/19 9:52 AM, Bill Cole wrote:
> On 28 Jul 2019, at 11:25, Loren Engrav via Mailman-Users wrote:
>
>> and searched archives
>> and see this goes back years and years
>> is there a quick fix I missed in the archives?
>
> This looks like a DMARC prob
Using mailman 2.1.26. I’m auditing the lists on my server for DMARC compliance
I’ve found several list configs that do not have the DMARC action set to
“munge_from.” It appears I need to edit all those list and fix that setting.
I’ve also noticed that in mm_cfg.py there is no setting
On 28 Jul 2019, at 11:25, Loren Engrav via Mailman-Users wrote:
> and searched archives
> and see this goes back years and years
> is there a quick fix I missed in the archives?
This looks like a DMARC problem.
See https://wiki.list.org/DEV/DMARC
--
Bill Cole
b...@scconsult.com
On 01/15/2017 08:58 PM, Scott Neader wrote:
>
> When yahoo.com or AOL.com users post to our
> lists, the Munging is not working. When I query for a DMARC record from
> the mail server, it can see the record, so I think it's not a resolver
> issue.
>
> I'm really stumped.
On Mon, Oct 10, 2016 at 5:32 PM, Jim Popovitch <jim...@gmail.com> wrote:
> On Mon, Oct 10, 2016 at 4:30 PM, Jim Popovitch <jim...@gmail.com> wrote:
>> SO... I've digging further into Mailman code looking to further
>> improve problems with DMARC. I've noticed that Mail
On 4/29/20 6:52 AM, Ben Edwards wrote:
> Hi, we have a list server with several lists and the setup seems
> different on some and not sure how to fix this.
>
> The problem is on some lists some people are not getting the names of
> the people who send emails (in thunder
is the fix? Help, please...
On Apr 16, 2014, at 10:48 AM, Mark Sapiro m...@msapiro.net wrote:
On 04/16/2014 06:58 AM, Lindsay Haisley wrote:
Has anyone seen issues with Gmail accounts and Yahoo's DMARC policy?
I've been working with the list admins of one of FMP's hosted lists and
they've seen over
in July as follows:
https://rhn.redhat.com/errata/RHSA-2015-1417.html and included
fixes for a number of DMARC issues. Including ... With this
update, domains with a reject DMARC policy are recognized
correctly..
Stock Mailman 2.1.12 doesn't do any DMARC detection. This is quite
bizarre
@mark:
The Hotmail error message does make it sufficiently clear that these
bounces are due to DMARC. I will probably file an RFE to catch these
against Mailman 3. Would you like me to do that for Mailman 2, or is
this "obvously not worth it" in your opinion? (I intend to s
(not if!) that abuse happens, the forces behind DMARC will come
back and say O no! You can't do THAT! And they (the PHBs,
I mean) will break the system again ... and again ... and again.
So, unfortunately, I think there is *no* fix based on presentation.
The only real fix is users who are sophisticated
FTR, I've updated the FAQ 6.15 to refer to this thread:
http://forum.odin.com/threads/fix-for-mailman-posts-being-rejected-due-to-yahoo-and-aol-dmarc-policy.302641/
Steve
--
Mailman-Users mailing list Mailman-Users@python.org
https
Lindsay Haisley writes:
> is an accomplished musician
Barry encourages participation by musicians!
Not official Barry-spokesman, but reasonably good at channeling :-)
--
Mailman-Users mailing list Mailman-Users@python.org
on the dmarc-ietf email
list - trying to discuss ways to fix DMARC to better coexist with
lists and other 3rd-party services (like send this article
to).
Unfortunately, it seems like the discussion is bogged down in two regards:
- the ietf-dmarc working group is charted to enhance DMARC
Hello
One member of a mailman mailing list on my system receives an error
message when posting to the list:
You are not allowed to post to this mailing list From: a domain which
publishes a DMARC policy of reject or quarantine, and your message has been
automatically rejected. If you
rav via Mailman-Users wrote:
>>
>>> and searched archives
>>> and see this goes back years and years
>>> is there a quick fix I missed in the archives?
>>
>> This looks like a DMARC problem.
>
>
> It is not a DMARC issue. The disconnect comes in
for
a number of DMARC issues. Including ... With this update, domains with
a reject DMARC policy are recognized correctly..
Normally the lists we use are configured with reply_goes_to_list and
anonymous_list is off. We have done some testing, and we have not been
able to identify settings
Hello,
I am runningseveral mailing lists with mailman version 2.1.18-1. Oneof
my mailing lists does not ever show the sender's name in the From:
headerfor DMARC domain policy=reject while the rest of my lists do show
the sender's name in the From: header. I have compared the individual
list
the suggestions there and report what you find.
Is this issue coincident with a cPanel update?
> Enabling the DMARC
> option on the general options page seems to fix it however but I am not sure
> in why this has suddenly become a problem with just using the privacy
> options -- sender filt
17-
> January/081821.html>.
> Follow the suggestions there and report what you find.
>
> Is this issue coincident with a cPanel update?
>
>
> > Enabling the DMARC
> > option on the general options page seems to fix it however but I am not
> sure
> > in
e list server's mailman address, were also bouncing. I would
> assume that messages which come directly from our server and are not
> reflected through a redirection or mailing list wouldn't be subject to
> rejection based on DMARC policy.
They aren't "probe" messages in the sen
come up with for MM 3, and then maybe
consider a backport.
> I should also fix the FAQ to mention the names of the new options, no?
Both FAQs could use tweaking or more. <https://wiki.list.org/x/17891458>
needs more about current options and the MM 3 section at
<https:
-us...@cru.fr sympa-us...@cru.fr,dm...@ietf.org
dm...@ietf.org
Folks,
Many of us just had to deal with the impacts of DMARC on our lists.
In the aftermath, I've been participating on the dmarc-ietf email list -
trying to discuss ways to fix DMARC to better coexist with lists and
other
ing from a large range of ipv6
addresses on a cloud server. Spamhause does something like this too,
but you can fix it by getting a "proper" ipv6 address that specifies
the range ("/64" at the end).
Some geneneral
On 11/29/21 00:51, Jayson Smith wrote:
Hi again,
Good point about D
I have had a lot of experience with these things. Here are some
observations. I have a list of 4000+ subscribers around the world. I
have SPF and DKIM but not DMARC. (I never say much point in DMARC, and
it does not seem necessary.) Right now every single one of the 4000+
subscribers accepts
to change the situation as well.
This is not a DMARC issue per se as gmail's DMARC policy is p=none.
I then attempted to set this setting to wrap message, which again did not fix
the issue.
Because gmail's DMARC policy is p=none, dmarc_moderation_action won't
apply to this mail.
At this point
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
Hi,
Ever since I upgraded Mailman to address DMARC issues in April a number of
archives have been having their HTML messages scrubbed.
The result is that the archived message shows all these scrubbed notices
instead of the actual message.
What is causing this and how do I resolve
On Apr 05, 2017, at 11:36 AM, Stephen J. Turnbull wrote:
>Barry encourages participation by musicians!
>
>Not official Barry-spokesman, but reasonably good at channeling :-)
Don't forget the secret bassplayer.py handler! You email it a drum pattern
and it replybots you a funky groove in E.
-B
te:
>>>
>>>> and searched archives
>>>> and see this goes back years and years
>>>> is there a quick fix I missed in the archives?
>>>
>>> This looks like a DMARC problem.
>>
>>
>> It is not a DMARC issue. T
to everybody, but emails from
@yahoo.com members are not, then the problem may very well be
Yahoo!'s DMARC policy.
Our ISP tells us domain is RFC-compliant and problem must be with
Bellsouth or Yahoo.
That's not very helpful of them.
How do we resolve this? What is the fix?
If in fact
On 07/11/2014 11:31 PM, Peter Knowles wrote:
Hi,
Ever since I upgraded Mailman to address DMARC issues in April a number of
archives have been having their HTML messages scrubbed.
I suspect you upgraded to 2.1.16 or 2.1.17 and that 2.1.18 and 2.1.18-1
do not have this behavior.
I'm
I'll jump in here and offer the quick solution that I'm using at FMP.
The primary culprit here is Yahoo, which publishes a DMARC p=reject
policy via DNS. To the best of our knowledge, so far, no one else is
doing this, although sbcglobal, att.net, comcast.net, Hotmail and a
number of other email
of settings is
organized. These may be stupid questions, but I can just about
guarantee you that all my list admins will trip on them :(
I hear you. It is badly explained and I need to fix it. Thanks for
raising this.
I changed it. In the 2.1.18 final it will say
On 06/27/2014 11:22 AM, Gordon Dickens wrote:
Hello,
I am runningseveral mailing lists with mailman version 2.1.18-1. Oneof
my mailing lists does not ever show the sender's name in the From:
headerfor DMARC domain policy=reject while the rest of my lists do show
the sender's name
if each incident is
years apart? Who knows?
Jayson
On 11/29/2021 6:55 AM, Jon Baron wrote:
I have had a lot of experience with these things. Here are some
observations. I have a list of 4000+ subscribers around the world. I
have SPF and DKIM but not DMARC. (I never say much point in DMARC, and
i
Thus spake Mark Sapiro:
On 05/28/2014 10:28 PM, Stephen J. Turnbull wrote:
Mark Sapiro writes:
If there are no 'DMARC' entries in Mailman's logs, it most likely means
the imports I show above didn't succeed in the python that Mailman is
using, in which case
others. How do I fix this?
Regards len
I found that DMARC is pervasive enough to cause this behavior. Using munge
from fixed it for me, be aware you need a very recent version of MM to have
the options.
If the posts that aren't received are all From: yahoo.com and aol.com
addresses
and I’m weary of messing anything up,
as I have basically no
time or background to fix it.
Yours,
Allan
On May 24, 2015, at 11:06 , Andrew Hodgson and...@hodgsonfamily.org wrote:
Allan Hansen wrote:
Stephen,
Much appreciated.
Checking for aol.com and yahoo.com here alone
is not for the faint of heart.
IIRC, that FAQ is quite old (like 2008?) At least it mentions Plesk 7
(currently Plesk is at 12+ it seems, with 11.x still in support).
According to this thread:
http://forum.odin.com/threads/fix-for-mailman-posts-being-rejected-due-to-yahoo-and-aol-dmarc-policy
use
there is "sufficient reason" for doing so. If you don't like it,
you'll have to take it up with the list owner, not with us.)
> Depending on list settings, a new, merged, Reply-To: or Cc: will be
> created and the original replaced,
Also From may be munged to disable DMARC, depending on list se
On Mon, 2017-01-16 at 10:23 -0800, Mark Sapiro wrote:
> Note that if you are seeing the
>
> DNS lookup for dmarc_moderation_action for list not
> available
>
> messages, restarting Mailman may fix it. Also, in this case try
>
> python -c "import dns.resolver&q
Mark Sapiro writes:
> Are you suggesting that we ignore bounces that can be determined to be
> due to DMARC policy.
Not *completely* ignore. There are several independent actions we can
take based on bounces, depending on list option settings. I'm
suggesting only that we not inc
On 2/27/20 1:37 PM, Brian Carpenter wrote:
Brian makes a number of good points. I just have a couple of
remarks/questions.
> 5. MM3 DMARC handling seems to have improved from reviews I have seen
> but NO BOUNCE PROCESSING.
I don't know why Mailman 3's DMARC mitigation is considered im
to be on digest will do nothing about
the problem. It is them posting that causes the problem.
Putting everyone on systems that respect the DMARC settings (which
include Yahoo, AOL, plus a number of others including Comcast, SBC, and
others) will fix the problem, as the digests don't claim to come from
site is at risk, should it be an option for list
owners at all?
Jim P's branch mentioned in his post at
https://mail.python.org/pipermail/mailman-users/2014-April/076383.html
is a general implementation for posts From: any domain with a reject
DMARC policy.
We are talking about
general DMARC mitigation approach is enabled for their lists or not, and
then allow the list admins to select the approach that is least unpalatable
for their users.
I agree, very valid point.
-Jim P.
--
Mailman-Users mailing list Mailman
On Tue, May 6, 2014 at 1:37 PM, Mark Sapiro m...@msapiro.net wrote:
A critical incompatibility between the Mailman 2.1.18 final release and
Python versions older than 2.6.5 or thereabouts affecting the DMARC Wrap
Message action was discovered and fixed. This incompatibility also
existed
and the package is
available, something should be logged unless the DNS lookup of DMARC
policy for the From: domain succeeds and doesn't find a p=reject (or
quarantine).
I have attached a patch to Mailman/Utils.py which is a fix for
https://bugs.launchpad.net/mailman/+bug/1324541 which
On 07/21/2014 07:58 PM, Conrad G T Yoder wrote:
[Using 2.1.17]
I just realized that with the DMARC mitigation “Mung From” option turned on,
the senders’ email addresses are not showing up in the archives. So,
basically impossible to contact them unless replying to the whole list
On Mar 3, 2015, at 8:08 PM, len ward len.w...@gmail.com wrote:
Hi
I manage a list of 60 members. If I send an email it does not get to
anybody, yet it is recorded in archives. Same for most others, although I
know one person gets through and maybe others. How do I fix this?
Regards len
issue. I.e. they released an update
which neglected to include that. It was there previously.
I don't know enough about cPanel to know if this will work, but assuming
you have pip,
sudo pip install dnspython
should fix it.
--
Mark Sapiro <m...@msapiro.net>The highway is for gamblers,
S
everal banks that participate in IETF discussions.
> Since 2013 for Yahoo! and LinkedIn IIRC.
So if enough users of Yahoo and AOL requested something such as
u...@list.aol.com to not be DMARC p=reject they /might/ listen?
Only list I help administer the owner simply moderates the few remaining hol
verse DNS.
It is not an issue with DMARC or DKIM signing as the disconnect occurred
before any of that information was sent.
Only DreamHost can fix this.
--
Mark Sapiro The highway is for gamblers,
San Francisco Bay Area, Californiabe
.
Gordon
On 06/27/2014 05:29 PM, Mark Sapiro wrote:
On 06/27/2014 11:22 AM, Gordon Dickens wrote:
Hello,
I am runningseveral mailing lists with mailman version 2.1.18-1. Oneof
my mailing lists does not ever show the sender's name in the From:
headerfor DMARC domain policy=reject while the rest
I am pleased to announce the release of Mailman 2.1.35.
This is a security and minor bug fix release. See the attached
README.txt for details. For those who just want a patch for the security
issues, see
<https://bazaar.launchpad.net/~mailman-coders/mailman/2.1/revision/1873>. The
helpful of them.
How do we resolve this? What is the fix?
If in fact the problem is Yahoo!'s DMARC policy, you can't resolve it
and there is no fix. Simply put, Yahoo! does not permit their users
to post to modern mailing lists that conform to the mail standards.
There are four possible workarounds
. How do I fix this?
Regards len
I found that DMARC is pervasive enough to cause this behavior. Using munge
from fixed it for me, be aware you need a very recent version of MM to have
the options.
If the posts that aren't received are all From: yahoo.com and aol.com
addresses, DMARC
his mailing list From: a domain which
> publishes a DMARC policy of reject or quarantine, and your message has been
> automatically rejected. If you think that your messages are being rejected
> in error, contact the mailing list owner at nssf-styre-ow...@nssf.us.
>
&g
On 5/27/20 1:32 AM, Lars Bjørndal wrote:
> Hello
>
> One member of a mailman mailing list on my system receives an error
> message when posting to the list:
>
> You are not allowed to post to this mailing list From: a domain which
> publishes a DMARC policy of reject or
with a fix for this
incompatibility. Please use 2.1.18-1 and not 2.1.18.
These releases have new features to help with mitigation of the impacts
of DMARC on mailing lists as well as fixing several bugs.
Python 2.4 is the minimum supported, but Python 2.7 is recommended.
There are significant new
ently been having bouncing
> > problems specifically with gmail addresses.
I'm surprised you have problems specifically with Gmail. Their DMARC
policy is still p=none, so DMARC is not why they're bouncing. Lack of
SPF seems more likely. AOL and Yahoo! are much more comon sources o
Mark and Jim,
Thank you for the information. I'm not sure exactly which isthe fix for me, I
don't want to make things worse. Maybe it will help if Ishared my settings and
what I've done so far.
- I'm running 11 mm lists 1.2.39 through cPanel. I have a VPS with InMotion
Hosting. I have
I am pleased to announce the release of Mailman 2.1.25.
Python 2.4 is the minimum supported, but Python 2.7 is strongly recommended.
This is a routine bug fix release with a minor new feature and some
accessibility improvements for screen readers. See the attached
README.txt for details
ent a fair amount of time on questions that ended
up being related to Debian patches (specifically the execrable
mailman-to-postfix script, although that did at least have a good
reason behind it from the point of view of the distro, it was very
fragile but Debian saw no need to fix it).
> and
issues come up all at once is that there's a problem between your server
and the destination mail server for those messages. It could be that the
DMARC settings in Mailman aren't set correctly and those servers are
rejecting messages they don't like, or it could be that your server's IP
address
pdated by Emerson Ribeiro
de Mello.
Bug fixes and other patches
- All addresses in data/virtual-mailman are now properly appended with
VIRTUAL_MAILMAN_LOCAL_DOMAIN and duplicates are not generated if the
site list is in a virtual domain. (LP: #1570630)
- DMARC mitig
to implement it.
Jim P's branch mentioned in his post at
https://mail.python.org/pipermail/mailman-users/2014-April/076383.html
is a general implementation for posts From: any domain with a reject
DMARC policy.
We are talking about this at PyCon now. At sprints starting tomorrow, we
will be working
of DMARC
policy for the From: domain succeeds and doesn't find a p=reject (or
quarantine).
I have attached a patch to Mailman/Utils.py which is a fix for
https://bugs.launchpad.net/mailman/+bug/1324541 which will log the
unavailability of DNS lookup.
--
Mark Sapiro m...@msapiro.net
On 13/12/2015 13:05, Jayson Smith wrote:
Hi,
Unfortunately, disabling automatic removal from the list will only fix
one effect of the problem, not the problem itself. There's something
going on which is causing mail to those addresses to bounce. If you are
receiving messages with the subject
currently working on providing a
fix that will be pushed out in an update. Meanwhile they did provide me a
workaround that fixes the issue. Here is what they said related to the
reported bug:
##
Indeed, I've replicated this concern on our test servers and I see
On Mon, 2017-04-03 at 15:03 -0500, Lindsay Haisley wrote:
> Actually, we try to be gentle with these folks and keep things as
> simple as possible. Some of them are pretty non-techie and these
> messages probably elicit a hormonal technophobia reaction. I'll just
> resubscribe them.
My list owner
On 04/03/2017 01:21 PM, Lindsay Haisley wrote:
>
> Good question! So we want to simply zero out all the bounce counts, and
> possibly the notification counts for the whole list on a one-time
> basis. Will turning off bounce_processing for a day or so do this?
You could turn off bounce
On Mon, 2017-04-03 at 12:40 -0700, Mark Sapiro wrote:
> So basically, the users that were unsubscribed ignored the fact that
> they weren't receiving list mail and ignored 10 messages informing them
> their delivery was disabled and telling them how to re-enable it.
OK, so I'm in the clear to
On Tue, 2018-01-09 at 09:10 -0800, Mark Sapiro wrote:
> See <https://bugs.launchpad.net/mailman/+bug/1614841>. The comment
> thread contains a link to a patch to fix versions >= 2.1.15 and <=
> 2.1.22, however the version "2.1.18-1" indicates this is some distro's
&
I run a small mailman server for our historical recreation group. Lately, I've
been seeing messages like:
: host al-ip4-mx-vip1.prodigy.net[144.160.235.143] said:
550 5.7.1 Connections not accepted from servers without a valid sender
domain.alph733 Fix reverse DNS for 149.28.67.38 (in reply
Vako Nicolian writes:
> Today suddenly all my member emails bounced as you see a sample
> below.
> What happened and how can I fix it?
This seems very unlikely to be a mailman problem at all.
If for some reason somebody tries to blame it on Mailman and you want
more help, pleas
. Other email providers seem to be getting the messages. Any ideas
on how to fix this?
Either ensure that General Options -> from_is List is either Munge From
or Wrap Message to apply DMARC mitigations to all mail or in Privacy
options... -> Sender filters,
dmarc_moderation_action is
is something backported the DMARC mitigations into your
Mailman 2.1.9 and also included code in Mailman/versions.py to update
older lists, but whether or not a list gets updated by this process
depends on the list's data_version being less than the DATA_FILE_VERSION
defined in Mailman/Version.py
is something backported the DMARC mitigations into your
Mailman 2.1.9 and also included code in Mailman/versions.py to update
older lists, but whether or not a list gets updated by this process
depends on the list's data_version being less than the DATA_FILE_VERSION
defined in Mailman/Version.py.
So, still
I am pleased to announce the release of Mailman 2.1.34.
This is a minor bug fix release and has updates to the Spanish i18n. See
the attached README.txt for details.
As noted Mailman 2.1.30 was the last feature release of the Mailman 2.1
branch from the GNU Mailman project. There has been some
From: header for messages with DMARC mitigations. (LP: #1643210)
- Fixed an issue causing UnicodeError in sending digests following a
change of a list's preferred_language. (LP: #1644356)
- Enhanced the fix for race conditions in MailList().Load(). (LP: #266464)
- Fix
hours
ago. (Apparently weren’t willing to wait to do testing on 2.1.18-1.) So we
will squint thoughtfully at the monitor, nod almost imperceptibly, pick a
setting which is the least egregious to fix this problem, and then have some
scotch.
-Conrad
On May 7, 2014, at 11:05 PM, Keith Bierman khb
to send and receive e-mail from the mailing list. Any
suggestions on how to fix this?
This message was created automatically by mail delivery software.
A message that you sent could not be delivered to one or more of its
recipients. This is a permanent error. The following address(es) failed
, next, thinking that the DMARC issues that have been plaguing the internet
lately were to blame, I tried changing the DMARC_Moderation setting to munge.
This failed to change the situation as well.
I then attempted to set this setting to wrap message, which again did not fix
the issue
Hi,
Unfortunately, disabling automatic removal from the list will only fix
one effect of the problem, not the problem itself. There's something
going on which is causing mail to those addresses to bounce. If you are
receiving messages with the subject of "Bounce action notific
gt; other addresses pass.
>
> The latest notice(s) are summarized below.
>
> Site5 people cannot seem to fix this.
>
> Any advice for me / Site5? (I am not expert at this)
...
> Final-Recipient: rfc822; engravosaurus...@aol.com
> <mailto:engravosaurus...@aol.com>
fix this easily. I know a little about this stuff, but I'm
basically just a list manager, not a full-on sysop, so please be gentle in your
terminology and instruction.
From Dreamhost support:
>Taking a look into the 're-wrenches-re-wrenches.org' list, the bounce
>errors point to possible
In a message of Sun, 13 Dec 2015 13:42:47 +0100, Hal writes:
>On 13/12/2015 13:05, Jayson Smith wrote:
>> Hi,
>>
>> Unfortunately, disabling automatic removal from the list will only fix
>> one effect of the problem, not the problem itself. There's something
>&g
ed,
Also From may be munged to disable DMARC, depending on list settings
and possibly a DNS check for DMARC policy.
> but headers like X-BeenThere: X-Mailman-Version:, etc., will just
> be added.
BTW, in my (recent) experience Mailman 2 does not handle List-Post and
List-ID correctly. I
members to change to a
different provider. (Even Outlook.com [Microsoft] is better than Yahoo.)
At Fri, 10 Mar 2023 18:30:30 + (UTC) annette carter
wrote:
>
>
> Mark and Jim,
>
> Thank you for the information. I'm not sure exactly which isthe fix for me, I
> don't want to
st.
This will at least give you some more information. If as I suspect you
do not control Mailman or the MTA on the host machine, there's probably
nothing you can do to fix this and since the host and the user's support
are pointing fingers at each other, there's not much hope for resolution
th
led by cPanel or by the distribution's suggested dependencies
map.
> > --
> cPanel has confirmed the bug and they are currently working on providing a
> fix that will be pushed out in an update. Meanwhile they did provide me a
>
on where To is
changed from the list to the subscriber, but that shouldn't cause
client problems or DMARC issues).
I don't see how we can do anything reliable about that. From is a
*required* field in RFC 5322 message syntax, and it *must* contain a
mailbox (perhaps along with a display name).
1 - 100 of 112 matches
Mail list logo
