Poste.io still thinks deleted local domain is active

[Scott MacDonald]

Poste.io v2.1.5

After deleting a local domain, and allowing sufficient time to pass for DNS records to update, any attempt to then send email to that domain which is now remote and hosted elsewhere results in a failure and Poste.io indicates that the user@domain has exceeded their mailbox limit. Yet Poste.io logs indicate the transaction never left Poste.io.

[Scott MacDonald]

After stopping, removing, and starting a new container for Poste.io emails are now flowing correctly. I suspect a simple restart of the existing container might have resulted in the same success.

[SH]

I suspect that there might be some DNS-cache handling error but its impossible for me to reproduce this bug localy. I’ll keep this ticket opened and will revisit this issue later

[Saad Ismail]

I ran into this same issue. I have stopped the container and restarted the same container. I will update later if it works.

EDIT: Only stopping and starting docker container worked for me.

[SB]

I am not sure if this is connected but I have noticed some strange DNS issues recently (last 60 days) where the mail server was struggling to resolve certain domains (Any apple domains icloud.com / me.com etc. along with some mimecast domains). Email sits in the delivery queue for a few days then fails.

Server DNS cache was cleared in terminal and and still the issue persisted. It was only resolved when updating the DNS from Azure to Google and restarting the server (which of course would restart the container too). I did read that some services were upgrading their DNS infractructure (Yahoo / BT / Sky etc.) around the time we had these issues.