As it happens, I have rather fussy HTML signature, with images inserted via inline CSS and other hijinks. I just tried adding it to my account in the SurgeWeb options, and it seems to kill the HTML signature editor. (Marijn, shall I send it to you off-list?)
Aside from that, I'd propose the following:
- Don't send raw HTML in a plain-text email. :)
- For HTML signatures that shrink in the wash, allow an optional additional plain-text version in the settings. (If it's optional, where's the harm?)
- On iOS, display the plain-text signature (custom or washed from HTML) in the editor. Then, when you send the message, search the text, and if you find the exact text of the plain-text signature, replace it with the HTML version and send the email as multipart/alternative.
BTW, note that having a good plain-text version of an HTML signature is relevant to all users of SurgeWeb. Messages sent from the full SurgeWeb interface still have a "Content-Type: text/plain" part that is seen by old-school BlackBerry users and the like.
Best,
Chris
Am 07.05.2013 um 03:48 schrieb Surgemail Support (Marijn) <surgemailHIDDEN@t@netwinsite.com>:
>
> Yes surgeweb does turn on the plain text editor if it detects it is running on an iOS device as there is no html editor available on those platforms like there is on the desktop browsers.
>
> I'd not done any testing in terms of interaction with signature handling, but yes that is expected behaviour and have just run some tests myself which confirms that.
>
> There is no easy way around it no as it stands. What are you proposing as the ideal behaviour for your "way around this"?
>
> Some thoughts, none of which ideal:
> - If plain text editor is detected and signature has html content I just wash wash the html by stripping the html tags. But that is bound to turn into a bit of a dogs dinner as soon as you have any form of significant formatting in an html signature.
> - Possibly easier solution is just to disable the signature addition for plain text messages. Would be easy and I would be in favour of this one, but that is bound to get the signature lovers up in arms.
> - Or separate signature for text mode, but that is a bit ugly in terms of maintenance etc...
>
>
> Marijn
>
>
>
>
> On Sunday 05/05/2013 at 1:16 pm, Lyle Giese wrote:
>> It looks like iOS makes SurgeWeb turn off the html editor and then outgoing messages are in plain text and an html signature looks mangled to the user(it's just showing the html source code actually).
>>
>> I don't have access to an iPad to test, but is there a way around this?
>>
>> Lyle Giese
>> LCR Computer Services, Inc.
>>
>>
>
>
>
>
|
