- Previous message: mouss: "Re: After Queue BCC"
- Maybe in reply to: Scott Merrill: "After Queue BCC"
- Next in thread: Victor Duchovni: "Re: After Queue BCC"
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ] [ attachment ]
|
|
|
From: Scott Merrill (no email)
Date: Mon Aug 01 2005 - 12:53:08 EDT
Wietse Venema wrote:
>>I originally asked that we encourage CLIENT to manually include the
>>necessary recipients, but my suggestion was rejected. =(
>
>
> Perhaps you can convince them this is a bad idea when you point
> out that the sender would never be able to have a private email
> conversation when a bunch of people is always forced to listen in.
The nature of the business relationship is such that management isn't
concerned about private conversations.
>>As a first attempt, I created an alias, 'client', and used this in a
>>sender_bcc_maps:
>>sender_bcc_maps = hash:/etc/postfix/sender_bcc_maps
>>
>>$ cat /etc/postfix/sender_bcc_maps
>>@client.com
>>
>> is an alias populated by the virtual users who need to
>>receive these messages.
>>
>>This works fine for people not directly addressed by CLIENT in the
>>original messages; but people included on the To or Cc lines are getting
>>duplicate messages, causing some confusion.
>
>
> What gets in the way is Postfix's original recipient handling,
> which is used for proper attribution in bounces or final delivery.
>
> With Postfix < 2.3 that can be killed by turning off original
> recipient support. With Postfix 2.3, however, there is also DSN
> original recipient which can't be turned off.
>
>
>>I _think_ I want to use an after-queue content filter to modify the
>>incoming messages from CLIENT. I hacked Bennett Todd's smtpprox filter
>>to determine which local recipients were not already recieiving the
>>message, and then add a BCC header for them.
>
>
> You're manupulating SMTP mail. Adding a HEADER has no effect. You
> need to add an RCPT TO command.
Ah! That's the information I was lacking. Thank you!
>>Management really wants the _original_ message sent to all necessary
>>local recipients, so that they can see who else was included in the
>>original delivery. Otherwise I'd just use a script to forward copies to
>>the necessary recipients.
>
>
> But they can't see who the original recipients are, because there
> is no requirement for those recipients to be listed in any
> message headers at all!
No, there's no requirement for the recipients to be listed. But it's a
(very) safe bet that CLIENT won't do anything but send messages from
desktop MUAs to a few recipients at a time.
If I can automatically BCC (nee RCPT TO) the missing recipients, they
can look at the To and Cc lines as displayed in their MUA to see who
CLIENT was sending to.
>>I tried using smtpprox as a before-queue filter, but kept getting:
>>"warning: received garbage from proxy 127.0.0.1:10025: Received DATA
>>command, beginning filtering."
>
>
> Turn off verbose chatting.
Thanks again!
Cheers,
Scott
-- | http://skippy.net/ gpg --keyserver pgp.mit.edu --recv-keys 9CFA4B35 506C F8BB 17AE 8A05 0B49 3544 476A 7DEC 9CFA 4B35
|
|
|