[Mailman-Users] Re: MAILMAN Sender name
Christian F Buser via Mailman-Users writes: > Hello Mark Sapiro. On Wed, 13 May 2020 13:35:41 -0700, you wrote: > > Do not add bbcn...@bellviewbaptistpaducah.com as a member of the > > list - that can cause mail loops. > I subscribe a possible sender to the list and sett this address to > "no message", so the address can be used for sending mails to the > list but does not get list messages - neither from the own address > nor from other users. Note that from the situation, most likely "bbcnews" *is the list*. Justin doesn't say enough to be sure, but if so that's a one-step mail loop. I'm pretty sure that's the situation Mark has in mind. Your solution is fine for human posters, but the cost of inadvertantly turning on delivery to the bbcnews address is "Sorcerer's Apprentice" levels of annoyance! It's up to Justin, of course, but I'm with Mark, it's not worth the risk. Steve -- Mailman-Users mailing list -- mailman-users@python.org To unsubscribe send an email to mailman-users-le...@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/
[Mailman-Users] Re: Errors with new version
Mark Sapiro writes: > -op, data = v > -if (op == Pending.SUBSCRIPTION and > -data.address.lower() == email.lower()): > +if (v[0] == Pending.SUBSCRIPTION and > +v[1].address.lower() == email.lower()): Pedantic Python at your service: -op, data = v +op, data = v[:2] Doesn't really matter, I guess, but if you can use mnemonic names, why not? -- Mailman-Users mailing list -- mailman-users@python.org To unsubscribe send an email to mailman-users-le...@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/
[Mailman-Users] Re: MAILMAN Sender name
Mark Sapiro writes: > On 5/13/20 9:55 AM, justinhumphres--- via Mailman-Users wrote: > > My question is how can I in the settings for when I email out the > > mass email that it says from: bbcn...@bellviewbaptistpaducah.com > > instead of being from my work email of: > > jus...@bellviewbaptistpaducah.com? I know it’s probably very > > simple, but any help would be great thanks! This looks like a pure announcement list. If the only sender is supposed to be "bbcnews", and that is the name of the list, wouldn't anonymous list or from_is_list DTRT? Then the only problem is restricting posting to justin@ (and any other authorized posters -- @justin, you should have other authorized posters in case you get sick or on vacation!) Steve -- Mailman-Users mailing list -- mailman-users@python.org To unsubscribe send an email to mailman-users-le...@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/
[Mailman-Users] Re: Minor nit needs correction/explanation
On 5/14/20 11:24 AM, Chip Davis wrote: > Under Privacy Options -> Recipient filters -> max_num_recipients, the > Details say: > > "*max_num_recipients* (privacy): Ceiling on acceptable number of > recipients for a posting. > > If a posting has this number, or more, of recipients, it is held for > admin approval. Use 0 for no ceiling." > > OK, which is it? It is "If a posting has this number, or more, of recipients, it is held for admin approval. Use 0 for no ceiling." Granted "ceiling" implies a maximum beyond which you can't go, rather than the lowest disallowed number, but at this stage in the life cycle of Mailman 2.1 this issue is not significant enough to warrant a change and the resultant i18n implications. -- Mark Sapiro The highway is for gamblers, San Francisco Bay Area, Californiabetter use your sense - B. Dylan -- Mailman-Users mailing list -- mailman-users@python.org To unsubscribe send an email to mailman-users-le...@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/
[Mailman-Users] Minor nit needs correction/explanation
Under Privacy Options -> Recipient filters -> max_num_recipients, the Details say: "*max_num_recipients* (privacy): Ceiling on acceptable number of recipients for a posting. If a posting has this number, or more, of recipients, it is held for admin approval. Use 0 for no ceiling." OK, which is it? Is the number specified in fact the "ceiling on _acceptable_ number of recipients" or "if a posting has this number ... of recipients, it is held for admin approval"? It would be clearer (regardless what the code does) if the answer was to change the Details to read: "If a posting has more than this number of recipients, it is held for admin approval." Then change the code if actually necessary. -Chip- -- Mailman-Users mailing list -- mailman-users@python.org To unsubscribe send an email to mailman-users-le...@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/
[Mailman-Users] Re: Errors with new version
Am 13.05.20 um 19:42 schrieb Mark Sapiro:
> On 5/13/20 4:48 AM, Sebastian Hagedorn wrote:
>> Hi,
>>
>> we seem to have new entries in the error log. I believe they have only
>> started to appear with the recent updates, but I cannot swear to that:
>>
>> admin(7095): [- Mailman Version: 2.1.33 -]
>> admin(7095): [- Traceback --]
>> admin(7095): Traceback (most recent call last):
>> admin(7095): File "/usr/lib/mailman/scripts/driver", line 117, in run_main
>> admin(7095): main()
>> admin(7095): File "/usr/lib/mailman/Mailman/Cgi/subscribe.py", line 113,
>> in main
>> admin(7095): process_form(mlist, doc, cgidata, language)
>> admin(7095): File "/usr/lib/mailman/Mailman/Cgi/subscribe.py", line 258,
>> in process_form
>> admin(7095): mlist.AddMember(userdesc, remote)
>> admin(7095): File "/usr/lib/mailman/Mailman/MailList.py", line 941, in
>> AddMember
>> admin(7095): if self.CheckPending(email):
>> admin(7095): File "/usr/lib/mailman/Mailman/MailList.py", line 849, in
>> CheckPending
>> admin(7095): op, data = v
>> admin(7095): ValueError: too many values to unpack
>>
>> I have no idea what causes that, and I have not been able to reproduce it.
>> It only seems to happen with a minority of subscribe attempts.
> This comes from the new in 2.1.30 feature:
>
> There is a new REFUSE_SECOND_PENDING mm_cfg.py setting that will cause a
> second request to subscribe to a list when there is already a pending
> confirmation for that user. This can be set to Yes to prevent
> mailbombing of a third party by repeatedly posting the subscribe form.
> (LP: #1859104)
>
> There is a bug in the code in that it assumes every entry in the
> pending.pck data is a 2-tuple which isn't correct. You can avoid this by
> not setting REFUSE_SECOND_PENDING = Yes in mm_cfg.py, or this patch will
> fix it
>
> === modified file 'Mailman/MailList.py'
> --- Mailman/MailList.py 2020-01-10 01:00:40 +
> +++ Mailman/MailList.py 2020-05-13 17:32:00 +
> @@ -846,9 +846,8 @@
> for k, v in pends.items():
> if k in ('evictions', 'version'):
> continue
> -op, data = v
> -if (op == Pending.SUBSCRIPTION and
> -data.address.lower() == email.lower()):
> +if (v[0] == Pending.SUBSCRIPTION and
> +v[1].address.lower() == email.lower()):
> return True
> return False
Thank you. I have applied the patch and will observe if the error
messages are gone.
--
.:.Sebastian Hagedorn - Weyertal 121 (Gebäude 133), Zimmer 2.02.:.
.:.Regionales Rechenzentrum (RRZK).:.
.:.Universität zu Köln / Cologne University - ✆ +49-221-470-89578.:.
--
Mailman-Users mailing list -- mailman-users@python.org
To unsubscribe send an email to mailman-users-le...@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/
