You are viewing a plain text version of this content. The canonical link for it is here.
Posted to server-user@james.apache.org by Mark Hale <ma...@gmail.com> on 2008/08/21 07:52:03 UTC
Re: RemoteDelivery Problem
David, et al.
I've really tried with no avail to get outbound messages to send. I
tried a corporate email (interwoven.com) to take gmail and yahoo out
of the equation. For all outbound mail, I still get a temporary
exception as follows. All retries give the same exception. I am able
to telnet to the port returned for the mx record (eg telnet
208.65.145.13 25) so that I know my fireway or ISP is not blocking.
==> mailet-2008-08-20-21-08.log <==
20/08/08 21:30:47 INFO James.Mailet: RemoteDelivery: Attempting
delivery of Mail1219293046382-2-to-interwoven.com to host
interwoven.com.inbound15.mxlogicmx.net. at 208.65.145.13 for addresses
[mark.hale@interwoven.com]
20/08/08 21:30:47 INFO James.Mailet: RemoteDelivery: Exception
delivering message (Mail1219293046382-2-to-interwoven.com) - smtp
20/08/08 21:30:47 INFO James.Mailet: RemoteDelivery: Temporary
exception delivering mail (Mail1219293046382-2-to-interwoven.com:
20/08/08 21:30:47 INFO James.Mailet: RemoteDelivery: Storing message
Mail1219293046382-2-to-interwoven.com into outgoing after 0 retries
Would anyone have an idea on what to try next? I am really stumped.
Thanks so much.
Mark
On Fri, Jul 11, 2008 at 7:26 AM, Mark Hale <ma...@gmail.com> wrote:
> Thank you for the informative response! I will give it a try and post
> back what I learn.
>
> Mark
>
>
> On Fri, Jul 11, 2008 at 1:43 AM, David Legg
> <da...@searchevent.co.uk> wrote:
>> Hi Mark,
>>
>>> I tried multiple email address
>>> (company, yahoo, gmail, etc) and they all exchibit the same temporary
>>> exception. I can telnet from my box to port 25 on the domains found
>>> in the mx records.
>>>
>>
>> I think this is perfectly normal behaviour. I believe the servers you are
>> sending the email to are using a form of Greylisting [1]. This means that
>> the first time James attempts to send it gets a Temporary exception
>> response. Ideally, James should attempt to re-deliver the email after a
>> suitable delay. The trouble is that large organizations like Google and
>> Yahoo don't have just the one mail server and so when James attempts
>> re-delivery it gets another server to talk to which likewise tells you to
>> come back later. If you are lucky you get the same server again which then
>> recognizes you and lets you send the email.
>>
>> The 'solution' I came up with is to increase the number and frequency of
>> retries that James makes by changing the Remotedelivery settings in
>> config.xml to the following: -
>>
>> <mailet match="All" class="RemoteDelivery">
>> ...
>> <delayTime> 5 minutes </delayTime>
>> <delayTime> 5 minutes </delayTime>
>> <delayTime> 20 minutes </delayTime>
>> <delayTime> 30 minutes </delayTime>
>> <delayTime> 1 hours </delayTime>
>> <delayTime> 2 hours </delayTime>
>> <maxRetries> 6 </maxRetries>
>> ...
>> </mailet>
>>
>> Without these changes a lot of emails sent to these addresses eventually
>> bounced back after 6 hours or so; often delaying important notifications
>> until the next day.
>>
>> Google and Yahoo users probably don't have these problems because messages
>> sent via the web site to another Google or Yahoo user aren't subject to
>> Greylisting.
>>
>> HTH
>>
>> David Legg
>>
>> [1] http://projects.puremagic.com/greylisting/whitepaper.html
>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: server-user-unsubscribe@james.apache.org
>> For additional commands, e-mail: server-user-help@james.apache.org
>>
>>
>
---------------------------------------------------------------------
To unsubscribe, e-mail: server-user-unsubscribe@james.apache.org
For additional commands, e-mail: server-user-help@james.apache.org
Re: Issues Forwarding Mail
Posted by Rex Posadas <re...@kalexo.com>.
Hi Folks,
Any ideas on this one? Or is my issue with forwarding non-James related?
Any clues would help. Thanks again,
- Rex
Rex Posadas wrote:
> Hi All,
>
> I would appreciate some help with this. I have 2 servers running
> James. Say... Domain.net and Domain.com.
>
> I want to:
> Step 1. - from google, write to Domain.net
> Step 2. - James in Domain.net then forwards that email to Domain.com
> Step 3. - James in Domain.com receives that email and processes that
> mail with some Mailet.
>
> James in Domain.net doesn't forward to Domain.com. I also noticed that
> when sending email from Domain.net to Domain.com I get a "relay
> Denied" error.
>
> Here is how I configured everything:
>
> In Domain.net:
> <servername>Domain.net</servername>
>
> <mailet match="All" class="Forward">
> <forwardTo>someuser@Domain.com</forwardTo>
> <passThrough>true</passThrough>
> <fakeDomainCheck>false</fakeDomainCheck>
> <debug>true</debug>
> </mailet>
>
> In Domain.com:
> <servername>Domain.com</servername>
> <authorizedAddresses>127.0.0.0/8, Domain.net</authorizedAddresses>
>
>
> Thanks,
>
> Rex
>
>
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: server-user-unsubscribe@james.apache.org
> For additional commands, e-mail: server-user-help@james.apache.org
---------------------------------------------------------------------
To unsubscribe, e-mail: server-user-unsubscribe@james.apache.org
For additional commands, e-mail: server-user-help@james.apache.org
Issues Forwarding Mail
Posted by Rex Posadas <re...@kalexo.com>.
Hi All,
I would appreciate some help with this. I have 2 servers running
James. Say... Domain.net and Domain.com.
I want to:
Step 1. - from google, write to Domain.net
Step 2. - James in Domain.net then forwards that email to Domain.com
Step 3. - James in Domain.com receives that email and processes that
mail with some Mailet.
James in Domain.net doesn't forward to Domain.com. I also noticed that
when sending email from Domain.net to Domain.com I get a "relay Denied"
error.
Here is how I configured everything:
In Domain.net:
<servername>Domain.net</servername>
<mailet match="All" class="Forward">
<forwardTo>someuser@Domain.com</forwardTo>
<passThrough>true</passThrough>
<fakeDomainCheck>false</fakeDomainCheck>
<debug>true</debug>
</mailet>
In Domain.com:
<servername>Domain.com</servername>
<authorizedAddresses>127.0.0.0/8, Domain.net</authorizedAddresses>
Thanks,
Rex
---------------------------------------------------------------------
To unsubscribe, e-mail: server-user-unsubscribe@james.apache.org
For additional commands, e-mail: server-user-help@james.apache.org
Re: RemoteDelivery Problem
Posted by Mark Hale <ma...@gmail.com>.
Well, you are clearly a much wiser person. I added the debug to my
config under RemoteDelivery. The debug statements followed and it
quickly brought me to the fact that I had mail.jar in my
james/SAR-INF/lib that I used when compiling my custom mailets that
conflicted. I removed it and all is working.
Thank you so much!
Mark
On Thu, Aug 21, 2008 at 10:48 AM, Stefano Bagnara <ap...@bago.org> wrote:
> Mark Hale ha scritto:
>>
>> Stefano.
>>
>>> Have you restarted james?
>>
>> Yes
>>
>>> What environment.xml file do you change? You have to change the expanded
>>> one
>>> and not the one inside the sar file.
>>
>> james/apps/james/SAR-INF/environment.xml. It is attached along with
>> the mailet log file.
>>
>> I do see debug statements in the other logs such as
>> smtpserver-2008-08-21-08-35.log. Just not for maillet.
>>
>> I would love to get a debug log with more details so I could trace
>> this down. Any help is appreciated.
>
> Try adding a:
> <debug>true</debug>
>
> in your RemoteDelivery configuration.
>
> Stefano
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: server-user-unsubscribe@james.apache.org
> For additional commands, e-mail: server-user-help@james.apache.org
>
>
---------------------------------------------------------------------
To unsubscribe, e-mail: server-user-unsubscribe@james.apache.org
For additional commands, e-mail: server-user-help@james.apache.org
Re: RemoteDelivery Problem
Posted by Stefano Bagnara <ap...@bago.org>.
Mark Hale ha scritto:
> Stefano.
>
>> Have you restarted james?
> Yes
>
>> What environment.xml file do you change? You have to change the expanded one
>> and not the one inside the sar file.
>
> james/apps/james/SAR-INF/environment.xml. It is attached along with
> the mailet log file.
>
> I do see debug statements in the other logs such as
> smtpserver-2008-08-21-08-35.log. Just not for maillet.
>
> I would love to get a debug log with more details so I could trace
> this down. Any help is appreciated.
Try adding a:
<debug>true</debug>
in your RemoteDelivery configuration.
Stefano
---------------------------------------------------------------------
To unsubscribe, e-mail: server-user-unsubscribe@james.apache.org
For additional commands, e-mail: server-user-help@james.apache.org
Re: RemoteDelivery Problem
Posted by Mark Hale <ma...@gmail.com>.
Stefano.
> Have you restarted james?
Yes
> What environment.xml file do you change? You have to change the expanded one
> and not the one inside the sar file.
james/apps/james/SAR-INF/environment.xml. It is attached along with
the mailet log file.
I do see debug statements in the other logs such as
smtpserver-2008-08-21-08-35.log. Just not for maillet.
I would love to get a debug log with more details so I could trace
this down. Any help is appreciated.
Thanks,
Mark
On Thu, Aug 21, 2008 at 7:04 AM, Stefano Bagnara <ap...@bago.org> wrote:
> Mark Hale ha scritto:
>>
>> Stefano,
>>
>> That is a problem I wrote about earlier. I enabled debug for
>> everything as shown below and I still get INFO messages for the
>> RemoteDelivery mailet. I would love more information to go on. Is
>> there a problem with how I defined it below? ( I extracted just this
>> piece of environment.xml.)
>
>
> Have you restarted james?
> What environment.xml file do you change? You have to change the expanded one
> and not the one inside the sar file.
>
> I see exceptions and a lot of lines for each delivery attempt.
>
> Stefano
>
>> Thanks,
>>
>> Mark
>>
>> <categories>
>> <category name="" log-level="DEBUG">
>> <log-target id-ref="default"/>
>> </category>
>> <category name="James.Mailet" log-level="DEBUG">
>> <log-target id-ref="James-Mailet-target"/>
>> </category>
>> <category name="James" log-level="DEBUG">
>> <log-target id-ref="James-target"/>
>> </category>
>> <category name="spoolmanager" log-level="DEBUG">
>> <log-target id-ref="spoolmanager-target"/>
>> </category>
>> <category name="dnsserver" log-level="DEBUG">
>> <log-target id-ref="dnsserver-target"/>
>> </category>
>> <category name="remotemanager" log-level="DEBUG">
>> <log-target id-ref="remotemanager-target"/>
>> </category>
>> <category name="pop3server" log-level="DEBUG">
>> <log-target id-ref="pop3server-target"/>
>> </category>
>> <category name="smtpserver" log-level="DEBUG">
>> <log-target id-ref="smtpserver-target"/>
>> </category>
>> <category name="nntpserver" log-level="DEBUG">
>> <log-target id-ref="nntpserver-target"/>
>> </category>
>> <category name="nntp-repository" log-level="DEBUG">
>> <log-target id-ref="nntp-repository-target"/>
>> </category>
>> <category name="mailstore" log-level="DEBUG">
>> <log-target id-ref="mailstore-target"/>
>> </category>
>> <category name="users-store" log-level="DEBUG">
>> <log-target id-ref="users-store-target"/>
>> </category>
>> <category name="objectstorage" log-level="DEBUG">
>> <log-target id-ref="objectstorage-target"/>
>> </category>
>> <category name="connections" log-level="DEBUG">
>> <log-target id-ref="connections-target"/>
>> </category>
>> <category name="sockets" log-level="DEBUG">
>> <log-target id-ref="sockets-target"/>
>> </category>
>> <category name="scheduler" log-level="DEBUG">
>> <log-target id-ref="scheduler-target"/>
>> </category>
>> <category name="fetchmail" log-level="DEBUG">
>> <log-target id-ref="fetchmail-target"/>
>> </category>
>> </categories>
>>
>>
>>
>>
>> On Thu, Aug 21, 2008 at 12:13 AM, Stefano Bagnara <ap...@bago.org> wrote:
>>>
>>> Mark Hale ha scritto:
>>>>
>>>> David, et al.
>>>>
>>>> I've really tried with no avail to get outbound messages to send. I
>>>> tried a corporate email (interwoven.com) to take gmail and yahoo out
>>>> of the equation. For all outbound mail, I still get a temporary
>>>> exception as follows. All retries give the same exception. I am able
>>>> to telnet to the port returned for the mx record (eg telnet
>>>> 208.65.145.13 25) so that I know my fireway or ISP is not blocking.
>>>>
>>>> ==> mailet-2008-08-20-21-08.log <==
>>>> 20/08/08 21:30:47 INFO James.Mailet: RemoteDelivery: Attempting
>>>> delivery of Mail1219293046382-2-to-interwoven.com to host
>>>> interwoven.com.inbound15.mxlogicmx.net. at 208.65.145.13 for addresses
>>>> [mark.hale@interwoven.com]
>>>> 20/08/08 21:30:47 INFO James.Mailet: RemoteDelivery: Exception
>>>> delivering message (Mail1219293046382-2-to-interwoven.com) - smtp
>>>> 20/08/08 21:30:47 INFO James.Mailet: RemoteDelivery: Temporary
>>>> exception delivering mail (Mail1219293046382-2-to-interwoven.com:
>>>> 20/08/08 21:30:47 INFO James.Mailet: RemoteDelivery: Storing message
>>>> Mail1219293046382-2-to-interwoven.com into outgoing after 0 retries
>>>>
>>>> Would anyone have an idea on what to try next? I am really stumped.
>>>
>>> Enable DEBUG output and check the logs.
>>> You can enable DEBUG by altering the
>>> <jamesfolder>/apps/james/SAR-INF/environment.xml file
>>>
>>> Stefano
>>>
>>>> Thanks so much.
>>>>
>>>> Mark
>>>>
>>>>
>>>> On Fri, Jul 11, 2008 at 7:26 AM, Mark Hale <ma...@gmail.com> wrote:
>>>>>
>>>>> Thank you for the informative response! I will give it a try and post
>>>>> back what I learn.
>>>>>
>>>>> Mark
>>>>>
>>>>>
>>>>> On Fri, Jul 11, 2008 at 1:43 AM, David Legg
>>>>> <da...@searchevent.co.uk> wrote:
>>>>>>
>>>>>> Hi Mark,
>>>>>>
>>>>>>> I tried multiple email address
>>>>>>> (company, yahoo, gmail, etc) and they all exchibit the same temporary
>>>>>>> exception. I can telnet from my box to port 25 on the domains found
>>>>>>> in the mx records.
>>>>>>>
>>>>>> I think this is perfectly normal behaviour. I believe the servers you
>>>>>> are
>>>>>> sending the email to are using a form of Greylisting [1]. This means
>>>>>> that
>>>>>> the first time James attempts to send it gets a Temporary exception
>>>>>> response. Ideally, James should attempt to re-deliver the email after
>>>>>> a
>>>>>> suitable delay. The trouble is that large organizations like Google
>>>>>> and
>>>>>> Yahoo don't have just the one mail server and so when James attempts
>>>>>> re-delivery it gets another server to talk to which likewise tells you
>>>>>> to
>>>>>> come back later. If you are lucky you get the same server again which
>>>>>> then
>>>>>> recognizes you and lets you send the email.
>>>>>>
>>>>>> The 'solution' I came up with is to increase the number and frequency
>>>>>> of
>>>>>> retries that James makes by changing the Remotedelivery settings in
>>>>>> config.xml to the following: -
>>>>>>
>>>>>> <mailet match="All" class="RemoteDelivery">
>>>>>> ...
>>>>>> <delayTime> 5 minutes </delayTime>
>>>>>> <delayTime> 5 minutes </delayTime>
>>>>>> <delayTime> 20 minutes </delayTime>
>>>>>> <delayTime> 30 minutes </delayTime>
>>>>>> <delayTime> 1 hours </delayTime>
>>>>>> <delayTime> 2 hours </delayTime>
>>>>>> <maxRetries> 6 </maxRetries>
>>>>>> ...
>>>>>> </mailet>
>>>>>>
>>>>>> Without these changes a lot of emails sent to these addresses
>>>>>> eventually
>>>>>> bounced back after 6 hours or so; often delaying important
>>>>>> notifications
>>>>>> until the next day.
>>>>>>
>>>>>> Google and Yahoo users probably don't have these problems because
>>>>>> messages
>>>>>> sent via the web site to another Google or Yahoo user aren't subject
>>>>>> to
>>>>>> Greylisting.
>>>>>>
>>>>>> HTH
>>>>>>
>>>>>> David Legg
>>>>>>
>>>>>> [1] http://projects.puremagic.com/greylisting/whitepaper.html
>>>>>>
>>>>>> ---------------------------------------------------------------------
>>>>>> To unsubscribe, e-mail: server-user-unsubscribe@james.apache.org
>>>>>> For additional commands, e-mail: server-user-help@james.apache.org
>>>>>>
>>>>>>
>>>> ---------------------------------------------------------------------
>>>> To unsubscribe, e-mail: server-user-unsubscribe@james.apache.org
>>>> For additional commands, e-mail: server-user-help@james.apache.org
>>>>
>>>>
>>>
>>> ---------------------------------------------------------------------
>>> To unsubscribe, e-mail: server-user-unsubscribe@james.apache.org
>>> For additional commands, e-mail: server-user-help@james.apache.org
>>>
>>>
>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: server-user-unsubscribe@james.apache.org
>> For additional commands, e-mail: server-user-help@james.apache.org
>>
>>
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: server-user-unsubscribe@james.apache.org
> For additional commands, e-mail: server-user-help@james.apache.org
>
>
Re: RemoteDelivery Problem
Posted by Stefano Bagnara <ap...@bago.org>.
Mark Hale ha scritto:
> Stefano,
>
> That is a problem I wrote about earlier. I enabled debug for
> everything as shown below and I still get INFO messages for the
> RemoteDelivery mailet. I would love more information to go on. Is
> there a problem with how I defined it below? ( I extracted just this
> piece of environment.xml.)
Have you restarted james?
What environment.xml file do you change? You have to change the expanded
one and not the one inside the sar file.
I see exceptions and a lot of lines for each delivery attempt.
Stefano
> Thanks,
>
> Mark
>
> <categories>
> <category name="" log-level="DEBUG">
> <log-target id-ref="default"/>
> </category>
> <category name="James.Mailet" log-level="DEBUG">
> <log-target id-ref="James-Mailet-target"/>
> </category>
> <category name="James" log-level="DEBUG">
> <log-target id-ref="James-target"/>
> </category>
> <category name="spoolmanager" log-level="DEBUG">
> <log-target id-ref="spoolmanager-target"/>
> </category>
> <category name="dnsserver" log-level="DEBUG">
> <log-target id-ref="dnsserver-target"/>
> </category>
> <category name="remotemanager" log-level="DEBUG">
> <log-target id-ref="remotemanager-target"/>
> </category>
> <category name="pop3server" log-level="DEBUG">
> <log-target id-ref="pop3server-target"/>
> </category>
> <category name="smtpserver" log-level="DEBUG">
> <log-target id-ref="smtpserver-target"/>
> </category>
> <category name="nntpserver" log-level="DEBUG">
> <log-target id-ref="nntpserver-target"/>
> </category>
> <category name="nntp-repository" log-level="DEBUG">
> <log-target id-ref="nntp-repository-target"/>
> </category>
> <category name="mailstore" log-level="DEBUG">
> <log-target id-ref="mailstore-target"/>
> </category>
> <category name="users-store" log-level="DEBUG">
> <log-target id-ref="users-store-target"/>
> </category>
> <category name="objectstorage" log-level="DEBUG">
> <log-target id-ref="objectstorage-target"/>
> </category>
> <category name="connections" log-level="DEBUG">
> <log-target id-ref="connections-target"/>
> </category>
> <category name="sockets" log-level="DEBUG">
> <log-target id-ref="sockets-target"/>
> </category>
> <category name="scheduler" log-level="DEBUG">
> <log-target id-ref="scheduler-target"/>
> </category>
> <category name="fetchmail" log-level="DEBUG">
> <log-target id-ref="fetchmail-target"/>
> </category>
> </categories>
>
>
>
>
> On Thu, Aug 21, 2008 at 12:13 AM, Stefano Bagnara <ap...@bago.org> wrote:
>> Mark Hale ha scritto:
>>> David, et al.
>>>
>>> I've really tried with no avail to get outbound messages to send. I
>>> tried a corporate email (interwoven.com) to take gmail and yahoo out
>>> of the equation. For all outbound mail, I still get a temporary
>>> exception as follows. All retries give the same exception. I am able
>>> to telnet to the port returned for the mx record (eg telnet
>>> 208.65.145.13 25) so that I know my fireway or ISP is not blocking.
>>>
>>> ==> mailet-2008-08-20-21-08.log <==
>>> 20/08/08 21:30:47 INFO James.Mailet: RemoteDelivery: Attempting
>>> delivery of Mail1219293046382-2-to-interwoven.com to host
>>> interwoven.com.inbound15.mxlogicmx.net. at 208.65.145.13 for addresses
>>> [mark.hale@interwoven.com]
>>> 20/08/08 21:30:47 INFO James.Mailet: RemoteDelivery: Exception
>>> delivering message (Mail1219293046382-2-to-interwoven.com) - smtp
>>> 20/08/08 21:30:47 INFO James.Mailet: RemoteDelivery: Temporary
>>> exception delivering mail (Mail1219293046382-2-to-interwoven.com:
>>> 20/08/08 21:30:47 INFO James.Mailet: RemoteDelivery: Storing message
>>> Mail1219293046382-2-to-interwoven.com into outgoing after 0 retries
>>>
>>> Would anyone have an idea on what to try next? I am really stumped.
>>
>> Enable DEBUG output and check the logs.
>> You can enable DEBUG by altering the
>> <jamesfolder>/apps/james/SAR-INF/environment.xml file
>>
>> Stefano
>>
>>> Thanks so much.
>>>
>>> Mark
>>>
>>>
>>> On Fri, Jul 11, 2008 at 7:26 AM, Mark Hale <ma...@gmail.com> wrote:
>>>> Thank you for the informative response! I will give it a try and post
>>>> back what I learn.
>>>>
>>>> Mark
>>>>
>>>>
>>>> On Fri, Jul 11, 2008 at 1:43 AM, David Legg
>>>> <da...@searchevent.co.uk> wrote:
>>>>> Hi Mark,
>>>>>
>>>>>> I tried multiple email address
>>>>>> (company, yahoo, gmail, etc) and they all exchibit the same temporary
>>>>>> exception. I can telnet from my box to port 25 on the domains found
>>>>>> in the mx records.
>>>>>>
>>>>> I think this is perfectly normal behaviour. I believe the servers you
>>>>> are
>>>>> sending the email to are using a form of Greylisting [1]. This means
>>>>> that
>>>>> the first time James attempts to send it gets a Temporary exception
>>>>> response. Ideally, James should attempt to re-deliver the email after a
>>>>> suitable delay. The trouble is that large organizations like Google and
>>>>> Yahoo don't have just the one mail server and so when James attempts
>>>>> re-delivery it gets another server to talk to which likewise tells you
>>>>> to
>>>>> come back later. If you are lucky you get the same server again which
>>>>> then
>>>>> recognizes you and lets you send the email.
>>>>>
>>>>> The 'solution' I came up with is to increase the number and frequency of
>>>>> retries that James makes by changing the Remotedelivery settings in
>>>>> config.xml to the following: -
>>>>>
>>>>> <mailet match="All" class="RemoteDelivery">
>>>>> ...
>>>>> <delayTime> 5 minutes </delayTime>
>>>>> <delayTime> 5 minutes </delayTime>
>>>>> <delayTime> 20 minutes </delayTime>
>>>>> <delayTime> 30 minutes </delayTime>
>>>>> <delayTime> 1 hours </delayTime>
>>>>> <delayTime> 2 hours </delayTime>
>>>>> <maxRetries> 6 </maxRetries>
>>>>> ...
>>>>> </mailet>
>>>>>
>>>>> Without these changes a lot of emails sent to these addresses eventually
>>>>> bounced back after 6 hours or so; often delaying important notifications
>>>>> until the next day.
>>>>>
>>>>> Google and Yahoo users probably don't have these problems because
>>>>> messages
>>>>> sent via the web site to another Google or Yahoo user aren't subject to
>>>>> Greylisting.
>>>>>
>>>>> HTH
>>>>>
>>>>> David Legg
>>>>>
>>>>> [1] http://projects.puremagic.com/greylisting/whitepaper.html
>>>>>
>>>>> ---------------------------------------------------------------------
>>>>> To unsubscribe, e-mail: server-user-unsubscribe@james.apache.org
>>>>> For additional commands, e-mail: server-user-help@james.apache.org
>>>>>
>>>>>
>>> ---------------------------------------------------------------------
>>> To unsubscribe, e-mail: server-user-unsubscribe@james.apache.org
>>> For additional commands, e-mail: server-user-help@james.apache.org
>>>
>>>
>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: server-user-unsubscribe@james.apache.org
>> For additional commands, e-mail: server-user-help@james.apache.org
>>
>>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: server-user-unsubscribe@james.apache.org
> For additional commands, e-mail: server-user-help@james.apache.org
>
>
---------------------------------------------------------------------
To unsubscribe, e-mail: server-user-unsubscribe@james.apache.org
For additional commands, e-mail: server-user-help@james.apache.org
Re: RemoteDelivery Problem
Posted by Mark Hale <ma...@gmail.com>.
Stefano,
That is a problem I wrote about earlier. I enabled debug for
everything as shown below and I still get INFO messages for the
RemoteDelivery mailet. I would love more information to go on. Is
there a problem with how I defined it below? ( I extracted just this
piece of environment.xml.)
Thanks,
Mark
<categories>
<category name="" log-level="DEBUG">
<log-target id-ref="default"/>
</category>
<category name="James.Mailet" log-level="DEBUG">
<log-target id-ref="James-Mailet-target"/>
</category>
<category name="James" log-level="DEBUG">
<log-target id-ref="James-target"/>
</category>
<category name="spoolmanager" log-level="DEBUG">
<log-target id-ref="spoolmanager-target"/>
</category>
<category name="dnsserver" log-level="DEBUG">
<log-target id-ref="dnsserver-target"/>
</category>
<category name="remotemanager" log-level="DEBUG">
<log-target id-ref="remotemanager-target"/>
</category>
<category name="pop3server" log-level="DEBUG">
<log-target id-ref="pop3server-target"/>
</category>
<category name="smtpserver" log-level="DEBUG">
<log-target id-ref="smtpserver-target"/>
</category>
<category name="nntpserver" log-level="DEBUG">
<log-target id-ref="nntpserver-target"/>
</category>
<category name="nntp-repository" log-level="DEBUG">
<log-target id-ref="nntp-repository-target"/>
</category>
<category name="mailstore" log-level="DEBUG">
<log-target id-ref="mailstore-target"/>
</category>
<category name="users-store" log-level="DEBUG">
<log-target id-ref="users-store-target"/>
</category>
<category name="objectstorage" log-level="DEBUG">
<log-target id-ref="objectstorage-target"/>
</category>
<category name="connections" log-level="DEBUG">
<log-target id-ref="connections-target"/>
</category>
<category name="sockets" log-level="DEBUG">
<log-target id-ref="sockets-target"/>
</category>
<category name="scheduler" log-level="DEBUG">
<log-target id-ref="scheduler-target"/>
</category>
<category name="fetchmail" log-level="DEBUG">
<log-target id-ref="fetchmail-target"/>
</category>
</categories>
On Thu, Aug 21, 2008 at 12:13 AM, Stefano Bagnara <ap...@bago.org> wrote:
> Mark Hale ha scritto:
>>
>> David, et al.
>>
>> I've really tried with no avail to get outbound messages to send. I
>> tried a corporate email (interwoven.com) to take gmail and yahoo out
>> of the equation. For all outbound mail, I still get a temporary
>> exception as follows. All retries give the same exception. I am able
>> to telnet to the port returned for the mx record (eg telnet
>> 208.65.145.13 25) so that I know my fireway or ISP is not blocking.
>>
>> ==> mailet-2008-08-20-21-08.log <==
>> 20/08/08 21:30:47 INFO James.Mailet: RemoteDelivery: Attempting
>> delivery of Mail1219293046382-2-to-interwoven.com to host
>> interwoven.com.inbound15.mxlogicmx.net. at 208.65.145.13 for addresses
>> [mark.hale@interwoven.com]
>> 20/08/08 21:30:47 INFO James.Mailet: RemoteDelivery: Exception
>> delivering message (Mail1219293046382-2-to-interwoven.com) - smtp
>> 20/08/08 21:30:47 INFO James.Mailet: RemoteDelivery: Temporary
>> exception delivering mail (Mail1219293046382-2-to-interwoven.com:
>> 20/08/08 21:30:47 INFO James.Mailet: RemoteDelivery: Storing message
>> Mail1219293046382-2-to-interwoven.com into outgoing after 0 retries
>>
>> Would anyone have an idea on what to try next? I am really stumped.
>
>
> Enable DEBUG output and check the logs.
> You can enable DEBUG by altering the
> <jamesfolder>/apps/james/SAR-INF/environment.xml file
>
> Stefano
>
>> Thanks so much.
>>
>> Mark
>>
>>
>> On Fri, Jul 11, 2008 at 7:26 AM, Mark Hale <ma...@gmail.com> wrote:
>>>
>>> Thank you for the informative response! I will give it a try and post
>>> back what I learn.
>>>
>>> Mark
>>>
>>>
>>> On Fri, Jul 11, 2008 at 1:43 AM, David Legg
>>> <da...@searchevent.co.uk> wrote:
>>>>
>>>> Hi Mark,
>>>>
>>>>> I tried multiple email address
>>>>> (company, yahoo, gmail, etc) and they all exchibit the same temporary
>>>>> exception. I can telnet from my box to port 25 on the domains found
>>>>> in the mx records.
>>>>>
>>>> I think this is perfectly normal behaviour. I believe the servers you
>>>> are
>>>> sending the email to are using a form of Greylisting [1]. This means
>>>> that
>>>> the first time James attempts to send it gets a Temporary exception
>>>> response. Ideally, James should attempt to re-deliver the email after a
>>>> suitable delay. The trouble is that large organizations like Google and
>>>> Yahoo don't have just the one mail server and so when James attempts
>>>> re-delivery it gets another server to talk to which likewise tells you
>>>> to
>>>> come back later. If you are lucky you get the same server again which
>>>> then
>>>> recognizes you and lets you send the email.
>>>>
>>>> The 'solution' I came up with is to increase the number and frequency of
>>>> retries that James makes by changing the Remotedelivery settings in
>>>> config.xml to the following: -
>>>>
>>>> <mailet match="All" class="RemoteDelivery">
>>>> ...
>>>> <delayTime> 5 minutes </delayTime>
>>>> <delayTime> 5 minutes </delayTime>
>>>> <delayTime> 20 minutes </delayTime>
>>>> <delayTime> 30 minutes </delayTime>
>>>> <delayTime> 1 hours </delayTime>
>>>> <delayTime> 2 hours </delayTime>
>>>> <maxRetries> 6 </maxRetries>
>>>> ...
>>>> </mailet>
>>>>
>>>> Without these changes a lot of emails sent to these addresses eventually
>>>> bounced back after 6 hours or so; often delaying important notifications
>>>> until the next day.
>>>>
>>>> Google and Yahoo users probably don't have these problems because
>>>> messages
>>>> sent via the web site to another Google or Yahoo user aren't subject to
>>>> Greylisting.
>>>>
>>>> HTH
>>>>
>>>> David Legg
>>>>
>>>> [1] http://projects.puremagic.com/greylisting/whitepaper.html
>>>>
>>>> ---------------------------------------------------------------------
>>>> To unsubscribe, e-mail: server-user-unsubscribe@james.apache.org
>>>> For additional commands, e-mail: server-user-help@james.apache.org
>>>>
>>>>
>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: server-user-unsubscribe@james.apache.org
>> For additional commands, e-mail: server-user-help@james.apache.org
>>
>>
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: server-user-unsubscribe@james.apache.org
> For additional commands, e-mail: server-user-help@james.apache.org
>
>
---------------------------------------------------------------------
To unsubscribe, e-mail: server-user-unsubscribe@james.apache.org
For additional commands, e-mail: server-user-help@james.apache.org
Re: RemoteDelivery Problem
Posted by Stefano Bagnara <ap...@bago.org>.
Mark Hale ha scritto:
> David, et al.
>
> I've really tried with no avail to get outbound messages to send. I
> tried a corporate email (interwoven.com) to take gmail and yahoo out
> of the equation. For all outbound mail, I still get a temporary
> exception as follows. All retries give the same exception. I am able
> to telnet to the port returned for the mx record (eg telnet
> 208.65.145.13 25) so that I know my fireway or ISP is not blocking.
>
> ==> mailet-2008-08-20-21-08.log <==
> 20/08/08 21:30:47 INFO James.Mailet: RemoteDelivery: Attempting
> delivery of Mail1219293046382-2-to-interwoven.com to host
> interwoven.com.inbound15.mxlogicmx.net. at 208.65.145.13 for addresses
> [mark.hale@interwoven.com]
> 20/08/08 21:30:47 INFO James.Mailet: RemoteDelivery: Exception
> delivering message (Mail1219293046382-2-to-interwoven.com) - smtp
> 20/08/08 21:30:47 INFO James.Mailet: RemoteDelivery: Temporary
> exception delivering mail (Mail1219293046382-2-to-interwoven.com:
> 20/08/08 21:30:47 INFO James.Mailet: RemoteDelivery: Storing message
> Mail1219293046382-2-to-interwoven.com into outgoing after 0 retries
>
> Would anyone have an idea on what to try next? I am really stumped.
Enable DEBUG output and check the logs.
You can enable DEBUG by altering the
<jamesfolder>/apps/james/SAR-INF/environment.xml file
Stefano
> Thanks so much.
>
> Mark
>
>
> On Fri, Jul 11, 2008 at 7:26 AM, Mark Hale <ma...@gmail.com> wrote:
>> Thank you for the informative response! I will give it a try and post
>> back what I learn.
>>
>> Mark
>>
>>
>> On Fri, Jul 11, 2008 at 1:43 AM, David Legg
>> <da...@searchevent.co.uk> wrote:
>>> Hi Mark,
>>>
>>>> I tried multiple email address
>>>> (company, yahoo, gmail, etc) and they all exchibit the same temporary
>>>> exception. I can telnet from my box to port 25 on the domains found
>>>> in the mx records.
>>>>
>>> I think this is perfectly normal behaviour. I believe the servers you are
>>> sending the email to are using a form of Greylisting [1]. This means that
>>> the first time James attempts to send it gets a Temporary exception
>>> response. Ideally, James should attempt to re-deliver the email after a
>>> suitable delay. The trouble is that large organizations like Google and
>>> Yahoo don't have just the one mail server and so when James attempts
>>> re-delivery it gets another server to talk to which likewise tells you to
>>> come back later. If you are lucky you get the same server again which then
>>> recognizes you and lets you send the email.
>>>
>>> The 'solution' I came up with is to increase the number and frequency of
>>> retries that James makes by changing the Remotedelivery settings in
>>> config.xml to the following: -
>>>
>>> <mailet match="All" class="RemoteDelivery">
>>> ...
>>> <delayTime> 5 minutes </delayTime>
>>> <delayTime> 5 minutes </delayTime>
>>> <delayTime> 20 minutes </delayTime>
>>> <delayTime> 30 minutes </delayTime>
>>> <delayTime> 1 hours </delayTime>
>>> <delayTime> 2 hours </delayTime>
>>> <maxRetries> 6 </maxRetries>
>>> ...
>>> </mailet>
>>>
>>> Without these changes a lot of emails sent to these addresses eventually
>>> bounced back after 6 hours or so; often delaying important notifications
>>> until the next day.
>>>
>>> Google and Yahoo users probably don't have these problems because messages
>>> sent via the web site to another Google or Yahoo user aren't subject to
>>> Greylisting.
>>>
>>> HTH
>>>
>>> David Legg
>>>
>>> [1] http://projects.puremagic.com/greylisting/whitepaper.html
>>>
>>> ---------------------------------------------------------------------
>>> To unsubscribe, e-mail: server-user-unsubscribe@james.apache.org
>>> For additional commands, e-mail: server-user-help@james.apache.org
>>>
>>>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: server-user-unsubscribe@james.apache.org
> For additional commands, e-mail: server-user-help@james.apache.org
>
>
---------------------------------------------------------------------
To unsubscribe, e-mail: server-user-unsubscribe@james.apache.org
For additional commands, e-mail: server-user-help@james.apache.org