You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The current default values for "FromEmail" and "HelloName" are causing incorrect "deliverable" results during SMTP checks. Would be great to update these defaults in the package.
It currently gives the following error (with some providers):
550 5.7.27 Sender address rejected: Domain example.org does not accept mail (nullMX) error
Quick fix:
Update the default from email and hello name.
On Wed, Oct 30, 2024 at 7:29 PM David Emiliano calzada morales < ***@***.***> wrote:
Hey! 👋
The current default values for "FromEmail" and "HelloName" are causing
incorrect "deliverable" results during SMTP checks. Would be great to
update these defaults in the package.
It currently gives the following error (with some providers):
550 5.7.27 Sender address rejected: Domain example.org does not accept mail (nullMX) error
Quick fix:
Update the default from email and hello name.
verifier := emailverifier.NewVerifier().
***@***.***").
HelloName("gmail.com")
To the maintainers of this repo, i recommend updating the default values
for this fields 👍
This is the fix to this related issue: #72
<#72>
Thanks, hope it helps
—
Reply to this email directly, view it on GitHub
<#133>, or unsubscribe
<https://github.com/notifications/unsubscribe-auth/BEDTLKXYL35O4V4FGUNO3S3Z6DQ4VAVCNFSM6AAAAABQ4FZOYWVHI2DSMVQWIX3LMV43ASLTON2WKOZSGYZDIMRQGY2TGMI>
.
You are receiving this because you are subscribed to this thread.Message
ID: ***@***.***>
Hey! 👋
The current default values for "FromEmail" and "HelloName" are causing incorrect "deliverable" results during SMTP checks. Would be great to update these defaults in the package.
It currently gives the following error (with some providers):
Quick fix:
Update the default from email and hello name.
To the maintainers of this repo, i recommend updating the default values for this fields 👍
This is the fix to this related issue: #72
Thanks, hope it helps
The text was updated successfully, but these errors were encountered: