I'm running mailman 3.3.0 and seeing odd behavior for "Settings/Message Acceptance/Acceptable aliases".
Two things strike me as odd:
- whenever I change content of that field interface keeps on wrapping it in more and more square brackets:
[u'[u\'[u"[u\\\'foo@my.com\\\']"]\']']
whereas I've started with simple foo@my.com. I've checked with mailmanclient library and it seems like this is happening at the core level not just an interface:
ml.settings['acceptable_aliases']=['foo@my.com'] ml.save() print ml.settings['acceptable_aliases']
am I using it wrong or is there a bug?
- Related to #1 - we've migrated our mailing lists from foo@my.com to foo@lists.my.com however we've preserved old addresses. But in new setup mail sent in gets stopped for moderation with: "X-Mailman-Rule-Hits: implicit-dest" . What's the best course of action here to get mailing list respond to multiple email addresses?
-- Sr System and DevOps Engineer SoM IRT
Not sure whether to mark this "SOLVED" yet - but when I manually updated postgres DB with the aliases I wanted - everything started to work as expected.
so it does sound like a bug in mailman-core 3.3.0 . Shall I file it or was it already fixed in 3.3.1 (anouncement page didn't list that fix)
On 01/19/2018 02:26 PM, Dmitry Makovey wrote:
I'm running mailman 3.3.0 and seeing odd behavior for "Settings/Message Acceptance/Acceptable aliases".
Two things strike me as odd:
- whenever I change content of that field interface keeps on wrapping it in more and more square brackets:
[u'[u\'[u"[u\\\'foo@my.com\\\']"]\']']
whereas I've started with simple foo@my.com. I've checked with mailmanclient library and it seems like this is happening at the core level not just an interface:
ml.settings['acceptable_aliases']=['foo@my.com'] ml.save() print ml.settings['acceptable_aliases']
am I using it wrong or is there a bug?
- Related to #1 - we've migrated our mailing lists from foo@my.com to foo@lists.my.com however we've preserved old addresses. But in new setup mail sent in gets stopped for moderation with: "X-Mailman-Rule-Hits: implicit-dest" . What's the best course of action here to get mailing list respond to multiple email addresses?
-- Sr System and DevOps Engineer SoM IRT
On 01/19/2018 03:09 PM, Dmitry Makovey wrote:
Not sure whether to mark this "SOLVED" yet - but when I manually updated postgres DB with the aliases I wanted - everything started to work as expected.
so it does sound like a bug in mailman-core 3.3.0 . Shall I file it or was it already fixed in 3.3.1 (anouncement page didn't list that fix)
As far as I know, this is not a bug in core. It is <https://gitlab.com/mailman/postorius/issues/58> however, this may in fact be a bug in the REST API in which case I don't think it's fixed in API 3.3.1
- Related to #1 - we've migrated our mailing lists from foo@my.com to foo@lists.my.com however we've preserved old addresses. But in new setup mail sent in gets stopped for moderation with: "X-Mailman-Rule-Hits: implicit-dest" . What's the best course of action here to get mailing list respond to multiple email addresses?
acceptable_aliases is the way to address this, but as you note, it can't be properly set via Postorius and possibly via REST.
-- Mark Sapiro <mark@msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan
On Fri, 2018-01-19 at 16:30 -0800, Mark Sapiro wrote:
On 01/19/2018 03:09 PM, Dmitry Makovey wrote:
Not sure whether to mark this "SOLVED" yet - but when I manually updated postgres DB with the aliases I wanted - everything started to work as expected.
so it does sound like a bug in mailman-core 3.3.0 . Shall I file it or was it already fixed in 3.3.1 (anouncement page didn't list that fix)
As far as I know, this is not a bug in core. It is <https://gitlab.com/mailman/postorius/issues/58> however, this may in fact be a bug in the REST API in which case I don't think it's fixed in API 3.3.1
I guess we are all talking about the same thing, but just to mention, 3.1.1 is the latest release (instead of 3.3.1).
- Related to #1 - we've migrated our mailing lists from foo@my.com to foo@lists.my.com however we've preserved old addresses. But in new setup mail sent in gets stopped for moderation with: "X-Mailman-Rule-Hits: implicit-dest" . What's the best course of action here to get mailing list respond to multiple email addresses?
acceptable_aliases is the way to address this, but as you note, it can't be properly set via Postorius and possibly via REST.
Mailman-users mailing list mailman-users@mailman3.org https://lists.mailman3.org/mailman3/lists/mailman-users.mailman3.org/
-- thanks, Abhilash Raj
participants (3)
-
Abhilash Raj -
Dmitry Makovey -
Mark Sapiro