[jira] [Commented] (JAMES-4171) Submission only server

    [ https://issues.apache.org/jira/browse/JAMES-4171?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=18057772#comment-18057772 ] 

Benoit Tellier commented on JAMES-4171:
---------------------------------------

> all the other security countermeasures seem to be implemented that way 🤷‍♂

Let me politely disagree 

Be it verifyIdentity or relay:
 - The code implements it as a hook
 - bundled by default
 - And does not expose the hook to end user but simpler properties in smtpserver.xml  

As a user oblivious to SMTP inner architecture I indeed prefer a built in option rather than having to seek doc for extension and configure one with tricky XML syntax. I think for basic option we need to provide our users some clarity.

> Submission only server
> ----------------------
>
>                 Key: JAMES-4171
>                 URL: https://issues.apache.org/jira/browse/JAMES-4171
>             Project: James Server
>          Issue Type: Improvement
>          Components: SMTPServer
>            Reporter: Benoit Tellier
>            Priority: Major
>          Time Spent: 0.5h
>  Remaining Estimate: 0h
>
> h3. Context 
> I end up having to provide a submission only server for one of my customer.
> Problem: James bundles together the MX and submission role thus always accept email of remote users addressed to local users.
> This unorthodox behaviour is not a problem when combining both roles (though surprising!) however not being able to say "only authenticated users here" prevents implementing the aformentionned use case
> h3. Proposal
> Add auth.required configuration option in SMTP
> If true, then discard unauthenticated senders.
> This shall be the documented + recommended value however for retro-compatibility I propose to keep the legacy value as a default value.



--
This message was sent by Atlassian Jira
(v8.20.10#820010)