email format and DNS verification in laravel, lumen php frameworks - laravel

Emails samples as below
abs.ss#gmail.com,example#yahoo.in,example#test.in,example#111.example.in
Email format and DNS verification in Laravel, lumen for emails campaign to decrease email bounce and increase the Reputation of the Sender

Solution #1
I got it my solution over GitHub Library https://github.com/egulias/EmailValidator
RFCValidation: Standard RFC-like email validation.
NoRFCWarningsValidation: RFC-like validation that will fail when warnings* are found.
DNSCheckValidation: Will check if there are DNS records that signal that the server accepts emails. This does not entail that the
email exists.
Solution #2
This email validation checks if the email address domain exists or is configured to receive emails. It gets all MX, A and AAAA DNS records for the host, and then it will count email address as valid if MX records exist and its target is not empty or if A and/or AAAA DNS records exist.
https://minuteoflaravel.com/validation/laravel-email-validation-be-aware-of-how-you-validate/

Related

DKIM - email passing through multiple services

If an email went from my helpdesk system (which has DKIM) to our exchange server to relay (which has DKIM) to our spam filter (which has DKIM) - will anything break?
Which DKIM record record will be used by the receiving party?

Email deliverability check without sending an email or checking without SMTP

Here is the scenario. I am using PHP and I want to check whether an email address is valid and deliverable. Here are the steps I take:
Validate email address via regex
Validate email address via php filter_var
Finally use SMTP to check whether the recipient exists
This thing works perfectly except that using an SMTP way is too slow and takes anywhere between 10 seconds to 40 seconds to validate. Sometimes the SMTP check is blocked by the recipient server and my server ip was blacklisted which made all the emails to that server as invalid.
There are professional services out there which do this for you but I don't want to use them for this particular project I am doing. Due to restrictions I cannot actually send an email to that email address.
Is there anyother way or faster way to validate the email addresses? How do these professional email validating companies do the validations so fast and cheaply?
I apologise if the question is not right for this forum. Please tell me and I will promptly delete this. I am new to stackoverflow.
P.S: I checked the other questions but they all pointed to using SMTP as the solution which I am already doing.

Laravel mail send got Email address is not verified

Does anyone came across with this error message when sending mail in Laravel, is there a way to solve this?
Swift_TransportException in AbstractSmtpTransport.php line 383:
Expected response code 250 but got code "554", with message "554 Message rejected: Email address is not verified.
"
I did verified the email addresses and its been "verified" but still came across this error..
Laravel is working fine. You are getting an error message from the AWS mail server.
http://docs.aws.amazon.com/ses/latest/DeveloperGuide/smtp-response-codes.html
You are trying to send email from an email address or domain that you have not verified with Amazon SES. If your account is still in the sandbox, you also need to verify the recipient address. For more information, see Verifying Email Addresses in Amazon SES.
Note that Amazon SES has endpoints in multiple AWS regions, and email address verification status is separate for each AWS region. You must complete the verification process for each sender in the AWS region(s) you want to use. For information about using Amazon SES in multiple AWS regions, see Regions and Amazon SES.
Make special note of that second paragraph. You may need to verify the email for the specific region you are trying to contact, or you need to change your contact address to the correct region.
For breif information refer below link
http://docs.aws.amazon.com/ses/latest/DeveloperGuide/smtp-response-codes.html

After merging a Mandrill account into Mailchimp, how can I accept a verification email if my sending domain is not setup to receive emails?

We've been using Mandrill for years to deploy our app's signup confirmation and password reset emails. This has worked perfectly as we've had SPF and DKIM records added to the DNS configuration according to Mandrill's documentation for verifying sending domains.
However, after merging the Mandrill account with a new Mailchimp account--which is mandated by April 27th--it's requiring me to send a verification email to an address at that domain. The problem is that we don't have a mail server set up to receive emails. The domain is only used to send the "noreply#domain.com" emails.
Any ideas on how I might resolve this? Mailchimp is not giving an option to undo the merge, so effectively I have an app that users are not able to sign up for at the moment, which is problematic to say the least.
You'll want to configure at least one mailbox on that domain somehow to receive mail. That's the only way to confirm ownership of the domain.

Laravel 4 and AmazonSES Emails not delivered

I had success setting up Laravel 4 mailer with AmazonSES smtp endpoints to send out emails using the Laravel default mailer and smtp.
This seems to work fine ( with most cases ).
We have a process that sends out approx 10k emails. But a few emails address are skipped and emails dont seem to get delivered to particular email addresses. I tried sending emails to 3 different email addresses of the same domain , which results in the mail never getting delivered to 2 email addresses. But the other one seems to work fine.
Same as for gmail addresses emails don't seem to get delivered to one particular email address. Apart from Geography there is no other common factor amoung the email accounts that don't receive the emails.
Any idea ? I am quite lost.
Updating the config/mail.php with the below worked
host => 'aws_end_point' // ie. email-smtp.us-west-2.amazonaws.com
username => 'your_aws_key'
password => 'your_aws_secret'

Resources