Raikia / FiercePhish

FiercePhish is a full-fledged phishing framework to manage all phishing engagements. It allows you to track separate phishing campaigns, schedule sending of emails, and much more.
https://github.com/Raikia/FiercePhish/wiki
GNU General Public License v3.0
1.31k stars 249 forks source link

SMTP Gmail #36

Closed cintainfinita closed 7 years ago

cintainfinita commented 7 years ago

Hello! I'm using Gmail's SMTP, port 587, TLS config on FiercePhish (or at least I'm trying).

I'm not being able to send single emails or by starting a campaign.. basically I'm getting this:

Error: Address in mailbox given [] does not comply with RFC 2822, 3.6.2.

I think that's the problem.. not because of using Google's SMTP (since I can use it in a Python script.. no 2FA on the account I'm configuring to send the emails from)

It seems that some variables are not getting the "TO:" email because it looks "blank"...

Any help? Fresh Ubuntu 16.04 Installation, FiercePhish Remote Installation the only thing running...

Thank you!

Raikia commented 7 years ago

I will look into this, I've honestly not tried with Google's SMTP servers.

Raikia commented 7 years ago

This took me a surprisingly long time to figure out, but its completely unrelated to Google's SMTP server. The "BCC" part is breaking.

For a quick fix, open your ".env" file and change:

 MAIL_BCC_ALL=

to

 MAIL_BCC_ALL=null

Then run "php artisan config:cache". This will resolve your problem.

A permanent solution will be in the next release.

cintainfinita commented 7 years ago

Perfect! I will try this tomorrow and let you know.

Thanks a lot!

On Tuesday, 28 February 2017, Chris King notifications@github.com wrote:

This took me a surprisingly long time to figure out, but its completely unrelated to Google's SMTP server. The "BCC" part is breaking.

For a quick fix, open your ".env" file and change: MAIL_BCC_ALL= to MAIL_BCC_ALL=null

Then run "php artisan config:cache". This will resolve your problem.

A permanent solution will be in the next release.

— You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub https://github.com/Raikia/FiercePhish/issues/36#issuecomment-283185171, or mute the thread https://github.com/notifications/unsubscribe-auth/ATQw-F9KWaSiIC8jx43GG2gwi61N-6wrks5rhKLOgaJpZM4MIJQN .

Raikia commented 7 years ago

Did my suggestion resolve it?

cintainfinita commented 7 years ago

Haven't tried it yet, sorry.

On Thursday, 9 March 2017, Chris King notifications@github.com wrote:

Did my suggestion resolve it?

— You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub https://github.com/Raikia/FiercePhish/issues/36#issuecomment-285445366, or mute the thread https://github.com/notifications/unsubscribe-auth/ATQw-AvUEKc-N4dPmLLC8VaSZQkl741dks5rkEtSgaJpZM4MIJQN .

Raikia commented 7 years ago

This has been fixed in v1.2.1. You can use the update script to update properly. Please let me know if this did not fix your specific issue and I will reopen the issue ticket.