Does the @[NAME] expression, that accepts posts to mailing list X by
subscribers of mailing list Y still work in mailman3? Strictly speaking,
it is not a regexp, but I rely on it heavily.

I am testing out mailman3 and I have to say, migration works much better
than I expected! Kudos!!

However, regexps from "accept_these_nonmembers" have not been migrated,
so I wonder if they are still recognized.



Am 29.09.20 um 17:26 schrieb Mark Sapiro:
> On 9/29/20 5:38 AM, Daniel Krause via Mailman-Users wrote:
>> Good Day
>> We are using mailman 3, and would like to whitelist a domain for acceptance
>> of messages as non-members.
>> It seems possible from my online searches, I have also tried with an online
>> python regex tester(, but I have not
>> managed to be successful.
>> Below are 2 examples I have tried
>> ^.+@noldor\.co\.za$
> This looks good.
>> ^[a-zA-Z0-9_.+-]+@(?:(?:[a-zA-Z0-9-]+\.)?[a-zA-Z]+\.)?noldor\.co\.za$
> This is unduly complex. These regexps are matched case insensitively so
> it isn't necessary to include both a-z and A-Z. Also, I don't thing you
> need to be concerned about invalid addresses, so
>   ^.+@(?:.+\.)?noldor\.co\.za$
> would do, or even simpler
>   ^.*[@.]noldor\.co\.za$
>> ^$
> This would allow user@gmailxcom, but probably not an issue.
>> ^.*gmail\.com$
> This is good.
> How are you unsuccessful? If you have say
>   ^.+@noldor\.co\.za$
> in accept_these_nonmembers, what happens when an address from that
> domain posts to the list?
> Note that while determination of whether a message is from a list member
> checks addresses in several things (default From:, envelope sender,
> Reply-To:, Sender), *_these_nonmembers checks only the first address
> found in From:, Sender:, envelope sender in that order by default, but
> if USE_ENVELOPE_SENDER is set True in, the order is Sender:,
> From:, envelope sender.
Mailman-Users mailing list --
To unsubscribe send an email to
Mailman FAQ:
Security Policy:
Searchable Archives:

Reply via email to