Re: [Mailman-Developers] What characters should be allowed in listnames
Hi Stephen,
At 10:12 PM 2/18/2017, Stephen J. Turnbull wrote:
The problem that I thought we may face is internationalized mailboxes
and domain names *are still ASCII* which encodes Unicode.
OK, I looked it up, and I was almost certainly wrong. The relevant
RFCs are actually 6531 (SMTPUTF8 extension), 5890 (IDNA), and 3492
(Punycode). IDNA allows "U-labels" (UTF-8), which we can gracefully
extend to, and "A-labels" (encoded using Punycode, which uses the
ASCII repertoire). AFAICT (haven't really looked carefully), Punycode
uses only letters, digits, and the hyphen ("-").
So I withdraw the comment.
RFC 5890 can be used for the domain name part. The issue would be
about what to do for the local part. If I recall correctly, the
question was not discussed as part of RFC 6531. I suggest taking a
look at RFC 7564.
Regards,
-sm
___
Mailman-Developers mailing list
Mailman-Developers@python.org
https://mail.python.org/mailman/listinfo/mailman-developers
Mailman FAQ: http://wiki.list.org/x/AgA3
Searchable Archives:
http://www.mail-archive.com/mailman-developers%40python.org/
Unsubscribe:
https://mail.python.org/mailman/options/mailman-developers/archive%40jab.org
Security Policy: http://wiki.list.org/x/QIA9
Re: [Mailman-Developers] Fixing DMARC problems with .invalid munge
Hi Stephen, At 23:28 05-05-2014, Stephen J. Turnbull wrote: Don't you have that backwards? It's pointing out lack of a formal hard requirement that is nit-picking. After all, Postel's Principle isn't written in any IETF procedure manual. Would you call that one a "nit", too? I labelled my previous comment as a nit (the previous comment was unimportant). I would not describe anything someone else writes as a nit. Regards, -sm ___ Mailman-Developers mailing list Mailman-Developers@python.org https://mail.python.org/mailman/listinfo/mailman-developers Mailman FAQ: http://wiki.list.org/x/AgA3 Searchable Archives: http://www.mail-archive.com/mailman-developers%40python.org/ Unsubscribe: https://mail.python.org/mailman/options/mailman-developers/archive%40jab.org Security Policy: http://wiki.list.org/x/QIA9
Re: [Mailman-Developers] Fixing DMARC problems with .invalid munge
Hi Stephen, At 01:07 05-05-2014, Stephen J. Turnbull wrote: Nor do I. I point to the *possibility* and our lack of ability to predict effects. The RFCs have proven over time to give us a system that works smoothly. We have rules of thumb that help to understand why they work as well as they do, but the most important one is that RFCs must be shown to work in practice before they become Proposed Standards. Ie, don't expect something to work until you see it. This is a nit. There isn't any requirement that RFCs have to be shown to work in practice before they become Proposed Standards. of the DMARC folks or the sysadmins at Yahoo. What matters is what "just plain folks" think. Remember, according to AOL, 2% of such Yes. No, that's the whole point. They will *not* strip the suffix, and instead prefix the phishing attack with We have repeatedly attempted to reach your email address, but our mail has been rejected due to your ISP's DMARC configuration. Thus we have used the .invalid convention to work around this problem for this important message. Yes. Regards, -sm ___ Mailman-Developers mailing list Mailman-Developers@python.org https://mail.python.org/mailman/listinfo/mailman-developers Mailman FAQ: http://wiki.list.org/x/AgA3 Searchable Archives: http://www.mail-archive.com/mailman-developers%40python.org/ Unsubscribe: https://mail.python.org/mailman/options/mailman-developers/archive%40jab.org Security Policy: http://wiki.list.org/x/QIA9
Re: [Mailman-Developers] Fixing DMARC problems with .invalid munge
Hi John, At 08:16 04-05-2014, John Levine wrote: The .invalid hack seems fine, no bounces, and no complaints about disappearing mail. There are mutant versions of this hack where you append a name with a wildcard that resolves but has an MTA that rejects all the mail, and a really evil one where you append a name that points to a server that rewrites the address and remails it, e.g. mme...@yahoo.com.remail.lists.org -> mme...@yahoo.com. For replies, I expected complaints, since I'm using it on some busy lists for my church where people complain about every little burp, but to my surprise I've gotten none. I think one reason is that you can still use an unmunged Reply-To, which a lot of users do, and the other is that it's pretty obvious what to do to get the address to work, unlike trying to guess the author's address if the From: is the list. Was there any occurrence of the ".invalid" in replies which were posted to the mailing list [1]? Regards, -sm 1. I assume that it would be caught on message submission. I am asking the question as what happens in practice might be different. ___ Mailman-Developers mailing list Mailman-Developers@python.org https://mail.python.org/mailman/listinfo/mailman-developers Mailman FAQ: http://wiki.list.org/x/AgA3 Searchable Archives: http://www.mail-archive.com/mailman-developers%40python.org/ Unsubscribe: https://mail.python.org/mailman/options/mailman-developers/archive%40jab.org Security Policy: http://wiki.list.org/x/QIA9
Re: [Mailman-Developers] Author_is_list option in upcoming mailman 2.1.16
Hi Franck, At 22:44 12-09-2013, Franck Martin wrote: In the upcoming mailman 2.1.16 there has been the introduction of the optional feature author_is_list "Replace the sender with the list address to conform with policies like ADSP and DMARC. It replaces the poster's address in the From: header with the list address and adds the poster to the Reply-To: header, but the anonymous_list and Reply-To: header munging settings below take priority. If setting this to Yes, it is advised to set the MTA to DKIM sign all emails. " There is an effort (not mailman-related) to mark ADSP as not recommended. Regards, -sm ___ Mailman-Developers mailing list Mailman-Developers@python.org https://mail.python.org/mailman/listinfo/mailman-developers Mailman FAQ: http://wiki.list.org/x/AgA3 Searchable Archives: http://www.mail-archive.com/mailman-developers%40python.org/ Unsubscribe: https://mail.python.org/mailman/options/mailman-developers/archive%40jab.org Security Policy: http://wiki.list.org/x/QIA9
Re: [Mailman-Developers] Adding DMARC support for Mailman 3
Hi Stephen, At 18:39 08-07-2013, Stephen J. Turnbull wrote: work better. Sometimes it's appropriate to "take ownership of From". There is a case where the mailing list administrator configured the list to take ownership of the "From". Telling people that it was not a good idea never works. It's easier to wait for the denial of service (which happened) and watch the complaints to pour in. Regards, -sm ___ Mailman-Developers mailing list Mailman-Developers@python.org http://mail.python.org/mailman/listinfo/mailman-developers Mailman FAQ: http://wiki.list.org/x/AgA3 Searchable Archives: http://www.mail-archive.com/mailman-developers%40python.org/ Unsubscribe: http://mail.python.org/mailman/options/mailman-developers/archive%40jab.org Security Policy: http://wiki.list.org/x/QIA9
Re: [Mailman-Developers] [Bug 985149] Add List-Post value to permalink hash input
At 10:33 20-04-2012, Terri Oda wrote: A question, though: what if the list gets migrated to a new server and the list id changes (e.g. because the domain or hostname changes)? I'm guessing we can handle it, but we should make sure there's a path for that. 'While it is perfectly acceptable for a List Identifier to be completely independent of the domain name of the host machine servicing the mailing list, the owner of a mailing list MUST NOT generate List Identifiers in any domain name space for which they do not have authority. For example, a mailing list hosting service may choose to assign List Identifiers in their own domain-based name space, or they may allow their clients (the list owners) to provide List Identifiers in a namespace for which the owner has authority.' The List-ID: is not tied to the server host name. To avoid migration pain, pick a domain name carefully. Regards, -sm ___ Mailman-Developers mailing list Mailman-Developers@python.org http://mail.python.org/mailman/listinfo/mailman-developers Mailman FAQ: http://wiki.list.org/x/AgA3 Searchable Archives: http://www.mail-archive.com/mailman-developers%40python.org/ Unsubscribe: http://mail.python.org/mailman/options/mailman-developers/archive%40jab.org Security Policy: http://wiki.list.org/x/QIA9
Re: [Mailman-Developers] [Bug 985149] [NEW] Add List-Post value to permalink hash input
Hi Barry, At 09:22 20-04-2012, Barry Warsaw wrote: What's the corner case? The corner case is Nested lists. Regards, -sm ___ Mailman-Developers mailing list Mailman-Developers@python.org http://mail.python.org/mailman/listinfo/mailman-developers Mailman FAQ: http://wiki.list.org/x/AgA3 Searchable Archives: http://www.mail-archive.com/mailman-developers%40python.org/ Unsubscribe: http://mail.python.org/mailman/options/mailman-developers/archive%40jab.org Security Policy: http://wiki.list.org/x/QIA9
Re: [Mailman-Developers] [Bug 985149] [NEW] Add List-Post value to permalink hash input
At 13:03 18-04-2012, Barry Warsaw wrote: https://bugs.launchpad.net/mailman/+bug/985149 The List-ID: can be assumed to be unique across different mailing lists. There's a corner case though. Regards, -sm ___ Mailman-Developers mailing list Mailman-Developers@python.org http://mail.python.org/mailman/listinfo/mailman-developers Mailman FAQ: http://wiki.list.org/x/AgA3 Searchable Archives: http://www.mail-archive.com/mailman-developers%40python.org/ Unsubscribe: http://mail.python.org/mailman/options/mailman-developers/archive%40jab.org Security Policy: http://wiki.list.org/x/QIA9
