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

[MM3-users] Re: mailman break DKIM signature by modifying body

by Mark Sapiro

On 6/5/23 07:06, Peter Münster wrote: > Hi, > > I'm using mailman 3.3.8. > > Some messages with attachments from Google users get rejected by spam > filters because of invalid DKIM signatures. > > It seems, that mailman alters some lines in the body. Here an example: > > Original message: > > --8<---------------cut here---------------start------------->8--- > Lines: 2031 > > --000000000000f846c505fc494b7a-- > --000000000000f846c705fc494b7c > Content-Type: application/pdf; > [...] > Content-Disposition: attachment; > [...] > --8<---------------cut here---------------end--------------->8--- > > Altered message: > > --8<---------------cut here---------------start------------->8--- > Lines: 2032 > > --000000000000f846c505fc494b7a-- > > --000000000000f846c705fc494b7c > Content-Type: application/pdf; > [...] > Content-Disposition: attachment; > [...] > --8<---------------cut here---------------end--------------->8--- > > An empty line is added, and the spaces after the semicolons are removed. > > Perhaps related to https://gitlab.com/mailman/mailman/-/issues/1079. > > What could I do please, to prevent such modifications of the body? Changes like those above are due to Python's stdlib email module. Short of actually modifying the email module, there's nothing you can do to prevent them. Instead, you should be DKIM signing your outgoing mail and perhaps applying Mailman's DMARC mitigations if DMARC is an issue. If you are DKIM signing your outgoing mail and mail is being rejected because of prior invalid signatures, you can remove those by adding `remove_dkim_headers: yes` to the [mta] section of mailman.cfg. Also, ARC signing <https://docs.mailman3.org/projects/mailman/en/latest/src/mailman/handlers/d…> may help. -- 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: Using external services for deliverability?

by Mark Sapiro

On 7/4/20 9:03 AM, tom(a)gather.coop wrote: > > So I hope there is not an expectation that the rDNS domain match the email sender domain. If so I'm toast. Is it just sort of a smell test to see if the server looks legitimate? Probably part of your confusion is the ambiguity of the term `sender` which can refer to any of: - the actual individual sending the original mail (the From: header) - the envelope sender (the listname-bounces@listdomain address in the case of list mail) - the sending server. In the case of FCrDNS we're talking about the server (MTA) delivering the message to the recipient MX. I.e., that server's IP should have a PTR to its name and its name should have a A (or AAAA in the case of IPv6) record with the same IP. That's what FCrDNS implies. Quoting from <https://en.wikipedia.org/wiki/Forward-confirmed_reverse_DNS>: "... the requirement is the forward and reverse lookup for the sending relay have to match, it does not have to be related to the from-field or sending domain of messages it relays." It is also good if the name by which the MTA identifies itself (the myhostname setting in Postfix) is the same as the server's name. Quoting from the same article: "Some e-mail mail transfer agents will perform FCrDNS verification on the domain name given on the SMTP HELO and EHLO commands. This can violate RFC 2821 and so e-mail is usually not rejected by default." -- 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: hyperkitty.lib.utils Failed to update the fulltext index

by Mark Sapiro

On 4/17/19 8:10 AM, Abhilash Raj wrote: > On Wed, Apr 17, 2019, at 8:06 AM, Ben Harris wrote: >> April 17, 2019 11:03 AM, "Abhilash Raj" <maxking(a)asynchronous.in> wrote: >>> >>> Which version of Hyperkitty are you using? >>> >>> Did you upgrade the version of Hyperkitty when you migrated to the >>> new host? >> >> I'm using the mailman3-full package in ubuntu (i'm aware it's behind a couple >> releases), so it's hyperkitty 1.1.4. >> >> I didn't upgrade anything with the move. > > I am not sure where does Debian packaged version store it's fulltext index, but > I am assuming the move somehow makes Hyperkitty not be able to read the > index. I think this is a known incompatibility between the Python 2.7 and Python 3 versions of Whoosh. From the tracebacks, the current HyperKitty is running under Python 2.7. If the prior server was running HyperKitty with Python 3, that would explain this. > Can you try removing and re-building the entire index? I don't know again > the right command for Django there, but the hyperkitty command you want > to run is called `rebuild_index`. For source package, something like: > > $ python manage.py rebuild_index > > Do note that this will take a lot of time if you have a big archive. If this is the incompatibility, rebuilding the index will fix it. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

6 years, 4 months

[MM3-users] Re: How to remove global ban using API?

by Mark Sapiro

On 5/15/19 9:46 AM, Nathan Dixon wrote: > > I can create the ban fine by the following: > > from mailmanclient import Client > client = Client(URI,apiuser,apipass) > client.bans.add("^(?!.*[(a)\.](validdomain1\.com|validdomain2\.org|validdomain3\.co\.uk)") This is apparently a typo - missing ')' - in the re as you have it correct below. > However, I cannot seem to be able to remove it using the api: >>>> client.bans[0].delete() ... >>>> client.bans.remove(str(client.bans[0])) ... >>>> > client.bans.remove("^(?!.*[(a)\.](validdomain1\.com|validdomain2\.org|validdomain3\.co\.uk))") All of the above work for me with both API 3.0 and 3.1 in a non-docker install of the current GitLab HEADs > And also, when I now try and go into the mailman-core docker image to use > the mailman.interfaces.bans, it will not let me see the global bans: > >>>> from mailman.interfaces.bans import IBanManager >>>> global_bans = IBanManager(None) > Traceback (most recent call last): > File "<stdin>", line 1, in <module> > TypeError: ('Could not adapt', None, <InterfaceClass > mailman.interfaces.bans.IBanManager>) I don't see this either. > I have opened an issue in Gitlab for this as I feel it may be a bug related > to regex and global bans (there was a similar one for list banned > addresses): https://gitlab.com/mailman/mailman/issues/598 I also commented on the GitLab issue. I think this must be an issue with the docker images. -- 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: Migrating mailman3 to latest ubuntu lts

by Mark Sapiro

On 12/18/23 6:24 AM, Helio Loureiro wrote: > Hi, > > Indeed it was the configuration. It was placed into > /etc/mailman3/mailman-web.py. After a I changed to > /etc/mailman3/settings.py a few things advanced a little bit more. > > I had to figure out how to fix mysqlclient installation since there isn't a > mention about it and the simple "pip install mysqclient" was breaking with > pkg-config issues. But it did work at the end. > > Now I can see further messages on mailman3-web than before. > > (venv) mailman@new-server ~ (v3.3.9)> mailman-web migrate > System check identified some issues: > > WARNINGS: > account.EmailAddress: (models.W036) MariaDB does not support unique > constraints with conditions. > HINT: A constraint won't be created. Silence this warning if you don't care > about it. > account.EmailAddress: (models.W043) MariaDB does not support indexes on > expressions. > HINT: An index won't be created. Silence this warning if you don't care > about it. > Operations to perform: > Apply all migrations: account, admin, auth, contenttypes, > django_mailman3, django_q, hyperkitty, postorius, sessions, sites, > socialaccount > Running migrations: > Applying account.0004_alter_emailaddress_drop_unique_email...Traceback > (most recent call last): I'm not sure why there would be an issue with this migration, but there is a possible compatibility issue depending on how you installed things. django-mailman3<=1.3.11 is not compatible with django-allauth>=0.58. In your venv, try ``` pip install django-allauth\<0.58 ``` -- 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

[MM3-users] Re: Held messages not delivered after approval

by Mark Sapiro

On 8/2/25 01:51, Stephen J. Turnbull wrote: > > IIRC all of the shunted messages that Stephen looked at with qfiles > were those special digest messages (ie, message component empty, > pointer to lists/$LIST/something.mmdf in the msg_data component). So > something is going wrong in the to-digest handler. And for every one of those shunted messages there should be an exception with traceback logged in mailman.log. Those tracebacks should be helpful. > The number of .tmp files lying around bothers me. AFA grep CS, the > only place that can happen is in switchboard.py:136 in .enqueue: > > with open(tmpfile, 'wb') as fp: > fp.write(msgsave) > pickle.dump(data, fp, protocol) > fp.flush() > os.fsync(fp.fileno()) > os.rename(tmpfile, filename) > > where `msgsave` is already a pickled object. So either pickle.dump is > choking on something in data (the metadata, which I believe is all > primitive Python data types), or something (OOM kill?) is happening at > the OS level. A crash in pickle.dump should leave an exception log > and backtrace in the logs. > > AFAIK, Mailman does not clean up .tmp files at startup, right? That is correct. The *.pck.tmp file is created by the above code and immediately after writing is renamed to *.pck. It is done this way to prevent another process picking up a partially written *.pck. If a *.pck.tmp file is somehow left behind, it is never looked at or deleted by any Mailman code. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

1 month, 1 week

[MM3-users] Re: Hyperkitty - Non-ascii sender address

by Mark Sapiro

On 10/28/18 12:03 PM, Guiseppin Thomas wrote: > Hi, > > I imported some mbox archives in Hyperkitty. > > I have lot issues like: > > /\Failed adding message <5b0900ab.1c69fb81.70ab.2f87(a)mx.google.com>: > ('Non-ascii sender address', <email.message.EmailMessage object at > 0x7f05f1606048>)// > //Non-ascii sender address from "Stéphane blipblop <stlablipblop at > gmail.com>" about [HATLAB][It] Re: A débarrasser ! / > > It's probably because "Stéphane". The 'Non-ascii sender address' message comes from > try: > from_str = header_to_unicode(message['From']) > from_name, from_email = parseaddr(from_str) > from_name = from_name.strip() > sender_address = from_email.encode('ascii').decode("ascii").strip() > except (UnicodeDecodeError, UnicodeEncodeError): > raise ValueError("Non-ascii sender address", message) Possibly the exception is thrown in parseaddr(), but much more likely, the email address, not the display name contains non-ascii. > Some advise to fix it ? All the other messages should have been imported. If you can find and fix the 'bad' ones in the mbox, you can make a new mbox with just those and import that. You could also import the entire mbox with fixed messages. The already added ones won't be re-imported because of duplicate Message-ID:, but it's extra processing. If the actual bad message From: header is From: Stéphane blipblop <stlablipblop(a)gmail.com> or From: Stéphane blipblop <stlablipblop at gmail.com> That shouldn't cause the error, so I'g guessing that 'blipblop' is not the actual value and the actual value in <stlablipblop at gmail.com> has non-ascii. -- 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

[MM3-users] Re: Changing Mailman's "from" domain

by Mark Sapiro

On 5/16/19 8:21 AM, Roger Hislop (IS) wrote: > > If I subscribed an address, no confirmation email would come through. Checked the Postfix log and see this: > > May 16 14:34:50 ip-172-31-23-250 postfix/smtp[5025]: 15B87A35FB: to=<iotic-za(a)reasondigital.co.za>, relay=email-smtp.eu-west-1.amazonaws.com[52.51.155.83]:587, delay=0.22, delays=0.01/0.02/0.1/0.1, dsn=5.0.0, status=bounced (host email-smtp.eu-west-1.amazonaws.com[52.51.155.83] said: 554 Message rejected: Email address is not verified. The following identities failed the check in region EU-WEST-1: test-list-request(a)iotcouncil.org.za, test-list-bounces(a)iotcouncil.org.za (in reply to end of DATA command)) > > I've verified the domain listman.iotcouncil.org.za, so it would seem the obvious solution is to change the domain the mails come from. > > It appeared that I just change the postfix config to specify domain list so: Those addresses are the From: address (test-list-request(a)iotcouncil.org.za) and the envelope sender (test-list-bounces(a)iotcouncil.org.za) These are set by Mailman in the message and the SMTP transaction. Postfix doesn't normally rewrite them. The domain in these addresses is 'web host' defined in Mailman's domain record associated with the list which is also the domain in the list's posting address If you want Postfix to rewrite the envelope sender domain, see <http://www.postfix.org/ADDRESS_REWRITING_README.html#generic> > I see that messages TO the mailman server are also not being delivered ("-- 5.1.1 Requested action not taken: mailbox unavailable"). So there's another problem. See <https://mailman.readthedocs.io/en/latest/src/mailman/docs/mta.html#postfix> -- 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: Upgrade Mailmam Core from

by Mark Sapiro

On 9/24/22 10:57, sascha.rissel(a)gmail.com wrote: > Hello, > > I have newly set up Mailman 3 on Ubuntu 20.04. > Sending and receiving mails between list members does work, but I am currently experiencing two issues: > 1) a lists non-members who send mails to the list don't get notified about the message being held for moderation. Moderation itself doesn't seem to work. The moderation list is always empty. > 2) Archiving is activated within list settings, but there isn't any archive created. > > I found this thread, where the first of these issues is also described: > https://lists.mailman3.org/archives/list/mailman-users@mailman3.org/thread/… > > Here there is an incompatibility between Mailmain 3 and Python depicted, which also seems to affect me. > I am running Mailman 3.2.2 on Python 3 .8.10. This is only one of the issues with the Debian/Ubuntu packages. > So I need to either upgrade Mailman Core or downgrade Python. > I already did >> apt-get upgrade >> apt-get update > Unfortunately this didn't upgrade Mailman Core's version. > > Which steps do I have to undertake to upgrade Mailman Core? I suggest first removing the Debian/Ubuntu packages and installing the PyPI packages following docs at https://docs.mailman3.org/en/latest/install/virtualenv.html. There are also other takes on this at https://wiki.list.org/x/17891998; https://wiki.list.org/x/17892066 and https://docs.google.com/document/d/1xIcSsoNFp2nHi7r4eQys00s9a0k2sHhu1V5Plan… This will require some effort, but you will be freed from dependence on out of date packages. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

2 years, 11 months

[MM3-users] Re: digests are created but not sent out

by Mark Sapiro

On 1/9/19 12:20 PM, "Jörg M. Schulz" wrote: > when I use the lines below, the templates are looked for in //var. > When I comment them out, the location is correct: /var/lib/mailman3/ (debian buster standard) . The user list has full access. The folder is empty. //var refers to the directory defined in mailman.cfg (or the default in mailman/config/schema.cfg) as [paths.master] var_dir: Exactly which of the following lines did you add and then comment out? Just the three lines > [language.en] > charset: utf-8 > enabled: yes or something more? > mailman.cfg: > > [mailman] > # This address is the "site owner" address. Certain messages which must be > # delivered to a human, but which can't be delivered to a list owner (e.g. a > # bounce from a list owner), will be sent to this address. It should point to > # a human. > site_owner: help(a)elternserver.de > > # This is the local-part of an email address used in the From field whenever a > # message comes from some entity to which there is no natural reply recipient. > # Mailman will append '@' and the host name of the list involved. This > # address must not bounce and it must not point to a Mailman process. > noreply_address: noreply > > # The default language for this server. > default_language: en > [language.en] > charset: utf-8 > enabled: yes > > [language.de] > description: German > charset: iso-8859-1 > enabled: yes -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

6 years, 8 months

Search results for query "sapiro"