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

[MM3-users] Re: Also deleted website example.com

by Mark Sapiro

On 7/17/20 4:58 AM, w.schoener(a)alp.dillingen.de wrote: > Hi there, > i also deleted the website example.com, while I tried to configure my mailman 3 site. > Now I get a Server-error, when I try to open my mailman3 sites: "An error occurred while processing your request" > > I tried to fix this problem by changing the SITE_ID=2 in my settings_local.py. > But nothing helped, also the SITE_ID=0 did change nothing. You need to look at the django_site table in your database and find the actual `id` of the site you want. it may be a number > 2 even if there is only one site listed under `sites` in Django Admin. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

4 years, 10 months

[MM3-users] Re: User suspended after too much spam

by Mark Sapiro

On 3/6/22 05:55, Eggert Ehmke wrote: > I have set up spamassassin as spamfilter, and it works reasonable so far. Some > spam passes the filter and I try to use it for training. However, one of my > users has a very restrictive spam filter and rejects all spam. This causes > mailman to suspend that user. I have to enable the user each time. > > How can I change that behaviour? I do not want my users to be suspended. Set verp_probes: yes in the [mta] section of mailman.cfg. This situation is exactly what verp probes are designed for. See https://docs.mailman3.org/projects/mailman/en/latest/src/mailman/model/docs… -- 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: Hyperkitty

by Mark Sapiro

On 1/30/23 11:58, Onyeibo wrote: >> 2. Your MM3 log files - do they say anything? >> > Nothing! No new errors. It is very strange and frustrating Are there files in /opt/mailman/mm/var/archives/hyperkitty/spool/? Do messages received from the list have an Archived-At: header:? Do messages received from the list have a List-Archive: header:? If the first answer is yes, the mailman_hyperkitty archive_message method is failing. If the second answer is no, the mailman_hyperkitty permalink method is failing. If the second answer is no, the mailman_hyperkitty list_url method is failing. All of these failures log errors to the mailman.archiver log which by default is written to mailman.log. If by chance there is an Archived-At: header, what is it? -- 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: Help with mailman2 to mailman3 archive migration

by Mark Sapiro

On 4/2/24 01:49, francisco.lopezayuso(a)sib.swiss wrote: > Hello all, > > I'm having some issues with a migration I'm performing right now from our old mailman2 server to a mailman3 one. The mailing lists imports work fine, but the archives seems to work sometimes: This means that some lists archives appear but others are missing when browsing the archives in the web UI. This happens despite the command line telling me that the import went fine. Here are the steps I run for the archives: All of which look fine. Have you set ``` FILTER_VHOSTS = True ``` in your Django settings? If so, does setting it `False` make a difference? -- 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: Hyperkitty stuck files

by Mark Sapiro

On 7/9/24 7:05 AM, zoltan(a)circle-interactive.co.uk wrote: > > This is the error in archiver.log > > Jul 09 10:56:12 2024 (47531) HyperKitty archiver processing queued filebase: 1720522497.980487+a88492922feca24ced15594a5ec165561956f3ad > Jul 09 10:56:12 2024 (47531) hyperkitty archiver: sending message <B9E91239-ED71-4CC6-8FFF-3308C5C4DE2E(a)me.com> > Jul 09 10:56:12 2024 (47531) HyperKitty failure on http://127.0.0.1:8000/archives/api/mailman/archive: It looks like hyperkitty is throwing an uncaught exception in attempting to archive this message. Try moving 1720522497.980487+a88492922feca24ced15594a5ec165561956f3ad.pck out of the spool/ directory and see if it processes the rest of the messages there. You can examine that message with the `mailman qfile` command. There might also be a traceback in the Django logs that will say more about why HyperKitty is failing. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

10 months, 1 week

[MM3-users] Re: List invisible to moderator

by Mark Sapiro

On 6/16/20 3:43 AM, Olaf Zaplinski via Mailman-users wrote: > I just have promoted a member to a moderator. Now when he logs in to > Postorius, he gets the message "There are currently no mailing lists.". > > I have set "Show list on index page" to "no" before. But as a moderator, > the list should be shown, right? I mean, all lists are shown to the > administrator also. > > When I manually enter the complete URL, the moderator can see the list. > I think this is a bug. Moderators should see their lists. What do you > thing? What Postorius version is this? It works for me in Postorius 1.3.3. -- 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: User settings triggers error

by Mark Sapiro

On 6/28/20 5:20 PM, Mark Dadgar wrote: > > That gives a slightly different error: > > mark@mail:/usr/lib/python3/dist-packages/hyperkitty/models$ sudo patch < /tmp/patch.txt > patching file email.py > Hunk #1 FAILED at 24. > patch: **** malformed patch at line 23: I don't know about the failure. That probably is due to the version mismatch. The malformation is my fault. There should be an empty line following the last line. You didn't say what your HyperKitty version is, but here's a patch against 1.3.0. If this doesn't work, you could just try patching it by hand. I'm going fishing tomorrow so I won't be here much longer. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

4 years, 10 months

[MM3-users] Re: mass subscribers disablement!?

by Mark Sapiro

On 11/26/21 9:39 AM, Christian Stalberg via Mailman-users wrote: > After the first time where users were unsubscribed automatically, I added > back one at a time all the subscribers who were unsubscribed. Now they have > all been unsubscribed again automatically. They are valid working email > addresses. How can I stop this behavior from occurring please? Do you have the bounce processing notifications `Notify owner on disable` and `Notify owner on removal` set to `Yes`. If not, set them. Then, what's in the notices you receive? You might also consider setting `verp_probes: yes` in the `[mta]` section of mailman.cfg. This will avoid some issues with users being disabled/unsubscribed due to list posts being rejected as spam. -- 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: Mailman3 reinstall fail, need some help

by Mark Sapiro

On 3/12/22 08:38, Yvan ♞ wrote: > Yes it's debian and I have root access but it's a more "user friendly" > server release. > I tryed this but it block > https://github.com/YunoHost-Apps/mailman3_ynh/blob/master/README.md > > https://yunohost.org/en/administrate/whatisyunohost > Sincerely I don't read French very well, but your original logs at https://paste.yunohost.org/raw/xiqoyajegi and https://paste.yunohost.org/raw/hujesebita show installation failing because it fails to create /etc/mailman3/mailman.cfg. This is either an issue with the Debian package or the YunoHost installer or an incompatibility between them. I would go first to YunoHost for help and then to Debian if necessary. -- 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: How to use the "recipient_delimiter" postfix parameter with Mailman3?

by Mark Sapiro

On 4/12/22 08:54, Pierre Malard via Mailman-users wrote: > Ok, thanks for the documentation. > > But as Mailman uses this functionality for its own processing of emails, if I leave it to be used for another processing, Mailman will no longer work correctly... Please elaborate your concerns. I don't understand. > Ok, that means I'm going to forbid the use of the escape character when processing mailing lists. I don't know if I understand. If you are going to set Mailman's recipient_delimiter to `_`, that means you can't have `_` characters in list names. There should be no other limitations. -- 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

Search results for query "sapiro"