| Index > Scribe > SendEnd failed error with SMTP | |
|---|---|
| Author/Date | SendEnd failed error with SMTP |
| Scott 31/03/2025 7:12am | When sending mail via SMTP, I am often getting a SendEnd failed error which seems to be dependent on the contents of the mail.
Messages containing the following contents will fail (note, I had to add a space after/before the square bracket to avoid PHP formatting): > [ img=https://statements.com/mail/mos/x.gif ] This message will succeed if this line is changed to: > img=https://statements.com/mail/mos/x.gif |
| memecode 31/03/2025 8:12am | You can look into that further by opening out the Status panel, clicking on the sending account, and looking at the Send log tab for the conversation with the SMTP server. It should have a red error somewhere there. Sometimes they put a useful message saying why they are rejecting the message.
Otherwise it's hard for me to give specific advise. It seems more like a SMTP server issue than a Scribe issue. I guess the real test would be to try the same message that fails in Scribe in another email client. If THAT other client works then we can assume it's something that Scribe is doing. |
| Scott 06/04/2025 5:44am | If I drag the emails to File Explorer and then drag them to Thunderbird, the resultant email can be sent without issue using the identical settings as Scribe.
Further investigation reveals the following: * currently, all emails are failing regardless of content * if multiple emails are queued to be sent only the first message gets sent * then an empty error message pops up, titled: "Scribe", content: "Error:" * send log shows: 354 Start mail input; end with* first message is actually sent. * email stays in Outbox and the property remains as "Ready to Send" A more verbose error message would be helpful. |
| Scott 24/07/2025 11:30am | This problem has not occurred for several months now.
It looks like the provider fixed their server. :) |
| Reply | |