Skip to content

JAMES-4171 Allow configure strong distinction between submission and …#2939

Merged
Arsnael merged 1 commit intoapache:masterfrom
chibenwa:JAMES-4171
Feb 10, 2026
Merged

JAMES-4171 Allow configure strong distinction between submission and …#2939
Arsnael merged 1 commit intoapache:masterfrom
chibenwa:JAMES-4171

Conversation

@chibenwa
Copy link
Contributor

@chibenwa chibenwa commented Feb 9, 2026

…mx ports

@chibenwa chibenwa self-assigned this Feb 9, 2026
@Arsnael Arsnael merged commit fe81bc7 into apache:master Feb 10, 2026
1 check passed
@chibenwa
Copy link
Contributor Author

This work touches a quite critical part of James code: the SMTP server

I would have had prefered the pull request to stay opened longer so that it has a chance to collect non-linagorian reviews.

As such, if any comments or suggestions arises I'd be happy to carry on follow up work.

- `true`: act as `strict`
- `false`: act as `disabled`

Please note that this parameter only intend to prevent spoofing, and still allow unauthenticated remote users (that do not use local identity) to send email to local users.
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

nitpick

Suggested change
Please note that this parameter only intend to prevent spoofing, and still allow unauthenticated remote users (that do not use local identity) to send email to local users.
Please note that this parameter only intends to prevent spoofing, and still allows unauthenticated remote users (that do not use local identity) to send email to local users.

public HookResult doCheck(SMTPSession session, MaybeSender sender) {
ExtendedSMTPSession nSession = (ExtendedSMTPSession) session;
if (nSession.verifyIdentity() == SMTPConfiguration.SenderVerificationMode.STRICT) {
if (!session.isRelayingAllowed() && !nSession.senderVerificationConfiguration().allowUnauthenticatedSender()) {
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

In this comment on the corresponding jira it was discussed adding a new defaultly loaded hook instead of changing the behaviour of an existing hook

did you change your mind ?

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

No I have some local work adapting this that apparently is not shared in the right place.
I will make sure this is adressed timely.

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

CF #2941
(Sorry)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

4 participants