Prev: blocking the null from address
Next: Mail application parsing files delivered by sendmail - problems with BCC Recipients
From: jmaimon on 11 Jun 2008 07:54
On Jun 9, 11:35 am, steven.heyl...(a)gmail.com wrote:
> In our company, we're writing a mail application.
>
> We have our sendmail process deliver the mails to files, which are
> picked up by the application and parsed.
>
> We added the X-Envelope-To: header in our sendmail config in order to
> make sure that the BCC-recipients were added in this header.
> Apparently, this only works when only 1 bcc-recipient and no other (to
> or cc) recipients are present.
>
> Is there any other way to make sure that all recipients (also bcc) are
> visible to our application?
>
> I've been looking in the direction of the Apparently-to header, but
> this option seems to be unsupported and as I read only working when no
> recipients are added.

If you dont want to follow the fine suggestions already in this thread
(which you really should), you can always do something like this to
scoop the mail from the queue directory, which as you note does have
all the recipients encoded.

http://jmaimon.com/misc/stuff/sm2mbox.zip

This example only extracts the sender address, but I imagine you could
modify it.

You really should be following Per's advice.
 | 
Pages: 1
Prev: blocking the null from address
Next: Mail application parsing files delivered by sendmail - problems with BCC Recipients