🚀 go-pugleaf

> We are translating non-local OfficeVision mail to RFC format through the
> PUMP software, which uses the "X-Acknowledge-To" header.  An OfficeVision
> message that is not converted through PUMP does not seem to have a
> registered mail header at all.  Unmodified OfficeVision messages are Notes
> with Format "MESSAGE."
>
> RiceMail honors the X-Acknowledge-To header.  It ignores
> "Return-Receipt-To."
>
> I was hoping that I could create a mapping in the MAPPINGS file to convert
> from one header to another.  Does this sound plausible?  Maybe there could
> be a mapping table per channel.

No this isn't terribly plausible since you cannot, in general, map between
header lines this way.  Each header line has its own syntax which must be
honored. To map from one header line to another you must know the syntax of
each header line, and you must parse the source header line and convert its
contents to the proper format in the destination header line.  In the most
general setting, this is a very non-trivial task as there are many
issues to consider.

Again, trying to fix this in PMDF seems like the wrong approach to me: I would
think you'd get a lot more mileage handling this problem on the IBM system
since PMDF is not the only mailer which will present the IBM with
Delivery-receipt-to header lines.

> When a delivery receipt is requested, PMDF uses the "Return-Receipt-To"
> header, correct?  What about the ad hoc standard (as you said),
> "Delivery-Receipt-To"?

I was confused, the ad-hoc standard is Return-receipt-to: which is what
PMDF uses out SMTP.  (Internally, PMDF will use Delivery-receipt-to: and
Read-receipt-to:.)

Dan