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

[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, 4 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

6 years

[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, 7 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, 4 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, 11 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, 9 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, 11 months

[MM3-users] Re: About to Install MM3 -- Seeking clarification

by Mark Sapiro

On 10/22/22 21:29, Onyeibo Oku wrote: > > Now Mailman starts, and stops as desired when running as mailman user (both in > virtual and non-virtual environments). However, running the service via systemd > still fails. I now get a different traceback: > > Oct 23 03:43:00 mail.server.tld mailman[19410]: Traceback (most recent call last): ... > Oct 23 03:43:00 mail.server.tld mailman[19410]: with open(self._claimfile, 'w') as fp: > Oct 23 03:43:00 mail.server.tld mailman[19410]: PermissionError: [Errno 13] Permission denied: '/opt/mailman/mm/var/locks/mailman-cfg.lck|server.tld|19410|619270043958240354' > Oct 23 03:43:00 mail.server.tld systemd[1]: mailman3.service: Control process exited, code=exited, status=1/FAILURE What are ownership and permissions on /opt/mailman/mm/var/locks/ Assuming they are drwxr-xr-x mailman mailman it must be the case that systemd is not running the `/opt/mailman/venv/bin/mailman start` command as the `mailman` user. I suspect this is a Fedora issue. I note that https://docs.fedoraproject.org/en-US/quick-docs/understanding-and-administe… does not mention User or Group. You might try replacing ``` ExecStart=/opt/mailman/venv/bin/mailman start ExecReload=/opt/mailman/venv/bin/mailman restart ExecStop=/opt/mailman/venv/bin/mailman stop with ExecStart=sudo -u mailman /opt/mailman/venv/bin/mailman start ExecReload=sudo -u mailman /opt/mailman/venv/bin/mailman restart ExecStop=sudo -u mailman /opt/mailman/venv/bin/mailman stop ``` -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

3 years, 11 months

[MM3-users] Re: Flooded non-members with "prvs=<number>=<mail>"

by Mark Sapiro

On 12/22/24 04:35, Torge Riedel via Mailman-users wrote: > > I checked the non-members list of all my mailman3 lists and found a lot > entries like "prvs=<number>=<mail>", the <mail> is always an address > from @freenet.de > > A quick research mentions something related to bouncing and that such > mails should be blocked/filtered. But no further details. > > Can you give a hint where I need to change what to block such mails and > avoid that such entries floods the non-members list? If these are in fact bounces, the mta at freenet.de is sending bounce DSNs to the list address instead of (or possibly in addition to) the list-bounces address which is the envelope sender of the mail from Mailman. This behavior is wrong, but it is beyond your control. If you can identify a pattern in the From: address that would match these and only these mails, you could probably configure the incoming MTA to discard them. E.g., for Postfix, see https://www.postfix.org/header_checks.5.html You might think of using Mailman's Header filters to discard the messages, but this won't keep the nonmembers from being created as the creation happens before any of those checks. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

1 year, 9 months

[MM3-users] Re: Debian 12 postfix errors: "warning: connect to transport private/lmtp: Connection refused" and "status=deferred (mail transport unavailable)"

by Mark Sapiro

On 4/7/25 12:00, Philip Bondi wrote: > [mta] > incoming: mailman.mta.postfix.LMTP > outgoing: mailman.mta.deliver.deliver > lmtp_host: 127.0.0.1 > lmtp_port: 9024 Why are you setting this? Testing uses port 9024 to avoid conflicts, but the default port 8024 should be used for production. > [799] # postconf -n ... > virtual_mailbox_maps = hash:/opt/mailman/mm/var/data/postfix_lmtp Why do you have this? It may well be the issue. > ebill(a)systemdatabase.ca lmtp:[127.0.0.1]:9024 > ebill-bounces(a)systemdatabase.ca lmtp:[127.0.0.1]:9024 > ebill-confirm(a)systemdatabase.ca lmtp:[127.0.0.1]:9024 > ebill-join(a)systemdatabase.ca lmtp:[127.0.0.1]:9024 > ebill-leave(a)systemdatabase.ca lmtp:[127.0.0.1]:9024 > ebill-owner(a)systemdatabase.ca lmtp:[127.0.0.1]:9024 > ebill-request(a)systemdatabase.ca lmtp:[127.0.0.1]:9024 > ebill-subscribe(a)systemdatabase.ca lmtp:[127.0.0.1]:9024 > ebill-unsubscribe(a)systemdatabase.ca lmtp:[127.0.0.1]:9024 > > [797] # telnet localhost 9024 > Trying ::1... > Connection failed: Connection refused > Trying 127.0.0.1... > Connected to localhost. > Escape character is '^]'. > 220 shackleton12.systemdatabase.ca GNU Mailman LMTP runner 2.0 > QUIT > 221 Bye > Connection closed by foreign host. It looks like you can connect to port 9024 in this way. However I recommend removing `lmtp_port: 9024` from your mailman.cfg and rerunning `mailman aliases` to regenerate the postfix maps. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

1 year, 6 months

Search results for query "sapiro"