Replies: 6 comments
-
just my 2 cents |
Beta Was this translation helpful? Give feedback.
-
Thanks for your reply, I did have MTA-STS already disabled, but it still complains about the MX records. I disabled it in |
Beta Was this translation helpful? Give feedback.
-
have you set the logging level to debug? may be that will show more information on whats going on and what stalwart tries to test. |
Beta Was this translation helpful? Give feedback.
-
now i have same constellation. webadmin tells that a remote host could be fqdn or IP. |
Beta Was this translation helpful? Give feedback.
-
I figured out a workaround by creating a domain |
Beta Was this translation helpful? Give feedback.
-
SMTP / Outbound / Limit if stalwart is used in a mixed relay (some are delivered to remote hosts and some are delivered thru MX lookup) then this workaround isn't working. |
Beta Was this translation helpful? Give feedback.
-
I have a server at my home that is running stalwart. I have a VPS in the cloud which I use to access my home server and to port forward. I do this using a wireguard tunnel, so on the VPS I have
10.0.0.2
as my home server, and on my home server I have10.0.0.1
as my VPS.I have set up a SMTP relay on the VPS so that I can send emails through the VPS. On my home server stalwart instance, I setup relaying to the VPS. However, this only works with the domain,
mail.1e99.eu
and not using10.0.0.1
. When sending an EMail and having the relay server configured by IP, it complains that it can not find a MX record.In the docs it says that it requires a FQDN, but is there some way to bypass that restriction and refer to the host just by it's IP?
Beta Was this translation helpful? Give feedback.
All reactions