![]() |
|
FastMail Forum All posts relating to FastMail.FM should go here: suggestions, comments, requests for help, complaints, technical issues etc. |
![]() |
|
Thread Tools |
![]() |
#16 | |
Essential Contributor
Join Date: Dec 2017
Location: Scotland
Posts: 431
|
Yes, I understood the intent.
Quote:
Looking back at the first RFC for Sieve, RFC3028, this is described. And interestingly it says that the only required Sieve parser escape sequences are backslash backslash, and backslash doublequote which I think means (unless a later RFC changed it) that is actually correct. That is, the Sieve parser won't swallow that backslash because it's not followed by either another backslash or a double quote! Or maybe not. The RFC also says: 'an undefined escape sequence (such as "\a" in a context where "a" has no special meaning) is interpreted as if there were no backslash (in this case, "\a" is just "a").' .... Which seems to me to be weird, because it seems to say that the escape character is elided in those situations, which means it IS being treated as an escape character and not a literal. Last edited by JeremyNicoll : 14 Mar 2023 at 05:59 AM. Reason: added last paragraph to sow confusion |
|
![]() |
![]() |
![]() |
#17 | |
Essential Contributor
Join Date: May 2018
Posts: 464
|
Quote:
So if you are a "purist" then that "^5\.[6-9]$" is incorrect but it's just not worth the ticket pestering FM about it since that '.' in the context of this regular expression for the spam score will match any character there but it's always going to be a '.' anyhow since FM always formats the spam score correctly. |
|
![]() |
![]() |
![]() |
#18 |
Essential Contributor
Join Date: Jan 2017
Posts: 257
|
|
![]() |
![]() |
![]() |
Thread Tools | |
|
|