Viktor Dukhovni via Postfix-users:
> On Wed, Jul 31, 2024 at 01:10:46PM -0400, Wietse Venema via Postfix-users
> wrote:
>
> > > > Now I tried to redirect mails from my private address sent to anybody
> > > > at charite.de to be redirected to someone else in the organisation,
> > > > like this:
>
* Viktor Dukhovni via Postfix-users :
> Making REDIRECT match naïve user expectations,
ey! :)
--
Ralf Hildebrandt
Geschäftsbereich IT | Abteilung Netz | Netzwerk-Administration
Invalidenstraße 120/121 | D-10115 Berlin
Tel. +49 30 450 570 155 | Fax: +49 30 450 570 962
ralf.hildebra...@ch
On Wed, Jul 31, 2024 at 01:10:46PM -0400, Wietse Venema via Postfix-users wrote:
> > > Now I tried to redirect mails from my private address sent to anybody
> > > at charite.de to be redirected to someone else in the organisation,
> > > like this:
> > >
> > > rxlf.hildebra...@gmail.com REDIRECT t
* Wietse Venema via Postfix-users :
> Is this an unexpanded virtual alias?
Yes
> The 'redirect' recipient is not subject
> to canonical mapping, masquerading, or virtual alias mapping.
That explains it.
> There were two recipients: the BCC recipient that was found in
> recipient_bcc_maps, and
I have updated some documentation:
> > We have an always_bcc setup in place for incoming mails:
> >
> > recipient_bcc_maps = pcre:/etc/postfix/backup_bcc.pcre
> >
> > /^(.*)@charite\.de$/backup+${1}=charite.de@backup.invalid
Added to the text f
Ralf Hildebrandt via Postfix-users:
> We have an always_bcc setup in place for incoming mails:
>
> recipient_bcc_maps = pcre:/etc/postfix/backup_bcc.pcre
>
> /^(.*)@charite\.de$/backup+${1}=charite.de@backup.invalid
>
> Now I tried to redirect mails from my pr
Ralf Hildebrandt via Postfix-users:
> > Jul 31 09:24:13 mail-cbf-int postfix/error[2664442]: 4WYk9n2SK3z20ycy:
> > to=,
> > orig_to=, relay=none,
> > delay=0.62, delays=0.57/0.02/0/0.03, dsn=5.1.1, status=bounced (User
> > unknown)
>
> It works, if I replace toscx.hrn...@charite.de with the ac
> Jul 31 09:24:13 mail-cbf-int postfix/error[2664442]: 4WYk9n2SK3z20ycy:
> to=,
> orig_to=, relay=none,
> delay=0.62, delays=0.57/0.02/0/0.03, dsn=5.1.1, status=bounced (User unknown)
It works, if I replace toscx.hrn...@charite.de with the actual mailbox
address after address expansion (thrn...
We have an always_bcc setup in place for incoming mails:
recipient_bcc_maps = pcre:/etc/postfix/backup_bcc.pcre
/^(.*)@charite\.de$/backup+${1}=charite.de@backup.invalid
Now I tried to redirect mails from my private address sent to anybody
at charite.de to be redirected to someone
r.barclay--- via Postfix-users:
> Hello,
>
> I have a Postfix installation for virtual mailboxes. It is the
> mail server (inbound MX and outbound) for a few domains. The server
> allows submission with SMTP AUTH (Dovecot SASL).
>
> At the moment I use always_bcc to "
Hello,
I have a Postfix installation for virtual mailboxes. It is the mail server
(inbound MX and outbound) for a few domains. The server allows submission with
SMTP AUTH (Dovecot SASL).
At the moment I use always_bcc to "copy" / mirror any inbound AND outbound
emails into an archi
On 12 Feb 2023, at 17:53, Wietse Venema wrote:
> To bcc to multiple recipients with existing Postfix versions, specify
> one address with always_bcc (or sender_bcc_maps or recipient_bcc_maps),
> and expand that into multiple recipients using virtual_alias_maps.
Right, so this match
Arrigo Triulzi:
> Hi,
>
> I was wondering what, if any, is the recommendation on how to have
> multiple recipients for always_bcc.
always_bcc accepts one recipient (as do sender_bcc_maps and
recipient_bcc_maps). Fixing that would require new code (I have
added this as a WISHLIST it
Hi,
I was wondering what, if any, is the recommendation on how to have multiple
recipients for always_bcc.
I was thinking of using something like alias@localhost and then expanding it
but I am concerned that it will go through mail filters (amavisd-new in my
case) multiple times.
Any
On Tue, Dec 20, 2022 at 9:46 AM Yanko Hernández Álvarez
wrote:
>
> That's a good one
>
> It seems possible. Let me check. The problem is the ldap query now.
> I'm not sure if I can do that with ldap. mailfilter does two ldap
> queries, one to lookup the "main" group/role and another to get the
gt; wrote:
>
> > On Mon, Dec 19, 2022 at 11:36 AM Matus UHLAR - fantomas
> > wrote:
> > > >#!/bin/sh
> > > >
> > > >/usr/bin/cat | /var/spool/filter/scripts/mailfilter |
> > > >/usr/sbin/sendmail -G -i "$@"
>
in/sendmail -G -i "$@"
> > >
> > >exit $?
> >
> > this means that the always_bcc is executed again.
> > usually the content_filter is supposed to inject mail on alternative port
> > where option:
> > receive_override_options = no_address_mappings
&
On Mon, Dec 19, 2022 at 11:36 AM Matus UHLAR - fantomas
wrote:
> >#!/bin/sh
> >
> >/usr/bin/cat | /var/spool/filter/scripts/mailfilter |
> >/usr/sbin/sendmail -G -i "$@"
> >
> >exit $?
>
> this means that the always_bcc is execute
se a post-queue content filter, *two* delivery
cycles are made per each email (before filter and after filter). During each
delivery a copy is sent to always_bcc. That's why you get two copies.
The best method (although maybe not simplest, in terms of coding) to fix
this is to replace after-queue f
o set up a very low traffic postfix mail server using:
- A Simple content filter
(http://www.postfix.org/FILTER_README.html#simple_filter). It's way
simpler than the advanced one and the traffic is low.
- dovecot as a delivery agent. (Because of maildir quotas and sieve filters)
- `always_bcc`
sing:
- A Simple content filter
(http://www.postfix.org/FILTER_README.html#simple_filter). It's way
simpler than the advanced one and the traffic is low.
- dovecot as a delivery agent. (Because of maildir quotas and sieve filters)
- `always_bcc` to keep copies of every mail sent. (Bussiness rule
Hi Wietse,
thank you for your help, all works fine.
Best regards
J.Karliak
Dne 2022-10-11 11:45, Wietse Venema napsal:
Josef Karliak:
Good morning,
what could cause the mail copied by postfix's always_bcc - copied
email is 2x or sometimes (?) 3x copied in the always_bcc
Josef Karliak:
>
>
>Good morning,
>
>what could cause the mail copied by postfix's always_bcc - copied
> email is 2x or sometimes (?) 3x copied in the always_bcc email.
>
>I use DKIM and DMARC milter and Spamassasisn as a
> "check_poli
Good morning,
what could cause the mail copied by postfix's always_bcc - copied
email is 2x or sometimes (?) 3x copied in the always_bcc email.
I use DKIM and DMARC milter and Spamassasisn as a
"check_policy_service". Could the passing to the milters cause it ?
Try sender_bcc_maps or recipient_bcc_maps.
once again, looking in the wrong place!
perfect, thx.
ix transport delivery targets, or not.
>
> Reading,
>
> https://www.postfix.org/postconf.5.html#always_bcc
>
> straightforward for bcc'ing all.
>
> But I don't immediately see that it support maps.
Try sender_bcc_maps or recipient_bcc_maps.
Wietse
On 2022-04-14 19:19, PGNet Dev wrote:
https://www.postfix.org/postconf.5.html#always_bcc
straightforward for bcc'ing all.
But I don't immediately see that it support maps.
maps what ?
(1) does always_bcc support maps? (doc or example?)
(2) is there a better alternative that
targets, or not.
Reading,
https://www.postfix.org/postconf.5.html#always_bcc
straightforward for bcc'ing all.
But I don't immediately see that it support maps.
(1) does always_bcc support maps? (doc or example?)
(2) is there a better alternative that always_bcc for this use?
> On 11 Jan 2022, at 3:43 am, Wietse Venema wrote:
>
> Recipients added with always_bcc, xxx_bcc_maps, etc., are treated
> just like any other recipients. All recipients are subject to
> content_filter, relayhost, etc.
Fortunately, they're also subject to transport tab
Zsombor B:
> Hi,
>
>
>
> We'd like to debug some emails sent through a multi instance withouth
> having any impact on the mail flow so I have added
> always_bcc=de...@whatever.com to the main.cf of that instance and
> reloaded it.
>
> But instead of sendin
My understanding is that always_bcc does not work:
- if receive_override_options includes no_address_mappings; or
- after Postfix has forwarded mail internally; or
- for mails generated by Postfix itself
On 10/01/2022 16:28, Zsombor B wrote:
We'd like to debug some emails sent through a
Hi,
We'd like to debug some emails sent through a multi instance withouth
having any impact on the mail flow so I have added
always_bcc=de...@whatever.com to the main.cf of that instance and
reloaded it.
But instead of sending copies of the emails to the debug address,
postfix r
On 20/04/2021 10:04, Matus UHLAR - fantomas wrote:
On 2021-04-16 12:03, Dominic Raferd wrote:
> I have started using a REDIRECT action in a header_checks table
> which works but seems to prevent always_bcc from operating -
> the email is not bcc'd.
On Fri, 16 Apr 2021, 20:07 Rob
Matus and Viktor, thank you for your responses!
I'm trying to add an additional BCC for some mail recipients but not for all.
All mails must go into the archive (always_bcc). This works so far.
But now, for some recipients, I'd like to have an additional BCC. So
recipient_bcc_maps s
On Mon, May 31, 2021 at 10:07:13AM +0200, r.barc...@habmalnefrage.de wrote:
> I use the "always_bcc" option to collect all emails for a local email archive.
>
> Can one use recipient_bcc_maps in addition to that?
>
> So I could make emails to "u...@example.org&qu
On 31.05.21 10:07, r.barc...@habmalnefrage.de wrote:
I use the "always_bcc" option to collect all emails for a local email archive.
Can one use recipient_bcc_maps in addition to that?
this worked here iirc.
So I could make emails to "u...@example.org" go into the archi
Hello!
I use the "always_bcc" option to collect all emails for a local email archive.
Can one use recipient_bcc_maps in addition to that?
So I could make emails to "u...@example.org" go into the archive (always_bcc)
and also to another BCC address defined through recipie
>> > receive_override_options = no_address_mappings
>> >
>> > and then permit mappings (which include always_bcc) to occur in the 2nd
>> > instance (for the mail that is returned by amavis), for example this
>> > might be in master.cf by:
Hi,
> > > > I thought I said transport...
> > >
> > > Postfix instance 1
> > >
> > > main.cf
> > > always_bcc = f...@example.com
> > >
> > > transport_maps
> > > f...@example.com -> Postfix instance 2
On Wed, Apr 21, 2021 at 04:19:52PM -0400, Alex wrote:
> > > I thought I said transport...
> >
> > Postfix instance 1
> >
> > main.cf
> > always_bcc = f...@example.com
> >
> > transport_maps
> > f...@example.com -> Postfix in
Alex:
> > It is more or less Viktor's suggestion.
> >
> > Some details will be missing: relay_domains needs to be set u so
> > that Postfix instance 1 won't reject mail with "relay access denied".
>
> Thanks for sticking with me here. That's a pretty big change for me.
> Victor helped me create th
Hi,
> Wietse:
> > Postfix instance 1
> >
> > main.cf
> > always_bcc = f...@example.com
> >
> > transport_maps
> > f...@example.com -> Postfix instance 2
> > all other mail -> content filter -> Postfix instance 2
> >
Wietse:
> Postfix instance 1
>
> main.cf
> always_bcc = f...@example.com
>
> transport_maps
> f...@example.com -> Postfix instance 2
> all other mail -> content filter -> Postfix instance 2
>
> Perhaps a picture is worth 1e3 words.
Alex:
ng special with Bcc mail).
> >
> > > Or perhaps local_recipient_maps? mydestination is not currently
> > > defined for this instance.
> >
> > I thought I said transport...
>
> Postfix instance 1
>
> main.cf
> always_bcc = f...@example.com
>
route that domain (via a suitable
> transport table entry) to a separate transport (perhaps bypass amavis
> entirely, unless you need amavis to do something special with Bcc mail).
>
> > Or perhaps local_recipient_maps? mydestination is not currently
> > defined for this instance.
On Wed, Apr 21, 2021 at 03:53:34PM -0400, Alex wrote:
> > This is why you have a multi-instance configuration. You can use the
> > transport table to selectively route specific recipients to specific
> > filter transports, ... by avoiding content_filter and using normal
> > Postfix transport-base
> > I should have made that more clear. The problem is that I'm trying to
> > create an address to which amavisd should forward all mail unfiltered,
> > but it only works if either all addresses are included in the policy
> > or the unfiltered address is the only address.
>
> This is why you have a
On Wed, Apr 21, 2021 at 03:29:07PM -0400, Alex wrote:
> I should have made that more clear. The problem is that I'm trying to
> create an address to which amavisd should forward all mail unfiltered,
> but it only works if either all addresses are included in the policy
> or the unfiltered address
7;s the problem?
>
> >> > If you are running amavis as a content filter, you need the initial
> >> > postfix instance (which feeds into amavis) to have
> >> >
> >> > receive_override_options = no_address_mappings
> >> >
> >> &g
> > How do I configure always_bcc to bypass amavisd altogether so it isn't
> > processed at all?
> >
> > # postconf -c /etc/postfix-116 always_bcc
> > always_bcc = bcc-user
> >
> > I'm unsure what postconf details I can provide, so I'll in
On Wed, Apr 21, 2021 at 11:17:19AM -0400, Alex wrote:
> I have postfix configured in a multi-instance setup in conjunction
> with amavisd. I'm using always_bcc to create a copy of each email sent
> or received.
This does not create a "copy", it adds a recipient to the me
Hi,
> > > How do I configure always_bcc to bypass amavisd altogether so it isn't
> > > processed at all?
> > >
> > > # postconf -c /etc/postfix-116 always_bcc
> > > always_bcc = bcc-user
> > >
> > > I'm unsure what postconf
Hi,
On Wed, Apr 21, 2021 at 11:31 AM Dominic Raferd wrote:
>
> On 21/04/2021 16:17, Alex wrote:
> > I have postfix configured in a multi-instance setup in conjunction
> > with amavisd. I'm using always_bcc to create a copy of each email sent
> > or received.
>
On 21/04/2021 16:17, Alex wrote:
I have postfix configured in a multi-instance setup in conjunction
with amavisd. I'm using always_bcc to create a copy of each email sent
or received.
The problem is that, while postfix appears to deliver the bcc-user
email separately from the other recip
Hi,
I have postfix configured in a multi-instance setup in conjunction
with amavisd. I'm using always_bcc to create a copy of each email sent
or received.
The problem is that, while postfix appears to deliver the bcc-user
email separately from the other recipients, amavis somehow delivers t
On 2021-04-16 12:03, Dominic Raferd wrote:
> I have started using a REDIRECT action in a header_checks table
> which works but seems to prevent always_bcc from operating -
> the email is not bcc'd.
On Fri, 16 Apr 2021, 20:07 Rob McGee, wrote:
It's ugly, but a possible work
On Fri, 16 Apr 2021, 20:07 Rob McGee, wrote:
> On 2021-04-16 12:03, Dominic Raferd wrote:
> > I have started using a REDIRECT action in a header_checks table
> > which works but seems to prevent always_bcc from operating -
> > the email is not bcc'd.
>
> It&#
On 2021-04-16 12:03, Dominic Raferd wrote:
I have started using a REDIRECT action in a header_checks table
which works but seems to prevent always_bcc from operating -
the email is not bcc'd.
It's ugly, but a possible workaround: REDIRECT to an address which
runs a script (transport_
On 16/04/2021 18:39, Wietse Venema wrote:
Dominic Raferd:
I have started using a REDIRECT action in a header_checks table which
works but seems to prevent always_bcc from operating - the email is not
bcc'd.
REDIRECT is a blunt tool that ignores all recipients. If there are
multiple red
Dominic Raferd:
> I have started using a REDIRECT action in a header_checks table which
> works but seems to prevent always_bcc from operating - the email is not
> bcc'd.
REDIRECT is a blunt tool that ignores all recipients. If there are
multiple redirect actions, then the last ac
I have started using a REDIRECT action in a header_checks table which
works but seems to prevent always_bcc from operating - the email is not
bcc'd.
I tried adding a subsequent BCC action triggered by the same header text
but it has no effect. I realise that this is consistent
On Fri, Mar 05, 2021 at 04:25:38AM -0500, Viktor Dukhovni wrote:
> There are only two common ways a message without duplicated recipients
> gets delivered to the same mailbox twice:
>
>1. Address rewriting (including BCC maps) duplicates a recipient,
> and "enable_original_recipient" is
Tom Hendrikx:
> Isn't this as simple as:
>
> 1. new email comes in, is delivered to content filter, with bcc to
> always_bcc recipient.
That is what is supposed to happen.
But see my description of what happens with a broken configuration.
> 2. content filter re-injects
On Fri, Mar 5, 2021 at 4:26 AM Viktor Dukhovni
wrote:
>
> On Fri, Mar 05, 2021 at 03:41:06AM -0500, Steve Dondley wrote:
>
> > Here are postfix config file: https://pastebin.com/bZxjHF5y
>
> I don't usually go chasing pastebin URLs...
>
> > Hopefully something jumps out at you.
>
> There are only
> 1. new email comes in, is delivered to content filter, with bcc to
> always_bcc recipient.
> 2. content filter re-injects email into the queue for final delivery,
> postfix performs final delivery, with bcc to the always_bcc recipient?
>
> Since these are 2 separate deliveri
On Fri, Mar 05, 2021 at 03:41:06AM -0500, Steve Dondley wrote:
> Here are postfix config file: https://pastebin.com/bZxjHF5y
I don't usually go chasing pastebin URLs...
> Hopefully something jumps out at you.
There are only two common ways a message without duplicated recipients
gets delivered
comes in, is delivered to content filter, with bcc to
always_bcc recipient.
2. content filter re-injects email into the queue for final delivery,
postfix performs final delivery, with bcc to the always_bcc recipient?
Since these are 2 separate deliveries (with different routes) as far as
postfix is
> You may also have disabled recipient duplication. We will
> never knwo unles yo reveal yur configration as described
> in http://www.postfix.org/DEBUG_README.html#mail.
I've been looking at this a lng time tonight. Despite my best
efforts, I did not find a reason for the duplicate email.
I
Steve Dondley:
> > If 'always_bcc' produces three copies (with spamassassin turned on)
> > for one email message with three recipients, then Postfix is
>
> It's actually generating 3 emails even if sending to only one recipient.
Consider that Postfix deduplicat
> If 'always_bcc' produces three copies (with spamassassin turned on)
> for one email message with three recipients, then Postfix is
It's actually generating 3 emails even if sending to only one recipient.
> mis-configured, for example, to deliver three one-recipient m
=spamassassin"
>
> However, if I want to leave that in (which I apparently do), how do I
> properly stop duplicates from happening?
If 'always_bcc' produces three copies (with spamassassin turned on)
for one email message with three recipients, then Postfix is
mis-configure
> do a lot of your own homework (because everyone here is busy). If this
> doesn't appeal, consider using a recipe for a postfix-based mail server
> such as https://mailinabox.email/ or https://www.iredmail.org/. You lose
> the flexibility of a bespoke setup but you get back some of your life -
> I
OK, I don't feel quite so foolish. The guide here is what I apparently
followed when I initially set up spamassassin:
https://wiki.debian.org/DebianSpamAssassin
So I now know how to fix the duplicates by removing the "-o
content_filter=spamassassin"
However, if I want to leave that in (which I a
I think I found the root cause of the problem (other than me being a
clueless idiot). I had this in my master.cf:
smtp inet n - y - -smtpd
-o content_filter=spamassassin
submission inet n - y - -smtpe
-o content_filter=spamassassin
Does the Postfix configuration send three copies to the filter, one for each
recipient?
Don't do that, it is wasteful.
Wietse
On Thu, Mar 04, 2021 at 01:24:59PM -0500, Steve Dondley wrote:
> After staring at these logs some more and piecing together the advice
> here, here's my understanding of what's happening:
>
> * Mail comes in via smtpd as user sends mail. It's going to 3
> recipients. I'm not sure who those might
After staring at these logs some more and piecing together the advice
here, here's my understanding of what's happening:
* Mail comes in via smtpd as user sends mail. It's going to 3
recipients. I'm not sure who those might be. Maybe the catchall
account and the two users the email is going to?
*
Here's an anonymized pastebin example of my actual log entries of an
outgoing email that generated 3 copies: https://pastebin.com/cw2XB5jp
to the "catchall" mailbox.
> It is worthwhile to know if the duplicates are caused by adding
> multiple 'always_bcc' a
> - mail comes to postfix (smtp or local injection)
> = address mappings (always_bcc) happen
> - postfix sends mail to spamassassin
> - spamassassin scans mail and sends to postfix
> = address mappings (always_bcc) happen
>
> one of those should be avoided by no_addres
(smtp or local injection)
= address mappings (always_bcc) happen
- postfix sends mail to spamassassin
- spamassassin scans mail and sends to postfix
= address mappings (always_bcc) happen
one of those should be avoided by no_address_mappings but choose wisely...
I'm on debian. As far as I
nds messages back info Postfix similar to
http://www.postfix.org/FILTER_README.html#simple_filter
It is worthwhile to know if the duplicates are caused by adding
multiple 'always_bcc' addresses to the same queue file.
Look for logging with "message-id=".
Mar 4 01:05:05 mail postfi
> The info can be found in the maillog file, and the Received: headers
> of the messages as delivered. Welcome to the vortex.
After a close inspection of the headers, I can see that all the email
received have headers injected by spamassassin and this revealing
line:
"Received: by email.example.c
Steve Dondley:
> > you only use should no_address_mappings if your mail loops back, not
> > generally - you usually want alias expantion, canonical mapping, and
> > automatic BCC (at least if you configure any of those).
>
> Sorry, I don't follow you.
>
> I'm on debian. As far as I can gather, al
> you only use should no_address_mappings if your mail loops back, not
> generally - you usually want alias expantion, canonical mapping, and
> automatic BCC (at least if you configure any of those).
Sorry, I don't follow you.
I'm on debian. As far as I can gather, all mail related activity is
lo
On Thu, Mar 4, 2021 at 7:48 AM Dominic Raferd wrote:
>
> On 04/03/2021 11:42, Steve Dondley wrote:
> >> On 03.03.21 18:23, Steve Dondley wrote:
> >>> I have enabled the always_bcc setting with:
> >>>
> >>> always_bcc = exam...@example.org
>
On 04/03/2021 11:42, Steve Dondley wrote:
On 03.03.21 18:23, Steve Dondley wrote:
I have enabled the always_bcc setting with:
always_bcc = exam...@example.org
It works, but I'm getting everything three times. How do I prevent duplicates?
this can happen if you use content_filter that
>-o content_filter=spamassassin
the question is, how does spamassassin push mail back to postfix.
On 04.03.21 07:06, Steve Dondley wrote:
I have no earthly idea. Not sure how SA works, exactly.
It's not how SA works, it's how it's configured in master.cf.
And it makes me wonder if I'm brea
>
>
>
> >-o content_filter=spamassassin
>
> the question is, how does spamassassin push mail back to postfix.
I have no earthly idea. Not sure how SA works, exactly. And it makes me
wonder if I'm breaking spam assassin by adding
-o receive_override_options=no_address_mappings
to my configuratio
On 03.03.21 18:23, Steve Dondley wrote:
>I have enabled the always_bcc setting with:
>
>always_bcc = exam...@example.org
>
>It works, but I'm getting everything three times. How do I prevent duplicates?
this can happen if you use content_filter that feeds mail back to postf
> On 03.03.21 18:23, Steve Dondley wrote:
> >I have enabled the always_bcc setting with:
> >
> >always_bcc = exam...@example.org
> >
> >It works, but I'm getting everything three times. How do I prevent
> >duplicates?
>
> this can happen if you
On 03.03.21 18:23, Steve Dondley wrote:
I have enabled the always_bcc setting with:
always_bcc = exam...@example.org
It works, but I'm getting everything three times. How do I prevent duplicates?
this can happen if you use content_filter that feeds mail back to postfix.
in these cases
> the parameters themselves.
>
> Wietse
>
> > On Wed, Mar 3, 2021 at 6:23 PM Steve Dondley wrote:
> > >
> > > I have enabled the always_bcc setting with:
> > >
> > > always_bcc = exam...@example.org
> > >
> > > It work
e at all,
> however. Is there a good basic tutorial that explains it?
http://www.postfix.org/master.5.html describes the syntax of "-o
name=value", and http://www.postfix.org/postconf.5.html describes
the parameters themselves.
Wietse
> On Wed, Mar 3, 2021 at 6:23 PM Steve D
Steve Dondley:
> I have enabled the always_bcc setting with:
>
> always_bcc = exam...@example.org
>
> It works, but I'm getting everything three times. How do I prevent duplicates?
Postfix by default deduplicates if one message has multiple identical
recipients. Ho
hat explains it?
On Wed, Mar 3, 2021 at 6:23 PM Steve Dondley wrote:
>
> I have enabled the always_bcc setting with:
>
> always_bcc = exam...@example.org
>
> It works, but I'm getting everything three times. How do I prevent duplicates?
--
Prometheus Labor Communication
I have enabled the always_bcc setting with:
always_bcc = exam...@example.org
It works, but I'm getting everything three times. How do I prevent duplicates?
I thought I could just generally throttle the default
delivery, and create another delivery agent that increases concurrency
for domains I know to be able to manage what is normally the default.
Hopefully that makes sense.
The problem is that I'm using always_bcc to deliver a copy of each
ema
Prince Law Offices:
> Thanks for the response, and sorry for my delayed reaction.
>
> I understand that always_bcc should send a copy to the address
> indicated or the alias of the address indicated. My situation is
> slightly different. It?s the initial recipient (the To:) th
Thanks for the response, and sorry for my delayed reaction.
I understand that always_bcc should send a copy to the address indicated or the
alias of the address indicated. My situation is slightly different. It’s the
initial recipient (the To:) that is aliased AND uses a transport to
always_bcc is implemented upon receving email, so that
always_bcc = arch...@example.com
will send a copy to arch...@example.com, unless you have aliased
that to something else. In that case, your BCC copy will be sent
there.
For example if you have a wild-card alias
@example.com
1 - 100 of 268 matches
Mail list logo
