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

[MM3-users] Re: Archiver Hyperkitty Not Found

by Mark Sapiro

On 3/3/23 15:16, pat(a)suwalski.net wrote: > Hello, > > I upgraded from Debian 10 to 11 today, and hyperkitty archiver stopped working. > >>From the mailman.log: > > AssertionError: Archiver not found: hyperkitty > > I followed along on a related thread: https://lists.mailman3.org/archives/list/mailman-users@mailman3.org/thread/… > > I don't see any resolution to that thread. The only thing that worked for me was removing the hyperkitty rows from the listarchiver table in the database. But of course, now I don't have working archiving. There is a resolution of sorts there: It was setting ``` [archiver.hyperkitty] enable: no ``` in mailman.cfg, restarting Mailman core and then setting it back to `enable: yes`. > Any ideas? How would I make the archiver available? This django stuff is infuriatingly difficult compared to other frameworks. Do you have ``` [archiver.hyperkitty] class: mailman_hyperkitty.Archiver enable: yes configuration: /opt/mailman/mm/mailman-hyperkitty.cfg ``` in your mailman.cfg where `/opt/mailman/mm/mailman-hyperkitty.cfg` is the actual path to mailman-hyperkitty.cfg and do you have in that file ``` [general] base_url: http://example.com/hyperkitty/ api_key: key matching the MAILMAN_ARCHIVER_KEY set in Django's settings. ``` Actually, even if these latter settings were wrong, the error would be different. -- 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: Apache shows No Lists

by Mark Sapiro

On 5/22/23 12:57, ceo(a)sartrack.nz wrote: > Postorius is running. > I just removed all mailing lists, and created new empty ones. > These now show in the Apache2 website, via the link to Postorius I assume. > Then I imported members from the old mailing list "Templist" into the new one. > Now the "templist" is no longer visible on the website! Did you do this import with `mailman import21`? If so, did you run it as the Mailman user and not as root? > It is here: > https://sartrack.nz/mailman3/ > Note that the existing list "Templist" is missing. https://sartrack.nz/mailman3/ is missing CSS. Apache doesn't know how to access /static/ or you never built it with the django admin collectstatic command. > Now I need to login as 'superuser' or whatever it is called, so I can manage all the lists. > Where do I set up my login and password for access via the web browser? You create a superuser with the django admin createsuperuser command. How you invoke the django admin command depends on how you installed Mailman. Please tell us how you installed Mailman so we don't have to guess about this and other things. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

2 years, 1 month

[MM3-users] Re: bounce handling in mm3 available?

by Mark Sapiro

On 1/24/22 05:20, Stefan Bauer wrote: > Hi, > > what happens with bounce-mails that are processed by mailmans postfix > instance? What Mailman core version? Prior to 3.3.1, bounce events were recorded in the bounceevent table but not otherwise processed. Subsequent to that, they are scored if recognized and what notices are sent depends on list settings. > Jan 24 10:46:03 l01 postfix/lmtp[8432]: DF4AE600623: > to=<company-newsletter-bounces(a)lists.company.tld>, > relay=127.0.0.1[127.0.0.1]:8024, delay=0.03, delays=0.01/0.01/0/0.01, > dsn=2.0.0, status=sent (250 Ok) > > But the list-owner does not get any notification, nor do i see any > bounce-information in the pistorious-gui. What are you expecting to see in Postorius? All you can see is if a member's delivery status is Disabled by Bounces. Things like Bounce score are not available in Postorius. What notices are sent depends on the settings in the Bounce Processing section in Postorius. For example, if your message logged by postfix was spam to the <company-newsletter-bounces(a)lists.company.tld> address that is not recognized as a DSN and `Forward unrecognized bounces` is Discard, the message will be silently discarded. Also, if that message was a non-fatal, message-delayed type of DSN, it will be ignored. -- 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: If I manually add email addresses to a list and then delete them, how do i permanent delete them from Users?

by Mark Sapiro

On 4/25/23 3:02 AM, Andrew Hodgson wrote: > Mark London wrote: > >> I added some email addresses manually to a mailing list and then removed them. But now I can't find how to totally remove them from mailman3. They show up in the Users list. > > You may find this script useful: > https://www.msapiro.net/scripts/clean_users.py That script will only delete Django users and optionally the Mailman user corresponding to the deleted Django user. I think the OP wants to delete Mailman users that are not members of any lists even if there is no corresponding Django user. That script won't do that. Mailman Users can be deleted from the Postorius Users view, but it's a one at a time process, and there's no indication that the User has memberships unless you first go to `Manage` to check. I will modify the script to enable deleting Mailman users with no memberships even if they aren't Django users and post here when it's done. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

2 years, 2 months

[MM3-users] Re: List nonmembers

by Mark Sapiro

On 7/8/19 6:50 PM, Andrew Bernard wrote: > Under Users for a list, there is a category for List nonmembers. What does this term mean? [It's rather curious philosophically when you think about it, because I would have thought that the category [all humans - list members] fits that category term.] > > But seriously, I don't understand it. I have several email addresses there and I don't know what do with them, if anything. Non-members are email addresses that are not members but have some connection to a list. Mailman 2.1 lists have attributes named accept_these_nonmembers, hold_these_nonmembers, reject_these_nonmembers and discard_these_nonmembers. These are lists of non-member addresses and regexps matching addresses, and posts from a non-member address in one of the lists will be accepted, held, rejected or discarded respectively. Mailman 3 does this differently. An address can be a non-member and that non-member record has a moderation setting to determine how a post from that non-member is handled. An address can become a non-member by being imported from Mailman 2.1 or by posting to the list. If a non-member posts to the list, a non-member record is created regardless of the disposition of the post. See <https://mailman.readthedocs.io/en/latest/src/mailman/chains/docs/moderation…>. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

5 years, 11 months

[MM3-users] Re: Strange password problem

by Mark Sapiro

On 9/22/23 09:50, Eggert Ehmke via Mailman-users wrote: > > -I try to log in as admin > -rejected because of wrong password (password is stored in browser) > -used forgotten password function, using my email address > -reset password to the stored value from browser > -login works now. Works also when logged out/in again > -however, the next day this behaviour repeats. So apparently the issue is that although you reset your login password to a known value, it doesn't stick and reverts overnight to some other value. > Can we try to catch this bug now, which is most likely in my configuration? Which is: > > Debian 12.1 Bookworm > Mailman in venv running with dedicated mailman user Is this the Debian package or installed following https://docs.mailman3.org/en/latest/install/virtualenv.html or something else. All I can think of is some cron may be resetting the password. If that's it, it's probably a Debian thing. Can you see if there's any cron running the Django admin changepassword command? If you set the password with the Django admin changepassword command, does it stick? Can you create another superuser with the Django admin createsuperuser command and does that user's password stick? -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

1 year, 9 months

[MM3-users] Re: Solved Re: after last upgrade I've got a CSRF failed verification

by Mark Sapiro

On 10/27/22 03:04, Guillermo Hernandez (Oldno7) via Mailman-users wrote: > > Since I made all the mailman3 enviroment wide server open (not using > venv) I already executed the migration doing a > > su -m mailman3 -c "python3 manage.py collectstatic" > su -m mailman3 -c "python3 manage.py migrate" > > Being mailman3 the user who runs all of mailman3 related stuff > > I had problems doing the migrate part, showing an error of lacking > perms. I solved it running the migration under root (I know it could be > trouble after, but...) It would be much better to identify the problem files/directories and adjust their ownership. It is possible that running stuff as root in the past left things owned by root causing the issue. > > After that the compress part showed errors... but the postorius web > maintenance was working well except for the CSRF error verification. I > will trace the compress errors and will try to find the problem later. Do you have `COMPRESS_ENABLED = True` in your settings? If that's not the issue, it may be in the settings for COMPRESS_PRECOMPILERS -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

2 years, 7 months

[MM3-users] Re: Starting from scratch

by Mark Sapiro

On 04/09/2018 10:01 AM, Benjamin Ragheb wrote: > > The two alternatives I am weighing right now are: > > 1. Stay the course, and see if I can fix this by learning more about Python, Pip, Django and tinkering with the configuration. > > 2. Ride the bleeding edge, and install postorius and hyperkitty from git. (I'll probably stick with Mailman Core from Pip, since that seemed to work just fine.) > > Right now I'm leaning toward #2, because it means I'll be in a better position to patch things if I need to, and it seems like Mailman 3 is still rough enough that I will need to. Also, it looks like the master branches of both postorius and hyperkitty are now Python 3 compatible, which could save me from managing two different versions of Python. > > Which is the least crazy option? If you are comfortable with 2), I think that's the better option. After PyCon in May when we release 3.2 and the rest of the suite, you should be able to install everything with pip and have it work. I'm not sure what the issues are now with a pip install. There is a 3rd option. See <https://packages.debian.org/stretch-backports/mailman3-full> -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

7 years, 2 months

[MM3-users] Re: Rerun emails in the queue/bad

by Mark Sapiro

On 11/20/18 8:20 AM, Kaleb White wrote: > How do I run the emails in the queue/bad again? I need to see why the failed and get them to work. Thanks. There should be error messages in the 'mailman' log for each preserved file. These would be like 'Skipping and preserving unparseable message: ....psv' 'Unpickling .bak exception: <error msg> Preserving file: ....psv' '.bak file max count, preserving file: ....psv' The first of these indicates an error in retrieving the message from it's original queue. The others have to do with how message loss is avoided. When a .pck file in a queue is processed, it is read and renamed to a .bak. Then if processing is interrupted by a crash, upon restart the .bak file will be processed. The second error above indicates a problem in unpickling the .bak and the third says the same .bak has already been tried too many times. You may be able to examine the files by pointing 'mailman qfile' at them. If that fails, either 'cat' or 'strings' may produce something useful. If they appear to be good, you can reprocess them by renaming to .pck, moving to queue/shunt and running 'mailman unshunt'. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

6 years, 7 months

[MM3-users] Re: translating templates (was: Re: spanish localization)

by Mark Sapiro

On 2/16/21 2:59 AM, Guillermo Hernandez (Oldno7) via Mailman-users wrote: > > /usr/local/lib/python3.7/site-packages/mailman # ls templates/es > domain:admin:notice:new-list.txt list:member:regular:header.txt > help.txt list:user:action:invite.txt > list:admin:action:post.txt list:user:action:subscribe.txt > list:admin:action:subscribe.txt list:user:action:unsubscribe.txt > list:admin:action:unsubscribe.txt list:user:notice:goodbye.txt > list:admin:notice:disable.txt list:user:notice:hold.txt > list:admin:notice:removal.txt list:user:notice:no-more-today.txt > list:admin:notice:subscribe.txt list:user:notice:post.txt > list:admin:notice:unrecognized.txt list:user:notice:probe.txt > list:admin:notice:unsubscribe.txt list:user:notice:refuse.txt > list:member:digest:header.txt list:user:notice:rejected.txt > list:member:digest:masthead.txt list:user:notice:warning.txt > list:member:generic:footer.txt list:user:notice:welcome.txt > > But mailman isn't aware of them (I restarted the server). May I have to > execute some process as "compilemessages" to mailman be capable to use > them? Now mailman is using the "en" templates for sure. Does Mailman have permission to search the templates/es directory and read the templates? Are there overriding templates in Mailman's var/templates/ directory? Are you sure your tests access the templates in a Spanish language context? -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

4 years, 4 months

Search results for query "sapiro"