You are viewing a plain text version of this content. The canonical link for it is here.
Posted to server-dev@james.apache.org by "Benoit Tellier (Jira)" <se...@james.apache.org> on 2022/10/03 01:35:00 UTC
[jira] [Commented] (JAMES-3820) DNS Blocklist: implement DNSRBLHandler as MailHook instead of RcptHook
[ https://issues.apache.org/jira/browse/JAMES-3820?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17612160#comment-17612160 ]
Benoit Tellier commented on JAMES-3820:
---------------------------------------
Merged.
We should be good, right?
Can I close the issue?
> DNS Blocklist: implement DNSRBLHandler as MailHook instead of RcptHook
> ----------------------------------------------------------------------
>
> Key: JAMES-3820
> URL: https://issues.apache.org/jira/browse/JAMES-3820
> Project: James Server
> Issue Type: Improvement
> Components: SMTPServer
> Reporter: ouvtam
> Priority: Minor
> Time Spent: 1h 40m
> Remaining Estimate: 0h
>
> At the moment the DNSRBL handler (org.apache.james.protocols.smtp.core.fastfail.DNSRBLHandler) is implemented as a RcptHook. Thus, for every RCPT TO call this handler will be called and a blocklist lookup will be issued.
> One can argue It makes sense to implement the handler as a ConnectHandler, so the blocklist check is done as early as possible. However, if SMTP AUTH is successful then we should allow the connecting client anyway.
> Therefore it makes sense to implement the DNSRBL handler at MAIL FROM stage that is MailHook. One exception is the following. According to [RFC 4954|https://datatracker.ietf.org/doc/html/rfc4954#section-5], authentication information can optionally provided as ESMTP AUTH parameter with a _single_ value in the '{{{}MAIL FROM:{}}}' command.
>
>
>
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
---------------------------------------------------------------------
To unsubscribe, e-mail: server-dev-unsubscribe@james.apache.org
For additional commands, e-mail: server-dev-help@james.apache.org