Copied to clipboard

Flag this post as spam?

This post will be reported to the moderators as potential spam to be looked at


  • Jan Molbech 18 posts 109 karma points
    Jun 26, 2017 @ 11:16
    Jan Molbech
    0

    Errormessage on failed delivery

    After updating to 2.1.7 we have seen a increase in failed deliveries.

    This errormessage is attached to each failed delivery

    Service not available, closing transmission channel. The server response was: Timeout waiting for data from client.
    at System.Net.Mail.MailCommand.CheckResponse(SmtpStatusCode statusCode, String response) at System.Net.Mail.SmtpTransport.SendMail(MailAddress sender, MailAddressCollection recipients, String deliveryNotify, Boolean allowUnicode, SmtpFailedRecipientException& exception) at System.Net.Mail.SmtpClient.Send(MailMessage message) at NewsletterStudio.Services.Mail.NsSmtpClient.Send(MailMessage mail) at NewsletterStudio.Services.SendNewsletterService.SendEmails()

    We are using AWS SES as our smtp provider.

    Any idea where the problem is situated? Is it configuration problems?

  • Markus Johansson 1902 posts 5706 karma points MVP c-trib
    Jun 26, 2017 @ 11:22
    Markus Johansson
    0

    Hi!

    That's an error from the core .NET email class that Newsletter Studio is using. I can't really say why that is happening, is there any patterns? Every X email or just randomly?

    What version of Newsletter Studio did you upgrade from?

  • Jan Molbech 18 posts 109 karma points
    Jun 26, 2017 @ 11:39
    Jan Molbech
    0

    we upgraded from 2.1.4.

    It looks random, but some (but not all) of the email addresses that fails are repeats

  • Markus Johansson 1902 posts 5706 karma points MVP c-trib
    Jun 26, 2017 @ 11:48
    Markus Johansson
    0

    Okey, we haven't made any changes to the email delivery-engine between these releases, did you ever have this issue before the upgrade?

Please Sign in or register to post replies

Write your reply to:

Draft