Tenyo,
> Indeed, I should remove the X-Envelope-To
> header before releasing the e-mail.
Right.
Also you may want to remove X-Envelope-From (possibly redundant,
depending if you re-send with the original sender address
or you supply a different one), and X-Quarantine-ID (as you like).
If releas
Thanks for the feedback! Indeed, I should remove the X-Envelope-To
header before releasing the e-mail. In my case I'm using SQL for the
quarantine, so all recipients are entered into the msgrcpt table.
It also appears that the X-Spam-Score header is missing (I'd like people
to be able to see tha
Noel wrote:
> At 04:54 PM 8/9/2006, Gary V wrote:
>>I could be mistaken, because I don't have a sample to look
>>at, but...
>>A couple caveats, it's possible in multi-recipient mail
>>that under
>>some circumstances you will not know who the other
>>recipients may have
>>been (BCC) so you canno
At 04:54 PM 8/9/2006, Gary V wrote:
>I could be mistaken, because I don't have a sample to look
>at, but...
>A couple caveats, it's possible in multi-recipient mail
>that under
>some circumstances you will not know who the other
>recipients may have
>been (BCC) so you cannot guarantee delivery t
Tenyo wrote:
> Hi, guys,
> I'm trying to find out what actions amavisd performs upon releasing a
> message from the quarantine. Using amavisd-release is not an option for
> my particular setup, so I'm manually releasing messages from the
> quarantine. At first glance, it appears that amavisd is
Hi, guys,
I'm trying to find out what actions amavisd performs upon releasing a
message from the quarantine. Using amavisd-release is not an option for
my particular setup, so I'm manually releasing messages from the
quarantine. At first glance, it appears that amavisd is not inserting
the X-S
