Search results for "sapiro" - lists.mailman3.org

[MM3-users] Re: Subscription notification sent from the site admins work-mail.

by Mark Sapiro

On 09/13/2018 05:01 AM, Henrik Rasmussen wrote: > One of my list administrators told me that all seven list administrators on a list received a "None <foo(a)example.com> has been successfully subscribed to [LIST NAME].", when someone subscribed to their list, however the sender of the mail (From:) was my own work mail address. I am not associated with the list other that I am site admin. This is expected behavior. In Mailman 2.1 notices like this were sent From: the site list (normally 'mailman'). In Mailman 3, there is no site list so the notices are from the site admin. If you'd rather not expose your work mail address in this way, set the site admin to something generic like mailman-admin(a)example.com and alias that to where you want the mail to go. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

8 years, 1 month

[MM3-users] Re: Cannot see the cron jobs for Mailman 3 Installed

by Mark Sapiro

On 1/23/20 4:49 AM, Shashikanth Komandoor wrote: > Hi, > > I have setup the Mailman 3 on my RHEL 7.5 box and found it was working > fine. But I found that I am not getting daily summary notifications for > which I learnt after browsing through different websites, there should be > an entry of *checkdb* in the cron job list. checkdbs is a Mailman 2.1 job The equivalent Mailman 3 job is `mailman notify` > But I did not find any such nor I don't find any cron job updated after > the installation of mailman 3. See <https://docs.mailman3.org/en/latest/config-core.html#configuring-cron-jobs> and <https://docs.mailman3.org/en/latest/config-web.html#scheduled-tasks-required> If you installed Mailman from a package and the cron's weren't installed, report this to the packager. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

6 years, 8 months

[MM3-users] Re: Subscription issue with ghost confirmations

by Mark Sapiro

On 10/31/20 7:28 AM, Brian Carpenter wrote: > > This has occurred again. A person sends an email to listname-subscribe@listdomain and the subscription policy of said list is set to moderate only. Instead of honoring this, a confirmation email is sent out. The issue is that when a request is received to subscribe an address to a list and that address is not verified and the pre_verified flag is not set in the request, the user is sent a confirmation request. This is not a request to confirm the subscription request, but rather a request to confirm the address, however they use the same template so they are indistinguishable. We probably should check the subscription policy and not send this request if the policy is moderate. We should also ignore a pending request if the policy is moderate per <https://gitlab.com/mailman/mailman/-/issues/789>. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

5 years, 11 months

[MM3-users] Re: Can't deliver mails in queue

by Mark Sapiro

On 5/19/21 2:45 PM, Nathanael Schneider wrote: > > They were in fact not identical, as I changed some stuff in hopes to get > it up and running again quickly. I now changed the completely new List > to be identical with the cleanly created one (as far as postorius shows > me) and it still works just fine. Do I understand correctly that you deleted the MM 2.1 imported list and created a new list in Postorius with just two members and it doesn't work. If that understanding is not correct, please outline all the steps you took to arrive at the current list that doesn't work. Also, please capture one of the .pck or .bak files from the out queue and send it to me off list. I will treat it confidentially, but there might be clues in it. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

5 years, 5 months

[MM3-users] Re: list footer web customization procedure

by Mark Sapiro

On 11/30/21 1:11 AM, Stephen J. Turnbull wrote: > > Does Django empty out the "spacetebasket" if it's all white space, or > does spurious whitespace in that box lead to an (apparently) empty > footer being added? Postorius used to remove leading and trailing whitespace from the template, but not since https://gitlab.com/mailman/postorius/-/issues/301 was fixed. > Anway, I recommend to the OP that they make sure there's no whitespace > in the Data box. A good recommendation. While a header or footer template with some whitespace might not be noticeable when added to a text/plain message, it will cause extra mime parts to be added to more complex messages. Also, if the goal in setting an empty footer is to avoid breaking a DKIM signature, even adding a bit of whitespace to a text/plain message is an issue. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

4 years, 10 months

[MM3-users] Re: Python 3.9 support

by Mark Sapiro

On 2/24/22 14:01, dancab(a)caltech.edu wrote: > > Only mail delivery was hung overnight. I had to restart the Gunicorn process followed by a Mailman core restart for mail to flow again. Because Mailman's "out" runner (/opt/mailmanve/lib/python3.9/site-packages/mailman/runners/outgoing.py from the above traceback) is what hit the exception and died. The master watcher should restart it, but see https://gitlab.com/mailman/mailman/-/issues/898 > Any insight into how we could monitor this in the future? For example which specific "runner" reported the error above? Something like ``` ps --ppid=`cat /opt/mailman/mm/var/master.pid|tr -d '\n'`|wc -l ``` will report the number of child processes of the master. You could test that against the expected number and do something. Note that `mailman restart` probably won't start a runner that died - you need to do `mailman stop;mailman start` to be sure. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

4 years, 7 months

[MM3-users] Re: Strange messages after upgrading Mailman3

by Mark Sapiro

On 12/4/22 20:09, Allan Hansen wrote: > Hi all, > > I have been getting a few of these messages after my Mailman 3 was upgraded: > > "The content of this message was lost. It was probably cross-posted to > multiple lists and previously handled on another list." > > The messages appear to come from list members and are distributed to the relevant lists, but with nothing of the original contents. > They have appeared on different lists with, apparently different senders (unless spoofed). > Other messages are going through the system unchanged. > > Anyone has any ideas? To what version did you upgrade? This is most likely https://gitlab.com/mailman/mailman/-/issues/955 which was fixed in Mailman core 3.3.6, but it could be https://gitlab.com/mailman/mailman/-/issues/1027 if the posts are to umbrella lists (lists with other lists as members). -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

3 years, 10 months

[MM3-users] Re: Messages hold for moderation - compared to mailman2 it appears that there are fewer options: missing option(?)

by Mark Sapiro

On 3/7/24 9:35 AM, Wikinaut wrote: > Hello, I miss sadly the option of > > both: > > i) discarding the current message of a sender (not member of a closed list) ; and in the same action > ii) adding this person to the whitelist, i.e. accept further mails from this sender. When you go to the held messages view in the web UI and click the Subject: of the held message, there is a dropdown to set the sender's moderation action. you can select `default processing` to accept subject to additional checks or `accept` to accept unconditionally, subsequent posts from that sender before clicking the `discard` or other button. This works for non-members as well as for members. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

2 years, 7 months

[MM3-users] Re: [Bug] Someone not a member of list is treated as member - strange

by Mark Sapiro

On 8/23/25 11:51, Wikinaut wrote: > > Because it may be a breaking change in mailman3 - no one wants this I do not think is is a breaking change and I strongly disagree that no one wants it. If you want prior Mailman behavior, just don't link multiple addresses to one user. You can have a separate user for each address and then each address will be considered as belonging to a different person which is apparently what you want. Going back to your original issue, why do you have a problem? The fact that a post from one of your addresses was accepted even though it wasn't from the address that was subscribed in no way says that a post from an arbitrary nonmember would be accepted. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

1 year, 1 month

[MM3-users] Re: Block members from sending cc's and bcc's

by Mark Sapiro

On 10/26/25 10:38, Cathryn McGuire wrote: > > Since setting to Default Processing, ALL members posts are being held for moderation. That's what happened last time. Obviously there's some setting somewhere that's telling the list to do that with that setting. We'll try to find it by doing testing like you said. Meanwhile, we're quite busy in our other endeavours and having to unblock every post (some days more than others, and not that many relatively speaking) is what we're doing. What is the reason given for the post being held? I don't know about affinity, but Postorius gives the reason in the list of held messages. Also the message itself has a X-Mailman-Rule-Hits: header that says which rule caused the message to be held -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

11 months, 3 weeks

Search results for query "sapiro"