-
Notifications
You must be signed in to change notification settings - Fork 53
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
503 5.5.0 Need MAIL before RCPT #2
Comments
Sorry for the late reply, I will find a solution to this right now. Thanks for checking out my repo! |
Are you using the python script, or the java version? |
No problem haha. I'm using Kali Linux with the Python script |
I'm sure it's not your tool specifically. I've tried a couple and i get the same error, but you were kind enough to reply. I hope you can help me. |
John, thank you so much for providing such an easy to use tool. However, I am experiencing the same issue as DramingBewilderedly did. I'm using Windows 10 Pro x64 and the python script. I have tried sending from different mail domains: gmail and mail.com. I've also tried sending a single text as well as several and have tried different wait times for sending (last line of #CONFIG). I keep getting NDRs for each one. When I send directly from Gmail or mail.com, it works. Thanks for any help you are willing to provide :) |
Good evening, i'm getting right to the point. I'm from Argentina, and the carrier of my phone (Where i'm testing the tool) is "Personal" SMTP: [email protected].
Your tool shows the message "sent" when i execute the script, but, I get an error in Gmail (The one stated in the title) and my text does not arrive the recipient. I hope you can provide some insight so I could fix the issue.
Error:
Final-Recipient: rfc822; (number)@alertas.personal.com.ar
Action: failed
Status: 5.5.0
Remote-MTA: dns; alertas.personal.com.ar (200.43.139.178, the server for the domain.)
Diagnostic-Code: smtp; 503 5.5.0 Need MAIL before RCPT
Last-Attempt-Date: Sat, 24 Jun 2017 21:51:06 -0700 (PDT)
Thanks!
The text was updated successfully, but these errors were encountered: