[ 
https://issues.apache.org/jira/browse/MPIR-401?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17324440#comment-17324440
 ] 

Lukas Theussl edited comment on MPIR-401 at 4/18/21, 7:20 AM:
--------------------------------------------------------------

To be specific: I just checked that with the following input
{quote}<subscribe>https://sf.net/subscribe</subscribe>
 <unsubscribe>unsubscr...@sf.net</unsubscribe>
{quote}
Using pir plugin 2.9 I get correct links. ie *only* the unsubscribe address 
gets a {{mailto:}}. With 3.1.1 *both* links get a {{mailto:}}.


was (Author: ltheussl):
To be specific: I just checked that with the following input

{{<subscribe>https://sf.net/subscribe</subscribe>}}
{{ <unsubscribe>unsubscr...@sf.net</unsubscribe>}}

Using pir plugin 2.9 I get correct links. ie *only* the unsubscribe address 
gets a {{mailto:}}. With 3.1.1 *both* links get a {{mailto:}}.

> Mailing list subscribe and unsubscribe links
> --------------------------------------------
>
>                 Key: MPIR-401
>                 URL: https://issues.apache.org/jira/browse/MPIR-401
>             Project: Maven Project Info Reports Plugin
>          Issue Type: Improvement
>          Components: mailing-lists
>    Affects Versions: 3.1.2
>            Reporter: Joshua
>            Priority: Major
>
> This is related to the fix done in 
> https://issues.apache.org/jira/browse/MPIR-398
> We were using the mailing list a little different that what was expected.
> So for us we don't have a mailing list, but we do have yammer and we were 
> using the subscribe and unsubscribe links to subscribe and unsubscribe to our 
> yammer group. We use the yammer group as a mailing list.
> When we took 3.1.2 it broke our links because now they have a mailto: before 
> the link.
> Curious if it would be possible to enhance this code to detect if the value 
> in the unsubscribe and subscribe is an email address or a URL. If it is an 
> email address then add the mailto: other wise don't.
>  



--
This message was sent by Atlassian Jira
(v8.3.4#803005)

Reply via email to