send failures

tiggit continues to have difficulties sending mail… In version 1.0.02 I  put loads of extra validation around the smtp protocol handler to be certain that messages have been successfully sent before removing them from the outbox. 

For some email services – notably Yahoo! –  this validation does not appear to work perfectly, resulting in messages being sent, but remaining in the outbox marked as failed.

The difficulty is knowing which messages have been sent, and which have actually failed. tiggit has a handy drop-copy feature that will automatically add a bcc address to all messages that it sends. This can be used to add yourself as a silent addressee to messages that are sent via tiggit, so that when you receive your own message you can delete it from the outbox.

Not really a solution I know, not even a messy work around, but until the bugs are fixed maybe a way of knowing whether a message has been sent.


One Response to send failures

  1. SteveH says:

    Hi Tiggit,

    Thanks for all of the rapid fixes and updates! Another issue I’ve noticed is that messages that are left in the Outbox as the result of a send failure appear as zero bytes and have no body in them. Attempting to resend them does not seem to work. This can be reproduced while trying to send a message with no network connection, in my case, WiFi is off. The message says that it is sent, but really isn’t. Also, the message is placed in the Outbox, but does not have the e-mail body.

Leave a Reply

Fill in your details below or click an icon to log in: Logo

You are commenting using your account. Log Out /  Change )

Google photo

You are commenting using your Google account. Log Out /  Change )

Twitter picture

You are commenting using your Twitter account. Log Out /  Change )

Facebook photo

You are commenting using your Facebook account. Log Out /  Change )

Connecting to %s

%d bloggers like this: