Non-member regexps
![](https://secure.gravatar.com/avatar/e35e5a2fbf397d4378418b8dee54dabb.jpg?s=120&d=mm&r=g)
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(https://www.regextester.com/94044), but I have not managed to be successful.
Below are 2 examples I have tried
^.+@noldor\.co\.za$ ^[a-zA-Z0-9_.+-]+@(?:(?:[a-zA-Z0-9-]+\.)?[a-zA-Z]+\.)?noldor\.co\.za$ ^.+@gmail.com$ ^.*gmail\.com$
Regards
--
*Daniel Krause* *Head of IT*
*Office: **+27 87 238 4238* <0872384238> *Mobile : **+971 55 418 4733* <0971554184733> *Email: **daniel@noldor.co.za* <daniel@noldor.co.za> *Web: **www.noldor.co.za* <http://www.noldor.co.za/>
![](https://secure.gravatar.com/avatar/56f108518d7ee2544412cc80978e3182.jpg?s=120&d=mm&r=g)
On 9/29/20 5:38 AM, Daniel Krause via Mailman-Users wrote:
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$
^.+@gmail.com$
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 mm_cfg.py, the order is Sender:, From:, envelope sender.
-- Mark Sapiro <mark@msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan
![](https://secure.gravatar.com/avatar/e35e5a2fbf397d4378418b8dee54dabb.jpg?s=120&d=mm&r=g)
It would seem the issue was that the sending address was already listed as a non-member with a default action Tested after clearing out the non-member and its working now
On Tue, Sep 29, 2020 at 7:29 PM Mark Sapiro <mark@msapiro.net> wrote:
--
*Daniel Krause* *Head of IT*
*Office: **+27 87 238 4238* <0872384238> *Mobile : **+971 55 418 4733* <0971554184733> *Email: **daniel@noldor.co.za* <daniel@noldor.co.za> *Web: **www.noldor.co.za* <http://www.noldor.co.za/>
![](https://secure.gravatar.com/avatar/e35e5a2fbf397d4378418b8dee54dabb.jpg?s=120&d=mm&r=g)
If I only have one address listed then the regexps work
Instructions are to have one address per line, yet this then fails I have tried terminating lines with commas and semicolons, neither have worked
This is what I have currently, each of these work if they are the only entry ^.+@gmail\.com$ ^.+@noldor\.co\.za$
On Wed, Sep 30, 2020 at 9:02 AM Daniel Krause <daniel@noldor.co.za> wrote:
--
*Daniel Krause* *Head of IT*
*Office: **+27 87 238 4238* <0872384238> *Mobile : **+971 55 418 4733* <0971554184733> *Email: **daniel@noldor.co.za* <daniel@noldor.co.za> *Web: **www.noldor.co.za* <http://www.noldor.co.za/>
![](https://secure.gravatar.com/avatar/56f108518d7ee2544412cc80978e3182.jpg?s=120&d=mm&r=g)
On 9/29/20 10:22 PM, Daniel Krause via Mailman-Users wrote:
Is this Mailman 2.1 or Mailman 3? If Mailman 3, please join the mailman-users@mailman3.org list at <https://lists.mailman3.org/mailman3/lists/mailman-users@mailman3.org/> and post there.
I will follow up once I know which Mailman this is.
-- Mark Sapiro <mark@msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan
![](https://secure.gravatar.com/avatar/56f108518d7ee2544412cc80978e3182.jpg?s=120&d=mm&r=g)
On 9/29/20 10:02 PM, Daniel Krause via Mailman-Users wrote:
This list is for Mailman 2.1. It appears you are using Mailman 3. The appropriate list for Mailman 3 is mailman-users@mailman3.org <https://lists.mailman3.org/mailman3/lists/mailman-users@mailman3.org/>.
-- Mark Sapiro <mark@msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan
![](https://secure.gravatar.com/avatar/4be100ab9eb4ca6f9ddb97fbd202b11f.jpg?s=120&d=mm&r=g)
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.
Cheers,
Johannes
Am 29.09.20 um 17:26 schrieb Mark Sapiro:
![](https://secure.gravatar.com/avatar/56f108518d7ee2544412cc80978e3182.jpg?s=120&d=mm&r=g)
Please do not use this list for Mailman 3 questions. The list for Mailman 3 is mailman-users@mailman3.org https://lists.mailman3.org/mailman3/lists/mailman-users@mailman3.org/
On 2/11/21 1:59 PM, Johannes Rohr wrote:
No. That is not in Mailman 3 at this time.
They are and they should have been migrated. If you have recent versions of Mailman core (specifically import21) and postorius, you should see them in Settings -> Message Acceptance.
Specifically, import21 should migrate non-regexp addresses in *_these_nonmembers as non-members with the appropriate moderation action and regexps into the corresponding MM 3 lists *_these_nonmembers.
-- Mark Sapiro <mark@msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan
![](https://secure.gravatar.com/avatar/56f108518d7ee2544412cc80978e3182.jpg?s=120&d=mm&r=g)
On 9/29/20 5:38 AM, Daniel Krause via Mailman-Users wrote:
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$
^.+@gmail.com$
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 mm_cfg.py, the order is Sender:, From:, envelope sender.
-- Mark Sapiro <mark@msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan
![](https://secure.gravatar.com/avatar/e35e5a2fbf397d4378418b8dee54dabb.jpg?s=120&d=mm&r=g)
It would seem the issue was that the sending address was already listed as a non-member with a default action Tested after clearing out the non-member and its working now
On Tue, Sep 29, 2020 at 7:29 PM Mark Sapiro <mark@msapiro.net> wrote:
--
*Daniel Krause* *Head of IT*
*Office: **+27 87 238 4238* <0872384238> *Mobile : **+971 55 418 4733* <0971554184733> *Email: **daniel@noldor.co.za* <daniel@noldor.co.za> *Web: **www.noldor.co.za* <http://www.noldor.co.za/>
![](https://secure.gravatar.com/avatar/e35e5a2fbf397d4378418b8dee54dabb.jpg?s=120&d=mm&r=g)
If I only have one address listed then the regexps work
Instructions are to have one address per line, yet this then fails I have tried terminating lines with commas and semicolons, neither have worked
This is what I have currently, each of these work if they are the only entry ^.+@gmail\.com$ ^.+@noldor\.co\.za$
On Wed, Sep 30, 2020 at 9:02 AM Daniel Krause <daniel@noldor.co.za> wrote:
--
*Daniel Krause* *Head of IT*
*Office: **+27 87 238 4238* <0872384238> *Mobile : **+971 55 418 4733* <0971554184733> *Email: **daniel@noldor.co.za* <daniel@noldor.co.za> *Web: **www.noldor.co.za* <http://www.noldor.co.za/>
![](https://secure.gravatar.com/avatar/56f108518d7ee2544412cc80978e3182.jpg?s=120&d=mm&r=g)
On 9/29/20 10:22 PM, Daniel Krause via Mailman-Users wrote:
Is this Mailman 2.1 or Mailman 3? If Mailman 3, please join the mailman-users@mailman3.org list at <https://lists.mailman3.org/mailman3/lists/mailman-users@mailman3.org/> and post there.
I will follow up once I know which Mailman this is.
-- Mark Sapiro <mark@msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan
![](https://secure.gravatar.com/avatar/56f108518d7ee2544412cc80978e3182.jpg?s=120&d=mm&r=g)
On 9/29/20 10:02 PM, Daniel Krause via Mailman-Users wrote:
This list is for Mailman 2.1. It appears you are using Mailman 3. The appropriate list for Mailman 3 is mailman-users@mailman3.org <https://lists.mailman3.org/mailman3/lists/mailman-users@mailman3.org/>.
-- Mark Sapiro <mark@msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan
![](https://secure.gravatar.com/avatar/4be100ab9eb4ca6f9ddb97fbd202b11f.jpg?s=120&d=mm&r=g)
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.
Cheers,
Johannes
Am 29.09.20 um 17:26 schrieb Mark Sapiro:
![](https://secure.gravatar.com/avatar/56f108518d7ee2544412cc80978e3182.jpg?s=120&d=mm&r=g)
Please do not use this list for Mailman 3 questions. The list for Mailman 3 is mailman-users@mailman3.org https://lists.mailman3.org/mailman3/lists/mailman-users@mailman3.org/
On 2/11/21 1:59 PM, Johannes Rohr wrote:
No. That is not in Mailman 3 at this time.
They are and they should have been migrated. If you have recent versions of Mailman core (specifically import21) and postorius, you should see them in Settings -> Message Acceptance.
Specifically, import21 should migrate non-regexp addresses in *_these_nonmembers as non-members with the appropriate moderation action and regexps into the corresponding MM 3 lists *_these_nonmembers.
-- Mark Sapiro <mark@msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan
participants (4)
-
Brian Carpenter
-
Daniel Krause
-
Johannes Rohr
-
Mark Sapiro