Mail (smtp): password and username not set in config

[maurocolella]

• Laravel Version: 5.4.12
• PHP Version: HipHop VM 3.18.1 (rel)
• Database Driver & Version: Ver 15.1 Distrib 10.1.21-MariaDB, for debian-linux-gnu (x86_64) using readline 5.2

Description:

If set in either config/mail.php, .env, or both, when using SMTP authentication over TLS or SSL, username and password are not set in config.

From a route, dd(Config::get('mail')); prints a configuration that misses username and password.

Steps To Reproduce:

Configure mail using either the global config/mail.php or .env file, eq.

MAIL_DRIVER=smtp
MAIL_HOST=smtp.gmail.com
MAIL_PORT=587
MAIL_USERNAME=support@domain.com
MAIL_PASSWORD=...
MAIL_ENCRYPTION=tls

Open matching outgoing ports (465 for ssl or 587 for tls). Authentication to the smtp server should fail (error 530). Server reports credentials are not set.

[themsaid]

This doesn't look as a framework issue to me, could be that your configs are cached. Please ask on the forums.

[maurocolella]

The forums are full of people who report the same issue, and I am 100% certain my configs are not cached. I have a test route, I dd them in real-time, switch back and forth between tls and ssl, my configs are updated right before my eyes - and password and username are and remain null.

…

On Mar 1, 2017 23:17, "Mohamed Said" ***@***.***> wrote: This doesn't look as a framework issue to me, could be that your configs are cached. Please ask on the forums. — You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub <#18170 (comment)>, or mute the thread <https://github.com/notifications/unsubscribe-auth/AAuftAwSjZVpoZBRVYfPkQ1mHdVq9hqIks5rhYwEgaJpZM4MPOkZ> .

[themsaid]

dd(Config::get('mail')); returns correct credentials for me, can you please point me to the posts in forums where the same issue is reported?

[maurocolella]

Will do asap (tomorrow). Thank you for your reply.

…

On Mar 1, 2017 23:28, "Mohamed Said" ***@***.***> wrote: dd(Config::get('mail')); returns correct credentials for me, can you please point me to the posts in forums where the same issue is reported? — You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub <#18170 (comment)>, or mute the thread <https://github.com/notifications/unsubscribe-auth/AAuftECzr6on-yqQJ889uQ6rIXJix95bks5rhY6sgaJpZM4MPOkZ> .

[maurocolella]

So: just to be on the safe side, I tried again to refresh my cache `php artisan config:cache` The issue is still there. The following threads are among many that report the same problem: http://stackoverflow.com/questions/22192133/laravel-default-mail-not-working http://stackoverflow.com/questions/32515245/how-to-to-send-mail-using-gmail-in-laravel-5-1 https://laracasts.com/discuss/channels/laravel/sending-email-problem-with-gmail?page=1 Now, this is a just a hunch, but if the issue appears to be sporadic, the common denominator might be HHVM. Ie. this could be some kind of low-level issue between core components and HHVM. I am going to install php7 and verify this again. Will keep you posted asap.

[maurocolella]

No. Issue is identical with php7 (stable) and hhvm.

[Dimimo]

What happens if you run composer dump-autoload -o? This command sometimes solves booting/settings issues.

[maurocolella]

Generating optimized autoload files

Issue is the same.

Swift_TransportException in AbstractSmtpTransport.php line 386:
Expected response code 250 but got code "530", with message "530-5.5.1 Authentication Required.

If I dump the configuration, I get:

array:9 [▼
  "driver" => "smtp"
  "host" => "smtp.gmail.com"
  "port" => "587"
  "from" => array:2 [▶]
  "encryption" => "tls"
  "username" => null
  "password" => null
  "sendmail" => "/usr/sbin/sendmail -bs"
  "markdown" => array:2 [▼
    "theme" => "default"
    "paths" => array:1 [▶]
  ]
]

If I force the configuration from within the route (eq. set the username and password actively), I can then send email.

[Dimimo]

I can't reproduce your issue, but I can give you some workflow I use when stuck with similar problems.

Run php artisan config:cache, open bootstrap/cache/config.php and look for the 'mail' array. If 'username' is empty, add it directly in config/mail.php, rerun config:cache and look again.
If it's there, have a look for a second 'mail' array in config.php. Then it gets overwritten somewhere. Search in the whole app for the keyword ('username'). I have 11 matches. If you see nothing suspicious, look for 'username'. I have 97 matches. If there is nothing out of the ordinary, try double quotes. The following could help you further.

Open vendor/laravel/framework/src/Illuminate/Mail/MailServiceProvider.php, at line 90 in registerSwiftMailer() add dd(Config::get('mail'), refresh the browser and see what rolls out.

I know it's dirty debugging but as I don't have a deep inside of the inner workings of Laravel, it's my way of pinpointing errors along the way. If the registry of the app config itself goes wrong, I have no idea how to work that out. Tinker can be helpful in many cases but I'm sure your 'username' and 'password' will be empty there too.

[devcircus]

For kicks and giggles, call

Config::set('mail.username', 'yourusername');
Config::set('mail.password', 'yourpassword');

just before you send the email, or just before you call dd. Just to see if it is picking up the new configs.

[maurocolella]

Yeah it does.

…

On Mar 3, 2017 05:44, "Clayton Stone" ***@***.***> wrote: For kicks and giggles, call Config::set('mail.username', 'yourusername'); Config::set('mail.password', 'yourpassword'); just before you send the email. Just to see if it is picking up the new configs. — You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub <#18170 (comment)>, or mute the thread <https://github.com/notifications/unsubscribe-auth/AAuftCEer29Yt5OzDF06ZK9sHR3alQOBks5rhzgxgaJpZM4MPOkZ> .

[devcircus]

Curious if you ever made any progress with this. I have no answers, just very intrigued by the problem.

[themsaid]

I don't this it's a framework issue as I can't replicate and based on the fact that many laravel apps use the mail feature already and it's working normally, checking the links you shared and all seem to be environment specific issues.

Closing the issue for now but please feel free to ping me if you every found that there's an actual bug in the framework core.