Mailpiler not receiving any emails

Issue #1197 closed
Rogerphilip created an issue

I had set up an instance of mailpiler (v1.3.4) on ubuntu 18.04. When I was setting it up, it was able to receive all the e-mails sent to it and archive them. But after that I have observed that it is not receiving any new mails. Whenever I send an email to the archival id, it bounces and I get back the following errors:

When the mail is sent from a mail id running on postfix I get the below error:

<info@customdomain.net>: Domain archive.mydomain.net does not accept mail

(nullMX)

From gmail, I get the following error:

Address not found
Your message wasn't delivered to archive@archive.mydomain.net because the domain archive.mydomain.net couldn't be found. Check for typos or unnecessary spaces and try again.

I wasn’t able to send emails using telnet either. In the web gui, the status for piler and smarthost are shown as OK.

Am I doing anything wrong? Can anyone help me please? Thanks in advance.

Comments (7)

  1. Janos SUTO repo owner

    I wonder why you installed an older release (1.3.4) instead of using a more recent version, eg. 1.3.11. Anyway, I suspect that the emails don’t reach the archive. I suggest to run a packet dump utility (eg. ngrep) on port 25 on the archive host, and verify that there’s an smtp traffic. Also what’s in the mail.log file? Any reference of piler-smtp receiving traffic?

  2. Rogerphilip reporter

    Thank you for the response. I destroyed the old instance and installed the latest docker build of mailpiler. However the issue still persists.

    I tried testing the smtp service using https://www.smtper.net/ and https://www.wormly.com/test-smtp-server. The test emails sent by these tools are received by piler, but mails sent from my primary domain and gmail are not being received. This has me very confused. I ran ngrep and it did capture the activity on port 25.

    As for the logs, I will share at the earliest. In it, there are references to mails received from the above mentioned tools but not from gmail or my primary domain.

  3. Log in to comment