Mail is being delivered to /var/mail/*user* instead of Maildir

2022-04-05 Thread Tan Mientras
Hi We are migrating an old Debian 6 Postfix smarthost/relay server to a new one, just copying the configuration files and some other files to a fresh Ubuntu 20.04 system. For some reason, in the new environment, *mail is being delivered to /var/mail/user instead of Maildir (/home/vmail/user/Maild

Re: Q: configuring Postfix as a front for Exchange 365

2022-04-05 Thread Arrigo Triulzi
On 5 Apr 2022, at 22:17, Viktor Dukhovni wrote: > > On Tue, Apr 05, 2022 at 08:35:55PM +0200, Arrigo Triulzi wrote: >> On 5 Apr 2022, at 18:38, Bastian Blank >> wrote: >> >> Indeed, you did not but the virtual_alias_map is being ignored. Mmh, must >> have done something stupid. > > The param

Re: Q: configuring Postfix as a front for Exchange 365

2022-04-05 Thread Viktor Dukhovni
On Tue, Apr 05, 2022 at 08:35:55PM +0200, Arrigo Triulzi wrote: > On 5 Apr 2022, at 18:38, Bastian Blank > wrote: > > Indeed, you did not but the virtual_alias_map is being ignored. Mmh, must > have done something stupid. The parameter name is "virtual_alias_maps". -- Viktor.

Re: Q: configuring Postfix as a front for Exchange 365

2022-04-05 Thread Arrigo Triulzi
On 5 Apr 2022, at 18:38, Bastian Blank wrote: > > On Tue, Apr 05, 2022 at 06:15:49PM +0200, Arrigo Triulzi wrote: >> In retrospect the above doesn’t work - I set up some valid relay recipients >> in the map and the virtual_alias_map is never used because you cannot have >> both a relay_domain

Re: Q: configuring Postfix as a front for Exchange 365

2022-04-05 Thread Viktor Dukhovni
On Tue, Mar 22, 2022 at 08:38:39AM +0100, Arrigo Triulzi wrote: > Unfortunately I have a slight complication: for a subset of valid > email addresses I need to “bleed them” out to a different domain (and > also archive all email but that is simply done with always_bcc). > > For example: > > u...

Re: Q: configuring Postfix as a front for Exchange 365

2022-04-05 Thread Bastian Blank
On Tue, Apr 05, 2022 at 06:15:49PM +0200, Arrigo Triulzi wrote: > In retrospect the above doesn’t work - I set up some valid relay recipients > in the map and the virtual_alias_map is never used because you cannot have > both a relay_domain and a virtual_domain set. Where exactly did I show virt

Re: Q: configuring Postfix as a front for Exchange 365

2022-04-05 Thread Arrigo Triulzi
> > Well. > > main.cf: > parent_domain_matches_subdomains = > > relay_domains: > example.com exists > > relay_rcipient_maps: > b...@example.com exists > f...@example.com exists > > transport_maps: > example.com smtp:exchange > list.example.com smtp:list > > virtual_alias_maps: > l...@example.

Re: Q: configuring Postfix as a front for Exchange 365

2022-04-05 Thread Arrigo Triulzi
On 22 Mar 2022, at 12:51, Matus UHLAR - fantomas wrote: > > virtual_alias_maps can do this. > >> So far my idea was to use virtual domains and re-write users but I fall > > I have done this by setting up the domain into relay_domains and configuring > transport_maps: "example.com smtp:[exampl

Re: Q: configuring Postfix as a front for Exchange 365

2022-04-05 Thread Arrigo Triulzi
> On Tue, Mar 22, 2022 at 08:38:39AM +0100, Arrigo Triulzi wrote: >> I was hoping to be able to use a transport re-write but if I set it up it is >> ignored because of the virtual domain settings. > > Please show real configs. Yes, I apologise, I should have done this. Please also excuse the lat

Re: wildcards in smtp_connection_cache_destinations

2022-04-05 Thread Viktor Dukhovni
On Tue, Apr 05, 2022 at 04:37:29PM +0200, Matus UHLAR - fantomas wrote: > >Why DISABLE on-demand connection caching? > > I was under impression that disabling caching on demand turns is on by > default. That's not the case, it just disables demand caching. > and having it on by default require

Re: wildcards in smtp_connection_cache_destinations

2022-04-05 Thread Wietse Venema
Matus UHLAR - fantomas: > >Matus UHLAR - fantomas: > >> does prefix ".domain" apply for smtp_connection_cache_destinations? > >> (debian's 3.5.6 doesn't seem to accept that). > > On 05.04.22 10:26, Wietse Venema wrote: > >Is it documented to support this? > > > >What is documented is that smtp_con

Re: wildcards in smtp_connection_cache_destinations

2022-04-05 Thread Matus UHLAR - fantomas
Matus UHLAR - fantomas: does prefix ".domain" apply for smtp_connection_cache_destinations? (debian's 3.5.6 doesn't seem to accept that). On 05.04.22 10:26, Wietse Venema wrote: Is it documented to support this? What is documented is that smtp_connection_cache_destinations supports type:name

Re: wildcards in smtp_connection_cache_destinations

2022-04-05 Thread Wietse Venema
Matus UHLAR - fantomas: > Hello, > > does prefix ".domain" apply for smtp_connection_cache_destinations? > (debian's 3.5.6 doesn't seem to accept that). Is it documented to support this? What is documented is that smtp_connection_cache_destinations supports type:name tables so you could specify

wildcards in smtp_connection_cache_destinations

2022-04-05 Thread Matus UHLAR - fantomas
Hello, does prefix ".domain" apply for smtp_connection_cache_destinations? (debian's 3.5.6 doesn't seem to accept that). we send mail to domains where multiple subdomains suffer from the same problem, while having different servers (perhaps problem of the same admin or the same hardware). I m

Re: Solved

2022-04-05 Thread Byung-Hee HWANG
Viktor Dukhovni writes: > On Tue, Apr 05, 2022 at 12:54:55PM +0900, Byung-Hee HWANG wrote: > >> soyeomul@yw-1204:~$ cat /etc/postfix/relay_clientcerts >> D7:5B:D1:A0:EA:A1:8D:9F:7A:4D:77:47:AD:DE:2D:07 yw-0919.doraji.xyz >> 01:7A:51:89:E5:C0:07:17:51:66:0D:C5:77:F8:77:38 smtp.gmail.com > > These