Skip to content

Loading…

SMTP Error when an image as signature #644

Closed
Marc95 opened this Issue · 20 comments

3 participants

@Marc95

When I create a JPG as signature, sending message from Conversation View generate an SMTP error.
The message is sending normally using the standard interface with the jpg at the bottom.

It's the same with a text signature in fact.

I use T15.0.1 and conversations 2.4.3

Marc

@protz
Owner
@Marc95
@Marc95

I retype the mesasge as I think the attachement is no accepted.

L'envoi du message a échoué.
Le message n'a pas pu être envoyé car la connexion au serveur SMTP "ns0.ovh.net" a expiré.
Essayez à nouveau ou contactez votre administrateur réseau

<<>>

@protz
Owner

I don't think it's related to the signature. More likely, the quick reply is picking the wrong identity for replying. Have you checked all your identities and smtp servers?

@Marc95
@protz
Owner

Do you have several identities?

@Marc95
@protz
Owner

Please check which email address the quick reply is picking; then, please check each identity associated to that email adress. The quick reply may be picking a different identity than the regular compose window.

@Marc95
@protz
Owner

Somehow the quick reply is picking your OVH server for sending the message.

@Marc95
@protz
Owner
@Marc95
@Marc95
@protz
Owner

the email interface for github doesn't allow you to attach pictures, so I'm not sure I can see what you're talking about

@Marc95
@protz
Owner
@milanspk

i'm having exactly the same problem when sending a quick reply with a .jpg signature:

"Sending of message failed. The message could not be sent because the connection to SMTP server smtp.gmail.com timed out. Try again or contact your network administrator."

  • disabling conversations
  • removing image signature, or
  • using thunderbird (not conversations quick reply) compose window fixes the problem.
@protz
Owner
@protz
Owner

Please try the latest version at http://jonathan.xulforum.org/files/gcv-nightlies/201406201054-html-reply.xpi and tell me if it fixes your issue (if it does, feel free to close this ticket!).

Thanks,

~ jonathan

@protz protz closed this
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Something went wrong with that request. Please try again.