Bug 5836 - SpamAssassin doesn't decode URL-encoding in mailto: scheme urls
Summary: SpamAssassin doesn't decode URL-encoding in mailto: scheme urls
Status: RESOLVED DUPLICATE of bug 5780
Alias: None
Product: Spamassassin
Classification: Unclassified
Component: spamassassin (show other bugs)
Version: 3.2.4
Hardware: Other other
: P5 normal
Target Milestone: Undefined
Assignee: SpamAssassin Developer Mailing List
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2008-02-25 13:59 UTC by Yanyan Yang
Modified: 2008-02-25 14:56 UTC (History)
1 user (show)



Attachment Type Modified Status Actions Submitter/CLA Status
Test case that contains url-encoded mailto address text/plain None Yanyan Yang [NoCLA]
The proposed patch to do url-decoding for mailto scheme as well text/plain None Yanyan Yang [NoCLA]

Note You need to log in before you can comment on or make changes to this bug.
Description Yanyan Yang 2008-02-25 13:59:27 UTC
Spammers start to do URL-encoding in mailto scheme, something like this:

<A HREF="mailto:someaddress@apache%2Eorg">someaddress@apache%2Eorg</a>

And the url list returned by SpamAssasin would look like:

mailto:someaddress@apache%2Eorg

Looks like that API uri_list_canonify() in Util.pm ignores mailto when doing
canonify process.

Will attach test case.
Comment 1 Yanyan Yang 2008-02-25 14:02:37 UTC
Created attachment 4264 [details]
Test case that contains url-encoded mailto address
Comment 2 Yanyan Yang 2008-02-25 14:06:00 UTC
Created attachment 4265 [details]
The proposed patch to do url-decoding for mailto scheme as well

Not sure if there was any performance concern or any other implications so the
mailto scheme was ignored in uri_list_canonify() in Util.pm.
Comment 3 Sidney Markowitz 2008-02-25 14:56:13 UTC
This test case already works in trunk due to the changes I made for bug 5780.

Here's a reminder to committers that we need one more vote for the fixes to bug
5780 and bug 5813 so I can commit their combined patch to the 3.2 branch.

Closing this bug as a duplicate of bug 5780.


*** This bug has been marked as a duplicate of 5780 ***