Closed ClaraLeigh closed 8 years ago
Been sending emails using 5.3 for a while now using several drivers, I don't think the issue is related to laravel, maybe some package you're using is overriding the behaviour of Swift mailer?
Can you regenerate the issue on a fresh 5.3 installation? if not then it's something related to that specific App.
Resolved after hours of debugging :cry: In my composer.json I had autoload: { "classmap": [ 'vendor'] } Don't know why the issue didn't occur pre-laravel 5.3 but removing it fixed the problem
Description:
After upgrading to laravel 5.3 all outgoing mail stopped working. I couldn't see anything in the upgrade docs about this type of thing, so I'm guessing something else is going on.
I initially wanted to try out notifications, which is why I performed the upgrade in the first place. After the upgrade I tried doing a simple test email notification with the default auto generated notification file.
My route code is as follows:
I have also tried sending via Mail::raw, Mail::to and also I tried changing the mail configuration to use a different driver (SMTP and Mailgun). Nothing works but if I change drivers the error message changes but only slightly.
After playing around with it I realised that while the error stack looks different for both drivers, the underlying cause is from this bit of code(in the vendor file), which varies only slightly depending on the driver used:
If I dump and die the 3rd and 4th line of this snippet inside the vendor file, I get an empty array. This is obviously where the issue is coming from in both instances but I'm not quite familiar with the whole inner workings to figure out why it is returning empty.
Has anyone experienced this issue before or does anyone know why this may be happening?
FYI the actual error stack when trying to email via Mailgun is: