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

[MM3-users] Re: Handling of (un)subscribe mails for already (un)subscribed users

by Andreas Barth

Hi Mark, thank you for your help. * Mark Sapiro (mark(a)msapiro.net) [201210 23:26]: > The issue is the code at > <https://gitlab.com/mailman/mailman/-/blob/master/src/mailman/app/subscripti…> > appears to not be executed as in my test at least, the workflow continued. Interessting. Here it ended with (current git version) ==> /var/log/mailman3/mailman.log <== Dec 13 23:27:04 2020 (15015) deque: Traceback (most recent call last): File "/srv/prod.mailman/lib/python3/dist-packages/mailman/app/workflow.py", line 69, in __next__ return step() File "/srv/prod.mailman/lib/python3/dist-packages/mailman/app/subscriptions.py", line 227, in _step_sanity_checks MemberRole.member) mailman.interfaces.member.AlreadySubscribedError: t3@$domain is already a MemberRole.member of mailing list t1@$domain This was a "live" run of mailman (however on my testing box). And, however, still no mail. Now I need to think how to continue. Regards, Andi

5 years, 2 months

[MM3-users] Re: Hyperkitty Error Curiosity

by Brian Carpenter

On 11/11/20 7:06 PM, Mark Sapiro wrote: > On 11/11/20 2:11 PM, Brian Carpenter wrote: >> This happened again. Is there a way to get HK to deal with such messages automatically? > > How would you like them dealt with? The issue is in mailman-hyperkitty. > When it's attempt to archive the message returns an error, it queues the > message for retry. It is not clear if any of these errors are actually > retryable - for sure some aren't but maybe others like HyperKitty not > responding are - but even if we think retry won't succeed what would you > like done with the message? > Some sort of auto-discard procedure after a number of retries? Is it possible to detect a message with a null characters and automatically discard them? Do such messages make it into the thread table? -- Brian Carpenter Harmonylists.com Emwd.com

5 years, 3 months

[MM3-users] KeyError: 'get_requests_count' after an upgrade

by Guillermo Hernandez (Oldno7)

I've just upgrade mailman 3 installation following Mr. Sapiro advice: did a pip install --upgrade django-mailman3 hyperkitty mailman mailmanclient mailman-hyperkitty postorius I did a "python3 manage.py migrate" after, too. And all seemed to run well. All the lists showed in postorius via web, but when I try to accesss into one of them the browser shows an error. In the log you can see: *-*-*-*-*-*-* Traceback (most recent call last): File "/usr/local/lib/python3.7/site-packages/mailmanclient/restbase/base.py", line 119, in __getattr__ return self._get(name) File "/usr/local/lib/python3.7/site-packages/mailmanclient/restbase/base.py", line 86, in _get raise KeyError(key) KeyError: 'get_requests_count' ... (And after all the traceback lines) AttributeError: 'MailingList' object has no attribute 'get_requests_count' *-*-*-*-*-*-*-* The lists seem to be distributing messeages well.. but I cannot acces via web administration (django/postorius) Can anyone point me in the right direction to solve this, please?

5 years

[MM3-users] Re: PGP - S/MIME signed messages

by Stephen J. Turnbull

Mark Sapiro writes: > On 7/28/25 13:29, Peter Adebahr via Mailman-users wrote: > > we are receiving a few PGP-signed posts as a S/MIME attachment. Some > > final recipients check these, and as mailman3 does not munge them - the > > original mail is signed, not mailman3's final posts - those get rejected. Besides Mark's suggestions, technically, PGP-signed and S/MIME are two different protocols. If you try to verify one with software expecting the other, it will fail. This seems unlikely (there would be reports of direct mail failing verification), but if Mark's suggestions don't help, you could verify that all the users are on the same page as to what signature protocols are being used. Steve -- GNU Mailman consultant (installation, migration, customization) Sirius Open Source https://www.siriusopensource.com/ Software systems consulting in Europe, North America, and Japan

6 months, 3 weeks

[MM3-users] Re: anomalous behavior

by Donato Molino

On Saturday 05 October 2024, alle 08:59, Mark Sapiro wrote: > On 10/5/24 04:14, donato(a)molino.it wrote: > > Hi, > > I installed mailman-full on debian 12. > > How? Did you follow > https://docs.mailman3.org/en/latest/install/virtualenv.html or did you > install the Debian packages. If the latter, please see > https://wiki.list.org/x/12812344 Ok you're right, I'll try to contact the debian developers. In any case, I will answer your questions below > > > Everything works perfectly except for the fact that for a single ML the messages are not delivered to the recipients. > > I have three MLs: > > 1) example(a)example.com > > 2) test(a)example.com > > 3) hello(a)example.com > > > > For the n. 2 and 3 are fine, but 1 doesn't deliver. > > The configurations are identical for all 3: > > > > smtp.log:Oct 05 11:37:44 2024 (42769) Peer: ('127.0.0.1', 37912) > > Oct 05 11:37:44 2024 (42769) ('127.0.0.1', 37912) handling connection > > Oct 05 11:37:44 2024 (42769) ('127.0.0.1', 37912) >> b'LHLO list.example.com' > > Oct 05 11:37:44 2024 (42769) ('127.0.0.1', 37912) >> b'MAIL FROM:<subscriber(a)domain.tld> SIZE=7873 BODY=7BIT' > > Oct 05 11:37:44 2024 (42769) ('127.0.0.1', 37912) sender: subscriber(a)domain.tld > > Oct 05 11:37:44 2024 (42769) ('127.0.0.1', 37912) >> b'RCPT TO:<example(a)list.example.com>' > > Oct 05 11:37:44 2024 (42769) ('127.0.0.1', 37912) recip: example(a)list.example.com > > Oct 05 11:37:44 2024 (42769) ('127.0.0.1', 37912) >> b'DATA' > > Oct 05 11:37:44 2024 (42769) ('127.0.0.1', 37912) >> b'QUIT' > > I also enabled all debugging in mailman.cfg. > > But everything is fine > > What's in the MTA log? Does list 1 have any non-digest members with delivery > enabled > `mailman members --regular --nomail enabled example(a)example.com` No all members have regular enabled no digest. MTA log accept the message: (relay=127.0.0.1[127.0.0.1]:8024 - status=sent (250 Ok)) then HyperKitty archived message, then smtp log show the message above but does not send to recipients. > > In addition to the above in smtp.log, I would expect to see entries similar > to the following for your post to this list. me too but nothing. All other list with the same configuration are perfect. I tried also delete an recreate the list but nothing. All the lists are no moderate. in any case thank you for the work you do for the Mailman community. Donato > Oct 05 11:15:02 2024 (3390806) > <172812689916.3390800.7261628565807094029(a)mail.mailman3.org> smtp to > mailman-users(a)mailman3.org for 4 recips, completed in 0.31321239471435547 > seconds > Oct 05 11:15:02 2024 (3390806) > <172812689916.3390800.7261628565807094029(a)mail.mailman3.org> post to > mailman-users(a)mailman3.org from mailman-users-owner(a)mailman3.org, 5028 bytes > Oct 05 15:22:57 2024 (3390806) > <172812689795.412444.17509223827906057290(a)mail.mailman3.org> smtp to > mailman-users(a)mailman3.org for 334 recips, completed in 52.519867181777954 > seconds > Oct 05 15:22:57 2024 (3390806) > <172812689795.412444.17509223827906057290(a)mail.mailman3.org> post to > mailman-users(a)mailman3.org from donato(a)molino.it, 1683 bytes > ``` > (the delay between 11:15:02 and 15:22:57 above is the time between arrival > and held message approval) > > Do you see things like that? > > -- > Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, > San Francisco Bay Area, California better use your sense - B. Dylan > > _______________________________________________ > Mailman-users mailing list -- mailman-users(a)mailman3.org > To unsubscribe send an email to mailman-users-leave(a)mailman3.org > https://lists.mailman3.org/mailman3/lists/mailman-users.mailman3.org/ > Archived at: https://lists.mailman3.org/archives/list/mailman-users@mailman3.org/message… > > This message sent to donato(a)molino.it

1 year, 4 months

[MM3-users] Re: Triaging message non-receipt

by Eric Abrahamsen

On 07/13/18 12:56 PM, Mark Sapiro wrote: > On July 13, 2018 12:11:13 PM PDT, Eric Abrahamsen <eric(a)ericabrahamsen.net> wrote: > >>All messages are correctly archived in hyperkitty. smtp.log always >>shows >>"for 5 recips", even for the messages that the two users aren't >>getting. >>These two users only ever miss messages sent by the other. >> > .... >> >>Is there any way to get a better sense of where things are going wrong? >>Turn up the logging verbosity? Send test messages? Get more >>diagnostics? > > > Mailman has delivered the messages to the outgoing MTA and can't tell > you any more. Mailman 3 bounce processing is broken. > > Look in the MTA logs for more. Okay, I'll see what postfix has to tell me. I appreciate the tip on bounce processing. Thanks, Eric

7 years, 7 months

[MM3-users] Re: How to Increase outgoing mail volume for Mailman 3

by Mark Dadgar

On Nov 10, 2020, at 1:18 PM, Mark Sapiro <mark(a)msapiro.net> wrote: >> >> The downside to this is that you lose automated bounce processing, of course. > > > You don't lose bounce processing. It just becomes a bit less reliable. > The VERPed envelope sender says exactly what address the message was > sent to. Without this information, Mailman (actually flufl.bounce > <https://fluflbounce.readthedocs.io/en/latest/README.html>) has to parse > the returned bounce message to determine the bouncing address. There are > many MTAs that do not send RFC 1894 compliant DSNs and we have several > heuristic recognizers to try to parse these, but they can fail. Brian specified: verp_personalized_deliveries: no Doesn’t that default back to regular mass delivery, as opposed to individualized VERPed envelopes, which mandates individual deliveries? - Mark ----- mark(a)pdc-racing.net | 408-348-2878

5 years, 3 months

[MM3-users] Re: Time Zone Issue in Postorius

by Henrik Rasmussen

> -----Oprindelig meddelelse----- > Fra: Mark Sapiro <mark(a)msapiro.net> > Sendt: 8. februar 2022 07:48 > Til: mailman-users(a)mailman3.org > Emne: [MM3-users] Re: Time Zone Issue in Postorius > > It should be TIME_ZONE = 'UTC' > > Times passed from Mailman core are naive times, I.e. they don't have > time zone info, but they are in UTC. Thus for Django to get the correct > time with time zone you need USE_TZ = True (without that, Django will > throw an exception about naive times) and the TIME_ZONE to apply is UTC. As https://stackoverflow.com/questions/29311354/how-to-set-the-timezone-in-dja… seems to say otherwise ("You can use TIME_ZONE = 'Europe/Istanbul'"), to make sure, am I right to understand it as for Mailman, Danish time should be stated as "TIME_ZONE = 'UTC+1' " with use of "USE_TZ = True"? /Henrik Rasmussen

4 years

[MM3-users] Re: mailman-full question

by Dave McGuire

On 9/25/22 13:34, Mark Sapiro wrote: >> - to configure the db in venv i would use mailman-web migrate - this >> works fine - but mailman-full install does not seem to include >> mailman-web >> or mailman3-web - the mailman info cmd works fine - do i need to >> also install mailman-web? i had thought the mailman-full included all >> components > > I'm not sure what it's called in the Debian/Ubuntu mailman-full package, > but the `mailman-web` command installed by `pip install mailman-web` is > the Django admin command, possibly called `django-admin` or `manage.py` > in the mailman-full package. In my (old) Ubuntu package installation, which I got locked into before I realized how awful that was going to be, mailman-web should be symlinked to /usr/share/mailman3-web/manage.py but isn't. -Dave -- Dave McGuire, AK4HZ New Kensington, PA

3 years, 4 months

[MM3-users] Re: Do i need a mailman-hyperkitty.cfg file?

by Bill Oliver

On Mon, 2024-10-28 at 21:08 -0700, Mark Sapiro wrote: > [ > [snip] > es. See the last part of the section at > https://docs.mailman3.org/en/latest/install/virtualenv.html#installing-mail… > > where it says in part `And, create the > /etc/mailman3/mailman-hyperkitty.cfg file containing these settings: > ...` > > > I found a template here: > > > > https://gitlab.com/mailman/mailman-hyperkitty/blob/master/mailman- > > hyperkitty.cfg > > > > > > Do I need to copy and paste that in my installation? > > > It, or something as mentioned in the above doc needs to be at the > location defined in the `configuration:` setting in the > `[archiver.hyperkitty]` section of mailman.cfg > > -- Hah! If it were a snake it woulda bit me. I can't believe I scanned right over it. Thanks! billo

1 year, 3 months

Search results for query "sapiro"