;Imessage or none, default=message/Ilt;/attachmentgt;
* lt;passThroughgt;Itrue or false, default=true/Ilt;/passThroughgt;
* lt;debuggt;Itrue or false, default=false/Ilt;/debuggt;
* lt;/mailetgt;
* /CODE/PRE
*
*
* @author Andreas Göggerle [EMAIL PROTECTED]
*
* @see
Hi,
finaly I got time to get things ready.
This Patch to RemoteDelivery introduces a new parameter dsnProcessor.
Here you can specify a processor, where DSN conform Bounces are created.
If this parameter is missing, mails get bounced the old way.
Here is a configuration example:
processor
Noel J. Bergman wrote:
Søren Hilmer wrote:
I agree that Andreas's DSN solution should make it into
the next build. My only concern is that we get yet
another processor with special meaning, besides root and
error. I suggest that we make the processor name a
parameter to RemoteDelivery.
Mark Daring wrote:
you dont need to write your own DataHandler, just use what
allready exists.
You could use the default Handler of the
message/rfc822-messages and extend
the MimeMessage class.
For example your mailcap-file (take a look at
mail.jar/META-INF/mailcap)
would then look
Hi,
I wrote a DSNBounce Mailet (extending Vincenzos AbstractNotify) that
produces Delivery Status Notifications using the format described in RFC
3462 - RFC 3464.
This Mailet gets the failed Message with the Exception that occured attached
as Attribute.
Therefor I replaced the call of
Hi everyone,
while writing a DSNBounce mailet that produces RFC3464 conform
Delivery Status Notifications I encountered a problem with the
MIME type message/delivery-status.
When I try to send a multipart mail with a bodypart having this
MIME type, I get the follwing runtime exception:
