Re: /usr/lib/sendmail delivery status/message id's (postdrop)

5 msg	postconf not displaying all options
3 msg	empty_address_recipient not mapped by virtual o...
5 msg	stop smtp from anyone unless sasl auth?
2 msg	'piped' aliases & DSNs
12 msg	Strange From: in headers
5 msg	Mail - Access Denied
4 msg	qpsmtpd support service for postfix
39 msg	pix workaround broken?
2 msg	X-Original-To after bcc contains wrong address

/usr/lib/sendmail delivery status/message id's ...
\ Jacqui caren (23 Jul 2007)
. \ mouss (23 Jul 2007)
. \ (Wietse Venema) (23 Jul 2007)
. . \ (Wietse Venema) (23 Jul 2007)
. . . \ Jacqui caren (24 Jul 2007)
. . \ (clemens fischer) (23 Jul 2007)
. . . \ Victor Duchovni (23 Jul 2007)
. . . . \ (Wietse Venema) (23 Jul 2007)

23 msg	Recommended Filesystems?
8 msg	Mail going to backup server instead main server
3 msg	outgoing rate control
5 msg	mail forwarding loop: how do I prevent this?
5 msg	Server relaying existing virtual mailbox
1 msg	how can I rewrite the Mail From
3 msg	Constant connections from user unknown sending ...
2 msg	sporadic deferrals
8 msg	transport_maps: different behavior if discard o...
4 msg	Address verification questions

Subject:	Re: /usr/lib/sendmail delivery status/message id's (postdrop)
Group:	Postfix-users
From:	Jacqui caren
Date:	24 Jul 2007

Wietse Venema wrote:
> Wietse Venema:
>
>>Jacqui caren:
>>
>>>I have been processing and forwarding email using a perl
>>>script and SMTP however this eats resources.
>>
>>Don't execute one script per message. Use a persistent process.
>>
>>
>>>What I would like to do is once I have processed the message
>>>I would like to use /usr/lib/sendmail -g -I or similar
>>>to deliver into the maildrop queue.
>>>
>>>However SMTP gives me a message ID that I use for an audit
>>>trail. The /usr/lib/sendmail delivery mechanism
>>>does not seem to have that option.
>>>
>>>FWUI /usr/lib/sendmail is a front end for an undocumented
>>>internal protocol (postdrop?). Could I write a perl module that
>>>would deliver the message using this protocol (and give me
>>>a message id etc) or is this protocol "subject to change
>>>without notice"?
>>
>>Using internal interfaces is unsupported. They change without
>>notice, and will break with the next release.
>
>
> It is possible to add a published submission interface to postdrop,
> but it still would not give control over the queue file name that
> the daemonized portion of Postfix will use.
>
> You can, however, submit mail into /usr/sbin/sendmail with your
> own unique Message-ID header, and use that for tracking. Reasonable
> mail systems, even those that don't implement the DSN protocol, will
> report the Message-ID information in an NDR.

It is more a case of clients complaining that they have received thier
urgent email sent less than five minutes previously.
We have to (from the database logs) track through to the message queue
id and then use this to find out when it was submitted (known in DB) and
delivered or bounced etc. For SLA we need to be able to *prove* an
attempt to deliver was made within one hour of generation and we did not
withhold delivery.