[
https://issues.apache.org/jira/browse/JAMES-4171?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=18057779#comment-18057779
]
Jean Helou commented on JAMES-4171:
-----------------------------------
I think I understand better, do you think it would make sense to keep the
behavior separate from AbstractAuthRequiredToRelayRcptHook and introduce a new
mandatory SubmissionServerHook which applies this new behavior ?
> I propose to update the SMTP default configuration to explicitly set
> authRequired = false on MX to be clearer.
Not sure I understand what you mean but I'll see in the PR :D
> Ideally yes but I'm not in for such a breaking change.
hmm adding a new kind of entry is not a breaking change but I admit it is
probably more work. especially given how the current code parses the
configuration
> 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)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
