How to close Smtp connection in SwiftMailer

Question

I use SwiftMailer to send emails from a gearman worker process. I'm using the Swift_SmtpTransport class to send emails.

The problem is that if this worker process stays idle for sometime, the SwiftMailer smtp connection times out. Now when the next job arrives, SwiftMailer fails to send emails as the connection has been timed out.

Ideally, I would want to close the smtp connection after every job. I'm unable to locate a api in the class which does this specifically. Neither does unset() object works since this is a static class.

Diphyllous

perhaps: $transport->stop(), $transport->start() – Raouf

@Dragon Omg ty so much! I have a background worker in an infinite loop and this solved it for me. – Hebraize

Answer 1

There is a rude option: stop the transport explicitly. On subsequent calls of the method sendMail, SwiftMailer will check whether the transport is up (it is not, now) and start it again. IMNSHO, SwiftMailer should intercept the SMTP timeout and reconnect automatically.But, for now, this is the workaround:

function sendMail($your_args) {
    try{ 
      $mailer = Swift_Mailer::newInstance($transport);
      $message = Swift_Message::newInstance('Wonderful Subject')
        ->setFrom(array('[email protected]' => 'John Doe'))
        ->setTo(array('[email protected]', '[email protected]' => 'A name'))
        ->setBody('Here is the message itself');

      $result = $mailer->send($message);
      $mailer->getTransport()->stop();

    } catch (Swift_TransportException $e) {
      //this should be caught to understand if the issue is on transport
    } catch (Exception $e) {
      //something else happened  
    }

}

Britt

Answer 2

I send mails in a loop and I was catching the Swift_TransportException and creating a new instance of Swift_Mailer but it wasn't the right fix: the problem is the transport, not the mailer. The solution is to issue an explicit call to Swift_SmtpTransport::stop():

foreach($recipients as $to => $body){
    try{
        $message->setTo($to);
        $message->setBody(body);
        $mailer->send($message);
    }catch(Swift_TransportException $e){
        $mailer->getTransport()->stop();
        sleep(10); // Just in case ;-)
    }
}

This way, Swift detects the mailer is stopped and starts it automatically, so it recovers correctly from communication errors.

Overmodest

But shouldn't you retry sending? – Caryophyllaceous

@Caryophyllaceous The question asks how to properly reset the mailer and that's what I try to answer. – Trudey

When pipe is broken $mailer->getTransport()->stop() will fail – Manganite

@Manganite Please define "fail"—the stop() method does several things. The code in my answer has been working fine for the Swift Mailer version available at the time. – Trudey

@ÁlvaroGonzález, broken pipe issue appears in daemon scripts mostly. Inside the stop method there is an executeCommand() and catch for Swift_TransportException only. When connection with the server is broken there will be a "broken pipe" error. github.com/swiftmailer/swiftmailer/issues/490 – Manganite

Answer 3

When pipe is broken $mailer->getTransport()->stop() will fail as well. And due to this error transport cannot be stopped. The workaround is

// Let's try to send an email.
$tries = 3;
while ($tries--) {
    try {
        $sent = $this->mailer->send($message);
        break;
    } catch (\Exception $e) {
        // Connection problems
        // @see https://github.com/swiftmailer/swiftmailer/issues/490
        try {
            // Try to stop
            $this->mailer->getTransport()->stop();
        } catch (\Exception $e) {
            // Got Exception while stopping transport.
            // We have to set _started to 'false' manually, because due to an exception it is 'true' now.
            $t = $this->mailer->getTransport();
            $reflection = new \ReflectionClass($t);
            $prop = $reflection->getProperty('_started');
            $prop->setAccessible(true);
            $prop->setValue($t, false);
            $prop->setAccessible(false);
        }
    }
}

Manganite

Answer 4

I'm running a worker in an infinite loop using Swiftmailer and AWS SES I was getting the error:

Expected response code 250 but got code "421", with message "421 Timeout waiting for data from client.

Solution for my script:

$love = true;
while($love) {
    $message = Message::to($record->to)
        ->from(array('[email protected]' => $user->name()))
        ->reply(array($user->email => $user->name()))
        ->subject($record->subject)
        ->body($body->value)
        ->html(true)
        ->send();

    if (! $message->was_sent())
        throw new Swift_TransportException($errstr . ': ' . $errno);
}

Hebraize

This answer could use an explantion. Do you mean that such error was not throwing Swift_TransportException, but doing it explicitly fixes the issue? – Trudey

Is this an answer or a question? – Taxicab