Re: Is the /etc/aliases file an anachronism on modern systems running OpenSMTPD?

2016-03-29 Thread Gilles Chehade
On Wed, Mar 23, 2016 at 09:38:12AM -0700, Seth wrote:
> I've been running several OpenSMPTD servers on OpenBSD for a while now
> without using the /etc/aliases file.
> 
> I'm having issues however with annoying email being generated from the
> r...@mx.domain.tld and mailer-dae...@mx.domain.tld addresses which get stuck
> in the delivery queue because I don't have the systems configured to accept
> email at the mx.domain.tld subdomain.
> 

Not quite sure I understand how this is related to aliases


> Maybe this is more of a question for the OpenBSD list, but I'm wondering if
> in this day and age, the '/etc/aliases' file is really just a dumb clunky
> sendmail throwback that needs to die in a fire and is unnecessary on modern
> OpenBSD/OpenSMTPD systems.
>

I don't know if you're talking about the aliases mechanism or the aliases
file itself, so I'll give you my opinion (fwiw) on this.

The aliases mechanism is not just a dumb clunky sendmail throwback, it has
use-cases that are very valid, that can't be achieved without aliases, and
that cannot be fullfilled with the "virtual" mechanism.

The /etc/aliases or /etc/mail/aliases file however is historical and comes
from a time where you would simply assume that one MX == one set of users.
I don't know about other MTA, but OpenSMTPD supporting per-domain userbase
we also had to support per-domain aliases mappings and so it does not make
sense to define one "aliases" file when there can be one per rule.

 
> If it's not necessary, is there anyway that I can force all system email
> generated for the root user to go to a designated email of my choosing,
> without having to use /etc/aliases and add the corresponding table and
> accept lines in smptd.conf? I can edit the cron /etc/daily|weekly|monthly
> scripts but that does not seem to address the smtpd daemon generated error
> messages.
>

something like (untested but you get the idea):

table myalias { root = gil...@poolp.org }
accept from any for any recipient root alias 


> Curious to know how other OpenSMTPD users address 'the aliases' question.
> 

I have /etc/mail/aliases-opensmtpd.org and used to also have
/etc/mail/aliases-poolp.org but no longer needed it



-- 
Gilles Chehade

https://www.poolp.org  @poolpOrg

-- 
You received this mail because you are subscribed to misc@opensmtpd.org
To unsubscribe, send a mail to: misc+unsubscr...@opensmtpd.org



Is the /etc/aliases file an anachronism on modern systems running OpenSMTPD?

2016-03-23 Thread Seth
I've been running several OpenSMPTD servers on OpenBSD for a while now  
without using the /etc/aliases file.


I'm having issues however with annoying email being generated from the  
r...@mx.domain.tld and mailer-dae...@mx.domain.tld addresses which get  
stuck in the delivery queue because I don't have the systems configured to  
accept email at the mx.domain.tld subdomain.


Maybe this is more of a question for the OpenBSD list, but I'm wondering  
if in this day and age, the '/etc/aliases' file is really just a dumb  
clunky sendmail throwback that needs to die in a fire and is unnecessary  
on modern OpenBSD/OpenSMTPD systems.


If it's not necessary, is there anyway that I can force all system email  
generated for the root user to go to a designated email of my choosing,  
without having to use /etc/aliases and add the corresponding table and  
accept lines in smptd.conf? I can edit the cron /etc/daily|weekly|monthly  
scripts but that does not seem to address the smtpd daemon generated error  
messages.


Curious to know how other OpenSMTPD users address 'the aliases' question.

--
You received this mail because you are subscribed to misc@opensmtpd.org
To unsubscribe, send a mail to: misc+unsubscr...@opensmtpd.org