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 Eric Charles <er...@apache.org> on 2012/07/27 16:07:36 UTC
Re: remotedelivery logging
Hi Tim,
Could you take gather all your proposals in a patch and upload it via
JIRA (https://issues.apache.org/jira/browse/JAMES)?
Thx, Eric
On 07/26/2012 11:25 PM, timprepscius wrote:
> Also, (sorry for being spammy)
>
> It would probably be good to put the example
>
> <!--
> <mail.smtp.starttls.enable>true</mail.smtp.starttls.enable>
> -->
>
> in the remote delivery mailet configuration
>
> -tim
>
> On Jul 26, 2012, at 5:14 PM, timprepscius wrote:
>
>> And of course, just after I email, I try "one more thing" and it is right.
>>
>> if you have similar problems, try this. (i don't know if both are necessary)
>>
>> <!-- 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">
>> <debug>true</debug>
>> <mail.debug>true</mail.debug>
>>
>>
>> -tim
>>
>> On Jul 26, 2012, at 5:07 PM, timprepscius wrote:
>>
>>> Ok I've been googling, and I just can't find the answer to this.
>>>
>>>
>>> So I forgot to set the EHLO name in the RemoteDelivery mailet.
>>> It's amazing any mail was sent actually.
>>>
>>>
>>>
>>> I think it might be a good idea to put a note in the SMTP conf
>>>
>>> <!-- This is the name used by the server to identify itself in the SMTP -->
>>> <!-- protocol. If autodetect is TRUE, the server will discover its -->
>>> <!-- own host name and use that in the protocol. If discovery fails, -->
>>> <!-- the value of 'localhost' is used. If autodetect is FALSE, James -->
>>> <!-- will use the specified value. -->
>>>
>>> something like
>>>
>>> <!-- You are not done setting the HELO name, this same HELO name needs to be set in the RemoteDelivery mailet. (see mailetcontainer.conf) -->
>>>
>>>
>>> Anyhow.
>>>
>>> So, I want to turn the debugging on for the RemoteDelivery mailet, and do a check to make sure that 1. I've identified the correct problem. 2. I successfully fix it.
>>>
>>>
>>> But I'm having problems turning on the RemoteDelivery mailet logging.
>>>
>>>
>>> I have:
>>>
>>> <mailet match="All" class="RemoteDelivery">
>>> <debug>true</debug>
>>>
>>>
>>> I have also:
>>>
>>> log4j.logger.james.mailetcontext=DEBUG, MAILETCONTAINER
>>>
>>> (I've also enabled DEBUG for any other "parent logging" that I see, although it makes no difference. (I'm grasping at straws))
>>>
>>> Any hints?
>>>
>>>
>>> -tim
>>>
>>>
>>>
>>> ---------------------------------------------------------------------
>>> 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
>>
>>
>
>
--
eric | http://about.echarles.net | @echarles
---------------------------------------------------------------------
To unsubscribe, e-mail: server-user-unsubscribe@james.apache.org
For additional commands, e-mail: server-user-help@james.apache.org
Re: remotedelivery logging
Posted by timprepscius <ti...@piratemail.se>.
Sure. Done. Does anything spring to mind with regard to the spam-filter question?
I think I'm looking for Bayesian filtering, but on some global constantly updated spam mail sample.
Any hints?
-tim
On Jul 27, 2012, at 10:07 AM, Eric Charles wrote:
> Hi Tim,
>
> Could you take gather all your proposals in a patch and upload it via JIRA (https://issues.apache.org/jira/browse/JAMES)?
>
> Thx, Eric
>
> On 07/26/2012 11:25 PM, timprepscius wrote:
>> Also, (sorry for being spammy)
>>
>> It would probably be good to put the example
>>
>> <!--
>> <mail.smtp.starttls.enable>true</mail.smtp.starttls.enable>
>> -->
>>
>> in the remote delivery mailet configuration
>>
>> -tim
>>
>> On Jul 26, 2012, at 5:14 PM, timprepscius wrote:
>>
>>> And of course, just after I email, I try "one more thing" and it is right.
>>>
>>> if you have similar problems, try this. (i don't know if both are necessary)
>>>
>>> <!-- 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">
>>> <debug>true</debug>
>>> <mail.debug>true</mail.debug>
>>>
>>>
>>> -tim
>>>
>>> On Jul 26, 2012, at 5:07 PM, timprepscius wrote:
>>>
>>>> Ok I've been googling, and I just can't find the answer to this.
>>>>
>>>>
>>>> So I forgot to set the EHLO name in the RemoteDelivery mailet.
>>>> It's amazing any mail was sent actually.
>>>>
>>>>
>>>>
>>>> I think it might be a good idea to put a note in the SMTP conf
>>>>
>>>> <!-- This is the name used by the server to identify itself in the SMTP -->
>>>> <!-- protocol. If autodetect is TRUE, the server will discover its -->
>>>> <!-- own host name and use that in the protocol. If discovery fails, -->
>>>> <!-- the value of 'localhost' is used. If autodetect is FALSE, James -->
>>>> <!-- will use the specified value. -->
>>>>
>>>> something like
>>>>
>>>> <!-- You are not done setting the HELO name, this same HELO name needs to be set in the RemoteDelivery mailet. (see mailetcontainer.conf) -->
>>>>
>>>>
>>>> Anyhow.
>>>>
>>>> So, I want to turn the debugging on for the RemoteDelivery mailet, and do a check to make sure that 1. I've identified the correct problem. 2. I successfully fix it.
>>>>
>>>>
>>>> But I'm having problems turning on the RemoteDelivery mailet logging.
>>>>
>>>>
>>>> I have:
>>>>
>>>> <mailet match="All" class="RemoteDelivery">
>>>> <debug>true</debug>
>>>>
>>>>
>>>> I have also:
>>>>
>>>> log4j.logger.james.mailetcontext=DEBUG, MAILETCONTAINER
>>>>
>>>> (I've also enabled DEBUG for any other "parent logging" that I see, although it makes no difference. (I'm grasping at straws))
>>>>
>>>> Any hints?
>>>>
>>>>
>>>> -tim
>>>>
>>>>
>>>>
>>>> ---------------------------------------------------------------------
>>>> 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
>>>
>>>
>>
>>
>
>
> --
> eric | http://about.echarles.net | @echarles
>
>
> ---------------------------------------------------------------------
> 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