Re: Virtual Mailbox Delivery with mixed address classes.

2019-05-06 Thread Andreas Thienemann
Hi Viktor, On Mon, 6 May 2019, Viktor Dukhovni wrote: In most cases virtual(5) is superior to aliases(5), but you still need it for mailman and pipes, so you'd rewrite those to localhost (or some suitable domain listed in mydestination). Right. Good point. Something to keep in mind. To para

Re: Virtual Mailbox Delivery with mixed address classes.

2019-05-06 Thread Viktor Dukhovni
On Mon, May 06, 2019 at 03:47:58AM +0200, Andreas Thienemann wrote: > > If you're not using /etc/aliases or .forward files in any substantive > > way, you could switch to a virtual mailbox domain. > > No .forward files at all. Users do not have local accounts on the machine > anymore, except uuc

Re: Virtual Mailbox Delivery with mixed address classes.

2019-05-05 Thread Andreas Thienemann
Hi Viktor, On Sun, 5 May 2019, Viktor Dukhovni wrote: On Mon, May 06, 2019 at 02:38:15AM +0200, Andreas Thienemann wrote: I currently have a mailserver that serves as final destination for a domain, say example.com which is configured as mydestination. This works, but I generally prefer to

Re: Virtual Mailbox Delivery with mixed address classes.

2019-05-05 Thread Viktor Dukhovni
On Mon, May 06, 2019 at 02:38:15AM +0200, Andreas Thienemann wrote: > I currently have a mailserver that serves as final destination for a > domain, say example.com which is configured as mydestination. This works, but I generally prefer to not put any "real" domains in mydestination, with addre

Virtual Mailbox Delivery with mixed address classes.

2019-05-05 Thread Andreas Thienemann
Hi, I am trying to wrap my head around the different address classes and how to combine that with the virtual mailbox delivery system. I currently have a mailserver that serves as final destination for a domain, say example.com which is configured as mydestination. I have users on that doma