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

[MM3-users] Re: Gmail/Fetchmail in Mailman3?

by Mark Sapiro

On 06/23/2018 02:48 PM, Bill Christensen wrote: > > Our Mailman2 setup uses Fetchmail to retrieve list mail from our > accounts on Gmail. > > Is there a similar setup for Mailman3? Delivery to Mailman is different in Mailman 3. What are you currently doing with Fetchmail? If you are doing something like getting the mail from google and delivering it via SMTP to an MTA on the Mailman server, that should still work for MM 3. If Fetchmail is piping it to a command like "| /path/to/mail/mailman post listname" that won't work in Mailman 3. Mailman 3 gets mail via its own LMTP server (which it calls a runner). Mail is normally delivered to an MTA which is configured to relay the mail via LMTP to the localhost port that Mailman is listening on. So Fetchmail can eithr deliver to the MTA and let the MTA relay to Mailman or deliver directly to Mailman's LMTP port. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

7 years, 10 months

[MM3-users] Re: Office365 posts shunted (authres.core.SyntaxError)

by Mark Sapiro

On 9/17/20 2:41 PM, brylon(a)oit.rutgers.edu wrote: > > [1] I currently applied this hack to get around the syntax error... > > $ diff -u venv/lib/python3.6/site-packages/mailman/handlers/validate_authenticity.py.ORIG venv/lib/python3.6/site-packages/mailman/handlers/validate_authenticity.py > --- venv/lib/python3.6/site-packages/mailman/handlers/validate_authenticity.py.ORIG 2020-09-16 14:23:03.565482574 -0400 > +++ venv/lib/python3.6/site-packages/mailman/handlers/validate_authenticity.py 2020-09-17 13:17:09.296409626 -0400 > @@ -70,10 +70,12 @@ > > if config.arc.trusted_authserv_ids and (AUTH_RESULT_HEADER in msg): > header = '{}: {}'.format(AUTH_RESULT_HEADER, msg[AUTH_RESULT_HEADER]) > - authserv_id = AuthenticationResultsHeader.parse(header).authserv_id > - if authserv_id in config.arc.trusted_authserv_ids: > - return header > - > + try: > + authserv_id = AuthenticationResultsHeader.parse(header).authserv_id > + if authserv_id in config.arc.trusted_authserv_ids: > + return header > + except: > + log.exception('AR header failed to parse for message: %s', msg['Message-ID']) > > @retry(Timeout, NUM_TIMEOUT_RETRIES) > def authenticate(msg, msgdata): I think that's fine. Also, you should look at <https://gitlab.com/mailman/mailman/-/issues/765>. -- 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: spanish localization

by Mark Sapiro

On 2/14/21 3:21 AM, Guillermo Hernandez (Oldno7) via Mailman-users wrote: > > I did some exploration this morning (Spain time) in the weblate > statistics and archives and I found that the changes done from > Victoriano and me were recorded. I did a screencopy of all that if > someone has any doubt about it. I downloaded this files: > > -rw-r--r-- 1 1002 wheel 11037 Feb 14 10:57 gnu-mailman-django-mailman3-es.po > -rw-r--r-- 1 1002 wheel 34511 Feb 14 10:54 gnu-mailman-hyperkitty-es.po > -rw-r--r-- 1 1002 wheel 143758 Feb 14 10:51 gnu-mailman-mailman-es.po > -rw-r--r-- 1 1002 wheel 104997 Feb 14 10:49 gnu-mailman-postorius-es.po > > The thing is that they differ from the .po installed via pip upgrade. > Mostly, as said, postorius, hyperkitty and django_mailman3. The latest packages in PyPI (pip) were released on Feb 2 except for django-mailman3 which was released on Jan 15. They don't include updates after those dates. -- 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: 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

3 years, 1 month

[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

1 year, 1 month

[MM3-users] Re: Change Member's Address

by Mark Sapiro

On 1/14/26 10:28 AM, Dennis Putnam via Mailman-users wrote: > > The table account_emailaddress has 3 entries: > > mysql> select * from account_emailaddress; > +----+-----------------------+----------+---------+---------+ > | id | email | verified | primary | user_id | > +----+-----------------------+----------+---------+---------+ > | 1 | uuuu(a)ddddddddd.net | 1 | 1 | 2 | > | 2 | uuuu(a)ddddddddd.net | 0 | 0 | 3 | > | 3 | xxxxxxxx(a)gmail.com | 1 | 1 | 4 | > +----+-----------------------+----------+---------+---------+ > 3 rows in set (0.00 sec) > > Yes, id 1 and 2 are the same email address. As a superuser, go to https://whatever/admin/account/emailaddress/ and find the uuuu(a)ddddddddd.net address that is not primary and get its user name. Then go to https://whatever/django/auth/user/ and delete that user. I thing this will delete the associated address, but go back to the addresses and if it's still there, delete it. You might instead try DELETE FROM account_emailaddress WHERE id = 2; DELETE FROM auth_user WHERE id = 3; But those may fail due to foreign key constraints. -- 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: 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

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

4 years

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

[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

1 year, 7 months

Search results for query "sapiro"