Dear James Users,

We have been using james-2.3.2 almost since it was released.
We find that after a while customers start to complain that emails are not
going out.
We usually then have to delete the james-plus/ directory which also then
deletes the subdirectory of james-2.3.2/apps/james-plus/var/mail/outgoing
and restart James with the james-plus.jar in the apps directory so it
automatically re-creates all the directories.  Then the emails start going
out again.
                                                                            
                                                       
1. Once emails are sent should they automatically be deleted from the
outgoing directory?  
Or should the files in the outgoing directory for the outgoing emails, just
keep building up forever?
2. Why after the outgoing directory has about 2500 files in it, do the
emails stop being sent?

Below is part of our configuration file:

<!-- Attempt remote delivery using the specified repository for the spool,
-->
         <!-- using delay time to retry delivery and the maximum number of
retries -->
         <mailet match="All" class="RemoteDelivery">
            <outgoing> file://var/mail/outgoing/ </outgoing>
            <!-- alternative database repository example below -->
            <!--
            <outgoing> db://maildb/spool/outgoing </outgoing>
            -->

            <!-- Delivery Schedule based upon RFC 2821, 4.5.4.1 -->
            <!-- 5 day retry period, with 4 attempts in the first
                 hour, two more within the first 6 hours, and then
                 every 6 hours for the rest of the period. -->
            <delayTime>  5 minutes </delayTime>
            <delayTime> 10 minutes </delayTime>
            <delayTime> 45 minutes </delayTime>
            <delayTime>  2 hours </delayTime>
            <delayTime>  3 hours </delayTime>
            <delayTime>  6 hours </delayTime>
            <maxRetries> 25 </maxRetries>

            <!-- The number of threads that should be trying to deliver
outgoing messages -->
            <deliveryThreads> 1 </deliveryThreads>

            <!-- If false the message will not be sent to given server if
any recipients fail -->
            <sendpartial>false</sendpartial>

            <!-- By default we send bounces to the "bounce" processor -->
            <!-- By removing this configuration James will fallback to
hardcoded bounce -->
            <!-- notifications -->
            <bounceProcessor>bounces</bounceProcessor>


If there is anything further you require, please feel free to contact us.
 
Kind Regards
 
eCommunicate Management
Tel   : 011 443 6164
Fax  : 088 011 443 6164
Mobile:   0832300002
mailto:[email protected]

Outlook SMS – Web SMS – Email 2 SMS Email - Developer Kit for SMS - .Mobi
Sites - Bulk SMS & Email Campaigns - SMS competitions – Premium rated Short
Codes - Opt-in cell phone billing - Database 2 SMS for backend automation –
MMS - USSD - WAP - Voice Over IP




---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to