Two things...
1. You only attached the RemoteDelivery patch, not the DSNBounce mailet.
2. The change to remote delivery... other people have requested handling how bounces work, so I might suggest we make this more generic. Basically the code would stay the same, just remove the DSN-specific naming, e.g., configure a <bounceProcessor> and store the exception as the delivery-error.
-- Serge Knystautas President Lokitech >>> software . strategy . design >> http://www.lokitech.com p. 301.656.5501 e. [EMAIL PROTECTED]
Andreas Göggerle wrote:
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 name="transport"> [...] <mailet match="All" class="RemoteDelivery"> [...] <!-- Processor for DSN creation --> <dsnProcessor>dsn</dsnProcessor> </mailet> </processor>
<processor name="dsn"> <mailet match="All" class="DSNBounce"> <!-- sender defaults to postmaster --> <sender> [EMAIL PROTECTED] </sender> <!-- Subject Prefix (default=Re:) --> <prefix> ERROR: </prefix> <passThrough> false </passThrough> </mailet> </processor>
The DSNBounce Mailet creates Bounce Mails in the format specified by RFCs 3462 to 3464. There is only one discrepancy: the MIME-type "text/plain" is used for the status-report part, instead of "message/delivery-status". JavaMail doesn't support "message/delivery-status".
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
