On Sun, Jan 21, 2024 at 06:53:58PM +0100, Simon Hoffmann via Postfix-users
wrote:
> > This copies only the message headers and body, but fails to capture the
> > message envelope, which contains the true recipient list. With
> > per-recipient addressing in "recipient_bcc_maps", and provided the
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
> 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
