Received mail is bounced at SMTP endpoint location #3080
Replies: 5 comments 1 reply
-
I'll also add that sending mail to myself (home mail server > postal > back to home mail server) results in the same error. |
Beta Was this translation helpful? Give feedback.
-
At some point in the chain, Postal is interpreting the message as being sent, rather than being incoming so it is looking for the correct domain in its configuration which apparently it does not have. I am not sure of the way around it, unfortunately Postal is quite specific in how it prefers to be used, rather than a super flexible traditional mail server. |
Beta Was this translation helpful? Give feedback.
-
I'm thinking having Postal and the mail server on the same domain is what's causing issues, and why Postal thinks incoming mail is sent mail. I'm going to try putting Postal on it's own domain and see how it behaves. |
Beta Was this translation helpful? Give feedback.
-
Well I've got postal running on a separate domain, |
Beta Was this translation helpful? Give feedback.
-
This is for received mail though. It's not coming from my domain. I tried checking the sender header setting but it didn't change anything. I was able to accomplish what I wanted using mailcow-dockerized so I am going to close the discussion. |
Beta Was this translation helpful? Give feedback.
-
Hi all,
I have a mailcow server running on my residential network with port 25 blocked. For the past few years I have been using Dynu's email store/forward and email backup to get around the blocked port 25. I have started adding some additional mail servers for a few other projects with different domains. It's becoming too expensive because I have to purchase a store/forward and email backup from Dynu per domain. My end goal is to replace what Dynu has been providing me on two (2) different VPS for redundancy, each with port 25 open.
I have gotten my two VPS setup, each running an almost identical postal server config. The only difference is the primary server is operating on
smtp.mydomain.com
, and the secondary server is onsmtp2.mydomain.com
. Sending emails from any of my mail servers (over port 26) to my postal server(s) works perfect. I've setup the firewall to route incoming port 26 to port 25. Postal receives all the outgoing mail and sends them out correctly. I don't have any deliverability problems to google, apple, etc.My DNS settings are as follows:
Postal Config:
My problems occur when receiving mail. What I want to happen is when someone send me an email at
[email protected]
the email is sent to the primary Postal server. The postal server then routes it to my home mail server atmail.mydomain.com
. I have configured to SMTP endpoint in Postal to use port 125, my home router then routes port 125 to port 25 for my residential mail server.If my primary Postal server is down it will be delivered to the secondary Postal server running on a different VPS. Secondary postal server is configured the same as the primary server where the SMTP endpoint send it to my home IP.
If my home mail server is down, then Postal will still receive the mail and retry delivery until the home server is online again.
The issue I am getting is mailcow is bouncing all emails that Postal sends it (emails that someone sends to me at
[email protected]
).Here is the exact error I get in mailcow Postfix logs:
I must be misunderstanding something regarding receiving mail in Postal. I do have some other DNS entries for things like
mx.smtp.mydomain.com
andrp.smtp.mydomain.com
but have not had any luck.Thank you
Beta Was this translation helpful? Give feedback.
All reactions