-
Notifications
You must be signed in to change notification settings - Fork 60
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
False positive Link Fraud with quoted .com url #621
Comments
Still looking at this one, trying to get caught up on these and others. |
Adding
These lines seem to be responsible for the different handling of .com tld and others. Do you know what the intention was for checking only these? v5/common/usr/share/MailScanner/perl/MailScanner/Message.pm Lines 7857 to 7858 in 668cea1
|
@Skywalker-11 Those look like common tlds, albeit a limited list of them. I'm not sure what the intent was here, but they seem to be there to catch urls containing them, perhaps if the other conditions don't catch? |
Feel free to create a PR. I think your suggested substitution is good. |
The PR fixes the quoting issue but the different actions for those specific TLDs should probably still be looked at again. |
Describe the bug
Quoted links eg. "http://example.com" are falsely identified as fraud url. This seems to only affect specific TLDs (here .com). Other TLDs eg. .de or fictional 3 letter TLDs like
.bla
seem to not be affected. The messageFound phishing fraud from http://www.example.com claiming to be www."http: in <msg-id>
is logged.EDIT: Even when the url does not contain
http://www.
the log message looks like thisFound phishing fraud from http://bla.example.com claiming to be www."http: in <msg-id>
To Reproduce
Send a mail with HTML only or HTML/plain-text mixed content which contains a link with quoted .com url eg.
Expected behavior
.com
TLD also shouldn't be handled differently than other TLDs regarding the fraud detection.Examples
Server (please complete the following information):
Additional context
Notice: Thunderbird automatically creates the link in the example when someone uses "http://xyz.tld" in a normal text (without explicitly defining at as a link).
The text was updated successfully, but these errors were encountered: