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

[MM3-users] Re: Mailing lists sometimes do not honor moderation_action of non-members

by Mark Sapiro

On 10/31/19 2:21 AM, Alan So wrote: > We notice that sometimes mailing lists do not honor moderation_action of non-members. Instead, it follows the default action of the lists. It looks like we can sometimes fix the issue by adding/removing the non-members or adding/removing them as owner in certain order but we are not sure about exactly what we have to do. So, it looks like that it is not caused by the list configuration. We have already verified from the web UI, mailman client and the DB table member that moderation_action of the corresponding non-members are set correctly. Any clues for us to provide further information to troubleshoot the issue and any recommended workaround to get around the issue? Thanks a lot. Reasons why a post From: a non-member would not be treated according to that non-members moderation_action include the following: If any address in any of the places configured in mailman -> sender_headers (default = From: header, envelope sender, Reply-To: header, Sender: header) is that of a member, that member's moderation_action will apply. If any of the addresses above matches an address or pattern in one of the lists *_these_nonmembers attributes that action will apply rather than the corresponding non-member's moderation_action. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

6 years, 9 months

[MM3-users] Re: Why aren't I getting bounce texts any more?

by Mark Sapiro

On June 8, 2026 4:31:31 PM PDT, Paul Tomblin via Mailman-users <mailman-users(a)mailman3.org> wrote: >I swear I used to get the exactly text of the bounce message when email to a list member bounced, but I'm not seeing it any more. Is there a setting I've overlooked? I've turned on "*Notify owner on bounce increment"* which was off for some reason. With "Notify owner on bounce increment" set to Yes, the list owner should receive a notice containing the bounce DSN whenever a user's bounce score is incremented. Since it was off for some reason, these would not have been sent. The other relevant settings are "notify owner on disable" and "notify owner on removal". The disable notice should also contain the DSN. What were these settings? >I just had 24 users bounced off a mailing list this morning for excessive bounces Removed or just had delivery disabled? If the latter, I can only think that both the bounce increment and disable notice settings were off. , and I can only think their ISP suddenly took exception to my setup somehow. It would have been nice to have to a warning when the first bounce happened. And you should have gotten it, but the setting was off. -- Mark Sapiro <mark(a)msapiro.net> Sent from my Not_an_iThing with standards compliant, open source software.

2 months, 1 week

[MM3-users] Re: Example Logrotate files for Mailman3

by Mark Sapiro

On 6/30/20 2:10 PM, Andrew Hodgson wrote: > Hi, > > Does anyone have any usable Logrotate files for Mailman3 (especially for the web stuff)? Here are two. They differ in the name and location of the Django log. Both of them signal gunicorn to reopen its logs. If you are using uWSGI or some other WSGI support, you'll need to figure that out. In this one, all the logs including Django's are in /opt/mailman/mm/var/logs/ > /opt/mailman/mm/var/logs/*.log { > missingok > sharedscripts > su mailman mailman > postrotate > /opt/mailman/mm/bin/mailman reopen &>/dev/null || true > if [ -r /opt/mailman/mm/var/gunicorn.pid ]; then > PID=`cat /opt/mailman/mm/var/gunicorn.pid` > kill -s USR1 $PID > fi > endscript > } This one is actually two because the Django log is in /var/log/ rather than /opt/mailman/mm/var/logs/. > /opt/mailman/mm/var/logs/*.log { > missingok > sharedscripts > su mailman mailman > postrotate > /opt/mailman/mm/bin/mailman reopen &>/dev/null || true > if [ -r /opt/mailman/mm/var/gunicorn.pid ]; then > PID=`cat /opt/mailman/mm/var/gunicorn.pid` > kill -s USR1 $PID > fi > endscript > } > } > /var/log/mailman-web/*.log { > missingok > notifempty > delaycompress > su mailman mailman > } -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

6 years, 1 month

[MM3-users] Re: Send MySQL data to mailman list for distribution

by Mark Sapiro

On 6/1/21 1:46 PM, Zden Pos via Mailman-users wrote: > I'm trying to connect existing MySQL data to the Mailman distribution list. > Actually, a message is sent from the web page. It remains on this page and is also stored in the MySQL table on the provider server. This is working fine. > I have also existing Mailman distribution list generated from the cPanel on the provider server as well. This list is working fine when used for a direct mailing. > > I need to link the MySQL table to the Mailman distribution list. When the message is posted on the web page and stored in the MySQL table, it is also to be sent to members as per the Mailman distribution list. I don't know where to configure it. In the phpMyAdmn page of the MySQL or in the Malman menu ? I am very confused because it appears that your Mailman list with MySQL data is a Mailman 3 list, but cPanel lists as far as I know are Mailman 2.1 only. My best guess is you want posts to the Mailman 3 list to be forwarded to thwe cPanel list. If so, just add thee cPanel list's posting address as a member of the Mailman 3 list. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

5 years, 2 months

[MM3-users] Re: Moving from forum to Mailman 3

by Mark Sapiro

On 10/9/20 4:39 PM, jonathan.mailing.lists(a)gmail.com wrote: > > Thanks for this. I’m sure I could turn that basic information (from, date, subject) into an mbox file somehow. What else does Mailman need, eg to work out which messages are in reply to which? To properly thread messages, each message should have a unique Message-ID: header and all replies should have an In-Reply-To: header with the Massage-ID: of the message to which it's a reply. E.g. the first message in a thread has Message-ID: <some_unique_string(a)example.com> A reply to that has Message-ID: <different_unique_string(a)example.com> In-Reply-To: <some_unique_string(a)example.com> and a reply to that message has Message-ID: <third_unique_string(a)example.com> In-Reply-To: <different_unique_string(a)example.com> The angle brackets around the strings are required and every Message-ID: in the entire archive for a list must be unique. If threading is not an issue, hyperkitty_import will generate a unique Message-ID: for any message without one. References: headers are not required. > Would it be possible to add ex-forum message “emails” like this to an existing mailing list archive? Yes. When running hyperkitty_import you probably need to specify since= in this case, otherwise only messages with dates newer that the newes message in the existing archive will be imported. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

5 years, 10 months

[MM3-users] Re: Fwd: [Django] ERROR (EXTERNAL IP): Internal Server Error: /mailman3/hyperkitty/api/mailman/archive

by Mark Sapiro

On 3/2/21 12:10 AM, David Partain via Mailman-users wrote: > > I'm not on the latest mailman, unfortunately. I use the bundled packages on Ubuntu 18.04, which are > > mailman3 3.1.1-9 > mailman3-doc 3.1.1-9 > mailman3-full 3.1.1-9 > mailman3-web 0+20170523-14 > >>From the mailman-web logs, it looks like it's using python2. That would explain a lot. In particular, it would explain why the .pyc files aren't located per PEP 3147 <https://www.python.org/dev/peps/pep-3147/>. But it also raise the question of how anything works at all. Python >= 3.6 is required. HyperKitty and Postorius used to run under Python 2, but haven't for some time. I'm not sure what versions are in Debian/Ubuntu 0+20170523-14 package. > Put the symlink back, and it works again. (But still without the emojis working, of course.) > > Postgres is what's in settings.py, but I assume that should be overriden by what's in settings_local.py. > > Baffling. I don't really know what to do next, but I'll keep looking. I suggest removing all the .pyc files and restarting the services. That will probably recreate .pyc files, but they should then be good. -- 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: Subscribe to a list on a Mailman3 server without account registration

by Mark Sapiro

On 6/6/23 01:07, c.buhtz(a)posteo.jp wrote: > Hello, > I might miss something here but I'm confused about a difference between Mailman2 and 3. > > On MM2 I just subscribed a mailinglist via my EMail address. I didn't need to create an account on the MM2 server first. > But it seems on MM3 it is otherwise. For example I use MM3 on python.org. It seems I have to register first before subscribing to a mailing list. > https://mail.python.org/mailman3/lists/twisted-web.python.org/ You can subscribe without creating an account. You do need an account if you want to manage your subscription via the web UI or to visit private archives, but not to just be a list member or visit public archives. The issue with the https://mail.python.org/mailman3/lists/ lists is that the anonymous subscribe form which looks like: ----------------------------------------- You can also subscribe without creating an account. If you wish to do so, please use the form below. Your email address __________ Your name (optional) __________ ----------------------------------------- has been removed from list info page because it was being abused by people attempting to subscribe third parties. You can still subscribe without creating an account by emailing twisted-web-subscribe(a)python.org. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

3 years, 2 months

[MM3-users] Re: Problems with signed messages from Apple Mail

by Mark Sapiro

On 11/12/21 6:06 AM, Rainer Herbst wrote: > Dear all, > > after upgrading his Mac to MacOS 12.0.1 Monterey, one of our users can > not send send signed messages to lists using Apple Mail v. 15.0 > (3693.20.0.1.32). > > mailman3 denys the delivery of the mail with error message: > host 172.19.0.4[172.19.0.4] said: 501 Message has defects > (in reply to end of DATA command) > > I.e. mailman does not process the message, but rejects it already in the > incoming smtp session. Is that a known issue? Incoming SMTP is relaying the message via LMTP to Mailman's LMTP runner which in turn parses the message using Python's email.message_from_bytes() method and the resultant message has defects. Rejecting such a message outright as we do may be too harsh, but it is hard to say without seeing the message and what Python's email package thinks the defects are. This could be a bug in Apple Mail or in the Python email module. If you wish to see the details, you could do the following in `mailman shell` ``` import email from mailman.email.message import Message content = b"""\ (paste the raw message here) """ msg = email.message_from_bytes(content, Message) msg.defects ``` This will show you what the defects are. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

4 years, 9 months

[MM3-users] Re: mailman3-suite not sending confirmation emails

by Mark Sapiro

On 1/2/19 11:59 PM, ccehb(a)nus.edu.sg wrote: > Hi, > > This is my first experience using mailman. I recently downloaded and setup mailman3 suite which comes with hyperkitty. I don't really understand why the email is not working. I had an external smtp server (mymailserver.com) residing on different IP from my web server that hosts mailman stuff. > > I had modified settings.py with debug = False and added the following: > > EMAIL_BACKEND = 'django.core.mail.backends.smtp.EmailBackend' > EMAIL_HOST = 'mymailserver.com' > EMAIL_PORT = 25 These should be OK, but they are only for messages from Django, not for list mail. Also if mymailserver.com requires authentication, you may need to set EMAIL_HOST_USER and EMAIL_HOST_PASSWORD. > I also added these inside mailman.cfg > > [mta] > outgoing: mailman.mta.deliver.deliver > lmtp_host: 127.0.0.1 > lmtp_port: 8024 The above are all defaults. > smtp_host: mymailserver.com > smtp_port: 25 Again, if mymailserver.com requires authentication, you need to set smtp_user and smtp_pass. > Thanks for your help! I check the logs but there isn't anything. When I sign up, nothing happens and I can't figure out why? Is Mailman running? If so, and there's nothing in logs, it is probably using some other (default) config and logging somewhere other than where you think. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

7 years, 7 months

[MM3-users] Re: Chinese characters in list name shows question mark (?)

by Mark Sapiro

On 10/23/19 7:12 AM, Franklin Weng wrote: > Hi list, > > I set up a mailman3 server and built a few lists to test. > > When I set the list name using Chinese characters, the web site shows > correctly. However in the subscribing welcome mail the list name was > shown in question marks. Screenshot is here: > > https://nextcloud.slat.org/index.php/s/CxPjpYMbQzQ6444 The name of the list from the screenshot seems to be zh-l10n(a)lists.linux.org.tw. The thing shown with ?s in the screenshot is the list's display_name (called Display name in Postorius). > The LANGUAGE_CODE settings.py (in Debian /etc/mailman3/mailman-web.py) > is set to zh-tw , and USE_I18N and USE_L10N are all set to True. These settings are all for Django and have nothing to do with how the list welcome message is sent. > Is there any other setting I should look at? The list's preferred_language setting (Postorius -> Settings -> List Identity -> Preferred Language. The list welcome message is encoded in Mailman's character set for the list's preferred_language. If this is English (USA), the character set is us-ascii. If it is set to Chinese (Taiwan), the character set is utf-8, and it should work. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

6 years, 9 months

Search results for query "sapiro"