Lighthouse has a new layout. Prefer the old one? Return to the old layout, and switch back any time from the link at the top of each page.

semicolon from nowhere

#165

When pasting url:s into mail messages, I habitually surround them with angle brackets:

<http://www.example.com/another_example/>

When sending the message, Mailmate adds a semicolon after the right bracket:

<http://www.example.com/another_example/>;

The semicolon is present in the message at the receiver’s end and (of course) also locally in the sent message. When clicking the link in the sent message the semicolon is added at the end of the url, which in most cases gives a 404 error message at the visited server.

Desired behaviour: 1. Do not add semicolon.
2. Only pick up the part of the url between the brackets.

Reported by Thomas Grundberg · June 24th, 2011 @ 11:41 AM

State: fixreleased
Milestone: none
Assigned to: benny benny

Activity

  1. benny
    benny
    • State changed from new to reproduced
    • Assigned user set to benny

    The problem is only display related. The message sent does not contain this semicolon. It is only when MailMate converts a plain text message to HTML that the problem arises (no matter which email client the message comes from). The semicolon arises because the '>' is converted into an HTML entity (>) before a search and replace is done for making links out of any URLs found in the message.

    Thanks for noticing this issue.

    June 24th, 2011 @ 04:19 PM

  2. Thomas Grundberg
    Thomas Grundberg

    Thanks, Benny. I was certain that Mailmate sent the semicolon, but then my test person was somewhat vague. Good to know that it’s only a local thing.

    June 25th, 2011 @ 08:35 AM

  3. benny
    benny

    For the record: The raw message can always be seen using “View ▸
    Show Raw Source” (⌥⌘U). Messages generated by MailMate are
    generally very readable in their raw form.

    June 25th, 2011 @ 12:15 PM

  4. Thomas Grundberg
    Thomas Grundberg

    Messages encoded as 8bit pose no problem in raw form:

    Content-Type: text/plain; charset=utf-8; format=flowed
    Content-Transfer-Encoding: 8bit
    X-Mailer: MailMate (1.2r2191)
    
    Attagirl! Uppriktigt sagt ser jag bara hermeliner på scen. Det enda du 
    behöver tänka på är att det alltid är bra att vara påläst.
    

    While quoted printable always messes up non-us-ascii chars:

    Content-Type: text/plain; charset=utf-8; format=flowed
    Content-Transfer-Encoding: quoted-printable
    X-Mailer: MailMate (1.2r2191)
    
    st=C3=B6tte p=C3=A5 en artikel om v=C3=A4rldens f=C3=B6r stunden snabbast=
    e dator:
    

    OTOH, the formatted message looks ok: stötte på en artikel om världens för stunden snabbaste dator:

    I have no idea what makes a mail client prefer one encoding before another. This is a royal pain in the behind when posting to mailing lists: there is no way to tell if the recipients’ mail software will render it correctly or not.

    Very off-topic, sorry, but had to get it off my chest.

    June 26th, 2011 @ 09:27 AM

  5. benny
    benny
    • State changed from reproduced to fixcommitted

    MailMate tries to avoid quoted-printable, but there are some exceptions currently (it can be tricky). If you have an example of an ordinary email for which you do not think MailMate should have chosen quoted printable (like indicated above) then you are welcome to send it to me. I prefer readable raw messages (within the limits of the email standards).

    I “hacked” a fix for the ';' issue. Auto-linking in text (or HTML) is a non-trivial problem.

    June 27th, 2011 @ 08:41 AM

  6. Thomas Grundberg
    Thomas Grundberg

    Thanks again, Benny. An example email will follow.

    June 27th, 2011 @ 02:50 PM

  7. benny
    benny
    • State changed from fixcommitted to fixreleased

    August 3rd, 2011 @ 12:04 PM

  8. Joachim Tingvold
    Joachim Tingvold

    I got this issue today. See attached email.

    The URL is displayed as <http://www.cisco.com/en/US/prod/collateral/wireless/ps5678/ps10981/design_guide_c07-693245.html>;., where the '>' is included in the link.

    June 5th, 2012 @ 09:53 AM

  9. benny
    benny

    Thanks, I've improved it and I think it should be pretty robust now (with regard to the ;-issue).

    June 7th, 2012 @ 07:33 AM

Please Sign in or create a free account to add a new ticket.

With your very own profile, you can contribute to projects, track your activity, watch tickets, receive and update tickets through your email and much more.