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

[MM3-users] Re: signup / registration error - permissions and cert chains

by Mark Sapiro

On 12/30/21 4:48 PM, David Newman wrote: > > The etc/mailman3/settings.py file includes these settings: > > EMAIL_BACKEND = 'django.core.mail.backends.smtp.EmailBackend' > EMAIL_HOST = 'localhost' > EMAIL_PORT = 25 These 2 (localhost and port 25) are defaults. > EMAIL_HOST_USER = 'dnewman(a)networktest.com' > EMAIL_HOST_PASSWORD = 'wouldnt-you-like-to-know' Why are you authenticating? This should not be necessary. > EMAIL_USE_TLS = 'True' > EMAIL_SSL_CERTFILE = '/etc/ssl/certs/myhost.crt' > EMAIL_SSL_KEYFILE = '/etc/ssl/private/myhost.key' And why are you trying to use TLS? This is only for SMTP between Django and the MTA on the loopback port. TLS is overkill. > But this might only be for email, not Postorius/Django. Actually it is only for mail from Django -- 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: Bulk changes to delivery mode and moderation action

by Mark Sapiro

On 1/7/22 1:51 PM, David Newman wrote: > > However, there's no evidence test messages to the list are going out. > (Nondelivery was the reason I was mucking around in the admin panel in > the first place.) > > The Postfix log shows delivery to the list address. > > MM3's smtp.log shows the usual handshake. > > However, I do not then see messages going out to subscribers in the > Postfix log, and as one of those subscribers I do not receive a copy > even though my preferences are set to receive my own posts. Are the messages in Mailman's var/queue/shunt queue? Are there errors and tracebacks in var/logs/mailman.log? -- 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: Backup and restore a single list

by Mark Sapiro

On 6/16/22 23:53, sherin(a)raidm.com wrote: > Hello, > I am new to mailman3 . I am looking for the procedure to backup and restore a single mailing list from mailman3. If any one know the procedure or the documentation , please point me Unlike Mailman 2.1, Mailman 3 stores all it's list specific data in a database. The database contains data for all lists, so backing up all lists would be a backup procedure for the database which depends on the database manager, i.e., sqlite, MySQL/MariaDB or PostgreSQL. A procedure to backup/restore a single list would require a script to extract/restore the data for that list from the DB. There is an open issue for this at https://gitlab.com/mailman/postorius/-/issues/13 -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

4 years, 4 months

[MM3-users] Re: Migrating users from MM2 to MM3 on a new server?

by Mark Sapiro

On 11/25/24 9:31 AM, jkoral(a)luc.edu wrote: > Is there a way to copy users from the old MM2 server to a new MM3 server? Also, will it copy their password as well? The `mailman import21` command imports am MM 2.1 config.pck to a MM 3 list. Passwords are not imported. MM 3 does not use a list member's password. The web management UI (Postorius) and web archiver (HyperKitty) are Django applications and the user has to sign up for a Django account via the web UI. This account is then connected to the users list memberships via the user's email address. Also, see this thread https://lists.mailman3.org/archives/list/mailman-users@mailman3.org/thread/… -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

1 year, 10 months

[MM3-users] Re: Issues sending to gmail and yahoo e-mails

by Mark Sapiro

On 9/11/25 15:22, jkoral(a)luc.edu wrote: > OK, so we are dealing with two servers. The old server is still setup to forward the addresses to the new server with a different domain. I would like to make the new server lists instead of listservnew. I am assuming I can just create the domain lists.luc.edu on the new server, but how would I move all the lists to that new domain? Please don't hijack threads, even ones you started. I.e. when posting a new question which is unrelated to the existing thread, post a new message with a relevant subject, not a reply to an unrelated message. You move the lists by moving the mailman and mailmanweb databases. -- 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: Mass change Digest delivery mode

by Mark Sapiro

On August 3, 2026 4:20:36 PM PDT, iMark <imark(a)posteo.net> wrote: >The variable 'm' is the mylist(a)lists.mydomain.com mailing list >>>> mailman.interfaces.member import DeliveryMode for member in m.subscribers: > File "<console>", line 1 > mailman.interfaces.member import DeliveryMode for member in m.subscribers: > ^^^^^^ >SyntaxError: invalid syntax It looks like your line breaks are not correct. The line should be from mailman.interfaces.member import DeliveryMode And for member in m.subscribers: is a separate line. It appears the 'from' is missing and maybe a line break is missing. Also, in mailman shell in interactive mode, the import line is not required at all as those things are all imported automatically, but in a script as Steve also suggested, the import is required. -- Mark Sapiro <mark(a)msapiro.net> Sent from my Not_an_iThing with standards compliant, open source software.

2 months, 2 weeks

[MM3-users] Re: log rotation

by Mark Sapiro

On 09/06/2018 08:34 AM, Dmitry Makovey wrote: > > We're running containerized deployment which complicates the matter > slightly, but having "some" approach for log rotation would be helpful. > So before I dig into the code looking for SIGUSR1 or SIGHUP handlers can > someone point me to a proper documentation for log management with MM3 ? Log rotation per se is not done by Mailman. It is up to some external process like logrotate. As far as reopening logs post rotation is concerned, the mailman command 'mailman reopen' is used for the core logs. What is done for web logs depends on the web configuration. With gunicorn I use if [ -r /opt/mailman/mm/var/gunicorn.pid ]; then PID=`cat /opt/mailman/mm/var/gunicorn.pid` kill -s USR1 $PID fi -- 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: required cron entries?

by Mark Sapiro

On 1/1/21 12:17 AM, Andreas Barth wrote: > > In my case, this was however > Uncaught runner exception: (raised as a result of Query-invoked > autoflush; consider using a session.no_autoflush block if this flush > is occurring prematurely) (sqlite3.OperationalError) database is > locked [SQL: 'UPDATE mailinglist SET last_post_at=?, post_id=? WHERE > mailinglist.id = ?'] [parameters: ('2020-12-23 10:18:41.030593', 10, > 11)] (Background on this error at: http://sqlalche.me/e/e3q8 > > > The 'fix' for that was turning it off and on again (i.e. rebooting the > VM), but now I have a few messages around. Do you mean you have messages in the shunt queue that were shunted because of this error? If so, just running Mailman's `mailman unshunt` command should reprocess and deliver those. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

5 years, 9 months

[MM3-users] Re: Unknown attribute: process_bounces

by Mark Sapiro

On 5/18/21 1:29 AM, xlefloch--- via Mailman-users wrote: > Hello, > > I've upgraded my Mailman installation from those versions: > mailman==3.2.2 > postorius==1.2.4 > mailmanclient==3.2.2 > > To those ones: > mailman==3.3.0 > postorius==1.3.3 > mailmanclient==3.3.2 > > I'm having issues in Postorius in the settings section: Unknown attribute: process_bounces. > When i'm printing the settings list for the concerned list retrieved by the REST API, i'am missing all the parameters related to the management of bounces. In the "mailinglist" table of the Mailman database, i have the columns managing these parameters. > > Anyone have any ideas? Postorius 1.3.3 requires Mailman core >=3.3.1 How did you upgrade?. If this was a package upgrade, your packager has produced an incompatible set of components. -- 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: Mailman REST API not available. Please start Mailman core.

by Mark Sapiro

On 2/12/25 15:39, Christian via Mailman-users wrote: > I followed instructions provided here. Well, I rebooted the server and I'm > getting the same error again at the web page of > > "Mailman REST API not available. Please start Mailman core." > > I again found locks in /opt/mailman/mm/var/locks . Once I removed them I > could start mailman. > > Perhaps I made a boo boo. I want mailman to start without locks upon reboot. If Mailman is properly shut down, it shouldn't leave locks. How did you reboot? If your /etc/systemd/system/mailman3.service file contains an appropriate ExecStop, reboot via a `reboot` or `shutdown -r` should stop Mailman appropriately. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

1 year, 8 months

Search results for query "sapiro"