[ http://issues.apache.org/jira/browse/JAMES-369?page=all ]
     
Vincenzo Gianferrari Pini reopened JAMES-369:
---------------------------------------------


The new approach taken, to always announce the SMTP auth capability, *breaks 
the behaviour of some webmail MUAs*. A safer approach is to have an extra 
config.xml parameter added: <authAnnounce>. When false, the behaviour would be 
as always (depend on <authRequired>); when true, would offer SMTP auth to every 
client, including the ones in the authorized subnets.
A question though arises: would it make sense to have both 
<authRequired>false</authRequired> and <authAnnounce>true</authAnnounce>? If 
not, it would be better to just add a new possible value to <authRequired>: 
<authRequired>announce</authRequired>, that implies 
<authRequired>true</authRequired>.
In the meantime, I will revert to the original behaviour to avoid problems.

> Always announce AUTH capability to clients
> ------------------------------------------
>
>          Key: JAMES-369
>          URL: http://issues.apache.org/jira/browse/JAMES-369
>      Project: James
>         Type: Improvement
>     Versions: 2.2.0
>     Reporter: Vincenzo Gianferrari Pini
>     Assignee: Vincenzo Gianferrari Pini
>     Priority: Minor
>      Fix For: 2.2.1

>
> It would be useful to have James always announce its ability to handle the 
> AUTH commands, even when it is not required to authenticate, in order to have 
> the sender optionally authenticate if able to do it.
> This way, if the sender MUA (or MTA) authenticates, the James server is able 
> to SMIMESign the message because the sender user is known, independently of 
> being or not in an authorized subnet and from becoming authorized to relay or 
> not.

-- 
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: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Reply via email to