On Tue, Jul 10, 2012 at 10:06:54AM +0200, Thomas Spycher wrote:
> Uhhh, this is a much more [sic] better Solution than getting this done
> by the content filter. I've set smtp_destination_recipient_limit = 1
I did point out that this should be a "dedicated" transport used
only for sending mail t
Uhhh, this is a much more better Solution than getting this done by the content
filter.
I've set smtp_destination_recipient_limit = 1 so every mail gets passed to the
content filter for each recipient and finally gets requeued as a complete new
mail. Perfect!
Thank you!
On Jul 10, 2012, at 02:
On Tue, Jul 10, 2012 at 12:45:34AM +0200, Jeroen Geilman wrote:
> I would probably opt to make it a fully controllable process by
> first queueing and re-injecting it into a second listener or postfix
> instance by utilizing ${second-smtpd}_recipient_limit = 1
Right idea, wrong implementation. A
On 07/09/2012 05:47 PM, Thomas Spycher wrote:
Hi,
if Postfix receives an mail with multiple recipients (eg. to, cc and bcc). This
mail gets processes as one single mail by postfix.
Only on reception; when it is queued, the message is duplicated as many
times as necessary to address all next-
Hi,
if Postfix receives an mail with multiple recipients (eg. to, cc and bcc). This
mail gets processes as one single mail by postfix. How could it get
accomplished to change the content of the mail for each recipient in an
different way?
Currently i've done this in an content filter. The Conte
