On 12/31/19 1:33 AM, ritwik p wrote: > > As there are 2 queue IDs in my postfix logs, I ran: postcat -vq QUEUE_ID , > for each of the queue ID. > One of them had my result: Confirmation email sent to 111.rise.xyz to leave > notg...@abcd.com > and the other had the whole confirmation email > which is stuck in postfix's deferred queue :(
The fact that they are stuck in Postfix is irrelevant to what you are trying to do. You can read the confirmation request with Postcat, so you know what it says. You don't need to receive it yu email. You can confirm by injecting a message to the command queue with Subject: comfirm (the token from the email> >>> This is not a Mailman issue. Postfix cannot connect to port 25 at >> nullmx.domainmanager.com[45.63.18.247] to deliver the mail. > > I tried allowing/opening port 25 on my firewall and nothing happened. > I think my ISP is blocking port 25, > Is there a workaround to this?? It is not unusual for ISPs to block outbound port 25. You may be able to use the submission port (587) with TLS authentication if the MX accepts that. -- Mark Sapiro <m...@msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan _______________________________________________ Mailman-Developers mailing list -- mailman-developers@python.org To unsubscribe send an email to mailman-developers-le...@python.org https://mail.python.org/mailman3/lists/mailman-developers.python.org/ Mailman FAQ: https://wiki.list.org/x/AgA3 Security Policy: https://wiki.list.org/x/QIA9
