不能赶上SwiftMailer例外？

问题描述 投票：1回答：2

我使用SwiftMailer（独立）。

下面的代码工作正常，但当我输入一个无效SMTP凭据，这样的错误被显示为一个完整的堆栈跟踪：

Failed to authenticate on SMTP server with username "MYUSERNAME" using 3 possible authenticators. Authenticator CRAM-MD5 returned Swift_TransportException: Expected response code 235 but got code "535", with message "535 5.7.0 Invalid login or password
" in /var/www/tester/vendor/swiftmailer/swiftmailer/lib/classes/Swift/Transport/AbstractSmtpTransport.php:457
Stack trace:
#0 /var/www/tester/vendor/swiftmailer/swiftmailer/lib/classes/Swift/Transport/AbstractSmtpTransport.php(341): Swift_Transport_AbstractSmtpTransport->assertResponseCode('535 5.7.0 Inval...', Array)
#1 /var/www/tester/vendor/swiftmailer/swiftmailer/lib/classes/Swift/Transport/EsmtpTransport.php(305): Swift_Transport_AbstractSmtpTransport->executeCommand('NmE0ODlmMWNmOTc...', Array, Array, false, NULL)
#2 /var/www/tester/vendor/swiftmailer/swiftmailer/lib/classes/Swift/Transport/Esmtp/Auth/CramMd5Authenticator.php(39): Swift_Transport_EsmtpTransport->executeCommand('NmE0ODlmMWNmOTc...', Array)
#3 /var/www/tester/vendor/swiftmailer/swiftmailer/lib/classes/Swift/Transport/Esmtp/AuthHandler.php(177): Swift_Transport_Esmtp_Auth_CramMd5Authenticator->authenticate(Object(Swift_SmtpTransport), 'MYUSERNAME', 'MYPASSWORD')
#4 /var/www/tester/vendor/swiftmailer/swiftmailer/lib/classes/Swift/Transport/EsmtpTransport.php(371): Swift_Transport_Esmtp_AuthHandler->afterEhlo(Object(Swift_SmtpTransport))
#5 /var/www/tester/vendor/swiftmailer/swiftmailer/lib/classes/Swift/Transport/AbstractSmtpTransport.php(148): Swift_Transport_EsmtpTransport->doHeloCommand()
#6 /var/www/tester/vendor/swiftmailer/swiftmailer/lib/classes/Swift/Mailer.php(65): Swift_Transport_AbstractSmtpTransport->start()
#7 /var/www/tester/public/index.php(32): Swift_Mailer->send(Object(Swift_Message))
#8 {main}. Authenticator LOGIN returned Swift_TransportException: Expected response code 250 but got an empty response in /var/www/tester/vendor/swiftmailer/swiftmailer/lib/classes/Swift/Transport/AbstractSmtpTransport.php:445
Stack trace:
#0 /var/www/tester/vendor/swiftmailer/swiftmailer/lib/classes/Swift/Transport/AbstractSmtpTransport.php(341): Swift_Transport_AbstractSmtpTransport->assertResponseCode('', Array)
#1 /var/www/tester/vendor/swiftmailer/swiftmailer/lib/classes/Swift/Transport/EsmtpTransport.php(305): Swift_Transport_AbstractSmtpTransport->executeCommand('RSET\r\n', Array, Array, false, NULL)
#2 /var/www/tester/vendor/swiftmailer/swiftmailer/lib/classes/Swift/Transport/Esmtp/Auth/LoginAuthenticator.php(40): Swift_Transport_EsmtpTransport->executeCommand('RSET\r\n', Array)
#3 /var/www/tester/vendor/swiftmailer/swiftmailer/lib/classes/Swift/Transport/Esmtp/AuthHandler.php(177): Swift_Transport_Esmtp_Auth_LoginAuthenticator->authenticate(Object(Swift_SmtpTransport), 'MYUSERNAME', 'MYPASSWORD')
#4 /var/www/tester/vendor/swiftmailer/swiftmailer/lib/classes/Swift/Transport/EsmtpTransport.php(371): Swift_Transport_Esmtp_AuthHandler->afterEhlo(Object(Swift_SmtpTransport))
#5 /var/www/tester/vendor/swiftmailer/swiftmailer/lib/classes/Swift/Transport/AbstractSmtpTransport.php(148): Swift_Transport_EsmtpTransport->doHeloCommand()
#6 /var/www/tester/vendor/swiftmailer/swiftmailer/lib/classes/Swift/Mailer.php(65): Swift_Transport_AbstractSmtpTransport->start()
#7 /var/www/tester/public/index.php(32): Swift_Mailer->send(Object(Swift_Message))
#8 {main}. Authenticator PLAIN returned Swift_TransportException: Expected response code 250 but got an empty response in /var/www/tester/vendor/swiftmailer/swiftmailer/lib/classes/Swift/Transport/AbstractSmtpTransport.php:445
Stack trace:
#0 /var/www/tester/vendor/swiftmailer/swiftmailer/lib/classes/Swift/Transport/AbstractSmtpTransport.php(341): Swift_Transport_AbstractSmtpTransport->assertResponseCode('', Array)
#1 /var/www/tester/vendor/swiftmailer/swiftmailer/lib/classes/Swift/Transport/EsmtpTransport.php(305): Swift_Transport_AbstractSmtpTransport->executeCommand('RSET\r\n', Array, Array, false, NULL)
#2 /var/www/tester/vendor/swiftmailer/swiftmailer/lib/classes/Swift/Transport/Esmtp/Auth/PlainAuthenticator.php(39): Swift_Transport_EsmtpTransport->executeCommand('RSET\r\n', Array)
#3 /var/www/tester/vendor/swiftmailer/swiftmailer/lib/classes/Swift/Transport/Esmtp/AuthHandler.php(177): Swift_Transport_Esmtp_Auth_PlainAuthenticator->authenticate(Object(Swift_SmtpTransport), 'MYUSERNAME', 'MYPASSWORD')
#4 /var/www/tester/vendor/swiftmailer/swiftmailer/lib/classes/Swift/Transport/EsmtpTransport.php(371): Swift_Transport_Esmtp_AuthHandler->afterEhlo(Object(Swift_SmtpTransport))
#5 /var/www/tester/vendor/swiftmailer/swiftmailer/lib/classes/Swift/Transport/AbstractSmtpTransport.php(148): Swift_Transport_EsmtpTransport->doHeloCommand()
#6 /var/www/tester/vendor/swiftmailer/swiftmailer/lib/classes/Swift/Mailer.php(65): Swift_Transport_AbstractSmtpTransport->start()
#7 /var/www/tester/public/index.php(32): Swift_Mailer->send(Object(Swift_Message))
#8 {main}.done

示例代码：

<?php

try {

    $transport = (new Swift_SmtpTransport($host, $port))
        ->setUsername($user)
        ->setPassword($pass);

    $mailer = new \Swift_Mailer($transport);

    $message = (new \Swift_Message('test'))
        ->setFrom(['[email protected]' => 'bar'])
        ->setTo(['[email protected]'])
        ->setBody('test');

    $mailer->send($message);

} catch (\Swift_TransportException $ex) {

    echo $ex->getMessage();

} catch (\Exception $ex) {

    echo $ex->getMessage();
}

是不是想捕捉异常？

有任何想法吗？

php exception swiftmailer
2个回答
1
投票

你可以尝试做the manual暗示什么：

如果您需要了解早期验证是否已经失败，一个异常将被抛出，呼吁建立运输的start（）方法。

所以生成的代码可以是：

$transport = (new Swift_SmtpTransport($host, $port))
    ->setUsername($user)
    ->setPassword($pass); 
$try {
    $transport->start();
} catch (\Swift_TransportException $ex) {
    echo $ex->getMessage();
    return; //whatever you want to do.
}
....

更新：经过进一步的分析，我认为我得到了它。你可能认为你不捕捉异常，但实际上你。问题是，在Swift_TransportException的getMessage()方法返回完整的堆栈跟踪（至少在我的包膜与SwiftMailer 6）...尝试做做这样的事情在你的catch块echo "Message start" . $ex->getMessage() . "Message End";，你应该看到您添加的文本。

更新2：如果你想达到什么是摆脱消息中的堆栈跟踪的，我能想到的唯一的解决办法是继承Swift_SmtpTransport，赶上前面的异常，并抛出一个新的具有较短的消息。一个不可能性的解决方案看起来是这样的

class Better_SwiftSmtpTransport extends  Swift_SmtpTransport
{
    public function __construct(string $host = 'localhost', int $port = 25, ?string $encryption = null)
    {
        parent::__construct($host, $port, $encryption);
    }

    public function start()
    {
        try {
            return parent::start();
        }
        catch (Swift_TransportException $ex) {
            throw new Better_SwiftSmtpTransportException(
                $ex->getMessage(), 
                $ex->getCode(), 
                $ex
            );
        }
    }
}

class Better_SwiftSmtpTransportException extends Swift_TransportException
{
    public function __construct(string $message, int $code = 0, Exception $previous = null)
    {
        $message = strtok($message, "\n"); // get only the first line of the message
        parent::__construct($message, $code, $previous);
    }
}

$transport = (new Better_SwiftSmtpTransport($host, 25))
    ->setUsername($user)
    ->setPassword($password)
;
try {
    $mailer = new \Swift_Mailer($transport);
    $message = (new \Swift_Message('test'))
        ->setFrom(['[email protected]' => 'bar'])
        ->setTo(['[email protected]'])
        ->setBody('test');
    $mailer->send($message);

} catch (Swift_TransportException $ex) {
    echo  $ex->getMessage();
}
2
投票

一些长期的挖掘后，我可以同意，我得出了相同的结论为@gere。

令人震惊的，因为它是具有$ex->getMessage();附加到它堆栈跟踪。

我发现，你可以通过注释掉foreach()循环，增加了所有的额外信息，该消息中的SwiftMailer核心文件之一禁用。这可能是未来的问题，如果你决定要更新您的SwiftMailer文件，但作为一个临时补丁，假设你的文件结构是一样的矿井，导航到（这是行187对我来说）：

/vendor/swiftmailer/swiftmailer/lib/classes/Swift/Transport/Esmtp/Authhandler.php

和定位功能public function afterEhlo(Swift_Transport_SmtpAgent $agent)

接近年底，代码如下所示：

$message = 'Failed to authenticate on SMTP server with username "' . $this->username . '" using ' . $count . ' possible authenticators.';
foreach ($errors as $error) {
    $message .= ' Authenticator ' . $error[0] . ' returned ' . $error[1] . '.';
}

throw new Swift_TransportException($message);

并注释掉foreach()循环，甚至只是内部表达式：

$message = 'Failed to authenticate on SMTP server with username "' . $this->username . '" using ' . $count . ' possible authenticators.';
/*foreach ($errors as $error) {
    $message .= ' Authenticator ' . $error[0] . ' returned ' . $error[1] . '.';
}*/

throw new Swift_TransportException($message);

编辑：我忘了提，在每一个在身份验证尝试使用，并吐出他们在一个堆栈跟踪的形式遇到的错误（或多个）认证符的这段代码迭代，也就是你看到的其他数据。只是为了澄清。

编辑2：这是固定的29天以前通过更换线路182：

$errors[] = [$authenticator->getAuthKeyword(), $e];

有：

$errors[] = [$authenticator->getAuthKeyword(), $e->getMessage()];

如图所示通过在GIT中，here提交消息

最新问题
© www.soinside.com 2019 - 2024. All rights reserved.