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(https://www.regextester.com/94044), 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$

^.+@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

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:

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:

...

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(https://www.regextester.com/94044), 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$

...

^.+@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

Mailman-Users mailing list -- mailman-users@python.org To unsubscribe send an email to mailman-users-leave@python.org https://mail.python.org/mailman3/lists/mailman-users.python.org/ Mailman FAQ: http://wiki.list.org/x/AgA3 Security Policy: http://wiki.list.org/x/QIA9 Searchable Archives: https://www.mail-archive.com/mailman-users@python.org/ https://mail.python.org/archives/list/mailman-users@python.org/

--

*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/

--

*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/

On 9/29/20 10:22 PM, Daniel Krause via Mailman-Users wrote:

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$

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

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:

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(https://www.regextester.com/94044), 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$

...

^.+@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.