Hi, Can I follow up on this? I can't figure out why always_bcc mail is being sent through the default content filter while mail designated for my domain-specific transport is sent through another in my multi-instance postfix config. I'd like the always_bcc user mail to still benefit from being filtered through amavis, but through the transport designed for the domain for which it was intended.
local_transport = error:5.1.1 Mailbox unavailable default_transport = smtp:[127.0.0.1]:10024 relay_transport = $default_transport virtual_transport = $default_transport transport_maps = ${indexed}transport /etc/postfix-120/transport domain1.com alex:[127.0.0.1]:10029 I've tried adding "receive_override_options = no_address_mappings" in main.cf but it seems to be ignored. I thought it might be helpful to show the log entries (except for the more involved amavisd entries). cable.example.com is my mail router. domain1.com is the recipient domain. I believe this shows how the mail goes from gmail.com to the domain1.com transport on port 10029 (amavisd). Both emails were then sent back to postfix-out on 10025 to be relayed on (or the always_bcc user to be delivered locally). Maybe this is even the preferred approach? I'm not used to seeing it this way, but I would think the transport corresponding with the recipient would be the one that should be used for the always_bcc user. May 21 13:40:12 cable postfix-120/qmgr[3714211]: 494948B53: from=< mysqlstud...@gmail.com>, size=3214, nrcpt=2 (queue active) May 21 13:40:12 cable amavis[3558243]: (3558243-06) ESMTP [127.0.0.1]:10024 /var/spool/amavisd/tmp/amavis-20230521T020900-3558243-jefENl_V: < mysqlstud...@gmail.com> -> <bcc-u...@cable.example.com> SIZE=3214 Received: from cable.example.com ([145.239.111.120]) by localhost (cable.example.com [127.0.0.1]) (amavis, port 10024) with ESMTP for <bcc-u...@cable.example.com>; Sun, 21 May 2023 13:40:12 -0400 (EDT) May 21 13:40:12 cable amavis[3558246]: (3558246-06) ESMTP [127.0.0.1]:10029 /var/spool/amavisd/tmp/amavis-20230521T032452-3558246-T4MBowCR: < mysqlstud...@gmail.com> -> <jre...@domain1.com> Received: from cable.example.com ([145.239.111.120]) by localhost (cable.example.com [127.0.0.1]) (amavis, port 10029) with ESMTP for <jre...@example.com>; Sun, 21 May 2023 13:40:12 -0400 (EDT) May 21 13:40:18 cable amavis[3558246]: (3558246-06) yz4rjN5FRAbF FWD from < mysqlstud...@gmail.com> -> <jre...@example.com>, BODY=7BIT 250 2.0.0 from MTA(smtp:[127.0.0.1]:10025): 250 2.0.0 Ok: queued as 0671630014B43 May 21 13:40:18 cable amavis[3558243]: (3558243-06) 1GoUW-HU8Lsg FWD from < mysqlstud...@gmail.com> -> <bcc-u...@cable.example.com>, BODY=7BIT 250 2.0.0 from MTA(smtp:[127.0.0.1]:10025): 250 2.0.0 Ok: queued as 070A730014B58 May 21 13:40:18 cable postfix/alex/smtp[3719703]: 494948B53: to=< jre...@domain1.com>, relay=127.0.0.1[127.0.0.1]:10029, delay=6.9, delays=1.2/0.02/0.01/5.7, dsn=2.0.0, status=sent (250 2.0.0 from MTA(smtp:[127.0.0.1]:10025): 250 2.0.0 Ok: queued as 0671630014B43) May 21 13:40:19 cable postfix-out/smtp[3719782]: 0671630014B43: to=< jre...@domain1.com>, relay=68.195.111.42[68.195.111.42]:25, delay=1.2, delays=0.01/0.02/0.82/0.33, dsn=2.0.0, status=sent (250 2.0.0 Ok: queued as E293A8078BEB) Thanks, Alex >> > Maybe my issue is that the always_bcc user is going through a transport >> at >> > all, and instead should just be delivered locally, or perhaps processed >> > only by the local_transport? How can I do that? >> > >> > I recall many years ago doing that, before I set up multi-instance >> postfix. >> >> A not uncommon issue is that virtual alias expansion or other address >> rewriting actions are performed twice, once on each side of a >> content_filter. This is covered in the "Advanced content filter: >> requesting that all mail is filtered" section of: >> >> http://www.postfix.org/FILTER_README.html#advanced_filter >> >> (receive_override_options). >> >> And of course you can always go multi-instance, and configure suitable >> rewriting for the pre and post filter instances. >> > > Yes, that's exactly what I'd like to do. I have multi-instance already > configured, but adding always_bcc to postfix-out doesn't seem to work. > > I've also just experimented with "receive_override_options = > no_address_mappings" (I also remember doing that many years ago, but would > have never been able to figure that out on my own this time), and it now > just doesn't actually create a copy of the email for the always_bcc user. > > Ideas on how to do it in my postfix-out instance? Ideally, I'd like it to > have been processed by amavis so I can benefit from the additional header > info. > > >
_______________________________________________ Postfix-users mailing list -- postfix-users@postfix.org To unsubscribe send an email to postfix-users-le...@postfix.org