Mark Sapiro wrote:
Hi Yes, I receive the logging with: subaddress: None, queue: in And then I have another few lines of logging, with nothing relevant ending up in Connection lost during _handle_client() That is normal. If I send with the prefix owner, after the same line I have a line saying: envsender: xxxx-teste222-bounces+emanuel-d-vitorino=telecom.pt@xxxxxxxx.pt, recipients: ['emanuel-d-vitorino@xxxxxx.pt'], size(msgtext): 464 This one comes from mailman/mta/connection.py when the message is being sent to the recipients. Since you don't see that, the message never gets
On 1/20/21 9:54 AM, costavitorino@gmail.com wrote: this far. Since mail to -owner works, the incoming runner is processing the 'in' queue so something happens between the message being picked up from the 'in' queue and delivery. First, check Mailman's bin/mailman members --regular --nomail enabled list.example.com returns two users. Mine that is also owner and another one that only subscribed the mailing list
where list.example.com is the actual list id to ensure there are members who should receive the mail. Then check Mailman's mailman.log and debug.log for clues. You may need to set [logging.debug] level: debug [logging.error] level:debug To get more logging.
Everything logging. No errors.
core/switchboard.py:97 (enqueue) Is this method that handles the queue? I'm logging the entire method, and on line 135 Im logging msgsave variable. And it's filled with some data After that, I receive DISCARD from chains/discard.py:45
If I send with prefix owner, I receive also from chains/owner.py OWNER:. .... here I believe that is the expected behavior. After this, it runs again enqueue and anything else. No DISCARD or anything
What happens before chains that could DISCARD the message? Could it be any misconfiguration of my part?
Wich methods can I check to debug whats happening?
Thank you very much Emanuel