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

[MM3-users] Re: Migrating from SQLite to PostgreSQL

by Mark Sapiro

On 07/17/2018 07:27 PM, Joe Steeve wrote: > > I have an installation on SQLite. I want to migrate it to PostgreSQL. Is that > feasible? Any gotchas I need to watch for? It is feasible. You would need to stop Mailman core and all Django processes including cron jobs and WSGI processes to ensure nothing is accessing the SQLite database, update the database section in mailman.cfg and the DATABASES settings in your Django settings, use SQLite tools to dump the relevant database(s) and PostgreSQL tools to create and load them, and finally restart Mailman core and all Django processes. -- 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: mailman3 does not send to the members of the lists

by Mark Sapiro

On 7/12/20 2:41 PM, maszap(a)tin.it wrote: > I can create a list, add members to the list, but when I create a new thread, I only get it on the email from the same domain as the list. While all the other members of the list, they do not receive the thread. > I tried to check the logs, but I don't see anything significant. > What can I check? This is most likely because the outgoing MTA can't deliver/relay to external domains. Check the MTA configuration and logs. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

6 years, 1 month

[MM3-users] Re: ModuleNotFoundError: No module named 'mailman_web'

by Mark Sapiro

On 11/10/23 09:02, gordon(a)dickens.com wrote: > > So, I put Mark's suggested contents in /opt/mailman/venv/bin/mailman and then executed the command: > > /opt/mailman/venv/bin/mailman -C /etc/mailman3/mailman.cfg > > which resulted in the following error message: > >> Traceback (most recent call last): >> File "/opt/mailman/venv/bin/mailman", line 5, in <module> >> from mailman.bin.mailman import main >> ModuleNotFoundError: No module named 'mailman' > > Any more ideas? Your mailman in your venv is broken. With your venv active try ``` pip install --force-reinstall mailman ``` -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

2 years, 9 months

[MM3-users] Re: All messages to a new list/domain shunted from "in" queue with no logged exceptions

by Mark Sapiro

On 11/25/23 7:53 AM, Jered Floyd wrote: > > File "/opt/app-root/src/.local/lib/python3.9/site-packages/mailman/rules/dmarc.py", line 284, in maybe_mitigate > for address in mlist.dmarc_addresses: > TypeError: 'NoneType' object is not iterable > Nov 25 15:49:26 2023 (90) SHUNTING: 1700927366.81852+6d2f84a8eb97e64c3ee93662f1744a2a756c7ca9 > [...] This may be a bug. I need to investigate. Meanwhile, go to the list's settings in Postorius and under DMARC Mitigations, put something in DMARC Addresses, save it and then remove it and save again. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

2 years, 8 months

[MM3-users] Re: auto-away notices as bounces

by Mark Sapiro

On 8/29/21 10:19 PM, Andreas Barth wrote: > * Mark Sapiro (mark(a)msapiro.net) [210830 04:30]: > >> That said, bounce processing should treat even a VERPed message as >> unrecognized if it doesn't look like some kind of DSN. This may not >> be the case in MM 3. > > Thanks, that's what I also think. Looking at the returned mail, they > definitly don't look like DSNs / bounces to me. > > > Anything I should be doing re this topic? I've created https://gitlab.com/mailman/mailman/-/issues/939 for this. I think this patch will fix it. --- a/src/mailman/runners/bounce.py +++ b/src/mailman/runners/bounce.py @@ -51,13 +51,18 @@ class BounceRunner(Runner): addresses = StandardVERP().get_verp(mlist, msg) if len(addresses) > 0: # Scan the message to see if it contained permanent or temporary - # failures. We'll ignore temporary failures, but even if there - # are no permanent failures, we'll assume VERP bounces are - # permanent. + # failures. We'll ignore temporary failures, and if there + # are no permanent failures, we'll assume this is a vacation + # response or similar. temporary, permanent = all_failures(msg) if len(temporary) > 0: # This was a temporary failure, so just ignore it. return False + if len(permanent) == 0: + log.info('VERPed bounce message but not a recognized DSN: %s', + msg.get('message-id', 'n/a')) + maybe_forward(mlist, msg) + return False else: # See if this was a probe message. addresses = ProbeVERP().get_verp(mlist, msg) (Watch for wrapped lines) -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

4 years, 11 months

[MM3-users] Re: Subscription requires confirmation when list is set as Open

by Mark Sapiro

On 12/18/24 18:22, Joachim Schrod wrote: > Mark Sapiro writes: >> >> It is not the subscription that requires confirmation. It is the user's >> email address. Even though the list's subscribe policy is open, a >> previously unknown email address has to be confirmed. > > I assume that's the verification that one can turn off in Postorious > `Mass Suscription' with the checkbox "Pre Verified". That is correct. > I maintain a mailing list for a private holiday where people don't > subscribe themselves; I subscribe them. I have vetted their email > address beforehand. (The subscribers are mostly not able to handle a > verification email, nor any email-based workflow at all.) Is there a > configuration option for a mailing list that sets "Pre Verified" to > true as a default? This is https://gitlab.com/mailman/postorius/-/issues/563 it was fixed by https://gitlab.com/mailman/postorius/-/merge_requests/930 which was later extended by https://gitlab.com/mailman/postorius/-/merge_requests/945 however these are not available until Postorius 1.3.14 which is not yet released. These add a setting, POSTORIUS_DEFAULTS, which can be used to set these defaults. E.g., setting POSTORIUS_DEFAULTS = {'mass_subscription_pre_verify': True} will set the default for Pre Verified to True. So far, the only defaults that can be set in this manner are mass_subscription_pre_confirm, mass_subscription_pre_approve, mass_subscription_pre_verify and mass_subscription_invite and those not until Postorius 1.3.14, but more may be added. -- 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: mailman 3 adding extraneous /var/ to pid path?

by Mark Sapiro

On 09/21/2017 01:29 PM, Andrew Hodder wrote: > > I keep getting around this by creating symlinks to the pid file and then > the stop works, but it's getting silly. It seems like mailman just assumes > CWD + /var/ + master.pid must be the location. Once I realized this, I > found I can do "mailman stop" so long as I'm only in /opt/mailman/ (since > it'd then add /var/master.pid). But that seems a little nonsensical. That is the normal expected behavior if devmode is enabled. Check your configs for this. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

8 years, 10 months

[MM3-users] Re: Using external services for deliverability?

by Mark Sapiro

On 7/3/20 7:27 AM, Tom @ Gather wrote: > Thank you both for the help. I have SPF and reverse DNS setup. But I > thought DKIM is no help because Mailman rewrites the email headers? In most cases, Mailman will make transformations to the message which will break any incoming DKIM signature, but you still want to DKIM sign your outgoing mail with your own domain's DKIM signature. This will not in itself allow list messages to pass DMARC which is why Mailman has DMARC mitigations, but it will still provide a valid DKIM signature from you which will help with deliverability. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

6 years, 1 month

[MM3-users] Re: User display name entry field input ignored

by Mark Sapiro

On 6/26/22 08:03, Christian via Mailman-users wrote: > Whether I try and add users using mass subscribe, or individually, it seems > the display name field entry is ignored. The default is then "none" for the > user. Please advise. Thank you! If the address you are mass subscribing is already known to mailman, i.e., is an existing user, it is that user that will be subscribed with that user's display name, even if it is None. If that address is not an existing user, the user will be subscribed with the display name you provide. -- 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

[MM3-users] Re: Held message notifications ending up in junk

by Mark Sapiro

On 9/14/22 10:52, Tibor Molnar wrote: > Hi all, > > After I put in a DKIM record for the specific domain the sender now gets notification about held messages in inbox, however the admin or owner of the list is still receiving notifications to the junk folder. I have tried to put in DKIM record under the owners domain also but it did not changed anything. Would you have any other suggestions on this? Are the admin notices DKIM signed? If not, and if you are using opendkim see the MAILING LISTS section at http://www.opendkim.org/opendkim-README -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

3 years, 11 months

Search results for query "sapiro"