- Previous message: Matt McAnelly: "Relaying a few emails after upgrade"
- Maybe in reply to: Scott Merrill: "After Queue BCC"
- Next in thread: mouss: "Re: After Queue BCC"
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ] [ attachment ]
|
|
|
From: Wietse Venema (no email)
Date: Mon Aug 01 2005 - 12:45:40 EDT
Scott Merrill:
> Hello all.
>
> I've searched for some time, and read a fair number of archive messages,
> but I haven't found anything addressing my need (quite possibly due to
> poor search terms on my part).
>
> Management wants to ensure that all emails from any sender at CLIENT are
> automatically sent to several local recipients. This needs to be done
> on the mail server to ensure that mail from CLIENT is always distributed
> internally regardless of which recipient PCs are running.
>
> 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.
> 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.
> 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!
> 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.
Wietse
|
|
|