I am looking to make contact with the maintainers of the SELinux policy
profile for Postfix on Fedora (presumably ultimately also RHEL), Debian
and other systems that ship with pre-installed SELinux policy rules for
Postfix.
If you're a maintainer of such policy rules please reach out. I had a
> 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
Viktor Dukhovni wrote:
FWIW, I'd like to recommend "recipient_bcc_maps" over always_bcc.
On Sat, Jan 20, 2024 at 05:44:25PM +0100, Simon Hoffmann 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
> >
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
On Sat, Jan 20, 2024 at 03:42:52PM +0100, Simon Hoffmann via Postfix-users
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
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
