One more question, is the Problem with outgoing email or local email ?

Bye,
Norman


2009/11/9 karthik <[email protected]>:
> Unfortunately, I cannot provide you complete information because of
> confidential reasons. So, I have made a change in the domain name.
>
>           <gateway>collabnet.mydomainname.com</gateway>
>           <gatewayPort>25</gatewayPort>
>         Please help.
>
>
> Regards,
> Karthik
>
>
> Norman Maurer wrote:
>>
>> Hi,
>>
>> could you show me the RemoteDelivery configuration part of your config.xml
>> ?
>>
>> Thx,
>> Norman
>>
>>
>> 2009/11/9 karthik <[email protected]>:
>>
>>>
>>> Thanks Norman, for your quick reply. I already looked into the mailet.log
>>> and the error message seem to be weird. All the mailets show this
>>>
>>> 25/07/09 09:30:17 INFO  James.Mailet: RemoteAddrNotInNetwork: Authorized
>>> addresses: [127.0.0.1/255.255.255.255]
>>> 25/07/09 09:30:17 INFO  James.Mailet: RemoteDelivery: maxRetries is
>>> larger
>>> than total number of attempts specified. Increasing last delayTime with
>>> 19
>>> attempts
>>> 25/07/09 09:30:17 INFO  James.Mailet: RemoteDelivery: Delay of 21600000
>>> msecs is now attempted: 20 times
>>>
>>>
>>>
>>> Not sure, how to proceed.  Also, I would make a note of upgrading james.
>>>
>>>
>>> Regards,
>>> Karthik
>>>
>>>
>>> Norman Maurer wrote:
>>>
>>>>
>>>> Hi Karthik,
>>>>
>>>> this "error" only tells you that the config files are already in place
>>>> and will not get replaced when unpacking the sar. So nothing to worry
>>>> about.
>>>>
>>>> About your problem, I would start digging in the mailet-*.log file.
>>>>
>>>> Bye,
>>>> Norman
>>>>
>>>> Ps: You should really think about upgrading to james 2.3.2, 2.2.0 is
>>>> really old and many bugs where fix since the release of it..
>>>>
>>>> 2009/11/9 karthik <[email protected]>:
>>>>
>>>>
>>>>>
>>>>> Hi All,
>>>>>
>>>>>      Today, When I was informed that users are not receiving mails, I
>>>>> found an errors in the Phoenix.log like below
>>>>>
>>>>> <Phoenix Snip >
>>>>>
>>>>>   Phoenix was not started by the daemon thus it will not be possible to
>>>>> restart the JVM via the Management interface.
>>>>> INFO 2009-11-01 15:31:08.804 [Phoenix.] (): Installing Sar located at
>>>>> file:/mnt/james/james-2.2.0/apps/james.sar.
>>>>>
>>>>> WARN 2009-11-01 15:31:08.816 [Phoenix.] (): The file
>>>>> SAR-INF/assembly.xml
>>>>> can not be extracted from the Sar
>>>>> "file:/mnt/james/james-2.2.0/apps/james.sar" into directory
>>>>>
>>>>> /mnt/james/james-2.2.0/apps/james/SAR-INF/assembly.xml because there is
>>>>> a
>>>>> file in the way.
>>>>>
>>>>> WARN 2009-11-01 15:31:08.818 [Phoenix.] (): The file SAR-INF/config.xml
>>>>> can
>>>>> not be extracted from the Sar
>>>>> "file:/mnt/james/james-2.2.0/apps/james.sar" into directory
>>>>> /mnt/james/james-2.2.0/apps/james/SAR-INF/config.xml because there is a
>>>>> file
>>>>> in the way.
>>>>> WARN 2009-11-01 15:31:08.820 [Phoenix.] (): The file
>>>>> SAR-INF/environment.xml
>>>>> can not be extracted from the Sar
>>>>> "file:/mnt/james/james-2.2.0/apps/james.sar" into directory
>>>>> /mnt/james-2.2.0/apps/james/SAR-INF/environment.xml because there is a
>>>>> file
>>>>> in the way.
>>>>>
>>>>>   <Phoenix Snip>
>>>>>
>>>>> How do i rectify the errors and ensure the mails start flowing for the
>>>>> users.
>>>>>
>>>>>
>>>>>
>>>>> Regards,
>>>>> Karthik
>>>>>
>>>>> ---------------------------------------------------------------------
>>>>> 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]
>>>>
>>>>
>>>>
>>
>> ---------------------------------------------------------------------
>> 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]

Reply via email to