Yes, your answer bring me to the right direction.
The "x-recipient" isn't added by the email client nor from mercury/32. It's added by the popfile-daemon.
It's the -t flag of the popfiled:
<p>Yes, your answer bring me to the right direction.</p><p>The "x-recipient" isn't added by the email client nor from mercury/32. It's added by the popfile-daemon.
</p><p>It's the -t flag of the popfiled:
</p><dl><dt><code>-t</code>&nbsp;&nbsp;&nbsp;&nbsp; If present, mail tagged with either the
<code>X-Text-Classification</code> or the <code>X-POPFile-Link</code>
headers will also receive the new header
<code>X-Recipient:&nbsp;&lt;recipient_name&gt;</code></dt><dt>&nbsp;</dt><dt>It seems to me: it's not a good idea to use the&nbsp; -t&nbsp; flag if BCC is used.
</dt><dt>&nbsp;</dt><dt>Thank you :-)
</dt><dd>
</dd></dl><p>&nbsp;</p>