New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

add a third option to temp. disable local mail delivery (for domain transfer purposes) #492

Open
rseffner opened this Issue Dec 7, 2017 · 2 comments

Comments

Projects
None yet
3 participants
@rseffner

rseffner commented Dec 7, 2017

There should be the posibillity to setup mail configuration for a domain without routing mails to local mailboxes.
This may be needed e.g. for situations of domaintransfer from any hoster to a froxlor using hoster.
If the *NIC knows the domain and froxlor knows the domain also, your (froxlor admins) customers will send mail to the new unknown mailboxes while rest of the world sends mail to the "old"/public mailboxes. REachability of this transfering customer is broken until setup, domain transfer and dns caches are ready - this takes usualy about 2 days (if you'r not able to route mail from your past provider to froxlor).

At the moment froxlor knows two states : domain is emailenabled or not. With disabling all alises, forwardings and mailboxes will be deleted. I'ld like to see a third state, which enables a parallel mail infrastructure : domain allows mailsettings (aliases, forwards, mailboxes up to fully functional smtp-auth and imap/pop3) but does not deliver local. Instead it should relay mail to offical MX.

At the moment I set inside SQL isemaildomain='2' and add official MX to postfix' relay_domains map. So I'm able to build the whole mail infrastructure, copy content and test access without loosing ability to contact the customer by official mail routing.

@d00p d00p self-assigned this Dec 8, 2017

@HolySephi

This comment has been minimized.

Show comment
Hide comment
@HolySephi

HolySephi Apr 6, 2018

Contributor

a third option for "isemaildomain" sounds useful - but adding anything as relay_domain should not be necessary because if postfix does not resolve the domain anymore (because the sql statement selects with WHERE isemaildomain = '1') the mail delivery should be working out-of-the-box for other domains on the Froxlor server.

Only users of the same domain as the one set to '2' won't be able to send mail to others because "Relay access denied"

Contributor

HolySephi commented Apr 6, 2018

a third option for "isemaildomain" sounds useful - but adding anything as relay_domain should not be necessary because if postfix does not resolve the domain anymore (because the sql statement selects with WHERE isemaildomain = '1') the mail delivery should be working out-of-the-box for other domains on the Froxlor server.

Only users of the same domain as the one set to '2' won't be able to send mail to others because "Relay access denied"

@rseffner

This comment has been minimized.

Show comment
Hide comment
@rseffner

rseffner Apr 6, 2018

Its not necessary for MTA but for FROXLOR. You are not able to manage mail settings als forwardings an mailboxes in FROXLOR without enabling e-mail. Because this is going hand in hand with dns (MX) and MTAs transport configuration through FROXLOR there is at the moment no posibility to set e-mail settings without being local mail destination.

rseffner commented Apr 6, 2018

Its not necessary for MTA but for FROXLOR. You are not able to manage mail settings als forwardings an mailboxes in FROXLOR without enabling e-mail. Because this is going hand in hand with dns (MX) and MTAs transport configuration through FROXLOR there is at the moment no posibility to set e-mail settings without being local mail destination.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment