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 "tuister (Jira)" <se...@james.apache.org> on 2021/10/27 09:11:00 UTC
[jira] [Updated] (JSPF-108) About Processing Limits:
SPFSession.MAX_DEPTH
[ https://issues.apache.org/jira/browse/JSPF-108?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
tuister updated JSPF-108:
-------------------------
Description:
Today, some companies will use many email service providers to send their emails, such as vivo.com
{code:java}
$ dig vivo.com txt|grep spf
vivo.com. 0 IN TXT "v=spf1 include:spf.163.com include:spf.protection.outlook.com include:mail.zendesk.com -all"{code}
Parsing such spf record will exceed the processing limit,
{code:java}
public void increaseCurrentDepth() throws PermErrorException {
this.currentDepth++;
if (currentDepth > MAX_DEPTH)
throw new PermErrorException(
"Maximum mechanism/modifiers calls done: "
+ currentDepth);
}
{code}
So how about making the field MAX_DEPTH mutable? This will be convenient for users.
Thanks
was:
Today, some companies will use varous email provider to send their emails, such as vivo.com
{code:java}
$ dig vivo.com txt|grep spf
vivo.com. 0 IN TXT "v=spf1 include:spf.163.com include:spf.protection.outlook.com include:mail.zendesk.com -all"{code}
Parsing such spf record will exceed the processing limit,
{code:java}
public void increaseCurrentDepth() throws PermErrorException {
this.currentDepth++;
if (currentDepth > MAX_DEPTH)
throw new PermErrorException(
"Maximum mechanism/modifiers calls done: "
+ currentDepth);
}
{code}
So how about making the field MAX_DEPTH mutable? This will be convenient for users.
Thanks
> About Processing Limits: SPFSession.MAX_DEPTH
> ---------------------------------------------
>
> Key: JSPF-108
> URL: https://issues.apache.org/jira/browse/JSPF-108
> Project: James jSPF
> Issue Type: Improvement
> Reporter: tuister
> Priority: Major
>
> Today, some companies will use many email service providers to send their emails, such as vivo.com
> {code:java}
> $ dig vivo.com txt|grep spf
> vivo.com. 0 IN TXT "v=spf1 include:spf.163.com include:spf.protection.outlook.com include:mail.zendesk.com -all"{code}
> Parsing such spf record will exceed the processing limit,
> {code:java}
> public void increaseCurrentDepth() throws PermErrorException {
> this.currentDepth++;
> if (currentDepth > MAX_DEPTH)
> throw new PermErrorException(
> "Maximum mechanism/modifiers calls done: "
> + currentDepth);
> }
> {code}
> So how about making the field MAX_DEPTH mutable? This will be convenient for users.
>
> Thanks
>
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
---------------------------------------------------------------------
To unsubscribe, e-mail: server-dev-unsubscribe@james.apache.org
For additional commands, e-mail: server-dev-help@james.apache.org