You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@ponymail.apache.org by ShaneCurcuru <gi...@git.apache.org> on 2016/10/13 02:37:01 UTC

[GitHub] incubator-ponymail issue #181: Reply via client breaks when message too larg...

GitHub user ShaneCurcuru opened an issue:

    https://github.com/apache/incubator-ponymail/issues/181

    Reply via client breaks when message too large

    When the message being replied too is too large (working theory; could possibly be odd characters but doesn't seem so), the Reply via your own mail client silently fails.
    
    Sample message that fails:
    https://lists.apache.org/thread.html/f2ba557c69611535038bdb24451ab725ae950aaf917983c18a996b27@%3Cdev.ponymail.apache.org%3E
    
    Mac/Chrome/Version 53.0.2785.143 (64-bit) with Thunderbird as default mail client (which works for short messages).
    
    Chrome developer tools shows the GET mailto:... link was clicked, but (cancelled). It seems to have the right headers and start of the email body content.
    
    It's likely various client OS/browsers/mail clients have slightly different max URL lengths.  Possible enhancements are either clipping the mailto: at some default max length, or somehow otherwise abbreviating or shortening some reply-level in the body somehow (but that would be arbitrary).

----

----


---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at infrastructure@apache.org or file a JIRA ticket
with INFRA.
---

[GitHub] incubator-ponymail issue #181: Reply via client breaks when message too larg...

Posted by Humbedooh <gi...@git.apache.org>.
Github user Humbedooh commented on the issue:

    https://github.com/apache/incubator-ponymail/issues/181
  
    Most likely a URI length issue here, various browsers only support a mailto link of N kilobytes, the trick is figuring out when the limit has been hit and then truncate. Obviously we need to improve that again


---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at infrastructure@apache.org or file a JIRA ticket
with INFRA.
---