[PATCH] RemoteDelivery and new DSNBounce Mailet

[Andreas Göggerle]

Hi,

finaly I got time to get things ready.

This Patch to RemoteDelivery introduces a new parameter .
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:


[...]
   
   [...]
  
  dsn
   



   
  
   [EMAIL PROTECTED] 

   ERROR: 
   false 
   


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".

Andreas


***
Mail: [EMAIL PROTECTED]
Web: www.pansoft.de
Tel.: +49 (0)721 62532 - 16
Fax: +49 (0)721 62532 - 44

PANSOFT GmbH
Tullastr. 28
76131 Karlsruhe
***
Index: RemoteDelivery.java
===
RCS file: 
/home/cvspublic/james-server/src/java/org/apache/james/transport/mailets/RemoteDelivery.java,v
retrieving revision 1.51
diff -u -r1.51 RemoteDelivery.java
--- RemoteDelivery.java 18 Jun 2003 15:59:44 -  1.51
+++ RemoteDelivery.java 27 Nov 2003 16:21:02 -
@@ -89,6 +89,7 @@
 import org.apache.mailet.GenericMailet;
 import org.apache.mailet.Mail;
 import org.apache.mailet.MailAddress;
+import org.apache.mailet.MailetContext;
 import org.apache.mailet.MailetContextConstants;
 import org.apache.mailet.SpoolRepository;
 
@@ -138,6 +139,7 @@
 private Collection deliveryThreads = new Vector();
 
 private volatile boolean destroyed = false; //Flag that the run method will check 
and end itself if set to true
+private String dsnProcessor = null; // the processor for creating DSNs
 
 /**
  * Initialize the mailet
@@ -174,6 +176,7 @@
 log("Invalid timeout setting: " + getInitParameter("timeout"));
 }
 sendPartial = (getInitParameter("sendpartial") == null) ? false : new 
Boolean(getInitParameter("sendpartial")).booleanValue();
+dsnProcessor = getInitParameter("dsnProcessor");
 
 String gateway = getInitParameter("gateway");
 gatewayPort = getInitParameter("gatewayPort");
@@ -543,7 +546,25 @@
 log(logBuffer.toString());
 }
 }
-bounce(mail, ex);
+
+if (dsnProcessor != null) {
+// do the new DSN bounce
+// setting attributes for DSN mailet
+mail.setAttribute("DSN-error", ex);
+mail.setState(dsnProcessor);
+// re-insert the mail into the spool for getting it passed to the 
dsn-processor
+MailetContext mc = getMailetContext();
+try {
+mc.sendMail(mail);
+} catch (MessagingException e) {
+// we shouldn't get an exception, because the mail was already 
processed
+log("Exception re-inserting failed mail: ", e);
+}
+} else {
+// do an old style bounce
+bounce(mail, ex);
+}
+
 return true;
 }
 

-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Re: [PATCH] RemoteDelivery and new DSNBounce Mailet

[Serge Knystautas]

Andreas,

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  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 .
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:


[...]
   
   [...]
  
  dsn
   


   
  
   [EMAIL PROTECTED] 

   ERROR: 
   false 
   

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]

RE: [PATCH] RemoteDelivery and new DSNBounce Mailet

[Andreas Göggerle]

> Two things...
> 1. You only attached the RemoteDelivery patch, not the
> DSNBounce mailet.
I dont't know why the mailet was not there, I'm sure I attached both .. but
here it is again.

> 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  and store the
> exception as the delivery-error.
My intention was to use this processor not only for bounces, but also for
positive and delayed DSNs once the required information is available
(i.e. the SMTP extension for DSN is implemented), so I named it
.
But if you prefer  ... it's changed in the patch I send
this time.

I hope this time both attachements make the way to you, but I'll doublecheck

Andreas

Index: RemoteDelivery.java
===
RCS file: 
/home/cvspublic/james-server/src/java/org/apache/james/transport/mailets/RemoteDelivery.java,v
retrieving revision 1.51
diff -u -r1.51 RemoteDelivery.java
--- RemoteDelivery.java 18 Jun 2003 15:59:44 -  1.51
+++ RemoteDelivery.java 2 Dec 2003 08:41:13 -
@@ -89,6 +89,7 @@
 import org.apache.mailet.GenericMailet;
 import org.apache.mailet.Mail;
 import org.apache.mailet.MailAddress;
+import org.apache.mailet.MailetContext;
 import org.apache.mailet.MailetContextConstants;
 import org.apache.mailet.SpoolRepository;
 
@@ -138,6 +139,7 @@
 private Collection deliveryThreads = new Vector();
 
 private volatile boolean destroyed = false; //Flag that the run method will check 
and end itself if set to true
+private String bounceProcessor = null; // the processor for creating Bounces
 
 /**
  * Initialize the mailet
@@ -174,6 +176,7 @@
 log("Invalid timeout setting: " + getInitParameter("timeout"));
 }
 sendPartial = (getInitParameter("sendpartial") == null) ? false : new 
Boolean(getInitParameter("sendpartial")).booleanValue();
+bounceProcessor = getInitParameter("bounceProcessor");
 
 String gateway = getInitParameter("gateway");
 gatewayPort = getInitParameter("gatewayPort");
@@ -543,7 +546,25 @@
 log(logBuffer.toString());
 }
 }
-bounce(mail, ex);
+
+if (bounceProcessor != null) {
+// do the new DSN bounce
+// setting attributes for DSN mailet
+mail.setAttribute("delivery-error", ex);
+mail.setState(bounceProcessor);
+// re-insert the mail into the spool for getting it passed to the 
dsn-processor
+MailetContext mc = getMailetContext();
+try {
+mc.sendMail(mail);
+} catch (MessagingException e) {
+// we shouldn't get an exception, because the mail was already 
processed
+log("Exception re-inserting failed mail: ", e);
+}
+} else {
+// do an old style bounce
+bounce(mail, ex);
+}
+
 return true;
 }
 

-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

RE: [PATCH] RemoteDelivery and new DSNBounce Mailet

[Andreas Göggerle]

> I hope this time both attachements make the way to you, but 
> I'll doublecheck
again the mailet got lost .. I'll resend it as .java.txt

Andreas/* 
 * The Apache Software License, Version 1.1
 *
 * Copyright (c) 2000-2003 The Apache Software Foundation.  All rights
 * reserved.
 *
 * Redistribution and use in source and binary forms, with or without
 * modification, are permitted provided that the following conditions
 * are met:
 *
 * 1. Redistributions of source code must retain the above copyright
 *notice, this list of conditions and the following disclaimer.
 *
 * 2. Redistributions in binary form must reproduce the above copyright
 *notice, this list of conditions and the following disclaimer in
 *the documentation and/or other materials provided with the
 *distribution.
 *
 * 3. The end-user documentation included with the redistribution,
 *if any, must include the following acknowledgment:
 *   "This product includes software developed by the
 *Apache Software Foundation (http://www.apache.org/)."
 *Alternately, this acknowledgment may appear in the software itself,
 *if and wherever such third-party acknowledgments normally appear.
 *
 * 4. The names "Apache", "Jakarta", "JAMES" and "Apache Software Foundation"
 *must not be used to endorse or promote products derived from this
 *software without prior written permission. For written
 *permission, please contact [EMAIL PROTECTED]
 *
 * 5. Products derived from this software may not be called "Apache",
 *nor may "Apache" appear in their name, without prior written
 *permission of the Apache Software Foundation.
 *
 * THIS SOFTWARE IS PROVIDED ``AS IS'' AND ANY EXPRESSED OR IMPLIED
 * WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES
 * OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE ARE
 * DISCLAIMED.  IN NO EVENT SHALL THE APACHE SOFTWARE FOUNDATION OR
 * ITS CONTRIBUTORS BE LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL,
 * SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES (INCLUDING, BUT NOT
 * LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES; LOSS OF
 * USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION) HOWEVER CAUSED AND
 * ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT LIABILITY,
 * OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT
 * OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF
 * SUCH DAMAGE.
 * 
 *
 * This software consists of voluntary contributions made by many
 * individuals on behalf of the Apache Software Foundation.  For more
 * information on the Apache Software Foundation, please see
 * .
 *
 * Portions of this software are based upon public domain software
 * originally written at the National Center for Supercomputing Applications,
 * University of Illinois, Urbana-Champaign.
 */

package org.apache.james.transport.mailets;

import java.io.PrintWriter;
import java.io.StringWriter;
import java.net.ConnectException;
import java.net.InetAddress;
import java.net.SocketException;
import java.net.UnknownHostException;
import java.util.Collection;
import java.util.Date;
import java.util.HashSet;
import java.util.Iterator;
import java.util.regex.Matcher;
import java.util.regex.Pattern;

import javax.mail.MessagingException;
import javax.mail.SendFailedException;
import javax.mail.Session;
import javax.mail.internet.InternetAddress;
import javax.mail.internet.MimeBodyPart;
import javax.mail.internet.MimeMessage;
import javax.mail.internet.MimeMultipart;

import org.apache.james.core.MailImpl;
import org.apache.mailet.Mail;
import org.apache.mailet.MailAddress;
import org.apache.mailet.RFC2822Headers;
import org.apache.mailet.dates.RFC822DateFormat;



/**
 *
 * Generates a Delivery Status Notification (DSN)
 * Note that this is different than a mail-client's
 * reply, which would use the Reply-To or From header.
 * Bounced messages are attached in their entirety (headers and
 * content) and the resulting MIME part type is "message/rfc822".
 * The reverse-path and the Return-Path header of the response is set to "null" ("<>"),
 * meaning that no reply should be sent.
 * A sender of the notification message can optionally be specified.
 * If one is not specified, the postmaster's address will be used.
 * Supports the passThrough init parameter (true if missing).
 *
 * Sample configuration:
 * 
 * 
 *   an address or postmaster or sender or unaltered, 
default=postmaster
 *   optional subject prefix prepended to the original 
message
 *   message or none, default=message
 *   true or false, default=true
 *   true or false, default=false
 * 
 * 
 *
 *
 * @author Andreas Göggerle <[EMAIL PROTECTED]>
 *
 * @see o

RE: [PATCH] RemoteDelivery and new DSNBounce Mailet

[Noel J. Bergman]

Andreas,

Please put everything in a jar, tar or zip.  Otherwise things still seem to
get filtered.

And for a proper DSN processor, I'd call it that, rather than a "bounce"
processor.  From the sounds of it, you've implemented, or plan to implement,
more than just failure notices.

--- Noel


-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

RE: [PATCH] RemoteDelivery and new DSNBounce Mailet

[Noel J. Bergman]

Serge, Soren and Andreas,

Soren just committed the change with Serge's modifications.  Did we ever get
the DSNBounce Mailet?

Reviewing the change change, two things occur to me:

  1 - there is a "bug" -- actually more of a limitation.
  Quoting RFC 3464:

A DSN can be used to notify the sender of a
message of any of several conditions: failed
delivery, delayed delivery, successful delivery,
or the gatewaying of a message into an environment
that may not support DSNs.

  The patch handles only bounces and not other types
  of Delivery Status Notification types.

  2 - It seems to me that the original DSN (as in Delivery Status
  Notification) seems more general than "Bounce."  I would
  change delivery-error to delivery-status.  The processor
  could be ...  ??  Just to prepare
  for when we do support more than just error notices.

I have not made any change for either.  Would consider changing for #2, and
would not want to touch #1 until post release, although if someone else has
the time, please feel free to look into it.

By the way, due to an error on my part (failing to do a cvs up before a
build), this change did NOT make it into a16.  It will be in a17.

--- Noel

-Original Message-
From: Serge Knystautas [mailto:[EMAIL PROTECTED]
Sent: Thursday, November 27, 2003 22:21
To: James Developers List
Subject: Re: [PATCH] RemoteDelivery and new DSNBounce Mailet


Andreas,

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  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 .
> 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:
>
> 
> [...]
>
>[...]
>   
>   dsn
>
> 
>
> 
>
>   
>[EMAIL PROTECTED] 
>   
>ERROR: 
>false 
>
> 
>
> 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]


-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Re: [PATCH] RemoteDelivery and new DSNBounce Mailet

[Soren Hilmer]

Hi Noel,

Yes, we did get the DSNBounce mailet from Andreas, there is a few reasons why 
I have not committed it.

i) It does not compile under 1.3 because:
a) Uses Java's regular expressions (have fixed that)
b) Uses InetAddress.getCanonicalHostName (I am still deciding on how this 
is best handled, either close your eyes and use getHostName, or extend and 
use our DNSServer).

ii) It uses text/plain instead of message/delivery-status as Content-type for 
the dsn message. This should be easy to resolve, given Steve Brewin's code.


I then decided that splitting the commit up, so the bounceprocessing feature 
was separately comitted to RemoteDelivery made sense, at least that way 
developers have the hook they need to do custom bounceprocessing.


--Søren


On Friday 26 March 2004 06:20, Noel J. Bergman wrote:
> Serge, Soren and Andreas,
>
> Soren just committed the change with Serge's modifications.  Did we ever
> get the DSNBounce Mailet?
>
> Reviewing the change change, two things occur to me:
>
>   1 - there is a "bug" -- actually more of a limitation.
>   Quoting RFC 3464:
>
> A DSN can be used to notify the sender of a
> message of any of several conditions: failed
> delivery, delayed delivery, successful delivery,
> or the gatewaying of a message into an environment
> that may not support DSNs.
>
>   The patch handles only bounces and not other types
>   of Delivery Status Notification types.
>
>   2 - It seems to me that the original DSN (as in Delivery Status
>   Notification) seems more general than "Bounce."  I would
>   change delivery-error to delivery-status.  The processor
>   could be ...  ??  Just to prepare
>   for when we do support more than just error notices.
>
> I have not made any change for either.  Would consider changing for #2, and
> would not want to touch #1 until post release, although if someone else has
> the time, please feel free to look into it.
>
> By the way, due to an error on my part (failing to do a cvs up before a
> build), this change did NOT make it into a16.  It will be in a17.
>
>   --- Noel
>
> -Original Message-----
> From: Serge Knystautas [mailto:[EMAIL PROTECTED]
> Sent: Thursday, November 27, 2003 22:21
> To: James Developers List
> Subject: Re: [PATCH] RemoteDelivery and new DSNBounce Mailet
>
>
> Andreas,
>
> 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  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 .
> > 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:
> >
> > 
> > [...]
> >
> >[...]
> >   
> >   dsn
> >
> > 
> >
> > 
> >
> >   
> >[EMAIL PROTECTED] 
> > 
> >ERROR: 
> >false 
> >
> > 
> >
> > 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]
>
>
> -
> To unsubscribe, e-mail: [EMAIL PROTECTED]
> For additional commands, e-mail: [EMAIL PROTECTED]

-- 
Søren Hilmer, M.Sc.
R&D manager Phone:  +45 70 27 64 00
TietoEnator IT+ A/S Fax:+45 70 27 64 40
Ved Lunden 12   Direct: +45 87 46 64 57
DK-8230 Åbyhøj  Email:  soren.hilmer  tietoenator.com


-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

RE: [PATCH] RemoteDelivery and new DSNBounce Mailet

[Noel J. Bergman]

Søren,

Thanks for the update.  :-)

> Yes, we did get the DSNBounce mailet from Andreas

Great.  I had looked in my archives, but I couldn't find it.

> i) It does not compile under 1.3 because:
> a) Uses Java's regular expressions (have fixed that)
> b) Uses InetAddress.getCanonicalHostName (I am still
>deciding on how this is best handled, either close
>your eyes and use getHostName, or extend and use
>our DNSServer).

For now, I would use:

  getMailetContext().getAttribute(Constants.HELLO_NAME)

and we'll address it further later.  So that takes care of JDK 1.3 issues.
:-)

> ii) It uses text/plain instead of message/delivery-status as
> Content-type for the dsn message. This should be easy to
> resolve, given Steve Brewin's code.

Cool.  Then let's do it.  :-)

--- Noel


-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Re: [PATCH] RemoteDelivery and new DSNBounce Mailet

[Soren Hilmer]

Ignore the last mail!!

For some reason my mail-client decided to resurrect some old mails and put 
them in the outboks ;-(

--Søren

On Friday 26 March 2004 11:29, Soren Hilmer wrote:
> Hi Noel,
>
> Yes, we did get the DSNBounce mailet from Andreas, there is a few reasons
> why I have not committed it.
>
> i) It does not compile under 1.3 because:
> a) Uses Java's regular expressions (have fixed that)
> b) Uses InetAddress.getCanonicalHostName (I am still deciding on how
> this is best handled, either close your eyes and use getHostName, or extend
> and use our DNSServer).
>
> ii) It uses text/plain instead of message/delivery-status as Content-type
> for the dsn message. This should be easy to resolve, given Steve Brewin's
> code.
>
>
> I then decided that splitting the commit up, so the bounceprocessing
> feature was separately comitted to RemoteDelivery made sense, at least that
> way developers have the hook they need to do custom bounceprocessing.
>
>
> --Søren
>
> On Friday 26 March 2004 06:20, Noel J. Bergman wrote:
> > Serge, Soren and Andreas,
> >
> > Soren just committed the change with Serge's modifications.  Did we ever
> > get the DSNBounce Mailet?
> >
> > Reviewing the change change, two things occur to me:
> >
> >   1 - there is a "bug" -- actually more of a limitation.
> >   Quoting RFC 3464:
> >
> > A DSN can be used to notify the sender of a
> > message of any of several conditions: failed
> > delivery, delayed delivery, successful delivery,
> > or the gatewaying of a message into an environment
> > that may not support DSNs.
> >
> >   The patch handles only bounces and not other types
> >   of Delivery Status Notification types.
> >
> >   2 - It seems to me that the original DSN (as in Delivery Status
> >   Notification) seems more general than "Bounce."  I would
> >   change delivery-error to delivery-status.  The processor
> >   could be ...  ??  Just to prepare
> >   for when we do support more than just error notices.
> >
> > I have not made any change for either.  Would consider changing for #2,
> > and would not want to touch #1 until post release, although if someone
> > else has the time, please feel free to look into it.
> >
> > By the way, due to an error on my part (failing to do a cvs up before a
> > build), this change did NOT make it into a16.  It will be in a17.
> >
> > --- Noel
> >
> > -Original Message-
> > From: Serge Knystautas [mailto:[EMAIL PROTECTED]
> > Sent: Thursday, November 27, 2003 22:21
> > To: James Developers List
> > Subject: Re: [PATCH] RemoteDelivery and new DSNBounce Mailet
> >
> >
> > Andreas,
> >
> > 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  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 .
> > > 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:
> > >
> > > 
> > > [...]
> > >
> > >[...]
> > >   
> > >   dsn
> > >
> > > 
> > >
> > > 
> > >
> > >   
> > >[EMAIL PROTECTED] 
> > >   
> > >ERROR: 
> > >false 
> > >
> > > 
> > >
> > > 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]
> >
> >
> > -
> > To unsubscribe, e-mail: [EMAIL PROTECTED]
> > For additional commands, e-mail: [EMAIL PROTECTED]

-- 
Søren Hilmer, M.Sc.
R&D manager Phone:  +45 70 27 64 00
TietoEnator IT+ A/S Fax:+45 70 27 64 40
Ved Lunden 12   Direct: +45 87 46 64 57
DK-8230 Åbyhøj  Email:  soren.hilmer  tietoenator.com


-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]