Ugh, thats what max_return_size is for. True, it will have the first
bit of the jpeg, but who cares. I'm not mailing back the entire jpeg
(or .EXE or anything else). If the sender wants to try again, they
should still have what they sent in the first place, and if they don't,
it couldnt have been all that important.
On Fri, 25 Jun 1999, Paul Makepeace wrote:
> Is there any work going/gone on/planned to enable exim to report delivery
> status notifications using RFC1892 multipart/report MIME messages? At
> present it seems to just appends the full headers and body to the
> human-readable delivery report (which isn't terribly pleasant if the
> message is a large JPEG image ;-). It would be great to have errors
> reported in a message/rfc822 attachment.
>
> RFC1892 says:
>
> <snip>
> The Multipart/Report content-type contains either two or three sub-
> parts, in the following order:
>
> (1) [required] The first body part contains human readable message.
> The purpose of this message is to provide an easily-understood
> description of the condition(s) that caused the report to be
> generated, for a human reader who may not have an user agent
> capable of interpreting the second section of the
> Multipart/Report.
>
> The text in the first section may be in any MIME standards-track
> content-type, charset, or language. Where a description of the
> error is desired in several languages or several media, a
> Multipart/Alternative construct may be used.
>
> This body part may also be used to send detailed information
> that cannot be easily formatted into a Message/Report body part.
>
> (2) [required] A machine parsable body part containing an account
> of the reported message handling event. The purpose of this body
> part is to provide a machine-readable description of the
> condition(s) which caused the report to be generated, along with
> details not present in the first body part that may be useful to
> human experts. An initial body part, Message/delivery-status is
> defined in [DSN]
>
> (3) [optional] A body part containing the returned message or a
> portion thereof. This information may be useful to aid human
> experts in diagnosing problems. (Although it may also be useful
> to allow the sender to identify the message which the report was
> issued, it is hoped that the envelope-id and original-recipient-
> address returned in the Message/Report body part will replace
> the traditional use of the returned content for this purpose.)
> </snip>
>
> Cheers,
> Paul
>
> --
> *** Exim information can be found at http://www.exim.org/ ***
>
>
--
*** Exim information can be found at
http://www.exim.org/ ***
