Masaharu Kawada writes:
> The failed mail shows an 'x-beenthere' header in it like below.
> The 'x-beenthere' header looks to be the reason why the problematic
> mailing list fails to receive mail from user, but I have no idea in
> what kind of situation we get 'x-beenthere' header in mail.
Bernd Petrovitsch writes:
> On 27/05/2020 01:08, Mark Sapiro wrote:
> > Basically unknown. For the most part, log files are us-ascii, but some
> > entries contain user entered data such as names or (malformed) email
>
> If the user enters his name in a HTML form with e.g. German umlauts,
>
Mark Sapiro writes:
> On 6/1/20 3:15 PM, Lucio Crusca wrote:
> > Ok, let's assume it is a deliverable address. Running the following
> > one-liner yields nothing:
My guess is that the real mailbox was replaced with a hash of that
mailbox. SHA-2-512 or SHA-3-512 would fit with the
Mark Sapiro writes:
> On 5/26/20 4:30 PM, Brett Delmage wrote:
> > Hi!
> >
> > What is the character set coding for the log files, please?
> > I'm using MM 2.1.29
>
> Basically unknown. For the most part, log files are us-ascii,
I would consider declaring ISO-8859-1, ISO-8859-15, or
Paul van der Vlis writes:
> I am the sysadmin of a server what runs Mailman version 2.1.23 (Debian).
> Yes, I know it's old and I should install a newer version ;-)
Hey, no apologies necessary. The day before we had a question about
2.1.9!
Christian F Buser via Mailman-Users writes:
> Hello Mark Sapiro. On Wed, 13 May 2020 13:35:41 -0700, you wrote:
> > Do not add bbcn...@bellviewbaptistpaducah.com as a member of the
> > list - that can cause mail loops.
> I subscribe a possible sender to the list and sett this address to
>
Mark Sapiro writes:
> -op, data = v
> -if (op == Pending.SUBSCRIPTION and
> -data.address.lower() == email.lower()):
> +if (v[0] == Pending.SUBSCRIPTION and
> +v[1].address.lower() == email.lower()):
Pedantic Python
Mark Sapiro writes:
> On 5/13/20 9:55 AM, justinhumphres--- via Mailman-Users wrote:
> > My question is how can I in the settings for when I email out the
> > mass email that it says from: bbcn...@bellviewbaptistpaducah.com
> > instead of being from my work email of:
> >
Jim Popovitch via Mailman-Users writes:
> Interestingly enough, here's a roadmap on exactly how to do it: :)
Jim, you're not helping. Until there are "I'll do it" hands up, no
port to Python 3 that is faithful to current Mailman 2 is viable.
Pushing it just serves to annoy those who are
Mark Sapiro writes:
> I'd say it depend on the details of how serious the vulnerability is,
> how easy it is to exploit and how hard it is to fix. I am not opposed to
> Mailman 2.1.30-x security fix releases.
Mark speaks for me, although it's been a long time since I've worked
on Mailman 2,
Mark Sapiro writes:
> Well, Steve channeled me earlier, so I'll return the favor.
And did it with extreme precision and accuracy. Sorry if I created
any misunderstandings.
The only thing I have to add is that mailman-users@python.org is not
going away. Furthermore, I expect that Mark and I,
Phil Stracchino writes:
> On 2020-02-28 05:44, Stephen J. Turnbull wrote:
> > str in Python 1, and the history of Mailman as an MLM for an American
> > rock band (who needs no steekin' accents, we just hammer and bend the
> > strings!)
>
> This is cl
Brian Carpenter writes:
> On 2/28/20 1:55 PM, Mark Sapiro wrote:
> > Quite a few core settings are not exposed in Postorius but we're
> > chipping away at that.
>
> Is there a list somewhere to see what core settings have not been
> exposed in Postorius yet?
Implicit in the Postorius UI
@mailman-users
I'm going to get into a lot of design here, so I'm moving the thread to
mailman-develop...@python.org. Reply-To set; please respect. Brian
kept in Reply-To as a courtesy, don't know if he's subscribed over there.
@mailman-developers Brian is planning to develop an alternative web
Brian Carpenter writes:
> I have hired a professional PHP developer to begin work on a new
> admin/forum interface for Mailman 3.
Too bad. I really sympathize with your goals but am unlikely to be
able to contribute directly to implementation (assuming an eventual
open-sourcing). Never
Phil Stracchino writes:
> Rewriting without breaking is hard.
True.
> There is a Python framework called Twisted.
Not an example appropriate to Mailman, though. The Twisted people were
doing amazing things with str, to which Unicode was irrelevant, because
their job was to shovel bytes from
Dennis Putnam writes:
> Since migrating to mailman 3 on the latest RHEL is going to take some
> time, I need an interim solution to DMARC mitigation. I understand
> version 2.1.18
Why 2.1.18? Do you have that already installed? It's already pretty
old, and many of the fixes still being made
Jim Popovitch via Mailman-Users writes:
> Mod_Rewrite is "too heavy" for something this simple.
It's only too heavy if it actually has an unacceptable impact on
system load. That said, I like the SetEnvIf* approach better.
> SetEnvIfNoCase Referer "https://.*/mailman/listinfo/;
Jim Popovitch via Mailman-Users writes:
> (I think I asked this a few months back, but I couldn't locate any
> emails on it)
>
> What is the Apache rule syntax for rejecting subscription linking that
> doesn't come from the same domain/site?
Don't know what you need exactly, but mod_rewrite
Thanks for the update, Bruce!
Bruce Johnson writes:
> This was the actual bounce error from one of the offending messages:
>
> 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:
>
>
>
Jim Dory writes:
> I have one problem that when a particular user (the city) sends an
> announcement, it tends to bounce hundreds of mainly one ISP's users.. that
> ISP being Alaska's GCI.com .
I assume you mean that the attempt to deliver to users at GCI bounce
back to you?
What we would
Chromatest J. Pantsmaker writes:
> I had sent some test email from gmail and several hours later those
> test messages didn't pass. Maybe I goofed something along the way.
If the GMail address used to send is the same as the address
subscribed to the test list, you won't see it because GMail
Allan Hansen writes:
> [ABH] The “From:” should contain the author address, but if we want to
> keep our Yahoo/AOL subscribers…
Exactly. This is what we economists call the Theorem of the Second
Best: When it's already broken, sometimes the best you can do is to
break it harder.
> [ABH]
Allan Hansen writes:
> But Apple Mail puts the mangled address To: into the ‘Previous
> Recipients’ list to help with auto-completion later.
I assume by "To" you mean "From". We don't munge "To" in this
situation (there is a personalized list configuration where To is
changed from the list to
rabin...@sasktel.net writes:
> I would still be interested in seeing and documentation on a known
> good list configuration to ensure
That doesn't exist. Spam fighters generally believe their users would
rather lose mail than receive spam, and act aggressively on that
belief. Some sites have
Mark Sapiro writes:
> Actually, that's still not quite correct. Ours looks like
>
> "xxx via list"
Thank you for the correction.
I wonder whether users would behave differently if we used "list on
behalf of xxx" instead of "xxx via list"?
> I suspect this latter is due to what Allan
Allan Hansen writes:
> I have set the ReplyTo: as the author, it’s not the immediate
> replying as such that is an issue, and the mangled string is
> factually correct. The issue comes when Apple Mail does
> auto-completion and hides the email address.
>
> A mangled From: address like
Allan Hansen writes:
> 1. Replace the From: address with a no-reply address on the list
>server. Don’t add the sender’s address in quotes.
I believe this requires a change in the Mailman code.
I guess you want the author's display name, if available, there? What
if there is no display
Stefan Bauer via Mailman-Users writes:
> More and more mails contain s/mime signatures. How to deal with
> that?
To add to what Mark says, I would say not at all. I would consider
broken S/MIME signatures to be a bug, because Mailman should be
treating the multipart/signed *part* as a block,
Reply-To set to mailman-us...@mailman3.org.
Allan Hansen writes:
> I need to upgrade from Mailman 2.1 - my hardware needs upgrading
> (badly) and the address mangling is having my subscribers rip their
> hair out.
That's not going to go away. We have ARC support in Mailman 3, but
(a) like
Mark Sapiro writes:
> > I also found this post where this guy says you need to remove the
> > DKIM headers:
> > https://blog.dogan.ch/2016/11/24/making-mailman-dmarc-compatible/
> It says that, but gives no reason or rationale for doing so.
I know several mail admins (small-scale, not any of
Dave Stevens writes:
> I was trying to log in to the mailman pending admin tasks page to
> delete an attempted post by a non-member.
>
> in /var/log/mailman/error is:
> admin(22004): File "/var/lib/mailman/Mailman/LockFile.py", line 422,
> in __write admin(22004): fp =
Tom Corcoran writes:
> Wow! Thanks, Steve!
>
> My mention of pdf here, crossed over with my other post and
> confused, sorry.
Not a problem. I'm still a little worried about your settings,
though. The question is, "Do you want to receive those PDFs?" If
"application/pdf" is not in
Tom Corcoran writes:
> All emails that come in I want to forward to our 2 addresses with no
> archive so as far, as I am concerned ongoing admin having to accept
> messages from new addresses, is overkill and I would avoid doing it and
> accept all messages if that was possible. Also,
Tom Corcoran writes:
> *But*, the mystery for me is if archives are turned off how are the
> attachments saved. Is there another setting? If not, surely one
> should be added so this unnecessary support request is not needed?
Mailman has a facility for saving attachments so that (1) space
Ralf Hildebrandt writes:
> That's [do you mean 4 hours?] quite a lot. I know that postfx for
> example would rescan the queue after 300s (5m) and probably retry
> the message then (after an initial failure).
Well, I wouldn't be surprised if nowadays defaults are like that. I
haven't changed
Jim Ziobro writes:
> Indeed email is not a synchronous messaging channel. But most
> email clients will sort incoming messages by header Date thus undo
> the effects of out-of-order delivery.
That's mostly true. However, traditionally the first retry was set
for 4 hours after the initial
Scott Neader writes:
> Hi Stephen (and all). Indeed, I am having MUCH luck with this! First, the
> option to base64 encode the recipient's email as a new header with the
> RCPT_BASE64_HEADER_NAME config setting (discussed in my last post) is
> working great! In addition, as you mentioned,
Loren Engrav via Mailman-Users writes:
> sometimes I load an invalid address (invalid name but valid domain)
> like x...@whidbey.com; whidbey.com is ok but there is no xyz
>
> with Mailman 2.1.26 at site5.com and 2.1.29 at mailmanlists.net
> I do not receive a bounce message
Some sites
Have you had any luck with this in the last couple of days?
Scott Neader writes:
> I have Personalization enabled, and have the subscriber's email
> address in the footer, but Comcast redacts the email address.
> Unfortunately, there are quite a few comcast.net users on this
> list, making
Sorry for the delay, I left this in my drafts folder "for lunch" and
forgot it.
Brett Delmage writes:
> And it is working!
Great! Thank you for reporting status.
> The stupid thing is that I never changed anything.
That's useful to know, it means I'm not going crazy. But these things
Loren Engrav via Mailman-Users writes:
> can whitelist on outlook
> that seems to have solved outlook problem
> yahoo and aol remain
> attempts to whitelist there have failed
I'm not sure what you're asking, if anything. Or are you just
reporting partial success at outlook.com but not
Christian,
Thanks for the analysis!
Brett,
Whenever possible, you should send the whole message, preferably as an
attachment, redacting only personally identifying information. This
includes display names and comments attached to mail addresses as well
as the addresses themselves in From, To,
Brett Delmage writes:
> I've been having trouble with one subscriber whose content was always
> stripped.
>
> After changing a Content filtering flag and discovering that lynx was not
> installed, my tests of my own multipart html + text, and html-only
> messages indicated I had finally
Norbert Bollow writes:
> On some of those lists, it is really strongly desirable to actively
> encourage the list's participants to see themselves as an
> international community, in particular as a community where US
> centric perspectives are not privileged over other perspectives.
Jim Popovitch via Mailman-Users writes:
> I just keep getting reminded
By your users? By Tommy Robinson fans, Boris Johnson, and football
hooligans? Or just when you see it in the list of supported languages?
> that we specifically support USA English and we offer no other
> English
Hi Jayson,
Roadrunner has been problematic in this way for decades. They don't
explain, they don't provide policy information or contact addresses,
and their staff have frequently been snotty about DoS'ing their own
customers.
You may have already seen this thread on the Spectrum forums. I
Fabian A. Santiago writes:
> i run a mailing list on mm 2.x. periodically i send out an event
> opening email to the list. this is typically followed by a
> conclusion email at the end of a specific period. in the interim
> period i would like to send out reminders of the event to the list
>
Grant Taylor via Mailman-Users writes:
> RFC 3464 has been out for 17 years. I think it's past time that we
> stop coddling people that can't conform to it.
It's not a matter of coddling nonconformers. The only thing we are
likely to be able to do about them is "Sleeping Giants" them on
Steven D'Aprano writes:
Mark's already answered, but I had a couple of minor points to add.
> I run an announcement-only mailing list which has become the target of a
> lot of spam, so I've set unsubscribed emails to be immediately
> discarded. 99% of the discarded emails are spam, but
Grant Taylor via Mailman-Users writes:
> On 4/23/19 5:02 AM, Kiffin Gish wrote:
> > Is it possible to configure mailman so that it is not possible for users
> > to change their email address, e.g. disabling the option and including
> > the service desk contact information instead?
I'll have
Mark Dale writes:
> We had a customer ask for their lists to have this option. Their
> lists are used with some kind of automated entry/exit logging
> processes.
Jim Popovitch via Mailman-Users writes:
> Ack. It's a narrow need, but there are reasons. Not every list is for raw
> public
Mark Dale writes:
> I've posted some notes on restricting a list's archive to Administrators
> only. They may be of use to some folks.
Could you say something about the use case? If there's a common
enough reason for doing this, we (the committers) should think about
adding such features to
Matthew Goebel writes:
> Won't redhat just apply/support fixes provided the software vendor?
For RHEL, no, they'll do a lot more than that if it's covered by the
support contract. That's the business model: if they were just
providing the integration testing, Centos would eat their lunch.
>
Mike Flannigan writes:
> I'm surprised to hear there is so much migration in Python with
> limited backward compatibility. Perl has never had that problem.
Of course it has. I had Perl 4 on my Debian box for a decade after
Perl 5 was released, because various apps had scripts or something
Carl Zwanzig writes:
> On 4/10/2019 11:36 AM, Dimitri Maziuk via Mailman-Users wrote:
> > (That said, given the history of python, my question would be if there
> > are any plans to port MM2 to golang or maybe gnat.)
Not within the Mailman project.
It seems pointless to me. If you want
Mark Sapiro writes:
> You may want to add
>
> PIPFile=/home/mailman/data/master-qrunner.pid
should that variable be PIDFile?
--
Mailman-Users mailing list Mailman-Users@python.org
https://mail.python.org/mailman/listinfo/mailman-users
Valentin Schwarze via Mailman-Users writes:
> I am the administrator of some mailman lists of the student
> self-administration of our university. We happend to have some spam
> issues on our mailman lists. These spammers were able to send
> emails on our lists through mail spoofing (only
Grant Taylor via Mailman-Users writes:
> Note: SPF by itself won't do anything to protect against From: header
> spoofing.
Sure, but if configured correctly, it gives you exactly the
information you need. The problem with SPF is that a lot of header
spoofing is legitimate (at least from the
Grant Taylor via Mailman-Users writes:
> I'm talking about bypassing the local MTA all together. Pipe fetcmail's
> STDOUT to a wrapper script to extract the command and mailing list
> before piping it into the mailman executable with said command and
> mailing list.
This should work in
Jim Dory writes:
> On Mon, Mar 18, 2019 at 4:39 AM Stephen J. Turnbull <
> turnbull.stephen...@u.tsukuba.ac.jp> wrote:
> > (You probably should also disable the Digestable option in
> > [Digest options]
When I wrote this, I was thinking of a new list, in the co
Davide Marchi writes:
> 1) How is it possible from Mailman monitor the delivery errors? Only
> sysadmin mail server from the logs?
That depends on what you mean by "monitor" and "delivery errors". If
you mean mail refused by some system (typically the final recipient)
and returned to
Crossposting and redirecting replies to mailman-us...@mailman3.org.
Steven Jones writes:
> I cant find anything on this so far but can Mailman3's webui use
> freeipa as the authentication mechanism?
Hi Steve,
I don't have a complete answer offhand (and right now I'm just
reducing my inbox so
Lothar Schilling writes:
> > What do you get if in that Python you do
> >
> > import string
> > lowercase
I think this should be 'string.lowercase'.
> import string
>
> lowercase
> Traceback (most recent call last):
> File "", line 1, in
> NameError: name 'lowercase' is not
karrageorgiou giannis via Mailman-Users writes:
> I was thinking of receiving a copy of the discarded
> messages for sometime, until I am sure the rule is
> fair, and manually forward as myself a mistakenly
> dropped text
I think Mark already alluded to this, but here are the details.
In
R. Diez writes:
> Your comments are surprisingly unfair for someone in a mailing list
> for mailing list software.
How would you be a good judge of fairness? Have you been developing
mailing list software for twenty years and reading the requests and
problems of users daily for that period?
R. Diez via Mailman-Users writes:
> I have the following recurring problem with mailing lists all over
> the Internet: people do reply to my posts, by they do not address
> or copy me in their replies. They send their e-mails only to the
> mailing list. Or they reply to the previous reply,
edi...@visionscience.com writes:
> Not sure if this is a mailman issue, but…
It's not, although possibly Mailman can help mitigate it.
> Occasionally as moderator I see messages in which "***SPAM*** “ has
> been prepended to the subject line. The messages are not spam. I
> do not want to
David Gibbs via Mailman-Users writes:
> On 1/28/19 2:25 PM, Mark Sapiro wrote:
> > List of addresses (or regexps) whose posts should always apply
> > dmarc_moderation_action regardless of any domain specific DMARC Policy.
>
> That's close to what I want ... the only issue is that I'm
Jim Ziobro writes:
> Are there any plans to support changing of mail interface addresses for
> other languages?
No. There won't be, and patches submitted will very likely be
rejected.
> In MTA/Utils.py I find:
> ('admin', 'bounces', 'confirm', 'join', 'leave', 'owner', 'request',
>
Dmitri Maziuk via Mailman-Users writes:
> On Mon, 3 Dec 2018 10:30:53 -0500
> Jim Ziobro wrote:
> ...
> > Is the directory “/etc/mailman” group-writable only to support the
> > creation of an aliases file?I would feel more confident if /etc/mailman
> > was only writable by root.
>
> So
Odhiambo Washington writes:
> I am running a list that has members joining and leaving.
> I'd like to get an inside of these changes:
> 1. how many members joined last month, this month..
> 2. How many members left last month, this month, this year.
Systers Mailman provides a console for
Mark Sapiro writes:
> On 11/24/18 9:17 PM, Jayson Smith wrote:
> > I had a Mailman/DNS problem after upgrading a lot of packages. A
> > message came in, Mailman couldn't properly look up the DMARC
> > policy of the sending ISP, didn't munge the From: and sent the
> > message on its way...
>
Richard Damon writes:
> Not all domains managed by Yahoo have a DMARC setting of reject,
True, I believe (although AIUI yahoo.co.* except for yahoo.co.jp have
p=reject, jp is franchised, not managed by Yahoo!), but those not
branded "Yahoo!" have p=whatever-the-domain-wants.
> I imagine only
Lindsay Haisley writes:
> hotmail-com.olc.protection.outlook.com [104.47.44.33]:
> >>> MAIL FROM:
> BODY=8BITMIME SIZE=5492
> <<< 550 5.7.1 Unfortunately, messages from [198.58.125.221] weren't
> sent. Please contact your Internet service provider since part of their
> network is on our
Peter Shute writes:
> At least one member of our list has received an unexpected email
> from the list server requesting confirmation of unsubscription. It
> looks to me like someone has filled in this member's address on the
> unsubscription form on their behalf in an attempt to remove them
Joseph Brennan writes:
> I don't have a Mailman recommendation, but the situation is worth some
> comment:
>
> Notice Gmail "blocks" with a 4xx temp fail, for a message they will never
> accept. That's a protocol violation. It's abusive.
This is unclear, and I lean to saying Google's
Bernie Cosell writes:
> I've gotten buried by 80 bounce messages, thanks to gmail's new
> policy [that was, apparently, put into effect yesterday]. The
> bounces say:
Can you provide more information about this, or are you deducing a new
policy from the sudden spate of bounces? I ask
Mark Sapiro writes:
> > What version is Mailman? I believe that recent versions put the PID
> > file in the 'lock' directory.
>
> There is a master_qrunner lock file in the locks directory but
> data/master-qrunner.pid contains the PID of the running Mailman.
OK, so this is a Debian
Hi Roger,
First let me apologize on behalf of the project for the delay in
distribution of your post. It appears a few posts got trapped in
limbo for about 10 days, and the delay was definitely between
Mailman's MTA and mine.
Roger writes:
> I inherited a mult-server install of Mailman.
>
Stephen J. Turnbull writes:
> David Andrews writes:
>
> > Are they screen shots or something???
>
> It's a very busy day so this is all you get now, but if nobody gets to
> it before I do I will test, add to FAQ *as text*, and post a link over
> the weekend.
As p
David Andrews writes:
> Are they screen shots or something???
It's a very busy day so this is all you get now, but if nobody gets to
it before I do I will test, add to FAQ *as text*, and post a link over
the weekend.
Many thanks to Mike for the link to
Dimitri Maziuk via Mailman-Users writes:
> Or they could check out list archives and see if their message is
> there.
Of course that's an option, if the list is archived (may not be), but
pretty clearly the subscribers in this case at least want a "push"
notification (ack in their inbox), and
Adam Morris writes:
> What I'm saying is that if a member posts a message they don't see
> it at all even though all other members do.
This is a familiar problem with GMail, and with sites that delegate
their email handling to Google. Google refuses to change it or
provide a user option to
Adam Morris writes:
> Someone sent me the below link.
> If this can be implemented by me on my lists how can I do it?
>
> https://www.lsoft.com/news/techtipLSV-issue2-2017.asp.
If I understand what you want correctly, this is possible and
controlled by the subscriber's "ack" option.
You
Peter Shute writes:
> We mostly have the Plain option ticked. Is that RFC 934? And
> unticked is Mime?
Yes and yes.
> I’ll try contacting bigpond, but as a non customer, I suspect I’ll be
> ignored at best.
True, but you're in a lot better position vis-a-vis petulant bigpond
customers if
Peter Shute writes:
> Have you been able to do anything about it? If we can't get their
> server to believe it's not spam, we're going to have to take all
> these people off digest, and some won't like it.
There are two digest formats, MIME and RFC 934 (older and somewhat
less robust, but
Loren Engrav via Mailman-Users writes:
> to finish this off case anyone else needs to know...
Thank you for the update!
Steve
--
Mailman-Users mailing list Mailman-Users@python.org
https://mail.python.org/mailman/listinfo/mailman-users
John Levine writes:
> In article <20180804141855.7510026c1...@sharky3.deepsoft.com> you write:
> >-=-=-=-=-=-
> >
> >Do you have access to your inbound mail server? If so, you need to
> >arrange for that server to *reject* all mail connections from
> >qq.com. qq.com is a *notorious* source
Jordan Brown writes:
> Wasn't this in the context of signature-checking schemes that detect
> forged origin metadata?
Context, yes. The question is did Intuit need extreme accuracy for
that? Maybe they did, but I see no evidence for that need.
Intuit was not a financial intermediary. It
Reply-To set to Mailman-Developers. Please clean up your header if
you use Reply-All.
Richard Damon writes:
> It would be nice if Mailman could tell the MTA as it was receiving the
> message that it wasn't acceptable so it could be rejected then, but
> since it generally can't, you need to
Grant Taylor via Mailman-Users writes:
> On 07/25/2018 03:53 AM, Stephen J. Turnbull wrote:
> > That's not how "on behalf of" worked in practice. What happened in April
> > 2014, was that a home business owner (HBO) would send a pile of completed
> &
Mark Sapiro writes:
> First, the MLM side of this proposal is exactly what the Mailman "Wrap
> Message" action does.
RFC-geeks-love-Mark!-ly y'rs
--
Mailman-Users mailing list Mailman-Users@python.org
Jordan Brown writes:
> Well, yeah, but to provide such a service in a way that has any
> resemblance to being secure, Intuit *must* have some secret that allows
> it to send mail "from" those subdomains. If Intuit doesn't need such a
> secret, then anybody could send mail like that.
Sure,
John R Levine writes:
> Large mail systems already know where all the mailing lists are.
Hm. Well, that may be true for Google et al, but the systems at my
employer regularly mark internal business mail as "possible spam",
occasionally mark it as "almost certainly spam", and pass through
John Levine writes:
> As I said a few messages ago, if lists did more stringent tests on
> incoming mail, a lot of this complexity could be avoided,
I don't understand this. If lists got a pass, every spam would grow
RFC 2369 header fields. No? So ISTM the received chain needs to be
Grant Taylor via Mailman-Users writes:
> On 07/24/2018 03:16 PM, John Levine wrote:
> > Turning it on for aol.com, yahoo.com, and other domains with user
> > mailboxes,
>
> So, are you stating that DMARC should NOT be used on domains that
> (predominantly) contain end user mailboxes?
Grant Taylor via Mailman-Users writes:
> I would think / hope / expect that such services would be from a
> different (sub)domain of the client that they are sending email on
> behalf of.
That's not how "on behalf of" worked in practice. What happened in
April 2014, was that a home
Grant Taylor via Mailman-Users writes:
> I'm questioning why domains that do use ARC headers that don't run
> mailing lists should not be white listed.
You're misunderstanding. The ARC community doesn't discourage
whitelisting other sites. The work to do whitelisting does. Mailing
lists
Mark Sapiro writes:
> The problem is downstream has to trust me. If I'm gmail.com, I'll
> probably be trusted. If I'm msapiro.net, probably not. Python.org, who
> knows.
The problem is the same butt-lazy admins that caused you to implement
DKIM-stripping.[1] Google and (AFAIK) Yahoo! and
201 - 300 of 1551 matches
Mail list logo
