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

[MM3-users] Re: How to identify the exact reason behind the shunting of the mails ?

by Shashikanth Komandoor

Thank you Mark for your immediate response. The below are the tracebacks I could find in the mailman log. *Jun 17 19:04:08 2021 (8642) Uncaught runner exception: sequence item 0: expected str instance, Header foundJun 17 19:04:08 2021 (8642) Traceback (most recent call last): File "/var/lib/mailman/mailman/src/mailman/core/runner.py", line 173, in _one_iteration self._process_one_file(msg, msgdata) File "/var/lib/mailman/mailman/src/mailman/core/runner.py", line 266, in _process_one_file keepqueued = self._dispose(mlist, msg, msgdata) File "/var/lib/mailman/mailman/src/mailman/runners/pipeline.py", line 37, in _dispose process(mlist, msg, msgdata, pipeline) File "/var/lib/mailman/mailman/src/mailman/core/pipelines.py", line 50, in process handler.process(mlist, msg, msgdata) File "/var/lib/mailman/mailman/src/mailman/handlers/avoid_duplicates.py", line 59, in process addrs = getaddresses(msg.get_all(header, [])) File "/usr/lib64/python3.6/email/utils.py", line 112, in getaddresses all = COMMASPACE.join(fieldvalues)TypeError: sequence item 0: expected str instance, Header foundJun 17 19:04:08 2021 (8642) SHUNTING: 1623936848.367641+4753f8127953071ddcabfe828ebe72fcf04d0ae2* In the shunt file, I see something like this as below in CC while To is good: *Cc: =?unknown-8bit?q?=22Support_Zimbra=22_=3Csupport-zimbra=40nic=2Ein=3E=2C?= =?unknown-8bit?b?ICLgpLbgpLDgpKYg4KSu4KS+4KSl4KWB4KSwIC0gU2hhcmFkIE1hdGh1ciIgPHN1cHBvcnQtdmFqcmFAc3VwcG9ydGdvdi5pbj4s?= =?unknown-8bit?b?ICLgpLDgpL7gpJzgpYfgpLYg4KS44KS/4KSC4KS5IC0gUmFqZXNoIFNpbmdoIiA8cmFqc0BuaWMuaW4+LA==?= =?unknown-8bit?b?ICJTYWJ5YXNhY2hpIENob3VkaHVyeSIgPHNhYnlhQG5pYy5pbj4sIG1haWxhZG1pbkBuaWMuaW4s?= =?unknown-8bit?b?ICJNUklUVU5KQVkgS1VNQVIiIDxta0BuaWMuaW4+LCAiQmhyaWd1IEt1bWFyIiA8YmhyaWd1QG5pYy5pbj4s?= =?unknown-8bit?b?ICJPbSBQcmFrYXNoIiA8b3AubmhxQG5pYy5pbj4sICJIYXJpaGFyYW4gTSIgPGhhcmloYXJhbi5tQGdvdi5pbj4s?= =?unknown-8bit?b?ICJQaGlzaGluZyBQaGlzaGluZyIgPHBoaXNoaW5nQG5pYy5pbj4sICJpbmNpZGVudCIgPGluY2lkZW50QG5pYy5pbj4s?= =?unknown-8bit?b?ICJNYW5hdiBSYWtoZWphIiA8bWFuYXYucmFraGVqYUBuaWMuaW4+?=* Also, I came to know that two of the recipients in CC block have their mail ID display name in their local language. While I am not sure, I doubt if it could be the issue of getting shunted. Please confirm and suggest any solution. On Thu, Jun 17, 2021 at 8:48 PM Mark Sapiro <mark(a)msapiro.net> wrote: > On 6/17/21 6:56 AM, Shashikanth Komandoor wrote: > > > > Is there any chance to find out the reason for shunting of the > > mails through any means ? > > > > > Look in Mailman's var/logs/mailman.log for the tracebacks associated > with the shunted messages. > > -- > 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/ > -- Thanks & Regards, Shashi Kanth.K 9052671936

4 years, 2 months

[MM3-users] Re: lmtp runner not starting

by Guillermo Hernandez (Oldno7)

El 1/4/23 a las 21:14, Mark Sapiro escribió: > On 4/1/23 12:00, Guillermo Hernandez (Oldno7) via Mailman-users wrote: >> >> El 1/4/23 a las 20:44, Mark Sapiro escribió: >>> ... >>> lmtp runner did not start because at some point it had died and >>> restarting Mailman won't restart a runner that died and was marked >>> to not restart. >>> >>> You need to stop Mailman and make sure when mailman is stopped that >>> there are no files in mailman's var/locks/ directory (remove any >>> that are there) and then start Mailman and lmtp runner should start. >>> >> I stopped mailman and removed all that was in there (there were many >> locked registers). Restarted mailman, and it shows the same error >> that in my previous mail. >> >> Now there is two new locked files, one (master.lck) which its content >> is the name of the other file. And the second one has the same content: >> >> master.lck|www.proteccion-civil.eu|9389|7022761192045613065 > Sorry, I sent my previous mail, and then received this > > Those are the master lock that prevents Mailman core from starting > when it is running. They should not be removed unless Mailman core is > stopped. Everytime I deleted that files I previously have stopped mailman, yes > >> will try deleting the content of var/locks and restarting the server > > If you had completely stopped Mailman core and then started it, lmtp > runner should have started. What are the complete log messages from > mailman.log following the start? > I sent them before > What does `mailman conf -s runner.lmtp` show? > Here it is: root@www:/usr/local/mailman3 # /usr/bin/su -m mailman3 -c "/usr/local/bin/mailman -C /usr/local/mailman3/var/etc/mailman.cfg conf -s runner.lmtp" [runner.lmtp] class: mailman.runners.lmtp.LMTPRunner [runner.lmtp] instances: 1 [runner.lmtp] max_restarts: 10 [runner.lmtp] path: [runner.lmtp] sleep_time: 1s [runner.lmtp] start: yes -- ___________________________________________ Mailman's content filtering has removed the following MIME parts from this message. Content-Type: image/png Name: firma-GHP-emails.png Replaced multipart/alternative part with first alternative.

2 years, 5 months

[MM3-users] Re: Single-Sign-out for List member

by Abhilash Raj

On Thu, Aug 13, 2020, at 10:04 AM, Mark Sapiro wrote: > On 8/13/20 6:21 AM, w.schoener(a)alp.dillingen.de wrote: > > > > So I would like to ad a link in the footer of every message, with which every receiver/member can sign out of the newsletter with one click. > > It does not seam to be possible, to put this into effect with mailman 3. > > Does anybody have any hints, how to create a link, and when this link is called, the user is signed out of the newsletter. > > > You can set the list's unsubscription_policy to open and set the link as > a mailto: to the list-leave address, but that still requires a second > click to send the mail. > > The solution is to create a web based CGI script which is called with a > URL like > <https://example.com/unsub_script/list.example.com/user@example.net> and > have that script invoke the appropriate `mailman` command to remove the > member from the list. Beginning with Mailman 3.3.2, this would be If this is one-click, can't this URL be hit by anyone trying to remove the user from any MailingList without any auth or anything? > > mailman delmembers -l list.example.com -m user(a)example.net -g > > to remove the member and send a goodbye message. In older Mailman, it > would be something like > > echo user(a)example.net | mailman members -x - list.example.com > > I understand you may have a legal requirement do do this, but these > "one-click - no user confirmation" links are a bad idea because usera > will reply to a list post or forward it and not remove the link and > userb will receive usera's reply and click usera's unsubscribe link > either maliciously or thinking it will unsubscribe userb. > > -- > 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/ > -- thanks, Abhilash Raj (maxking)

5 years

[MM3-users] Re: mailman3 does not send to the members of the lists

by Mark Sapiro

On 7/12/20 4:16 PM, maszap(a)tin.it wrote: > Hi > My mail.log > > Jul 13 01:15:12 gamelia postfix/smtpd[1973]: connect from localhost[127.0.0.1] > Jul 13 01:15:12 gamelia postfix/trivial-rewrite[1974]: warning: do not list domain pratico.work in BOTH virtual_mailbox_domains and relay_domains > Jul 13 01:15:12 gamelia postfix/trivial-rewrite[1974]: warning: do not list domain pratico.work in BOTH virtual_mailbox_domains and relay_domains > Jul 13 01:15:12 gamelia postfix/smtpd[1973]: 276C0C202B7: client=localhost[127.0.0.1] > Jul 13 01:15:12 gamelia postfix/cleanup[1975]: 276C0C202B7: message-id=<20200712231512.1546.30031(a)mail.pratico.work> > Jul 13 01:15:12 gamelia opendkim[726]: 276C0C202B7: DKIM-Signature field added (s=mail2020, d=pratico.work) > Jul 13 01:15:12 gamelia postfix/qmgr[1533]: 276C0C202B7: from=<admin(a)pratico.work>, size=586, nrcpt=2 (queue active) > Jul 13 01:15:12 gamelia postfix/smtpd[1973]: disconnect from localhost[127.0.0.1] ehlo=1 mail=1 rcpt=1 data=1 quit=1 commands=5 > Jul 13 01:15:12 gamelia postfix/smtpd[1978]: connect from localhost[127.0.0.1] > Jul 13 01:15:12 gamelia postfix/trivial-rewrite[1974]: warning: do not list domain pratico.work in BOTH virtual_mailbox_domains and relay_domains > Jul 13 01:15:12 gamelia postfix/trivial-rewrite[1974]: warning: do not list domain pratico.work in BOTH virtual_mailbox_domains and relay_domains > Jul 13 01:15:12 gamelia postfix/smtpd[1978]: C3A57C20D52: client=localhost[127.0.0.1] > Jul 13 01:15:12 gamelia postfix/trivial-rewrite[1974]: warning: do not list domain pratico.work in BOTH virtual_mailbox_domains and relay_domains > Jul 13 01:15:12 gamelia postfix/cleanup[1975]: C3A57C20D52: message-id=<20200712231512.1546.30031(a)mail.pratico.work> > Jul 13 01:15:12 gamelia opendkim[726]: C3A57C20D52: DKIM-Signature field added (s=mail2020, d=pratico.work) > Jul 13 01:15:12 gamelia postfix/qmgr[1533]: C3A57C20D52: from=<admin(a)pratico.work>, size=1610, nrcpt=2 (queue active) > Jul 13 01:15:12 gamelia postfix/smtpd[1978]: disconnect from localhost[127.0.0.1] ehlo=1 mail=1 rcpt=2 data=1 quit=1 commands=6 > Jul 13 01:15:12 gamelia postfix/trivial-rewrite[1974]: warning: do not list domain pratico.work in BOTH virtual_mailbox_domains and relay_domains > Jul 13 01:15:12 gamelia postfix/trivial-rewrite[1974]: warning: do not list domain pratico.work in BOTH virtual_mailbox_domains and relay_domains > Jul 13 01:15:12 gamelia amavis[1566]: (01566-01) Passed CLEAN {RelayedInbound}, [127.0.0.1]:36322 <admin(a)pratico.work> -> <admin(a)pratico.work>,<info@pratico$ > Jul 13 01:15:12 gamelia postfix/smtp[1976]: 276C0C202B7: to=<admin(a)pratico.work>, orig_to=<max(a)pratico.work>, relay=127.0.0.1[127.0.0.1]:10024, delay=0.76, $ > Jul 13 01:15:12 gamelia postfix/smtp[1976]: 276C0C202B7: to=<info(a)pratico.work>, orig_to=<max(a)pratico.work>, relay=127.0.0.1[127.0.0.1]:10024, delay=0.76, d$ > Jul 13 01:15:12 gamelia postfix/qmgr[1533]: 276C0C202B7: removed > Jul 13 01:15:12 gamelia dovecot: lmtp(1980): Connect from local > Jul 13 01:15:12 gamelia dovecot: lmtp(admin(a)pratico.work)<1980><wZyjNoCZC1+8BwAA0Fextg>: sieve: msgid=<20200712231512.1546.30031(a)mail.pratico.work>: stored $ > Jul 13 01:15:12 gamelia dovecot: lmtp(info(a)pratico.work)<1980><wZyjNoCZC1+8BwAA0Fextg:2>: sieve: msgid=<20200712231512.1546.30031(a)mail.pratico.work>: stored$ > Jul 13 01:15:12 gamelia postfix/lmtp[1979]: C3A57C20D52: to=<admin(a)pratico.work>, relay=mail.pratico.work[private/dovecot-lmtp], delay=0.13, delays=0.09/0.0$ > Jul 13 01:15:12 gamelia postfix/lmtp[1979]: C3A57C20D52: to=<info(a)pratico.work>, relay=mail.pratico.work[private/dovecot-lmtp], delay=0.13, delays=0.09/0.01$ > Jul 13 01:15:12 gamelia postfix/qmgr[1533]: C3A57C20D52: removed > Jul 13 01:15:12 gamelia dovecot: lmtp(1980): Disconnect from local: Client has quit the connection (state=READY) > Jul 13 01:15:16 gamelia dovecot: imap-login: Login: user=<admin(a)pratico.work>, method=PLAIN, rip=173.249.18.220, lip=173.249.18.220, mpid=1983, TLS, session$ > Jul 13 01:15:16 gamelia dovecot: imap(admin(a)pratico.work)<1983><IiFCv0aqJoyt+RLc>: Logged out in=297 out=5915 deleted=0 expunged=0 trashed=0 hdr_count=11 hd$ The issue here is the message is being delivered to Dovecot via LMTP rather than to Mailman via LMTP. See this thread <https://lists.mailman3.org/archives/list/mailman-users@mailman3.org/thread/…>. > sudo mailman conf -s logging.smtp > > [logging.smtp] datefmt: %b %d %H:%M:%S %Y > [logging.smtp] every: $msgid smtp to $listname for $recip recips, completed in $time seconds > [logging.smtp] failure: $msgid delivery to $recip failed with code $smtpcode, $smtpmsg > [logging.smtp] format: %(asctime)s (%(process)d) %(message)s > [logging.smtp] level: info > [logging.smtp] path: smtp.log > [logging.smtp] propagate: no > [logging.smtp] refused: $msgid post to $listname from $sender, $size bytes, $refused failures > [logging.smtp] success: $msgid post to $listname from $sender, $size bytes With these settings, posts should be logged. They aren't because no mail is delivered to Mailman at all. The Mail that local users receive doesn't come from the list. It comes from Dovecot. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

5 years, 1 month

[MM3-users] Re: Edit archived email? Is it possible?

by Prasanth Nair

Hi Mark, Thank you for your help. Let me try this. Kind regards, Prasanth On Tue, 28 Sept 2021 at 18:03, Mark Sapiro <mark(a)msapiro.net> wrote: > On 9/28/21 6:02 AM, Prasanth Nair wrote: > > Hello, > > > > Does anyone know how to edit an archived email in Mailman3? It is > possible > > in Mailman2 ( > > > https://wiki.list.org/DOC/How%20do%20I%20edit%20the%20archives%20of%20a%20M… > ). > > Is there any option similar to this in Mailman3? > > > In some sense the process is the same but possibly even simpler in > Mailman 3. You need to modify the underlying data which requires > appropriate access to the server. > > In Mailman 3, the data are in the hyperkitty_email table in Mailman's > database. You can get the Message-ID hash from the URL to the archived > message, e.g. for the message to which I'm replying, the URL is > > https://lists.mailman3.org/archives/list/mailman-users@mailman3.org/message… > and the hash is 7PVJL23DLSWMXXL44ALQUO6VSYBRZ4OA. Then if you have > access, you can do database queries like > ``` > SELECT subject, content FROM hyperkitty_email WHERE message_id_hash = > '7PVJL23DLSWMXXL44ALQUO6VSYBRZ4OA'; > ``` > and > ``` > UPDATE hyperkitty_email SET content = '<new content>' WHERE > message_id_hash = '7PVJL23DLSWMXXL44ALQUO6VSYBRZ4OA'; > UPDATE hyperkitty_email SET subject = '<new subject>' WHERE > message_id_hash = '7PVJL23DLSWMXXL44ALQUO6VSYBRZ4OA'; > ``` > If the message has attachments, they are in the hyperkitty_attachment > table and can be referenced by `email_id` which is the corresponding > `id` from the hyperkitty_email entry. > > You can also do similar things via `django-admin shell`. E.g. > ``` > $ django-admin shell > Python ... > (InteractiveConsole) > >>> from hyperkitty.models.email import Email > >>> x = > Email.objects.filter(message_id_hash='7PVJL23DLSWMXXL44ALQUO6VSYBRZ4OA') > >>> print(x[0].content) > ``` > but this requires some knowledge of HyperKitty's models and Django's ORM. > > -- > 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/ >

3 years, 11 months

[MM3-users] Re: What to backup?

by Alain Kohli

Thank you, that's perfect! For anyone that might stumble upon this, I had to make two minor adjustments to automate it. import os msg_ids = {} lm = getUtility(IListManager) ms = getUtility(IMessageStore) for mlistin lm.mailing_lists: requestdb = IListRequests(mlist) for rqin requestdb.held_requests: key, msgdata = requestdb.get_request(rq.id) if msgdata['_request_type'] !='held_message': continue msg = ms.get_message_by_id(key) msg_ids[(msg['Message-ID-Hash'])] =True for root, dirs, filesin os.walk('/docker/var/messages'): for filein files: if not msg_ids.get(file, False): msg = ms.get_message_by_hash(file) # It happened to me that msg was 'None' if msg: ms.delete_message(msg['Message-ID']) # I couldn't run it with '--run' and if you pipe it into 'mailman shell' # I needed this or the loop above wouldn't execute. pass On 5/27/19 6:22 AM, Mark Sapiro wrote: > On 5/26/19 3:07 PM, Mark Sapiro wrote: >> You could modify the above to write the list to a file and then wrap the >> whole thing in a shell script which would make the list and then do >> something like >> >> for f in `find var/messages -type f`;do >> n=`cut -d / -f5 <<<$f` >> for keep in `cat list` ;do >> k=0 >> if [ $n == $keep ] ;then >> k=1 >> break >> fi >> done >> if [ $k -eq 0 ]; then >> rm $f >> fi >> done > Actually, I thought about it a bit more, and I decided that arcane shell > script was a bit obscure and it would be easier to just do it in Python. > Plus, you can properly delete the message that way. > > A complete script for `mailman shell` is like > > import os > msg_ids = {} > lm = getUtility(IListManager) > ms = getUtility(IMessageStore) > for mlist in lm.mailing_lists: > requestdb = IListRequests(mlist) > for rq in requestdb.held_requests: > key, msgdata = requestdb.get_request(rq.id) > if msgdata['_request_type'] != 'held_message': > continue > msg = ms.get_message_by_id(key) > msg_ids[(msg['Message-ID-Hash'])] = True > > for root, dirs, files in os.walk('path/to/var/messages'): > for file in files: > if not msg_ids.get(file, False): > msg = ms.get_message_by_hash(file) > ms.delete_message(msg['Message-ID']) > >

6 years, 3 months

[MM3-users] Re: [EXTERNAL] Re: Database deadlock when trying to delete a member.

by Simon Coggins

Thanks I’ll give that a try. Also in my tracing of the code I noticed https://gitlab.com/mailman/mailman/-/blob/master/src/mailman/interfaces/dat… it starts with a single quote and ends with triple quotes so the single quote is never terminated. -Simon From: Mark Sapiro <mark(a)msapiro.net> Date: Wednesday, 24 March 2021 at 4:10 am To: "mailman-users(a)mailman3.org" <mailman-users(a)mailman3.org> Subject: [MM3-users] Re: [EXTERNAL] Re: Database deadlock when trying to delete a member. On 3/22/21 9:53 PM, Simon Coggins wrote: > Ok after bit tracking I’ve worked out that the bouncer is dangling transactions when it’s sending warning messages. When https://gitlab.com/mailman/mailman/-/blob/3.3.4/src/mailman/model/bounce.py…<https://gitlab.com/mailman/mailman/-/blob/3.3.4/src/mailman/model/bounce.py…> is called and it get to update last_warn_sent it does the following in the DB: > > 2021-03-23 14:42:50.622 AEST [11693] LOG: statement: UPDATE member SET last_warning_sent='2021-03-23T04:42:50.622015'::timestamp, total_warnings_sent=1 WHERE member.id = 169331 > > But it never COMMITs this transaction. So all write operations are now hung waiting for the transction to be closed as the member record has been modified. As a test I added config.db.commit() after https://gitlab.com/mailman/mailman/-/blob/3.3.4/src/mailman/model/bounce.py…<https://gitlab.com/mailman/mailman/-/blob/3.3.4/src/mailman/model/bounce.py…> and restarted. And my mailman syncmembers worked perfectly and I didn’t have any hangs it correctly removed everyone it should have. In the database logs I can see the COMMIT. > > I’m pretty sure this is not the right spot for a config.db.commit() but hopefully this helps point to what might be going wrong. Thank you for all the research on this. It is extremely helpful. Instead of adding a commit after line 277 please try adding the @transactional decorator to the send_warnings_and_remove method at line 210 @transactional @dbconnection def send_warnings_and_remove(self, store): I think that is the proper fix. Let us know if that works. -- 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/<https://lists.mailman3.org/mailman3/lists/mailman-users.mailman3.org>

4 years, 5 months

[MM3-users] Re: (Custom) Plugins: Proper file path(s) for adding a handler?

by Thomas Ward

I was able to instantiate the class AND get the expected three objects from it - pre_hook, post_hook, and resource. >>> from mailman_customizations.hooks import MailmanCustomizations >>> instance = MailmanCustomizations() >>> dir(instance) ['__class__', '__delattr__', '__dict__', '__dir__', '__doc__', '__eq__', '__format__', '__ge__', '__getattribute__', '__gt__', '__hash__', '__implemented__', '__init__', '__init_subclass__', '__le__', '__lt__', '__module__', '__ne__', '__new__', '__providedBy__', '__provides__', '__reduce__', '__reduce_ex__', '__repr__', '__setattr__', '__sizeof__', '__str__', '__subclasshook__', '__weakref__', 'post_hook', 'pre_hook', 'resource'] I know Abhilash Raj is probably well versed in this from statements made elsewhere, so I've added them in the CC field. Abhilash Raj, any ideas? Thomas -----Original Message----- From: Mark Sapiro <mark(a)msapiro.net> Sent: Tuesday, October 24, 2023 10:36 PM To: mailman-users(a)mailman3.org Subject: [MM3-users] Re: (Custom) Plugins: Proper file path(s) for adding a handler? On 10/24/23 3:56 PM, Thomas Ward via Mailman-users wrote: > > When I DO NOT have the module loaded in the configuration, `mailman > shell` works. Since that was functional, I went into the shell and > executed this: > > > from mailman_customizations.hooks import MailmanCustomizations > > This worked fine, but obviously importing the class doesn't > necessarily > *activate* the class. So something is up with how I'm *supposed* to > activate the plugin in the config, and we know that it's visible to > Mailman in its shell, but it can't autoload it. I'm past the limit of my knowledge here and only stabbing in the dark, but what happens after you import it. Can you instantiate it, e.g. ``` instance = MailmanCustomizations() dir(instance) ``` I'm not saying this should succeed, just that it may possibly provide useful information. -- 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 teward(a)thomas-ward.net

1 year, 10 months

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

by "Jörg M. Schulz"

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. See 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 > Am 09.01.2019 um 21:12 schrieb Mark Sapiro <mark(a)msapiro.net>: > > On 1/9/19 12:02 PM, "Jörg M. Schulz" wrote: >> start fails when I use >> >> >> # The default language for this server. >> default_language: en >> [language.en] >> charset: utf-8 >> enabled: yes >> >> when I comment out the lines above, mailman starts. > > > And in what section is this put? I.e. if the last preceding section > header is not [mailman], the default_language: en is in a section where > it doesn't belong. > > Or are you saying that you had set the server default_language to > something other than 'en' and the above is intended to change it to > 'en'. In that case, look at var/templates/en and ensure it and > subordinates are user:group list:list > > -- > 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/

6 years, 8 months

[MM3-users] Re: Disabled by bounce

by Allan Hansen

Mark, I can see your argument here, but if a 'Disabled by bounce' subscription is enabled, it would require just looking at that particular subscription and set the bounce count to 0, so that the next bounce (before staleness) does not disable it again. __ Yours, Allan On 2/2/23, 13:44, "Mark Sapiro" <mark(a)msapiro.net> wrote: On 2/2/23 04:54, Danil Smirnov wrote: > Hi Mark > > On Wed, Feb 1, 2023 at 9:28 PM Mark Sapiro <mark(a)msapiro.net> wrote: > >> Yes and no. If 'Bounce info stale after' is set to 3d and no bounces for >> a user are received in a 3 day period, the user's bounce score is not >> immediately reset, but it will be reset (to 1) the next time a bounce is >> received for the user. I.e., it is effectively the same thing unless you >> are looking at the user's bounce score which doesn't change until the >> next bounce. >> > > Isn't this a bug? We are now showing users' bounce scores on the Members > page and this would be misleading. Is it difficult from internals > perspective to have the bounce score reset immediately? Yes, it is not difficult, but it's a lot of processing. It would require something like a task runner task to periodically look at each row in the member table and if the bounce score is > 0, find the associated list's bounce_info_stale_after and if last_bounce_received + bounce_info_stale_after < now, reset the score. Consider a site like mail.python.org that at this moment has 79024 rows in the member table and 7531 of those have bounce_score > 0. That's a lot of processing, and is it really an issue to show a non-zero bounce score that's stale? -- 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: mailman-users(a)mailman3.org <https://lists.mailman3.org/archives/list/<a href=>/message/ERW6LLR3VIJHUS5ECDA7A2P53WD7ZZEB/">https://lists.mailman3.org/archives/list/mailman-users@mailman3.org/message… This message sent to hansen(a)rc.org

2 years, 7 months

Search results for query "sapiro"