Hey Mark, Thanks for replying.

Mark Sapiro wrote:

> > It also would have worked if you had put 'unsubscribe' rather than
> > 'unsubs' in the Subject: as 'unsubscribe' is a valid command and
> > 'unsubs' is not.

This Worked :)
Here's what I executed:

mailman inject -f - -q command notg...@abcd.com
From: 1...@rise.xyz
To: notgood-le...@abcd.com
Subject: unsubscribe
Message-ID: <1_37_pm_31...@rise.xyz>

unsubscribe

Which has now generated 2 SMTP requests
My new SMTP logs are:

smtp to notg...@abcd.com for 1 recips, completed in 0.30856752395629883 seconds
post to notg...@abcd.com from 
notgood-confirm+2dc8268db9cdf0dd2861f2733bf466640c6f4...@abcd.com, 979 bytes
smtp to notg...@abcd.com for 1 recips, completed in 0.05134224891662598 seconds
post to notg...@abcd.com from notgood-boun...@abcd.com, 616 bytes

And my Postfix logs are:

connect from localhost[::1]
postfix/smtpd[7873]: A823945640: client=localhost[::1]
postfix/cleanup[7878]: A823945640: 
message-id=<157777969122.7709.13375533265519975517@Ratwik>
postfix/qmgr[3336]: A823945640: from=<notgood-boun...@abcd.com>, size=1194, 
nrcpt=1 (queue active)
postfix/smtpd[7873]: disconnect from localhost[::1] ehlo=1 mail=1 rcpt=1 data=1 
quit=1 commands=5
postfix/smtpd[7873]: connect from localhost[::1]
postfix/smtpd[7873]: BC9A945650: client=localhost[::1]
postfix/cleanup[7878]: BC9A945650: 
message-id=<157777969130.7709.11350895285421379080@Ratwik>
postfix/qmgr[3336]: BC9A945650: from=<notgood-boun...@abcd.com>, size=825, 
nrcpt=1 (queue active)
postfix/smtpd[7873]: disconnect from localhost[::1] ehlo=1 mail=1 rcpt=1 data=1 
quit=1 commands=5
postfix/smtp[7880]: connect to nullmx.domainmanager.com[45.63.18.247]:25: 
Connection timed out
postfix/smtp[7879]: connect to nullmx.domainmanager.com[45.63.18.247]:25: 
Connection timed out
postfix/smtp[7879]: A823945640: to=<y...@yourdomain.com>, relay=none, delay=31, 
delays=0.06/0.01/31/0, dsn=4.4.1, status=deferred (connect to 
nullmx.domainmanager.com[45.63.18.247]:25: Connection timed out)
postfix/smtp[7880]: BC9A945650: to=<y...@yourdomain.com>, relay=none, delay=31, 
delays=0.05/0.01/31/0, dsn=4.4.1, status=deferred (connect to 
nullmx.domainmanager.com[45.63.18.247]:25: Connection timed out)

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 :(

> > 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??

Thanks Mark :)
_______________________________________________
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

Reply via email to