title: Laravel + Swift Mailer: Error: no valid recipients
body: <p>Note: this sadly is no <a href="https://stackoverflow.com/questions/54616706/how-do-we-solve-error-554-5-5-1-no-valid-recipients-when-using-php-swiftmailer?rq=1">duplicate</a>, I already tried everything mentioned there.</p>
  
  <p>I tried to set up a connection to my mailserver with <code>Laravel/Swiftmailer</code>. The Mailing section of my .env looks as follows:</p>
  
  <pre><code>MAIL_DRIVER=smtp
  MAIL_HOST=&lt;THE MAILHOST&gt;
  MAIL_PORT=465
  MAIL_USERNAME=&lt;THE USERNAME&gt;
  MAIL_PASSWORD=&lt;THE PASSWORD&gt;
  MAIL_ENCRYPTION=ssl
  </code></pre>
  
  <p>Personal information is censored for obvious reasons, but the configuration does work. I tested it by connecting to the server with this configuration with thunderbird and it works like a charm. </p>
  
  <p>Here is where I call the Mailable: </p>
  
  <pre><code>   public function from_id(string $id): User
     {
           .
           .
           .
          Mail::to(&lt;WORKING EMAIL ADRESS&gt;)-&gt;send(new OrderShipped());
      }
  </code></pre>
  
  <p>Thats how the Mailable looks like (it basically is the example one from the laravel docs): </p>
  
  <pre><code>   public function build()
     {
        return $this-&gt;view('email_templates.simple_test');
     }
  </code></pre>
  
  <p>I debugged into the code and there are actually two exceptions thrown, altough whoops! only shows the latter: </p>
  
  <blockquote>
    <p>Expected response code 250/251/252 but got code "554", with message
    "554 5.7.1 : Recipient address rejected: Access
    denied"</p>
    
    <p>Expected response code 354 but got code "554", with message "554 5.5.1
    Error: no valid recipients"</p>
  </blockquote>
  
  <p>I tried to sent an email from the perfectly working mailserver via thunderbird to the <code>&lt;WORKING EMAIL ADRESS&gt;</code> and the mail got sent and received in a fraction of a second and without any problems/errors. Basically, I tried to reproduce the exact same scenario with a different tool. So from my point of view, the error must be in the codebase. </p>
  
  <p>Thanks in advance</p>