News for hackers. Stuff that matters.
Re:Announcing Notqmail by amaccuish on Tuesday August 20, 2019 @08:22PM (#20753585)
I've got a similar thing with my postfix setup though. My users can go to their account portal and apply for an alias, which when approved (to avoid taking of important names like postmaster etc.) is added to their otherMailboxes LDAP attribute. They can delete the alias themselves when they're done with it.

I'm tempted to start auto-allowing new aliases and just having a list of names that can't be used (postmaster, webmaster) etc, that some services use for domain ownership verification.

As an aside I do hope qmail offers similar limiting abilities. It wouldn't be great if a user could make themselves receive [email protected] emails!

Re:Announcing Notqmail by schmonz on Tuesday August 20, 2019 @09:11PM (#20753815)
They can’t, unless qmail has been configured to know they control mail for domain.tld. The admin configuration mechanism for this (control/virtualdomains) is simple and powerful.
Re:Announcing Notqmail by amaccuish on Wednesday August 21, 2019 @05:25AM (#20755680)
Sorry I'm confused. If your mail server is setup for control of a domain (e.g. domain.tld), then what stops someone from putting [email protected] in this .qmail file?
Re:Announcing Notqmail by schmonz on Wednesday August 21, 2019 @09:50AM (#20757107)
People can put whatever they want in their own .qmail files. That doesn't affect anything unless qmail believes those .qmail files are relevant to what it's delivering. A user controls .qmail files for a domain if and only if an admin has configured qmail to delegate that domain to that user.
Re:Announcing Notqmail by amaccuish on Thursday August 22, 2019 @05:09AM (#20766082)
Ahh I see. So it's a per domain thing, and you can't restrict more granularly. That's a shame.
Re:Announcing Notqmail by schmonz on Friday August 23, 2019 @11:10AM (#20778415)
I haven't experienced a need for more granular restrictions. Can you give an example of a problem it would solve?