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

[MM3-users] Re: Change 'from' server for outgoing messages

by Mark Sapiro

On 3/11/23 16:44, Benjamin Goldberg wrote: > > BTW the errors that I had been getting were, at first: > response exception: (450, b'The from.email must be verified. The from.email must be verified.') > but later changed to: > response exception: (450, b'Sorry, please try again. 429 Too many requests.') > > I had assumed both errors were being generated by MailerSend but now I'm not sure Yes, they are from your smtp_host which was mailersend Both those are retryable and will be retried by Mailman to a point. I suggest if you want to use mailersend that in Postorius DMARC Mitigations you set DMARC mitigation action to Replace From: with list address and DMARC Mitigate unconditionally to yes. That will ensure all posts are From: the list address and will probably avoid the 'The from.email must be verified. The from.email must be verified.' error. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

2 years, 3 months

[MM3-users] Re: How to process emails with Mailman3?

by Mark Sapiro

On 3/10/25 12:24 AM, Kyle Lahnakoski wrote: > > When I add a user (like myself) I get a welcome email from all- > request(a)mymaillist.org. When I respond, the mail arrives in the S3 > bucket, but I do not know how to give it to mailman3. The "inject" > command will not work because there is no "all-request" mailing list. > > > How do I feed these administrative mails to mailman3? You can use `inject` with something like ``` /opt/mailman/venv/bin/mailman inject -f <somefile> -q command all(a)mymaillist.org ``` but > I have tried netcat the email to the ?LMTP? port, but it fails: this is the better way. The issue is you are not using `nc` correctly. When you do $ nc localhost 8024 < /tmp/pbTw1oqmV1rZtHXV707Jcov264hr you are telling nc to take commands from the file /tmp/pbTw1oqmV1rZtHXV707Jcov264hr. You need to give it a command to send the file. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

3 months, 3 weeks

[MM3-users] Re: How to Increase outgoing mail volume for Mailman 3

by Mark Sapiro

On 11/10/20 12:30 PM, Brian Carpenter wrote: > Hello everyone, > > We had a new client come on board that brought a list that had the > largest out-going mail volume that I have ever dealt with. So I did what > any sane server administrator would do that is running Mailman 3: I ran > to Mark Sapiro for help! Here is what the Sage of all things Mailman > counseled me to do: Thank you <blush> > 1. Disabled VERP delivery. VERP can help improve mail delivery by > delivering 1 message per SMTP transaction (I think I got that right). > Using VERP is counter-productive as it can seriously delay outgoing mail > delivery for a high-volume list. So you can use something like the > following in the MTA section of your mailman.cfg: Actually, I mentioned VERP, but I don't think I recommended disabling it. Also note that these settings: > [mta] > verp_confirmations: no > verp_personalized_deliveries: no > verp_delivery_interval: 0 are the defaults. Further, verp_confirmations is a holdover from MM 2.1 and has no effect, although prior to Mailman 3.3.2 confirmations were sent with `confirm <token>` as the Subject: and beginning with Mailman 3.3.2, confirmations are sent with `Your confirmation is needed ...` as the Subject:. Actually, I think enabling VERP with [mta] verp_delivery_interval: 1 is generally a good idea for more reliable bounce detection. > 2. I configured Mailman 3 to run 4 outgoing runners. The default is 1. > This action was the game changer. It allows Mailman to handle 4 incoming > messages at a time instead of 1. My client's incoming list volume was > high enough where it was overwhelming the single outgoing runner. Here > is what I added to the mailman.cfg file: > > [runner.out] > instances: 4 > > Doing this step immediately solved the backlog in var/queue/out. -- 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: DMARC Munging

by Mark Sapiro

On 1/26/20 4:43 PM, Allan Hansen wrote: > All, > > The munged From: header in MM3 still says > 'name' via ‘listname’ <‘listaddress’> > > This caused me and my subscribers a lot of grief in MM2: > Some mail clients use the first part up to the From for future key-ahead for new email to ’name’, hiding the address, so what they think is a personal message for ’name’, instead goes to the entire list. Red faces all around. > > Stephen Thurnbull earlier suggested further munging by replacing the list address in the From: header like this: > > 'name' via ‘listname’ <‘whoopsieaddress’> > > Which will return an automated reply explaining the issue. I like this option. How can I get that in? You can file an issue at <https://gitlab.com/mailman/mailman/issues>. That will at least get it on the table, but there are no guarantees as to if/when it would be implemented. -- 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: Apple Mail encoding again

by Mark Sapiro

On 4/21/22 04:53, tlhackque via Mailman-users wrote: > > Note that MailMan is encapsulating a multipart/signed message in a > multipart/mixed in order to append it's footer, and reports that it > removed the signature part of the multipart/signed. This makes the > signed message format invalid. So at least, MM3 needs to handle signed > messages better: either include the signature or remove the signature > headers (an unwrapping exercise to convert the message to unsigned)... > Note that this can be recursive where a signed message contains a > message/rfc822 part that contains a signed message, that.... This was an issue with Mailman's content filtering for the mailmanusers(a)mailman3.org list. Pass types was: multipart message/rfc822 text application/pgp-signature So the application/x-pkcs7-signature part was removed. I have just updated Pass types to: multipart message/rfc822 text application/pgp-signature application/x-pkcs7-signature to not remove application/x-pkcs7-signature parts going forward. -- 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: Recently active discussions - Hyperkitty

by Mark Sapiro

On 6/3/24 8:55 AM, Sam Darwin wrote: > > Try this: > > systemctl reload mailman3-web > or > systemctl restart mailman3-web > > The "Recently Active Discussions" listing is refreshed! That fixes it. > > --- > > Related issue, #2 > > On the "Recently Active Discussions" page, click on a message, a test message, and then "Delete this thread". It's deleted. > > Now "Recently Active Discussions" hangs. A spinning icon, indefinitely. In the logs file: "hyperkitty.models.thread.Thread.DoesNotExist: Thread matching query does not exist." > Re-running recent_threads_cache, and restarting Django, fixes it. However in production you wouldn't want to wait 24 hrs, and also manually restart the web. As you say, these issues may be related. The latter is already reported at https://gitlab.com/mailman/hyperkitty/-/issues/504 and as it says there, I am unable to duplicate it; it may be related to which database manager you use. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

1 year

[MM3-users] Re: when on particular person sends a message to the list dozens of OTHER users have their bounce score incremented

by Mark Sapiro

On 8/30/24 14:34, Ken Alker wrote: > I just found and then changed the "Settings/Alter Messages/Replay goes > to list" from "No Munging" to "Reply goes to list" to combat the reply > issue I mentioned above. I suppose this means that if someone sent a > specific Reply-to: in their original email, it gets overwritten. I > suppose there is no perfect solution. If `Reply goes to list` is set to `Reply goes to list`, the list posting address is added to the Reply-To: header. I.e., if there is a Reply-To: in the incoming message, The resultant Reply-To: contains the original plus the list posting address unless `First strip Reply-To` is `Yes` in which case it contains only the list posting address. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

9 months, 3 weeks

[MM3-users] Re: MM2 to MM3 Archives Loading

by Mark Sapiro

On 12/4/24 12:45, Joshua Bushe wrote: > > This link is an example you sent earlier: > https://lists.mailman3.org/archives/list/mailman-users@mailman3.org/ > > This link is above is the page where i can't see any of my lists outputs on my mailman3 gui. All i visually see is three loading icons spinning. Also, mark said it will only show threads with post in the last 30 days. so i made a test list and made a new thread and still the problem persists. Still see the three loading icons spinning. I've manually added the test list and also did it through the gui. Same outcome. We've seen issues like this before? Are you running the django cron tasks <https://docs.mailman3.org/en/latest/install/virtualenv.html#cron-jobs-for-m…>. Sometimes the `daily` jobs fix this. Also if you haven't done so, restarting the WSGI server (uWSGI, gunicorn, Apache mod_wsgi) may help. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

6 months, 3 weeks

[MM3-users] Re: Problem with perms on /etc/mailman3/mailman.cfg while following https://docs.list.org/en/latest/install/virtualenv.html on new mailman3 Debian 12 installation

by Mark Sapiro

On March 25, 2025 1:20:22 AM GMT+07:00, Philip Bondi <pjbondi(a)systemdatabase.com> wrote: > >The instructions https://docs.list.org/en/latest/install/virtualenv.html#installing-mailman-… do not say what to do with existing file. > >root@shackleton12:~# ls -alF /etc/mailman3/mailman.cfg >-rw-r--r-- 1 root list 11119 Mar 20 11:45 /etc/mailman3/mailman.cfg > >Should we move the /etc/mailman3/mailman.cfg out of the way and create new file as user and group mailman:mailman ? How did that file get there? It looks like at some point you installed the Debian package. If you are following <https://docs.list.org/en/latest/install/virtualenv.html you shouldn't install the Debian package. In any case, just remove the file. Probably it's best to remove the Debian package completely and start over. -- Mark Sapiro <mark(a)msapiro.net> Sent from my Not_an_iThing with standards compliant, open source software.

3 months, 1 week

[MM3-users] Re: content filtering in version 3.1

by Mark Sapiro

On 5/11/21 8:45 PM, Simon Handfield via Mailman-users wrote: > Hi everyone, > > I'm sorry to resurrect this thread from so long ago but it appeared to provide exactly the answer I was looking for, trying to manage pass_types in 3.1.1 on Ubuntu 18.04. > > GNU Mailman 3.1.1 (Between The Wheels) > > Unfortunately when I run: > > ./bin/mailman shell -l [list address] > > I receive: > > usage: mailman [-h] [-v] [-C CONFIG] > {help,aliases,conf,create,digests,import21,info,inject,lists,members,qfile,remove,reopen,restart,shell,start,status,stop,unshunt,version,withlist} > ... > mailman: error: unrecognized arguments: -l > > Can anyone advise how I can use the -l switch to manage this setting for a list? Older versions of Mailman core did not support the -l/--listspec option for mailman shell. They expected the listname as an argument as in ``` mailman shell list(a)example.com ``` What does ``` mailman shell --help ``` show in your case? -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

4 years, 1 month

Search results for query "sapiro"