Re: Text wrapping and quoted-printable

[Sean McBride]

On Jun 14, 2011, at 18:45, Ben Kennedy wrote:

>> New release (6.1b3) has fixed this it seems!
> 
> Indeed it is -- woohoo.  Thanks, Jérôme!

Yes, this small change makes a huge difference!  Though I've given up on 
PowerMail at home, this will let me hang on a little longer at work (where the 
2 GB limit is less of a problem).

Sean

Re: Text wrapping and quoted-printable

[Ben Kennedy]

Derry Thompson wrote at 4:57 PM (+0100) on 6/14/11:

>New release (6.1b3) has fixed this it seems!

Indeed it is -- woohoo.  Thanks, Jérôme!

cheers,

-ben


--
Ben Kennedy (chief magician)
zygoat creative technical services
http://www.zygoat.ca

Re: Text wrapping and quoted-printable

[Derry Thompson]

Ben Kennedy at b...@zygoat.ca said on Fri, 25 Feb 2011 12:03:22 -0800

>What was the final word on the state of PowerMail's handling of text-
>wrapping in outbound messages?
>
>I routinely get hell from my colleagues using Mail.app when I try to
>send them URLs that get broken across line breaks.  Mail.app does not
>respect the angle-bracket convention, so it only sees the first part of
>the URL.


New release (6.1b3) has fixed this it seems!

Cheers

--
Derry

Re: Text wrapping and quoted-printable

[Tobias Jung]

Sean McBride wrote (Wed, 9 Mar 2011 22:12:43 -0500):

>> I routinely get hell from my colleagues using Mail.app when I try to
>> send them URLs that get broken across line breaks.  Mail.app does not
>> respect the angle-bracket convention, so it only sees the first part of
>> the URL.
>
> More chance of Apple fixing this.  Is it just a convention or it is
> actually in an RFC or something?

RFC 3986 says:
"Using <> angle brackets around each URI is especially recommended as a
delimiting style for a reference that contains embedded whitespace."
... and of course, the line break IS a whitespace. Moreover, it
recommends to "recognize and strip both delimiters and embedded whitespace".


So it's just a recommendation but it has been around long enough so
Apple Mail (and every other email client) should know and respect this...
But of course we know that this is not the case so I still use  (or rather, the iTiny URL Dashboard Widget) whenever I
have to send long URLs. Hate to do this, but it seems to be the only
reasonable way...

Kind regards,
Tobias Jung

Re: Text wrapping and quoted-printable

[Sean McBride]

On Feb 25, 2011, at 15:03, Ben Kennedy wrote:

> Hey all,
> 
> I'm loath to revive an old and (I thought settled) discussion, but I did
> a search of my saved email and can't seem to find the particulars.
> 
> What was the final word on the state of PowerMail's handling of text-
> wrapping in outbound messages?

This bug annoys me as well. No doubt it will never be fixed. :(

> I routinely get hell from my colleagues using Mail.app when I try to
> send them URLs that get broken across line breaks.  Mail.app does not
> respect the angle-bracket convention, so it only sees the first part of
> the URL.

More chance of Apple fixing this.  Is it just a convention or it is actually in 
an RFC or something?

Sean

Re: Text wrapping and quoted-printable

[Charles Watts-Jones]

On 25 February Peter Lovell  wrote:

> I'm also having a *lot* of problem with PM not dealing with
> multi-part MIME content boundaries, such as
> Content-type: multipart/alternative;
> boundary*0=;
> boundary*1=000
>
> I get many messages formatted this way and PM is useless -
> it shows zero content!. Nothing. Nada. Zilch.  This is a
> real pain.

Checking my files, I see that this issue was raised last September by
the 'usual suspects'. I find it seriously annoying with my only solution
being to read the affected mail on-line. Far from ideal, especially when
I want to keep the message. Now that CTM is up-to-date with PM and
FoxTrot, perhaps we'll see some action.

-- Charles

Re: Text wrapping and quoted-printable

[Peter Lovell]

On Fri, Feb 25, 2011, Ben Kennedy  wrote:

>Hey all,
>
>I'm loath to revive an old and (I thought settled) discussion, but I did
>a search of my saved email and can't seem to find the particulars.
>
>What was the final word on the state of PowerMail's handling of text-
>wrapping in outbound messages?
>
>I routinely get hell from my colleagues using Mail.app when I try to
>send them URLs that get broken across line breaks.  Mail.app does not
>respect the angle-bracket convention, so it only sees the first part of
>the URL.
>
>It appears that PM sends outbound messages with a "Content-Transfer-
>Encoding: quoted-printable", which should facilitate soft wrapping by
>encoding soft EOLs with "=".  However, PM omits the "=" in favour of a
>plain CR/LF, which is interpreted as a hard line break.
>
>Why is this?  Is there some rationale in its favour?  It is not obvious
>to me how this is at all desirable.
>
>cheers,
>
>-ben

Hi Ben,

I have noticed similar issues and filed a bug report back in November
about the issue.

I hadn't recognized it as an encoding issue - so I just complained that
PM was hard-folding lines when sending, unlike Mail.app.

So far I've not received any response but maybe it's time to push the
issue again as it is quite problematic.

I'm also having a *lot* of problem with PM not dealing with multi-part
MIME content boundaries, such as
Content-type: multipart/alternative;
 boundary*0=;
 boundary*1=000

I get many messages formatted this way and PM is useless - it shows zero
content!. Nothing. Nada. Zilch.  This is a real pain.

Regards.Peter