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

[MM3-users] Re: Newbie question 2: Rewriting issue for bounced emails

by Mark Sapiro

On 12/26/21 3:06 PM, William Oliver wrote: > > When running mailman3, do I need to set up a completely different > virtual domain for it to run in? No. > My "real" domain name is > libertyfp.org, and I'm trying to make mailman work on that domain, e.g. > "testlist(a)libertyfp.org." I'm starting to get the idea that I need to > stick a completely different domain in there for the mailinglist. No. However, in Postfix, libertyfp.org is a virtual_mailbox_domain so you have to use an alias domain in Mailman. An alias domain is not a real domain. It is only known to Mailman and Postfix. It is not exposed in DNS or anywhere outside your server. Have you actually set an alias domain in Postorius for the libertyfp.org domain. It doesn't matter what name it is as long as it isn't a real domain. A good choice is x.libertyfp.org. Have you set that or something similar? If you do and run `mailman aliases` you should get things like testlist(a)libertyfp.org testlist(a)x.libertyfp.org testlist-bounces(a)libertyfp.org testlist-bounces(a)x.libertyfp.org testlist-confirm(a)libertyfp.org testlist-confirm(a)x.libertyfp.org ... in postfix_vmap and things like testlist(a)x.libertyfp.org lmtp:[mail.libertyfp.org]:8024 testlist-bounces(a)x.libertyfp.org lmtp:[mail.libertyfp.org]:8024 testlist-confirm(a)x.libertyfp.org lmtp:[mail.libertyfp.org]:8024 ... in postfix_lmtp > Which I can do -- I've got another two or three domain names to play > with. Is it a problem to run the mailinglist on the same domain that > the machine sits on for its regular business? A lot of the errors I'm > getting seem to be from trying to do regular mail *and* the mailinglist > on the same domain. > > Now that I've installed all this stuff a couple of times, I can easily > re-install for a second virtual domain, if that's what I should be > doing. > > But, on to what's not working now... > > Unfortunately, I seem to have completely screwed the pooch on getting > postfix/dovecot to play nicely with respect to *receiving* mail. > > First, adding "virtual_alias_domains" (and putting libertyfp.org in it) > and commenting out "virtual_mailbox_domains" resulted in postfix > ignoring all my virtual mailboxes. Don't do that. Leave libertyfp.org as a virtual_mailbox_domain and don't set it as a virtual_alias_domain. I think that should work., but you may need to add hash:hash:/opt/mailman/mm/var/data/postfix_vmap to virtual_mailbox_maps instead of virtual_alias_maps. ... > # mailman3 changes > > owner_request_special = no > always_add_missing_headers = yes > transport_maps = hash:/opt/mailman/mm/var/data/postfix_lmtp > local_recipient_maps = proxy:unix:passwd.byname $alias_maps > hash:/opt/mailman/mm/var/data/postfix_lmtp You shouldn't need to add hash:/opt/mailman/mm/var/data/postfix_lmtp to local_recipient_maps, but it probably doesn't hurt. > relay_domains = hash:/opt/mailman/mm/var/data/postfix_domains > default_destination_recipient_limit = 30 > default_destination_concurrency_limit = 15 > virtual_alias_domains = hash:/etc/postfix/domains You don't want virtual_alias_domains. > virtual_alias_maps = hash:/opt/mailman/mm/var/data/postfix_vmap > #hash:/etc/postfix/virtual Everything you've posted so far says you haven't set an alias domain in Mailman for the libertyfp.org domain. Please be sure you have. -- 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: Mailman sends Welcome emails, but does not send [List] postings emails

by Mark Sapiro

On 6/8/23 11:16, Nelson Strother wrote: > Here are the (four identical, but for timestamps and process numbers, at > a glance) tracebacks, and some related info: > > --- from /var/log/syslog > Jun 8 03:35:47 localhost mailman[13107]: Traceback (most recent call > last): > Jun 8 03:35:48 localhost mailman[13107]: File > "/var/tmp/mailman/.local/bin/runner", line 8, in <module> > Jun 8 03:35:48 localhost mailman[13107]: sys.exit(main()) > Jun 8 03:35:48 localhost mailman[13107]: File > "/var/tmp/mailman/.local/lib/python3.9/site-packages/click/core.py", > line 1130, in __call__ > Jun 8 03:35:48 localhost mailman[13107]: return self.main(*args, > **kwargs) > Jun 8 03:35:48 localhost mailman[13107]: File > "/var/tmp/mailman/.local/lib/python3.9/site-packages/click/core.py", > line 1055, in main > Jun 8 03:35:48 localhost mailman[13107]: rv = self.invoke(ctx) > Jun 8 03:35:48 localhost mailman[13107]: File > "/var/tmp/mailman/.local/lib/python3.9/site-packages/click/core.py", > line 1404, in invoke > Jun 8 03:35:48 localhost mailman[13107]: return > ctx.invoke(self.callback, **ctx.params) > Jun 8 03:35:48 localhost mailman[13107]: File > "/var/tmp/mailman/.local/lib/python3.9/site-packages/click/core.py", > line 760, in invoke > Jun 8 03:35:48 localhost mailman[13107]: return __callback(*args, > **kwargs) > Jun 8 03:35:48 localhost mailman[13107]: File > "/var/tmp/mailman/.local/lib/python3.9/site-packages/click/decorators.py", line 26, in new_func > Jun 8 03:35:48 localhost mailman[13107]: return > f(get_current_context(), *args, **kwargs) > Jun 8 03:35:48 localhost mailman[13107]: File > "/var/tmp/mailman/.local/lib/python3.9/site-packages/mailman/bin/runner.py", line 160, in main > Jun 8 03:35:49 localhost mailman[13107]: initialize(config_file, verbose) > Jun 8 03:35:49 localhost mailman[13107]: File > "/var/tmp/mailman/.local/lib/python3.9/site-packages/mailman/core/initialize.py", line 231, in initialize > Jun 8 03:35:49 localhost mailman[13107]: > initialize_2(propagate_logs=propagate_logs) > Jun 8 03:35:49 localhost mailman[13107]: File > "/var/tmp/mailman/.local/lib/python3.9/site-packages/mailman/core/initialize.py", line 189, in initialize_2 > Jun 8 03:35:49 localhost mailman[13107]: config.db = > getUtility(IDatabaseFactory, utility_name).create() > Jun 8 03:35:49 localhost mailman[13107]: File > "/var/tmp/mailman/.local/lib/python3.9/site-packages/mailman/database/factory.py", line 60, in create > Jun 8 03:35:49 localhost mailman[13107]: return database > Jun 8 03:35:49 localhost mailman[13107]: File > "/var/tmp/mailman/.local/lib/python3.9/site-packages/flufl/lock/_lockfile.py", line 470, in __exit__ > Jun 8 03:35:49 localhost mailman[13107]: self.unlock() > Jun 8 03:35:49 localhost mailman[13107]: File > "/var/tmp/mailman/.local/lib/python3.9/site-packages/flufl/lock/_lockfile.py", line 420, in unlock > Jun 8 03:35:49 localhost mailman[13107]: raise > NotLockedError('Already unlocked') > Jun 8 03:35:49 localhost mailman[13107]: > flufl.lock._lockfile.NotLockedError: Already unlocked The runners are all trying to access the Mailman database. During the access <https://gitlab.com/mailman/mailman/-/blob/master/src/mailman/database/facto…> the database is locked. This code is executed by each runner and the lock keeps them from stepping on each other. It should only take milliseconds to execute, not minutes. The lock is created with the DEFAULT_LOCK_LIFETIME which is 15 seconds. The runner which has the lock is taking longer than 15 seconds in the create code and another waiting runner breaks the lock causing this error I would look to your database manager for the issue. -- 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: How to let mailman log every single email that it sends out?

by Mohsen Masoudfar

Thank you, Mark, but Sorry, I don't see them there. I read that the mta log level should be set to debug in order to see them. When I send an email to a list with +3000 subscribers and need to see in the log email has been sent to each of those email addresses Thanks Mohsen ________________________________ From: Mark Sapiro <mark(a)msapiro.net> Sent: Friday, September 8, 2023 3:58:10 PM To: mailman-users(a)mailman3.org <mailman-users(a)mailman3.org> Subject: [MM3-users] Re: How to let mailman log every single email that it sends out? [EXTERNAL EMAIL] On 9/8/23 12:41, Mohsen Masoudfar wrote: > > I'm curious about the configuration required to have Mailman record logs for every individual email it sends. I see that it sends to the entire list, but I'm interested in obtaining log entries for each email sent to every individual subscriber on the list. > How can I access this information? > > Is it a postfix setting, or a Mailman3 setting? > I have checked /var/log/mail.log and all the logs under /var/log/Mailman3/* > Mailman is running on Ubuntu 18.3 You should see the information about the mail being sent an delivered to recipient MX servers in /var/log/mail.log. -- 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://nam12.safelinks.protection.outlook.com/?url=https%3A%2F%2Flists.mai…<https://lists.mailman3.org/mailman3/lists/mailman-users.mailman3.org/> Archived at: https://nam12.safelinks.protection.outlook.com/?url=https%3A%2F%2Flists.mai…<https://lists.mailman3.org/archives/list/mailman-users@mailman3.org/message…> This message sent to mmasoudf(a)aaas.org

2 years, 5 months

[MM3-users] Re: UnicodeEncodeError: 'ascii' codec can't encode character

by Mark Sapiro

On 12/11/19 12:43 AM, Marvin Gülker wrote: > > Thanks for this information. Ubuntu's mailman stores the messages below > /var/lib/mailman3/messages. The "mailman" command is in the $PATH. > >> This should print the file name and Message-ID-Hash (two lines the same) >> for each message in the messages directory until it prints only one line >> followed by the UnicodeEncodeError exception. That list line is the file >> name/Message-ID-Hash of the offending message. > > I've execucted that code, but it does not cause an exception at all. It > quietly runs through. I've attached the transcript of the shell session > to this mail. With a little crude use of grep(1), however I found my > held message in WQ/ZS/WQZSFFJLVMWQHMG4VYKGXJEKQVQXVK67. Here's a revised script: ``` $ mailman shell Welcome to the GNU Mailman shell >>> import os >>> import pickle >>> for root, dirs, files in os.walk('/var/lib/mailman3/messages'): ... for fn in files: ... print(fn) ... with open(os.path.join(root, fn), 'rb') as fp: ... msg = pickle.load(fp) ... print(msg['Message-ID']) ... x = msg.as_string() ... ``` I have adjusted the paths for your package, changed the second print to print the message-is and added the ` x = msg.as_string()` line. Now we expect to see the hash of each message-id followed by the message-id followed by the exception for the offending message. > Does the messages directory contain only held messages? I've looked at > some messages and all of these I looked at were spam. The directory > structure contains 40 messages in total, accumulating to 480 KiB disk > space. Yes, the directory and the corresponding database table contains only messages held for moderator approval. > >> DELETE FROM message WHERE message_id_hash = xxx; > > As the exception you expected did not occur, I didn't do this yet. I can > make a database and directory backup and then run it, though. Should I try? > > I assume after this I should also delete the respective files from the > messages/ directory? Actually, a better way to deal with this is in mailman shell ``` Welcome to the GNU Mailman shell >>> ms = getUtility(IMessageStore) >>> ms.delete_message('xxx') >>> ``` where xxx is the message-id value printed from the above script. >> As of Mailman core 3.3.0 there is a 'mailman notify' command designed to >> be run periodically by cron to notify owners/moderators of pending >> requests. > > I did receive an e-mail to the list owner address that told me that the > e-mail from my incorrect e-mail address "requires approval". That was > the first time I received such an e-mail. In parallel, on the incorrect > e-mail address, I received the notification for moderator approval. Yes, those are the only messages unless you are running `mailman notify`. It seems however that the latest Debian (hence Ubuntu) package doesn't have 3.3 yet. As to why you didn't receive owner notices about the held spam, perhaps they were spam filtered or somehow otherwise lost. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

6 years, 2 months

[MM3-users] Re: Error Logging - what changed with the New Year releases?

by Odhiambo Washington

On Sat, Jan 14, 2023 at 11:57 PM Mark Sapiro <mark(a)msapiro.net> wrote: > On 1/14/23 11:44, Odhiambo Washington wrote: > > On Sat, Jan 14, 2023 at 7:13 PM Mark Sapiro <mark(a)msapiro.net> wrote: > > > >> Nothing in those releases per se would affect this. This is Django and > >> django-allauth. Perhaps when you updated the Mailman packages, you also > >> updated these dependencies. > >> > > > > Which dependencies would those be? > > Django and django-allauth. > (venv) [mailman@gw ~/mm]$ pip freeze | grep jango Django==4.1.5 django-allauth==0.52.0 django-appconf==1.0.5 django-compressor==4.1 django-extensions==3.2.1 django-gravatar2==1.4.4 django-haystack==3.2.1 django-mailman3==1.3.9 django-picklefield==3.1 django-q==1.3.9 djangorestframework==3.14.0 > > > > When I upgraded, the command I ran was: > > > > pip install --upgrade --force mailman mailmanclient postorius hyperkitty > > mailman-hyperkitty django-mailman3 > > > Do you mean --force-reinstall? pip has no --force option. I *think* > --force-reinstall will upgrade dependencies. Depending on your pip > version, --upgrade alone may or may not upgrade dependences. Older > versions of pip will, but newer versions, at least without > --force-upgrade require --upgrade-strategy eager to update dependencies. > I have used --force-reinstall. > > And how do I find out what is suppressing the logging for the social > > accounts? > > That's a django-allauth question. > Let me go RTFM again :-) -- Best regards, Odhiambo WASHINGTON, Nairobi,KE +254 7 3200 0004/+254 7 2274 3223 "Oh, the cruft.", egrep -v '^$|^.*#' ¯\_(ツ)_/¯ :-)

3 years, 1 month

[MM3-users] Re: Bulk delivery status change?

by Stephen Daniel

Thanks all! I will use these pronto. On Sun, Nov 10, 2024 at 11:42 AM Mark Sapiro <mark(a)msapiro.net> wrote: > On 11/10/24 08:34, Odhiambo Washington via Mailman-users wrote: > > On Sun, Nov 10, 2024 at 7:16 PM Stephen Daniel <swd(a)pobox.com> wrote: > > > >> Mistakes were made, and for while every single outbound email bounced. > >> I've fixed the mistakes, but now in my largest and most active email > list, > >> every single user's delivery status is "Disabled by Bounces". > >> > >> Is there a way to bulk fix this? Or do I have to go into each user, > one at > >> a time, and fix them? > > > > Please see this thread: > > > https://lists.mailman3.org/archives/list/mailman-users@mailman3.org/message… > > The script in that post does all lists. For a single list see > > https://lists.mailman3.org/archives/list/mailman-users@mailman3.org/message… > but note that the command line > ``` > $ shell -l list(a)example.com > ``` > should be > ``` > $ mailman shell -l list(a)example.com > ``` > > -- > 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 swd(a)pobox.com >

1 year, 3 months

[MM3-users] Re: 120 gmail users removed from lists !

by Thomas Ward

Mark: Gmail will handle it as Gmail handles it. If the mail domain is Google even if it's custom-domain-example.com and it points to Google Workspace and Google Mail stuff, it'll bounce on the same rules unfortunately. I know this from working with Google Workspace domains myself with lists, it's a pain and they want a lot more stringent controls now. Thomas -----Original Message----- From: Mark Sapiro <mark(a)msapiro.net> Sent: Tuesday, October 24, 2023 1:21 PM To: mailman-users(a)mailman3.org Subject: [MM3-users] Re: 120 gmail users removed from lists ! On 10/24/23 10:04 AM, Andrew Hodgson wrote: > > Speaking of the new additions in Mailman 3.3.9, does anyone have a list of the domains Google are using which we can add to the list so we can disable the unconditional DMARC mitigations for all list posts? Its probably somewhere obvious on a Gitlab issue or similar, but haven't found it yet. The only domains you need to consider are those of your list members, probably only gmail.com, and maybe googlemail.com. I'm not sure how gmail would treat mail From: user(a)some.other.domain where the MX for some.other.domain is a google server, but that could be potentially any domain. -- 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

2 years, 3 months

[MM3-users] Re: warning: database postfix_domains.db is older than source file postfix_domains

by Mark Sapiro

On 10/26/20 10:07 AM, Torge Riedel wrote: > Hi, > > I frequently get this warning mail.log. stat'ing the files give: > > # stat /opt/mailman/var/data/postfix_domains > File: /opt/mailman/var/data/postfix_domains > Size: 361 Blocks: 8 IO Block: 4096 regular file > Device: 801h/2049d Inode: 1573095 Links: 1 > Access: (0660/-rw-rw----) Uid: ( 1004/ mailman) Gid: ( 1002/ mailman) > Access: 2020-10-24 19:52:16.887258326 +0200 > Modify: 2020-10-20 07:09:48.792000000 +0200 > Change: 2020-10-20 07:09:48.792000000 +0200 > Birth: - > # stat /opt/mailman/var/data/postfix_domains.db > File: /opt/mailman/var/data/postfix_domains.db > Size: 12288 Blocks: 24 IO Block: 4096 regular file > Device: 801h/2049d Inode: 1583965 Links: 1 > Access: (0640/-rw-r-----) Uid: ( 1004/ mailman) Gid: ( 1002/ mailman) > Access: 2020-10-26 07:46:54.569935782 +0100 > Modify: 2020-10-20 07:09:47.575889000 +0200 > Change: 2020-10-20 07:09:47.575889000 +0200 > Birth: - I don't understand how this is happening. With defaults for mailman.cfg settings you should have in the [mta] section configuration: python:mailman.config.postfix which points to the file mailman/config.postfix.py in the installation which has in its [postfix] section postmap_command: /usr/sbin/postmap These settings say whenever mailman updates `/opt/mailman/var/data/postfix_domains`, it runs `/usr/sbin/postmap` /opt/mailman/var/data/postfix_domains` to update `/opt/mailman/var/data/postfix_domains.db`. These files, `postfix_domains` and `postfix_lmtp`should be written and closed before invoking the posymap command, so Y don't understand why the modify/change times on the .db files would be 1.22 seconds earlier than those on the source. > I do not have the feeling that this is really a problem, cause > everything works well. But it is confusing and misleading and might > makes me missing a problem in the future, when the database is really > outdated. > > Could this be easily fixed in mailman? I don't think it's a Mailman issue. For example on the server that supports this list I see $ stat /opt/mailman/mm/var/data/postfix_* File: ‘/opt/mailman/mm/var/data/postfix_domains’ Size: 391 Blocks: 8 IO Block: 4096 regular file Device: ca11h/51729d Inode: 5113910 Links: 1 Access: (0660/-rw-rw----) Uid: ( 110/ mailman) Gid: ( 118/ mailman) Access: 2020-10-24 19:30:44.787818101 +0000 Modify: 2020-10-24 19:30:44.731817318 +0000 Change: 2020-10-24 19:30:44.731817318 +0000 Birth: - File: ‘/opt/mailman/mm/var/data/postfix_domains.db’ Size: 12288 Blocks: 24 IO Block: 4096 regular file Device: ca11h/51729d Inode: 5112421 Links: 1 Access: (0644/-rw-r--r--) Uid: ( 110/ mailman) Gid: ( 118/ mailman) Access: 2020-10-26 19:39:45.452615116 +0000 Modify: 2020-10-24 19:30:44.787818101 +0000 Change: 2020-10-24 19:30:44.787818101 +0000 Birth: - File: ‘/opt/mailman/mm/var/data/postfix_lmtp’ Size: 3465 Blocks: 8 IO Block: 4096 regular file Device: ca11h/51729d Inode: 5113909 Links: 1 Access: (0660/-rw-rw----) Uid: ( 110/ mailman) Gid: ( 118/ mailman) Access: 2020-10-24 19:30:44.775817934 +0000 Modify: 2020-10-24 19:30:44.719817150 +0000 Change: 2020-10-24 19:30:44.719817150 +0000 Birth: - File: ‘/opt/mailman/mm/var/data/postfix_lmtp.db’ Size: 12288 Blocks: 24 IO Block: 4096 regular file Device: ca11h/51729d Inode: 5112424 Links: 1 Access: (0644/-rw-r--r--) Uid: ( 110/ mailman) Gid: ( 118/ mailman) Access: 2020-10-26 19:40:38.509356931 +0000 Modify: 2020-10-24 19:30:44.775817934 +0000 Change: 2020-10-24 19:30:44.775817934 +0000 Birth: - Which is what I expect. Note that the only times both the `postfix_domains` and `postfix_lmtp` are updated together is when one of the `mailman` subcommands `aliases` or `start` is run. Are you possibly running both these at the same time causing some kind of race condition? -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

5 years, 3 months

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

by Jered Floyd

This was entirely my fault. *facepalm* I replace styles/base.py when I do my container builds, so that I can override list defaults (personalization, subscription_policy, and dmarc_mitigate_action). I failed to notice the added dmarc_attributes attribute added to apply() --Jered ----- On Nov 25, 2023, at 7:49 PM, Mark Sapiro mark(a)msapiro.net wrote: > On 11/25/23 16:25, Jered Floyd wrote: >> Via mailman-web. I’ll try to reproduce the behavior tomorrow, once I am home >> from another episode of turkey overconsumption. >> >> I confess that I am not a python expert - once I create a new list, what’s the >> easiest way to inspect the object state? > > ``` > $ mailman shell -l list(a)example.com > Welcome to the GNU Mailman shell > Use commit() to commit changes. > Use abort() to discard changes since the last commit. > Exit with ctrl+D does an implicit commit() but exit() does not. > The variable 'm' is the list(a)example.com mailing list > >>> print(m.dmarc_addresses) > [] > >>> > ``` > > -- > 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 jered(a)convivian.com

2 years, 2 months

[MM3-users] Re: Migration from 2.1 to 3

by Mark Sapiro

On 12/26/19 5:22 AM, brunol(a)agro.uba.ar wrote: > > No errors/tracebacks in mailman.log. This is the output of debug.log configured as shown in my first post: > > Dec 26 10:02:37 2019 (696) <CAOwJ5NW3sYhUCCJAVS7ZdiwtyU8SGrArfnPTt5052m1H+V=+nQ(a)mail.gmail.com> to: lispruebas(a)mailman3.agro.uba.ar, list: lispruebas, sub: None, dom: mailman3.agro.uba.ar > Dec 26 10:02:37 2019 (696) <CAOwJ5NW3sYhUCCJAVS7ZdiwtyU8SGrArfnPTt5052m1H+V=+nQ(a)mail.gmail.com> subaddress: None, queue: in > Dec 26 10:02:37 2019 (696) b'250 Ok\r\n' > Dec 26 10:02:37 2019 (696) _handle_client readline: b'QUIT\r\n' > Dec 26 10:02:37 2019 (696) ('127.0.0.1', 43354) Data: b'QUIT' > Dec 26 10:02:37 2019 (696) b'221 Bye\r\n' > Dec 26 10:02:37 2019 (696) ('127.0.0.1', 43354) connection lost > Dec 26 10:02:37 2019 (696) Connection lost during _handle_client() > Dec 26 10:02:38 2019 (699) Using agent: <mailman.mta.bulk.BulkDelivery object at 0x7fb0d7fbbb70> > Dec 26 10:02:38 2019 (699) Using agent: <mailman.mta.bulk.BulkDelivery object at 0x7fb0d7f83fd0> > Dec 26 10:02:38 2019 (699) Using agent: <mailman.mta.bulk.BulkDelivery object at 0x7fb0d483e0b8> > Dec 26 10:02:38 2019 (699) Using agent: <mailman.mta.bulk.BulkDelivery object at 0x7fb0d8079438> > Dec 26 10:02:38 2019 (699) Using agent: <mailman.mta.bulk.BulkDelivery object at 0x7fb0d7f70f28> > Dec 26 10:02:38 2019 (699) Using agent: <mailman.mta.bulk.BulkDelivery object at 0x7fb0d4a60f28> > Dec 26 10:02:38 2019 (699) Using agent: <mailman.mta.bulk.BulkDelivery object at 0x7fb0d4981860> > Dec 26 10:02:38 2019 (699) Using agent: <mailman.mta.bulk.BulkDelivery object at 0x7fb0d483eda0> > Dec 26 10:02:38 2019 (699) Using agent: <mailman.mta.bulk.BulkDelivery object at 0x7fb0d49e2f28> > Dec 26 10:02:38 2019 (699) Using agent: <mailman.mta.bulk.BulkDelivery object at 0x7fb0d80792b0> > Dec 26 10:02:38 2019 (699) Using agent: <mailman.mta.bulk.BulkDelivery object at 0x7fb0d4981e10> > Dec 26 10:02:38 2019 (699) Using agent: <mailman.mta.bulk.BulkDelivery object at 0x7fb0d49e9780> > Dec 26 10:02:38 2019 (699) Using agent: <mailman.mta.bulk.BulkDelivery object at 0x7fb0d4d02c50> > Dec 26 10:02:38 2019 (699) Using agent: <mailman.mta.bulk.BulkDelivery object at 0x7fb0d7fbb550> > Dec 26 10:02:38 2019 (699) Using agent: <mailman.mta.bulk.BulkDelivery object at 0x7fb0d49cf048> > Dec 26 10:02:38 2019 (699) Using agent: <mailman.mta.bulk.BulkDelivery object at 0x7fb0d4983fd0> > > Those "Using agent: <mailman.mta.bulk.BulkDelivery object at " are constantly appearing, is this behavior normal due to the verbosity of the level? What do you mean by constantly appearing? Do you mean endlessly repeating or that they just repeat a number of times equal to the number of expected recipients of the post? On 12/26/19 10:24 AM, brunol(a)agro.uba.ar wrote: > I've also noticed that the messages are stuck in the "message" table (postgresql) and the corresponding files exists under /var/lib/mailman3/messages/ This indicates the held message has not been removed from the held message queue. You previously posted that you saw a log message > Dec 23 12:35:47 2019 (701) held message approved, message-id: CAOwJ5NX=_bUnfb5ZNqVLFeF3EeOP0GMJW7NeeOWZqVmn5ViyBg(a)mail.gmail.com This message comes from mailman.app.moderator.handle_message() (in mailman/app/moderator.py). After logging that message, it requeues it in the 'pipeline' queue for further processing and deletes it from the message table and /var/lib/mailman3/messages/. This indicates that possibly subsequent processing is holding the message again. > Is there any relevant logger i should look on debug too besides the ones i already configured? set [logging.debug] level: debug in mailman.cfg to get more in debug.log. -- 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

Search results for query "sapiro"