[
https://issues.apache.org/jira/browse/JSPF-108?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17434751#comment-17434751
]
Benoit Tellier commented on JSPF-108:
-------------------------------------
Hello,
Which class does the code sample code from?
I think this contant needs to become configurable.
Would you like to champion this issue?
Regards,
Benoit
> 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: [email protected]
For additional commands, e-mail: [email protected]
