[pfx] Re: Authentication question

michaelof--- via Postfix-users wrote: > > Thank you so much for answering, Wietse! > > Followed your recommendations, master.cf for submission and smtps now looks > as follows: > > > Opened smtps service in firewalld. > > Changed email user config for testing in Thunderbird from port 578

[pfx] Re: Change unknown_address_reject_code on a smarthost to a 5xx reply?

Matus UHLAR - fantomas via Postfix-users wrote: > On 15.02.24 15:27, Simon Hoffmann via Postfix-users wrote: > > I have a dedicated postfix machine that I use as a smarthost for all my > > outgoing > > email from my internal servers. The smarthost even has only ports 465 and

[pfx] Re: Change unknown_address_reject_code on a smarthost to a 5xx reply?

Jaroslaw Rafa via Postfix-users wrote: > Dnia 15.02.2024 o godz. 15:27:48 Simon Hoffmann via Postfix-users pisze: > > > > - it took 4h for the sender to get a notification that the domain was not > > found > > - after they "corrected" it by sending a secon

[pfx] Change unknown_address_reject_code on a smarthost to a 5xx reply?

Hello all, I have a dedicated postfix machine that I use as a smarthost for all my outgoing email from my internal servers. The smarthost even has only ports 465 and 587 enabled/opened. Recently we had the case that an internal used composer an email to an external recipient and had a typo

[pfx] Re: problem to add, alias failed

Maurizio Caloro via Postfix-users wrote: > if adding a new user with postfixadmin 3.3.8 or with cli this will run > without problem. > > > > GRANT ALL PRIVILEGES ON mailserver.* TO markus@'domain.com > ' IDENTIFIED BY > '***';

[pfx] Re: Preparation of switch from OpenSMTPd to Postfix -> syntax/behaviuor of virtual_alias_maps

Viktor Dukhovni via Postfix-users wrote: > On Sun, Jan 21, 2024 at 07:21:26PM +0100, Simon Hoffmann via Postfix-users > wrote: > > > The old virtual_domains file just lists all domains (one per line), and can > > directly be used in > > virtual_alias_domai

[pfx] Preparation of switch from OpenSMTPd to Postfix -> syntax/behaviuor of virtual_alias_maps

Hey all, I found a second topic where I am not sure how postfix behaves. The old virtual_domains file just lists all domains (one per line), and can directly be used in virtual_alias_domains. However, in my virtual aliases table on OpenSMTPd, I have the following line-types

[pfx] Re: Preparation of switch from OpenSMTPd to Postfix -> behaviour of smtpd_sender_login_maps pattern matching

Viktor Dukhovni wrote: > > > - You may want to "preserve the envelope", by generating a > > > recipient-specific bcc address. Just "always_bcc" fails > > > to record "bcc" recipients, and may record header recipients > > > who weren't actually (envelope) recipients of the

[pfx] Re: Preparation of switch from OpenSMTPd to Postfix -> behaviour of smtpd_sender_login_maps pattern matching

Viktor Dukhovni wrote: > > > I am currently planning to switch from OpenSMTPd to postfix for two reasons > > > > - smtpd_sender_login_maps functionality not really implemented in OpenSMTPd > > - always_bcc not possible on OpenSMTPd > > FWIW, I'd like to recommend "recipient_bcc_maps" over

[pfx] Preperation of switch from OpenSMTPd to Postfix -> behaviour of smtpd_sender_login_maps pattern matching

Hey yall, I am currently planning to switch from OpenSMTPd to postfix for two reasons - smtpd_sender_login_maps functionality not really implemented in OpenSMTPd - always_bcc not possible on OpenSMTPd While reading up on the postfix manual for smtpd_sender_login_maps I've read that postfix