[jira] Commented: (JAMES-444) Add support for "Expires" header in remotedelivery

["Stefano Bagnara (JIRA)" <se...@james.apache.org>]

    [ http://issues.apache.org/jira/browse/JAMES-444?page=comments#action_12422890 ] 
            
Stefano Bagnara commented on JAMES-444:
---------------------------------------

Attach interesting comments from the list:
-----------------------
Noel J. Bergman wrote:
>>> http://issues.apache.org/jira/browse/JAMES-444
>>>       
>> What about have the feature configurable:
>> onExpires=off      // default
>> onExpires=drop   // discard expired mail without notice (my patch)
>> onExpires=bounce  // or other actions??
>>     
>
> If we were to introduce this into RemoteDelivery, it would be necessary only
> because RemoteDelivery does its own internal queuing.
>
> If you have not seen the discussion on server-dev@ for a new approach to
> spooling, you may want to read the thread starting with Message-ID:
> <NB...@devtech.com> in the archives.  In brief,
> part of that proposal includes moving rescheduling outside of the mailets
> and to the processor boundary, allowing us more flexibility on what to
> reschedule.
>
> As a nearer-term thing, even in the absence of the additional work required
> to change the spool store and wrap processors into transactions, if we can
> allow you to have something like:
>
>   <processor name="RemoteDelivery">
>     <schedule>
>       ...
>     </schedule>
>
>     <mailet match="Expired" class="[Null|Bounce|...]"
>     </mailet>
>
>     <mailet class="RemoteDelivery">
>     </mailet>
>   </processor>
>
> would that satisfy your requirements?
>   
Yes, great!

You can see my use case under
 
   
http://www.xmlblaster.org/xmlBlaster/doc/requirements/protocol.email.html#expires

here it could happen that if there was some network problem some 100000 ping
emails where queuing up in james (but only the most recent ping email is 
of relevance)
and when the network recovered all 100000 emails flushed.

I did assume that Expires follows the time format

    Expires: Thu, 15 Dec 2005 21:45:01 +0100 (CET)

instead of a more standard (ISO 8601) format:
 
   Expires: 2005-12-15T21:44:56.296Z

correct?
Does it make sense to support both?

best regards
Marcel


> Add support for "Expires" header in remotedelivery
> --------------------------------------------------
>
>                 Key: JAMES-444
>                 URL: http://issues.apache.org/jira/browse/JAMES-444
>             Project: James
>          Issue Type: Improvement
>          Components: Matchers/Mailets (bundled)
>    Affects Versions: 2.3.0a1
>            Reporter: Stefano Bagnara
>         Assigned To: Stefano Bagnara
>            Priority: Minor
>
> Every of our emails has a
> Expires: Thu, 15 Dec 2005 21:45:01 +0100 (CET)
> header (new RFC 822 'Expires:' header and http://www.faqs.org/rfcs/rfc2156.html).
> If the follow-up MTA is down for say one day all mails
> are hold by james in its outgoing queue.
> As most of our mails expire after one minute there
> may be say 20000 mails which are expired during a day.
> I don't want to forward them when the folloup MTA comes
> up again but just silently erase them.
> I think the mailet interface is invoked when the mail
> arrives to james (and is not expired at this point)
> but not when james tries to forward them - true?
> thanks for some insight,
> Marcel 

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira

        

---------------------------------------------------------------------
To unsubscribe, e-mail: server-dev-unsubscribe@james.apache.org
For additional commands, e-mail: server-dev-help@james.apache.org