Feature Request
Context
Is your Feature Request related to a Problem?
Right now, you need to modify the postfix config in order to use a bare domain (FAQ). I'd like to remove that requirement.
The warning which a misconfigured deploy can produce,
do not list domain in BOTH mydestination and virtual_mailbox_domains
has been mentioned in 23 issues, 2 open. Scanning though a few of them, I think many were related to an email account being @$myhostname and thus delivered with the local delivery agent rather than the virtual delivery agent.
Describe the Solution you'd like
I'd like to make the change described in that FAQ in the project's Postfix main.cf. So change
mydestination = $myhostname, localhost.$mydomain, localhost
to
mydestination = localhost.$mydomain, localhost
In fact, I don't know if those other two items are useful either... perhaps we should just unset mydestination altogether.
Are you going to implement it?
Yes, because I know the probability of someone else doing it is low and I can learn from it.
What are you going to contribute??
I'll contribute that change and modifications to relevant code. So I'd remove this workaround for LDAP, the root->postmaster alias, and maybe more.
Additional context
Alternatives you've considered
I can't really think of another solution. For inspiration, I looked at mailcow's main.cf. They don't assign $myhostname to mydestination.
Who will that Feature be useful to?
Anyone hosting on a bare domain. Possibly other people who have related issues that have gone stale.
What have you done already?
I've found that this change (just removing $myhostname, or unsetting mydestination completely) breaks three unit tests:
[SMTP] (delivery) delivers mail to existing account[SMTP] (delivery) user1 should have received 8 mails[SMTP] (delivery) mail for root was delivered
All three are broken because a locally sent message to root (with sendmail) isn't delivered correctly to [email protected]. I haven't investigated why yet.
Unsetting mydestination completely would prevent people from sending mail to system users of the container. But I can't imagine anyone does that now.
Feature Request
Context
Is your Feature Request related to a Problem?
Right now, you need to modify the postfix config in order to use a bare domain (FAQ). I'd like to remove that requirement.
The warning which a misconfigured deploy can produce,
has been mentioned in 23 issues, 2 open. Scanning though a few of them, I think many were related to an email account being
@$myhostnameand thus delivered with thelocaldelivery agent rather than thevirtualdelivery agent.Describe the Solution you'd like
I'd like to make the change described in that FAQ in the project's Postfix
main.cf. So changeto
In fact, I don't know if those other two items are useful either... perhaps we should just unset
mydestinationaltogether.Are you going to implement it?
Yes, because I know the probability of someone else doing it is low and I can learn from it.
What are you going to contribute??
I'll contribute that change and modifications to relevant code. So I'd remove this workaround for LDAP, the root->postmaster alias, and maybe more.
Additional context
Alternatives you've considered
I can't really think of another solution. For inspiration, I looked at mailcow's main.cf. They don't assign
$myhostnametomydestination.Who will that Feature be useful to?
Anyone hosting on a bare domain. Possibly other people who have related issues that have gone stale.
What have you done already?
I've found that this change (just removing
$myhostname, or unsettingmydestinationcompletely) breaks three unit tests:[SMTP] (delivery) delivers mail to existing account[SMTP] (delivery) user1 should have received 8 mails[SMTP] (delivery) mail for root was deliveredAll three are broken because a locally sent message to
root(withsendmail) isn't delivered correctly to[email protected]. I haven't investigated why yet.Unsetting
mydestinationcompletely would prevent people from sending mail to system users of the container. But I can't imagine anyone does that now.