You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Just installed Mailflow and it sure looks promising!
I am self-hosting Exim and Dovecot, and now setting up Mailflow (using the recommended docker installation) on the same server. However, Mailflow does not allow me to set up an account on my mailserver, because "Host resolves to a private or reserved IP address". Which is true, as indeed the mail services run on the very same home-server.
Which leads me to the question: it appears it was a conscious decision to disallow access to localhost. Yet I am sure I am not the only self-hosting hobbyist that runs everything on the same server. What was the reason for the decision, and would it be possible to accommodate my use case?
reacted with thumbs up emoji reacted with thumbs down emoji reacted with laugh emoji reacted with hooray emoji reacted with confused emoji reacted with heart emoji reacted with rocket emoji reacted with eyes emoji
Uh oh!
There was an error while loading. Please reload this page.
-
Just installed Mailflow and it sure looks promising!
I am self-hosting Exim and Dovecot, and now setting up Mailflow (using the recommended docker installation) on the same server. However, Mailflow does not allow me to set up an account on my mailserver, because "Host resolves to a private or reserved IP address". Which is true, as indeed the mail services run on the very same home-server.
Which leads me to the question: it appears it was a conscious decision to disallow access to localhost. Yet I am sure I am not the only self-hosting hobbyist that runs everything on the same server. What was the reason for the decision, and would it be possible to accommodate my use case?
Thanks!
Beta Was this translation helpful? Give feedback.
All reactions