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

[MM3-users] Re: "this held message has been lost"

by Mark Sapiro

On 9/28/21 8:42 PM, Ethan Furman wrote: > I have now seen this message on two different occasions. Any ideas on > what is happening? Happy to provide additional information if I am told > what is needed (and how to get it -- I'm a web moderator for the list > without access to the machine it runs on). :) The most likely reason is the message was cross-posted to multiple lists and held on more than one. When the message is handled on the first list, it is removed from the database and this is not available on the second list. This can also happen in a race situation if two moderators are handling the same message on the same list. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

3 years, 9 months

[Test] mailman-users@mailman3.org

by Mark Sapiro

The subject list exists and I think is configured appropriately. It is currently unadvertised. I am ready to advertise it and announce it. I have both Google and Facebook OAuth2 login working and advertised along with Persona on the login page. I have removed Yahoo from the login page because we don't yet have DMARC mitigations and I don't want to encourage Yahoo addresses. Twitter OAuth2 almost works, but it doesn't return email address. Rumor has it you can't get email from Twitter, so it can't work. Things that need to be fixed soon in core are confirmation required for email unsubscribe <https://gitlab.com/mailman/mailman/issues/213> and DMARC mitigations, but I think we can open it up and announce it. If no one objects, I'll do that tomorrow. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

9 years, 3 months

[MM3-users] Re: easy way to delete old mails in hyperkitty?

by Mark Sapiro

On 4/8/19 1:38 AM, l.schimmer(a)cgv.tugraz.at wrote: > Hi! > > is thjere a easy way to delete old mails in hyperkitty? > > e.g. with a list and checkmarks, or via a cli command? > > We got several mailinglists and we did import them from mailman2.x into mailman 3.2. Now it is time to remove old posts before 2016. But I do not see a easy way to remove old posts in one go, just the "remove thread" button in each mail view. I don't think it would be difficult to create a cli command to do this, but nothing currently exists. You could create an issue for this at <https://gitlab.com/mailman/hyperkitty/issues> -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

6 years, 2 months

[MM3-users] Re: Importing config and archives only partially succeeded?

by Mark Sapiro

On 12/12/20 2:33 PM, Eric Broens via Mailman-users wrote: > Today I have migrated about 30 mailinglists from mailman 2.1 to mailman 3.3.2 & Hyperkitty 1.3.3. > Although no error responses were given when importing the 2.1 pck files, and neither for importing the archives, for about half of the mailinglists the hyperkitty webpage doesn't show any subscribers, nor archived emails. > The imported members and other settings are correctly shown in the postorius page. > Is there anything that I can verify why the archive is not shown on the hyperkitty page?The hyperkitty_email database table does contain the emails. Did you specify --no-sync-mailman when you ran hyperkitty_import? If so did you run the django sync_mailman job when you finished importing? -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

4 years, 6 months

[MM3-users] Re: How to modify system preferences

by Mark Sapiro

On 2/19/21 5:15 AM, Jack Lenox via Mailman-users wrote: > > The documentation states that these are only accessible in a read-only > format via the REST API, but presumably there is a way of modifying > these somewhere? I can't find a way of specifying this in my config and > can't find a relevant example in the sample schema.cfg. > > At this stage, all I want to do is set the default for > "receive_own_postings" to False. Can anyone point me in the right > direction here? The defaults for settings like this are not directly configurable. You need to patch the relevant entry in mailman/core/constants.py I have just filed <https://gitlab.com/mailman/mailman/-/issues/832> for this. -- 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: 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

3 years, 6 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

3 years, 5 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

3 years

[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

7 months, 1 week

[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

6 years, 10 months

Search results for query "sapiro"