Ошибка 530 smtp

SMTP Error 530 Authentication Required is a screw-up customer gets while sending messages. This screw-up happens when customers mastermind invalid login nuances, sender IP gets boycotted, “530 Authentication is Required Before Sending”, and so on Around Here at ARZHOST, we often get requesting to fix SMTP bumbles as a piece of our Server Management Services.

How might I fix Error 530?

It may be subverted because of the wrong cPanel revives or mixed up FTP server changes. Database pollution may cause impressively additional major problems, then 530 login check botches. The fastest method of dealing with this issue is changing from pure FTP to positive to FTP and back – “530 Authentication is Required Before Sending”, this recovers the informational index with passwords.

What is a 503 connection required?

503 This mail server requires approval when attempting to send off a non-close email address. Assuming no, “530 Authentication is Required Before Sending”, one mind, check your mail client settings or contact your director to confirm that the region or address is described for this server.

How might I test SMTP connection using telnet?

“530 Authentication is Required Before Sending”, To test SMTP connection through telnet:

1. In a telnet client like Putty, interface with the SMG mechanical assembly: telnet 587.
2. Welcome to the mail server: EHLO mailserver.com.
3. Tell SMG you wanted to confirm with it: AUTH LOGIN.
4. Paste the base64 encoded username.
5. Paste the base64 encoded secret expression for the username.

Would I have the option to make my SMTP server?

Concerning building an SMTP server, there are a few courses that you can take. You can use a worked with SMTP hand-off help that gives versatile email giving off-limits straightforwardly out of the case. “530 Authentication is Required Before Sending”, Then again you can plan your SMTP server, by developing top of an open-source SMTP server course of action.

How might I course of action on an SMTP server?

Bit by bit directions to mastermind an SMTP server

1. Select the voice “Record Settings” in your mail client, overall in the “Instruments” menu.
2. Pick the “Dynamic server (SMTP)” voice:
3. Push the “Add” button to set another SMTP. “530 Authentication is Required Before Sending”, A popup window will appear:
4. By and by fundamentally fill the voices as follows:

What is SMTP access?

Engaging SMTP Access grants you to send emails through your mail server. Realize that your mail server executive may limit the volume of email you’re allowed to send. To engage SMTP Access, “530 Authentication is Required Before Sending”, you ought to at this point have a Direct Mail account.

What’s the difference between SMTP and IMAP?

SMTP is the show for sending email whether it is from the client or in servers for spreading the email towards the arranged target. In assessment, “530 Authentication is Required Before Sending”, IMAP is a show that courses of action with regulating and recuperating email messages from the server.

Which is better IMAP or SMTP?

The indispensable thing to recollect while considering whether to use SMTP or IMAP is that SMTP is connected to sending an email. Consequently, if you’re wanting to enable email sending inside your application, “530 Authentication is Required Before Sending”, you’ll need to continue with using SMTP over IMAP.

Which is better POP or IMAP?

IMAP is better on the off chance that you will get your email from different devices, similar to a work PC and a high-level cell. POP3 works better on the off chance that you are simply using one device, “530 Authentication is Required Before Sending”, but have an outstandingly huge number of messages. It is moreover better if you have a defenseless web affiliation and need to get to your messages disengaged.

Would I have the option to have both POP and IMAP engaged?

No, having two exceptional devices access a comparable record through two unmistakable shows (IMAP/POP) will not work splendidly. IMAP is expected to store messages on the mail server. “530 Authentication is Required Before Sending”, stores drawing closer and dynamic messages on the server in coordinators. POP3 is planned to store messages on the close-by contraption.

How might I say whether I have POP3 or IMAP?

Android tablets and cells

1. Go to Settings peer down to the Accounts portion and select your email account.
2. Select Account Settings.
3. Select the record you wanted to check.
4. Look to Server Settings and select Incoming settings.
5. You’ll have the choice to see whether you’re using IMAP or POP by the server type.

What is an IMAP mail server?

In enrolling, the Internet Message Access Protocol (IMAP) is an Internet standard show used by email clients to recuperate email messages from a mail server over a TCP/IP affiliation. IMAP is described by RFC 3501. “530 Authentication is Required Before Sending”, An IMAP server regularly tunes in on port number 143.

Would it be prudent for me to disable IMAP?

But in case you’re using a pariah mail client that uses IMAP, no, there’s not any justification for having IMAP turned on. To be sure, “530 Authentication is Required Before Sending”, to keep your letterbox more secure, you should keep it off. IMAP is for examining Gmail messages in other mail clients, like Microsoft Outlook and Apple Mail.

How might I interface with an IMAP server?

Set up IMAP

1. On your PC, open Gmail.
2. In the upper right, click Settings. See all settings.
3. Snap the Forwarding and POP/IMAP tab.
4. In the “IMAP Access” region, select Enable IMAP.
5. Snap Save Changes.

How might I sign into my IMAP email?

Setting Up Outlook (IMAP)

1. Snap File → Info → Add account.
2. Enter an email address to add your record.
3. Snap Advanced decisions and check the case for Let me set up my record truly.
4. Snap Connect.
5. Pick the record type IMAP.
6. Use the going with settings:
7. Snap Connect.

How would I recuperate my IMAP secret word?

On your iPhone or iPad, go to Settings > Accounts and Passwords and tap Add Account. Tap Other, then, “530 Authentication is Required Before Sending”, at that point, tap Add Mail Account. Concerning resetting your email specialist co-op secret phrase as you’ve failed to remember it, you wanted to contact your supplier or go onto their site and search for a possibility for failing to remember the secret word.

How would I fix my IMAP server?

To adjust/fix the server settings of a General email account, do the accompanying:

1. Open Settings > Accounts.
2. Select your General email account.
3. Pull the view down until you see the Pulley menu show up from a higher place.
4. Select “Server settings”
5. Roll out the improvements and swipe right to save settings and to leave the settings to see.

SMTP mistake 530

SMTP is liable for sending messages. If an email isn’t sent, it gives mistake messages with codes. This aids in simple investigating.

An SMTP mistake code is of a 3-digit design, with every digit having particular importance. One such mistake that appears while sending an email is ‘SMTP error 530’. Generally, this is a validation issue. The fundamental purposes behind this are invalid login subtleties, “530 Authentication is Required Before Sending”, boycotted sender IP, etc.

How about we examine how our Hosting Expert Planners fix this mistake for our clients.

How do we fix the SMTP error 530?

SMTP errors have characterized mistake codes. Be that as it may, finding the explanations behind certain errors are precarious. Our Dedicated Engineers, “530 Authentication is Required Before Sending”, with mastery longer than 10 years in Email administrations, are skillful in fixing such SMTP errors for our clients.

Presently, how about we see the potential causes and fixes for the confirmation error.

1. Verify the email customer

The clearest justification behind SMTP error 530 isn’t verifying the Email customer appropriately. “530 Authentication is Required Before Sending”, This normally happens when the client is ignorant of the setting of another Email customer.

For example, email customer verification in Microsoft Outlook is as per the following:

• First select File>> Account Settings.
• Snap the Email tab and select the email address.
• Then, click on the More Settings.
• Presently, Internet E-mail Settings show up.
• Snap-on the tab Outgoing Server and enter the subtleties.
• At long last, click the checkbox ‘My active server (SMTP) requires validation.

Our Hosting Expert Planners give a point-by-point guide about validation for each Email customer.

2. Invalid Login accreditations

Essentially, “530 Authentication is Required Before Sending”, invalid or inaccurate login subtleties bring about this SMTP mistake. A few clients enter invalid email addresses and email customers show mistake 530.

In such circumstances, our Hosting Expert Planners request that the clients’ twofold check login qualifications. We handhold the clients to arrange their mail customers without errors.

We likewise ensure that the beneficiary’s email address is substantial.

3. Boycotted Sender IP

Another explanation that can cause an SMTP mistake is boycotting of IP by the beneficiary server. The sender’s IP address might have been boycotted some way or another. If the sender utilizes this server to send sends, “530 Authentication is Required Before Sending”, it shows mistake 530.

For this situation, we check if the beneficiary server has obstructed the sender’s IP. Along these lines, we demand them to unban or whitelist it.

4. ISP hindering port

The default SMTP port is 25. In any case, “530 Authentication is Required Before Sending”, in case the client’s ISP blocks admittance to this SMTP port, mistake 530 can happen. This is generally done as an action to abstain from spamming.

A workaround we do is to arrange SMTP to utilize a substitute port and empower this port via the post office customer settings to send letters through Outlook, Thunderbird, and so forth

Conclusion

So, SMTP Error 530 is a confirmation error. Generally, this mistake demonstrates an unauthenticated email customer. “530 Authentication is Required Before Sending”, Different purposes behind this mistake are boycotting of sender IP or invalid email address. Today, we perceived how our Hosting Expert Planners fix this mistake for our clients.

In this article, we will focus on the Mailer error: The following From address failed: info@abc.com : MAIL not accepted from server, 530,5.7.0 Authentication Required.

This is a common error that occurs while sending email through Gmail Link: https://mail.google.com/ account and while using PHPMailer Class link: https://github.com/PHPMailer/PHPMailer.

Now, let us look at the causes and solutions to this error.

What causes this error?

Let us look at the reasons for this error.

Cause 1: Incorrect SMTP Setting for Email

This error may arise due to incorrect SMTP settings.

Solution

Thus, check your SMTP settings first.

$mail->isSMTP();     // Set mailer to use SMTP
$mail->Host = 'smtp.gmail.com';  // Specify main and backup SMTP servers
$mail->SMTPAuth = true;     // Enable SMTP authentication
$mail->Username = 'info@abc.com';  // SMTP username
$mail->Password = 'password';  // SMTP password
$mail->SMTPSecure = 'tls';     // Enable TLS encryption, `ssl` also accepted
$mail->Port = 587;           // TCP port to connect to

Important: You have to check the SMTP and PORT settings.

$mail->Port = 587; & $mail->SMTPSecure = 'tls';

Doing this might solve the issue.

Cause 2: Less Secure App Accessed is not Enabled

Less secure apps are usually 3rd party applications that send your credentials directly to Gmail. Here, an authorization mechanism such as OAuth isn’t used. If the “Less secure app access” is disabled in Gmail, you’ll face this error.

To avoid this, you need to enable “Less secure app access” in your Gmail account settings.

Steps to enable less secure app

i) Login to your Gmail account

ii) Click on the top right Profile iconand then click on Account

iii) In the Account Window that opens up, click on the Security button on the left navigation column

iv) Scroll down and search for the option “Less secure app access”. If you have previously enabled the “2 Step Verification” option, then the “Less secure app access” will not be available. Therefore, you have to disable the “2 Step Verification” option

v) Now, scroll up to the “Signing in to Google” section. Then, click on the “2-Step Verification”button

vi) A 2-Step Verificationwindow will pop up. Here, click on the “TURN OFF” option to disable this feature

Now, go back to the previous page and you’ll see the “Less secure app access” has appeared.

vii) You can enable the “Less secure app access” option now. For this, click on “Turn on access (not recommended)”

viii) This will take you to a page called Less secure app access. Here, click on the toggle button beside “Allow less secure apps access” asshown in the image. This will enable less secure applications.

Or, click on the link given below and turn off the toggle button –
https://myaccount.google.com/u/1/lesssecureapps

Conclusion

If you have followed the steps mentioned above, you can easily send and receive emails on your Gmail account. In case you are still facing the Mailer error: The following From address failed: info@abc.com : MAIL not accepted from server,530,5.7.0 Authentication Required error, then feel free to write about it in the comment section below.

I have a problem on sending mail to my domain from an external address (I suspect more particularly the Exchange servers).
The error is:

myaddress : mail.mydomain.com #<mail.mydomain.com #5.7.0 smtp; 530 5.7.0 Must issue a STARTTLS command first> #SMTP#

Yet watching other posts discussing the same theme, I think I have correctly configured TLS.
My configuration is detailed below:

#######################
## GENERALS SETTINGS ##
#######################

smtpd_banner         = $myhostname ESMTP $mail_name
biff                 = no
append_dot_mydomain  = no
readme_directory     = no
delay_warning_time   = 4h
mailbox_command      = procmail -a "$EXTENSION"
recipient_delimiter  = +
disable_vrfy_command = yes
message_size_limit   = 50240000
mailbox_size_limit   = 1024000000
inet_interfaces = all
inet_protocols = ipv4

myhostname    = mail.mydomain.com
myorigin      = mail.mydomain.com
mydestination = localhost localhost.$mydomain 
mynetworks    = 127.0.0.0/8 [::ffff:127.0.0.0]/104 [::1]/128 192.168.0.0/28 192.168.1.0/28 192.168.2.0/28
relayhost     =

alias_maps     = hash:/etc/aliases
alias_database = hash:/etc/aliases

####################
## TLS PARAMETERS ##
####################
# Smtp ( OUTGOING / Client )
smtp_tls_loglevel            = 1
smtp_tls_security_level      = may
smtp_sasl_security_options = noanonymous
smtp_tls_CAfile              = /etc/ssl/certs/mydomain.cert.pem
smtp_tls_cert_file = /etc/ssl/certs/mydomain.crt
smtp_tls_key_file = /etc/ssl/private/mydomain.key
smtp_tls_protocols           = TLSv1, TLSv1.1, Tlsv1.2, !SSLv2, !SSLv3
smtp_tls_mandatory_protocols = TLSv1, TLSv1.1, Tlsv1.2, !SSLv2, !SSLv3
smtp_tls_mandatory_ciphers   = high
smtp_tls_exclude_ciphers = MEDIUM, LOW, aNULL, eNULL, SEED, 3DES, DES, MD5, EXP, CBC, PSD, PSK, SRP, DSS, RC4
smtp_tls_mandatory_exclude_ciphers = MEDIUM, LOW, aNULL, eNULL, SEED, 3DES, DES, MD5, EXP, CBC, PSD, PSK, SRP, DSS, RC4
tls_high_cipherlist=EDH+CAMELLIA:EDH+aRSA:EECDH+aRSA+AESGCM:EECDH+aRSA+SHA384:EECDH+aRSA+SHA256:EECDH:+CAMELLIA256:+AES256:+CAMELLIA128:+AES128:+SSLv3:!aNULL:!eNULL:!LOW:!3DES$
smtp_tls_note_starttls_offer = yes
smtp_use_tls = yes
smtpd_tls_ask_ccert = yes
smtpd_tls_req_ccert = no
smtp_tls_enforce_peername = no
# ---------------------------------------------------------------------------------------------------

# Smtpd ( INCOMING / Server )
smtpd_tls_loglevel            = 1
smtpd_delay_reject = yes
smtpd_helo_required = yes
smtpd_tls_auth_only           = yes
smtpd_tls_security_level      = may
smtpd_tls_received_header     = yes
#smtpd_tls_protocols           = !SSLv2, !SSLv3
smtpd_tls_mandatory_protocols = !SSLv2, !SSLv3
smtpd_tls_mandatory_ciphers   = medium

# Infos (voir : postconf -d)
# Medium cipherlist = aNULL:-aNULL:ALL:!EXPORT:!LOW:+RC4:@STRENGTH
# High cipherlist   = aNULL:-aNULL:ALL:!EXPORT:!LOW:!MEDIUM:+RC4:@STRENGTH

# smtpd_tls_exclude_ciphers   = NE PAS modifier cette directive pour des raisons de compatibilité
#                               avec les autres serveurs de mail afin d'éviter une erreur du type
#                               "no shared cipher" ou "no cipher overlap" puis un fallback en
#                               plain/text...
# smtpd_tls_cipherlist        = Ne pas modifier non plus !

smtpd_tls_cert_file           = /etc/ssl/certs/mail.mydomain.com.crt
smtpd_tls_key_file            = /etc/ssl/private/mydomain.key
smtpd_tls_dh1024_param_file   = $config_directory/dh2048.pem
#smtpd_tls_dh512_param_file    = $config_directory/dh512.pem

tls_preempt_cipherlist = yes
tls_random_source      = dev:/dev/urandom

smtp_tls_session_cache_database  = btree:${data_directory}/smtp_scache
smtpd_tls_session_cache_database = btree:${data_directory}/smtpd_scache
lmtp_tls_session_cache_database  = btree:${data_directory}/lmtp_scache

# ----------------------------------------------------------------------

#####################
## SASL PARAMETERS ##
#####################

smtpd_sasl_auth_enable          = yes
smtpd_sasl_type                 = dovecot
smtpd_sasl_path                 = private/auth
smtpd_sasl_security_options     = noanonymous
smtpd_sasl_tls_security_options = noanonymous
smtpd_sasl_local_domain         = $mydomain
smtpd_sasl_authenticated_header = yes
smtpd_sasl_local_domain         = $mydomain
smtpd_sasl_authenticated_header = yes

broken_sasl_auth_clients = yes

##############################
## VIRTUALS MAPS PARAMETERS ##
##############################

virtual_uid_maps        = static:5000
virtual_gid_maps        = static:5000
virtual_minimum_uid     = 5000
virtual_mailbox_base    = /data/mail
virtual_transport       = lmtp:unix:private/dovecot-lmtp
virtual_mailbox_domains = mysql:/etc/postfix/mysql-virtual-mailbox-domains.cf
virtual_mailbox_maps    = mysql:/etc/postfix/mysql-virtual-mailbox-maps.cf
virtual_alias_maps      = mysql:/etc/postfix/mysql-virtual-alias-maps.cf

######################
## ERRORS REPORTING ##
######################

# notify_classes = bounce, delay, resource, software
notify_classes = resource, software

error_notice_recipient     = admin@mydomain.com
# delay_notice_recipient   = admin@domain.tld
# bounce_notice_recipient  = admin@domain.tld
# 2bounce_notice_recipient = admin@domain.tld

##################
## RESTRICTIONS ##
##################

smtpd_relay_restrictions =
     permit_mynetworks,
     permit_sasl_authenticated,
     reject_non_fqdn_recipient,
     reject_unauth_destination,
     reject_unknown_recipient_domain,
     reject_rbl_client zen.spamhaus.org

smtpd_helo_restrictions =
     permit_mynetworks,
     permit_sasl_authenticated,
     reject_invalid_helo_hostname,
     reject_non_fqdn_helo_hostname
     # reject_unknown_helo_hostname

smtpd_client_restrictions =
     permit_mynetworks,
smtpd_client_restrictions =
     permit_mynetworks,
     permit_inet_interfaces,
     permit_sasl_authenticated

smtpd_sender_restrictions =
     reject_non_fqdn_sender,
     reject_unknown_sender_domain

##########
## DKIM ##
##########

milter_protocol = 6
milter_default_action = accept
#smtpd_milters = unix:/var/spool/postfix/opendkim/opendkim.sock, unix:/var/spool/postfix/opendmarc/opendmarc.sock, unix:/var/run/clamav/clamav-milter.ctl
smtpd_milters         = inet:localhost:12345,inet:localhost:54321
non_smtpd_milters     = $smtpd_milters

debug_peer_list = mail.domain_with_error_5.7.0.fr #log problematic host

Edit :

Mar 21 14:31:57 raspi01 postfix/smtpd[11686]: warning: match_list_parse: comment at end of line is not supported: #log problematic host
Mar 21 14:31:58 raspi01 postfix/smtpd[11686]: connect from mail.domain_with_error_5.7.0.fr[86.xx.xx.xx]
Mar 21 14:31:58 raspi01 postfix/smtpd[11686]: smtp_stream_setup: maxtime=300 enable_deadline=0
Mar 21 14:31:58 raspi01 postfix/smtpd[11686]: match_hostname: mail.domain_with_error_5.7.0.fr ~? 127.0.0.0/8
Mar 21 14:31:58 raspi01 postfix/smtpd[11686]: match_hostaddr: 86.xx.xx.xx ~? 127.0.0.0/8
Mar 21 14:31:58 raspi01 postfix/smtpd[11686]: match_hostname: mail.domain_with_error_5.7.0.fr ~? [::ffff:127.0.0.0]/104
Mar 21 14:31:58 raspi01 postfix/smtpd[11686]: match_hostaddr: 86.xx.xx.xx ~? [::ffff:127.0.0.0]/104
Mar 21 14:31:58 raspi01 postfix/smtpd[11686]: match_hostname: mail.domain_with_error_5.7.0.fr ~? [::1]/128
Mar 21 14:31:58 raspi01 postfix/smtpd[11686]: match_hostaddr: 86.xx.xx.xx ~? [::1]/128
Mar 21 14:31:58 raspi01 postfix/smtpd[11686]: match_hostname: mail.domain_with_error_5.7.0.fr ~? 192.168.0.0/28
Mar 21 14:31:58 raspi01 postfix/smtpd[11686]: match_hostaddr: 86.xx.xx.xx ~? 192.168.0.0/28
Mar 21 14:31:58 raspi01 postfix/smtpd[11686]: match_hostname: mail.domain_with_error_5.7.0.fr ~? 192.168.1.0/28
Mar 21 14:31:58 raspi01 postfix/smtpd[11686]: match_hostaddr: 86.xx.xx.xx ~? 192.168.1.0/28
Mar 21 14:31:58 raspi01 postfix/smtpd[11686]: match_hostname: mail.domain_with_error_5.7.0.fr ~? 192.168.2.0/28
Mar 21 14:31:58 raspi01 postfix/smtpd[11686]: match_hostaddr: 86.xx.xx.xx ~? 192.168.2.0/28
Mar 21 14:31:58 raspi01 postfix/smtpd[11686]: match_list_match: mail.domain_with_error_5.7.0.fr: no match
Mar 21 14:31:58 raspi01 postfix/smtpd[11686]: match_list_match: 86.xx.xx.xx: no match
Mar 21 14:31:58 raspi01 postfix/smtpd[11686]: auto_clnt_open: connected to private/anvil
Mar 21 14:31:58 raspi01 postfix/smtpd[11686]: send attr request = connect
Mar 21 14:31:58 raspi01 postfix/smtpd[11686]: send attr ident = smtp:86.xx.xx.xx
Mar 21 14:31:58 raspi01 postfix/smtpd[11686]: private/anvil: wanted attribute: status
Mar 21 14:31:58 raspi01 postfix/smtpd[11686]: input attribute name: status
Mar 21 14:31:58 raspi01 postfix/smtpd[11686]: input attribute value: 0
Mar 21 14:31:58 raspi01 postfix/smtpd[11686]: private/anvil: wanted attribute: count
Mar 21 14:31:58 raspi01 postfix/smtpd[11686]: input attribute name: count
Mar 21 14:31:58 raspi01 postfix/smtpd[11686]: input attribute value: 1
Mar 21 14:31:58 raspi01 postfix/smtpd[11686]: private/anvil: wanted attribute: rate
Mar 21 14:31:58 raspi01 postfix/smtpd[11686]: input attribute name: rate
Mar 21 14:31:58 raspi01 postfix/smtpd[11686]: input attribute value: 1
Mar 21 14:31:58 raspi01 postfix/smtpd[11686]: private/anvil: wanted attribute: (list terminator)
Mar 21 14:31:58 raspi01 postfix/smtpd[11686]: input attribute name: (end)
Mar 21 14:31:58 raspi01 postfix/smtpd[11686]: report connect to all milters
Mar 21 14:31:58 raspi01 postfix/smtpd[11686]: milter_macro_lookup: "j"
Mar 21 14:31:58 raspi01 postfix/smtpd[11686]: milter_macro_lookup: result "mail.mydomain.com"
Mar 21 14:31:58 raspi01 postfix/smtpd[11686]: milter_macro_lookup: "{daemon_name}"
Mar 21 14:31:58 raspi01 postfix/smtpd[11686]: milter_macro_lookup: result "mail.mydomain.com"
Mar 21 14:31:58 raspi01 postfix/smtpd[11686]: milter_macro_lookup: "v"
Mar 21 14:31:58 raspi01 postfix/smtpd[11686]: milter_macro_lookup: result "Postfix 2.11.3"
Mar 21 14:31:58 raspi01 postfix/smtpd[11686]: milter8_connect: non-protocol events for protocol version 6:
Mar 21 14:31:58 raspi01 postfix/smtpd[11686]: milter8_connect: transport=inet endpoint=localhost:12345
Mar 21 14:31:58 raspi01 postfix/smtpd[11686]: trying... [127.0.0.1]
Mar 21 14:31:58 raspi01 postfix/smtpd[11686]: vstream_tweak_tcp: TCP_MAXSEG 21845
Mar 21 14:31:58 raspi01 postfix/smtpd[11686]: fd=18: stream buffer size old=0 new=43690
Mar 21 14:31:58 raspi01 postfix/smtpd[11686]: milter8_connect: my_version=0x6
Mar 21 14:31:58 raspi01 postfix/smtpd[11686]: milter8_connect: my_actions=0x1ff SMFIF_ADDHDRS SMFIF_CHGBODY SMFIF_ADDRCPT SMFIF_DELRCPT SMFIF_CHGHDRS SMFIF_QUARANTINE SMFIF_CHGFROM SMFIF_ADDRCPT_PAR SMFIF_SETSYMLIST
Mar 21 14:31:58 raspi01 postfix/smtpd[11686]: milter8_connect: my_events=0x1fffff SMFIP_NOCONNECT SMFIP_NOHELO SMFIP_NOMAIL SMFIP_NORCPT SMFIP_NOBODY SMFIP_NOHDRS SMFIP_NOEOH SMFIP_NR_HDR SMFIP_NOUNKNOWN SMFIP_NODATA SMFIP_SKIP SMFIP_RCPT_REJ SMFIP_NR_CONN SMFIP_NR_HELO SMFIP_NR_MAIL SMFIP_NR_RCPT SMFIP_NR_DATA SMFIP_NR_UNKN SMFIP_NR_EOH SMFIP_NR_BODY SMFIP_HDR_LEADSPC
Mar 21 14:31:58 raspi01 postfix/smtpd[11686]: milter8_connect: milter inet:localhost:12345 version 6
Mar 21 14:31:58 raspi01 postfix/smtpd[11686]: milter8_connect: events SMFIP_NOHELO SMFIP_NOUNKNOWN SMFIP_NODATA SMFIP_SKIP SMFIP_HDR_LEADSPC
Mar 21 14:31:58 raspi01 postfix/smtpd[11686]: milter8_connect: requests SMFIF_ADDHDRS SMFIF_CHGHDRS SMFIF_SETSYMLIST
Mar 21 14:31:58 raspi01 postfix/smtpd[11686]: milter8_conn_event: milter inet:localhost:12345: connect mail.domain_with_error_5.7.0.fr/86.xx.xx.xx
Mar 21 14:31:58 raspi01 postfix/smtpd[11686]: event: SMFIC_CONNECT; macros: j=mail.mydomain.com {daemon_name}=mail.mydomain.com v=Postfix 2.11.3
Mar 21 14:31:58 raspi01 postfix/smtpd[11686]: reply: SMFIR_CONTINUE data 0 bytes
Mar 21 14:31:58 raspi01 postfix/smtpd[11686]: milter8_connect: non-protocol events for protocol version 6:
Mar 21 14:31:58 raspi01 postfix/smtpd[11686]: milter8_connect: transport=inet endpoint=localhost:54321
Mar 21 14:31:58 raspi01 postfix/smtpd[11686]: trying... [127.0.0.1]
Mar 21 14:31:58 raspi01 postfix/smtpd[11686]: vstream_tweak_tcp: TCP_MAXSEG 21845
Mar 21 14:31:58 raspi01 postfix/smtpd[11686]: fd=19: stream buffer size old=0 new=43690
Mar 21 14:31:58 raspi01 postfix/smtpd[11686]: milter8_connect: my_version=0x6
Mar 21 14:31:58 raspi01 postfix/smtpd[11686]: milter8_connect: my_actions=0x1ff SMFIF_ADDHDRS SMFIF_CHGBODY SMFIF_ADDRCPT SMFIF_DELRCPT SMFIF_CHGHDRS SMFIF_QUARANTINE SMFIF_CHGFROM SMFIF_ADDRCPT_PAR SMFIF_SETSYMLIST
Mar 21 14:31:58 raspi01 postfix/smtpd[11686]: milter8_connect: my_events=0x1fffff SMFIP_NOCONNECT SMFIP_NOHELO SMFIP_NOMAIL SMFIP_NORCPT SMFIP_NOBODY SMFIP_NOHDRS SMFIP_NOEOH SMFIP_NR_HDR SMFIP_NOUNKNOWN SMFIP_NODATA SMFIP_SKIP SMFIP_RCPT_REJ SMFIP_NR_CONN SMFIP_NR_HELO SMFIP_NR_MAIL SMFIP_NR_RCPT SMFIP_NR_DATA SMFIP_NR_UNKN SMFIP_NR_EOH SMFIP_NR_BODY SMFIP_HDR_LEADSPC
Mar 21 14:31:58 raspi01 postfix/smtpd[11686]: milter8_connect: milter inet:localhost:54321 version 6
Mar 21 14:31:58 raspi01 postfix/smtpd[11686]: milter8_connect: events SMFIP_NOHELO SMFIP_NOBODY SMFIP_NOUNKNOWN SMFIP_NODATA SMFIP_SKIP
Mar 21 14:31:58 raspi01 postfix/smtpd[11686]: milter8_connect: requests SMFIF_ADDHDRS SMFIF_QUARANTINE
Mar 21 14:31:58 raspi01 postfix/smtpd[11686]: milter8_conn_event: milter inet:localhost:54321: connect mail.domain_with_error_5.7.0.fr/86.xx.xx.xx
Mar 21 14:31:58 raspi01 postfix/smtpd[11686]: event: SMFIC_CONNECT; macros: j=mail.mydomain.com {daemon_name}=mail.mydomain.com v=Postfix 2.11.3
Mar 21 14:31:58 raspi01 postfix/smtpd[11686]: reply: SMFIR_CONTINUE data 0 bytes
Mar 21 14:31:58 raspi01 postfix/smtpd[11686]: > mail.domain_with_error_5.7.0.fr[86.xx.xx.xx]: 220 mail.mydomain.com ESMTP Postfix
Mar 21 14:31:58 raspi01 postfix/smtpd[11686]: watchdog_pat: 0x554664b8
Mar 21 14:31:58 raspi01 postfix/smtpd[11686]: < mail.domain_with_error_5.7.0.fr[86.xx.xx.xx]: EHLO mail.domain_with_error_5.7.0.fr
Mar 21 14:31:58 raspi01 postfix/smtpd[11686]: report helo to all milters
Mar 21 14:31:58 raspi01 postfix/smtpd[11686]: milter_macro_lookup: "{tls_version}"
Mar 21 14:31:58 raspi01 postfix/smtpd[11686]: milter_macro_lookup: "{cipher}"
Mar 21 14:31:58 raspi01 postfix/smtpd[11686]: milter_macro_lookup: "{cipher_bits}"
Mar 21 14:31:58 raspi01 postfix/smtpd[11686]: milter_macro_lookup: "{cert_subject}"
Mar 21 14:31:58 raspi01 postfix/smtpd[11686]: milter_macro_lookup: "{cert_issuer}"
Mar 21 14:31:58 raspi01 postfix/smtpd[11686]: milter8_helo_event: milter inet:localhost:12345: helo mail.domain_with_error_5.7.0.fr
Mar 21 14:31:58 raspi01 postfix/smtpd[11686]: event: SMFIC_HELO; macros: (none)
Mar 21 14:31:58 raspi01 postfix/smtpd[11686]: skipping event SMFIC_HELO for milter inet:localhost:12345
Mar 21 14:31:58 raspi01 postfix/smtpd[11686]: milter8_helo_event: milter inet:localhost:54321: helo mail.domain_with_error_5.7.0.fr
Mar 21 14:31:58 raspi01 postfix/smtpd[11686]: event: SMFIC_HELO; macros: (none)
Mar 21 14:31:58 raspi01 postfix/smtpd[11686]: skipping event SMFIC_HELO for milter inet:localhost:54321
Mar 21 14:31:58 raspi01 postfix/smtpd[11686]: match_list_match: mail.domain_with_error_5.7.0.fr: no match
Mar 21 14:31:58 raspi01 postfix/smtpd[11686]: match_list_match: 86.xx.xx.xx: no match
Mar 21 14:31:58 raspi01 postfix/smtpd[11686]: > mail.domain_with_error_5.7.0.fr[86.xx.xx.xx]: 250-mail.mydomain.com
Mar 21 14:31:58 raspi01 postfix/smtpd[11686]: > mail.domain_with_error_5.7.0.fr[86.xx.xx.xx]: 250-PIPELINING
Mar 21 14:31:58 raspi01 postfix/smtpd[11686]: > mail.domain_with_error_5.7.0.fr[86.xx.xx.xx]: 250-SIZE 50240000
Mar 21 14:31:58 raspi01 postfix/smtpd[11686]: > mail.domain_with_error_5.7.0.fr[86.xx.xx.xx]: 250-ETRN
Mar 21 14:31:58 raspi01 postfix/smtpd[11686]: > mail.domain_with_error_5.7.0.fr[86.xx.xx.xx]: 250-STARTTLS
Mar 21 14:31:58 raspi01 postfix/smtpd[11686]: > mail.domain_with_error_5.7.0.fr[86.xx.xx.xx]: 250-ENHANCEDSTATUSCODES
Mar 21 14:31:58 raspi01 postfix/smtpd[11686]: > mail.domain_with_error_5.7.0.fr[86.xx.xx.xx]: 250-8BITMIME
Mar 21 14:31:58 raspi01 postfix/smtpd[11686]: > mail.domain_with_error_5.7.0.fr[86.xx.xx.xx]: 250 DSN
Mar 21 14:31:58 raspi01 postfix/smtpd[11686]: watchdog_pat: 0x554664b8
Mar 21 14:31:58 raspi01 postfix/smtpd[11686]: < mail.domain_with_error_5.7.0.fr[86.xx.xx.xx]: MAIL FROM:<external@domain_with_error.com> SIZE=3853
Mar 21 14:31:58 raspi01 postfix/smtpd[11686]: > mail.domain_with_error_5.7.0.fr[86.xx.xx.xx]: 530 5.7.0 Must issue a STARTTLS command first
Mar 21 14:31:58 raspi01 postfix/smtpd[11686]: watchdog_pat: 0x554664b8
Mar 21 14:31:58 raspi01 postfix/smtpd[11686]: < mail.domain_with_error_5.7.0.fr[86.xx.xx.xx]: RCPT TO:<internal@mydomain.com> ORCPT=rfc822;internal@mydomain.com
Mar 21 14:31:58 raspi01 postfix/smtpd[11686]: > mail.domain_with_error_5.7.0.fr[86.xx.xx.xx]: 530 5.7.0 Must issue a STARTTLS command first
Mar 21 14:31:58 raspi01 postfix/smtpd[11686]: watchdog_pat: 0x554664b8
Mar 21 14:31:58 raspi01 postfix/smtpd[11686]: < mail.domain_with_error_5.7.0.fr[86.xx.xx.xx]: DATA
Mar 21 14:31:58 raspi01 postfix/smtpd[11686]: > mail.domain_with_error_5.7.0.fr[86.xx.xx.xx]: 530 5.7.0 Must issue a STARTTLS command first
Mar 21 14:31:58 raspi01 postfix/smtpd[11686]: watchdog_pat: 0x554664b8
Mar 21 14:31:58 raspi01 postfix/smtpd[11686]: < mail.domain_with_error_5.7.0.fr[86.xx.xx.xx]: RSET
Mar 21 14:31:58 raspi01 postfix/smtpd[11686]: > mail.domain_with_error_5.7.0.fr[86.xx.xx.xx]: 530 5.7.0 Must issue a STARTTLS command first
Mar 21 14:31:58 raspi01 postfix/smtpd[11686]: watchdog_pat: 0x554664b8
Mar 21 14:31:58 raspi01 postfix/smtpd[11686]: < mail.domain_with_error_5.7.0.fr[86.xx.xx.xx]: QUIT
Mar 21 14:31:58 raspi01 postfix/smtpd[11686]: > mail.domain_with_error_5.7.0.fr[86.xx.xx.xx]: 221 2.0.0 Bye
Mar 21 14:31:58 raspi01 postfix/smtpd[11686]: match_hostname: mail.domain_with_error_5.7.0.fr ~? 127.0.0.0/8
Mar 21 14:31:58 raspi01 postfix/smtpd[11686]: match_hostaddr: 86.xx.xx.xx ~? 127.0.0.0/8
Mar 21 14:31:58 raspi01 postfix/smtpd[11686]: match_hostname: mail.domain_with_error_5.7.0.fr ~? [::ffff:127.0.0.0]/104
Mar 21 14:31:58 raspi01 postfix/smtpd[11686]: match_hostaddr: 86.xx.xx.xx ~? [::ffff:127.0.0.0]/104
Mar 21 14:31:58 raspi01 postfix/smtpd[11686]: match_hostname: mail.domain_with_error_5.7.0.fr ~? [::1]/128
Mar 21 14:31:58 raspi01 postfix/smtpd[11686]: match_hostaddr: 86.xx.xx.xx ~? [::1]/128
Mar 21 14:31:58 raspi01 postfix/smtpd[11686]: match_hostname: mail.domain_with_error_5.7.0.fr ~? 192.168.0.0/28
Mar 21 14:31:58 raspi01 postfix/smtpd[11686]: match_hostaddr: 86.xx.xx.xx ~? 192.168.0.0/28
Mar 21 14:31:58 raspi01 postfix/smtpd[11686]: match_hostname: mail.domain_with_error_5.7.0.fr ~? 192.168.1.0/28
Mar 21 14:31:58 raspi01 postfix/smtpd[11686]: match_hostaddr: 86.xx.xx.xx ~? 192.168.1.0/28
Mar 21 14:31:58 raspi01 postfix/smtpd[11686]: match_hostname: mail.domain_with_error_5.7.0.fr ~? 192.168.2.0/28
Mar 21 14:31:58 raspi01 postfix/smtpd[11686]: match_hostaddr: 86.xx.xx.xx ~? 192.168.2.0/28
Mar 21 14:31:58 raspi01 postfix/smtpd[11686]: match_list_match: mail.domain_with_error_5.7.0.fr: no match
Mar 21 14:31:58 raspi01 postfix/smtpd[11686]: match_list_match: 86.xx.xx.xx: no match
Mar 21 14:31:58 raspi01 postfix/smtpd[11686]: send attr request = disconnect
Mar 21 14:31:58 raspi01 postfix/smtpd[11686]: send attr ident = smtp:86.xx.xx.xx
Mar 21 14:31:58 raspi01 postfix/smtpd[11686]: private/anvil: wanted attribute: status
Mar 21 14:31:58 raspi01 postfix/smtpd[11686]: input attribute name: status
Mar 21 14:31:58 raspi01 postfix/smtpd[11686]: input attribute value: 0
Mar 21 14:31:58 raspi01 postfix/smtpd[11686]: private/anvil: wanted attribute: (list terminator)
Mar 21 14:31:58 raspi01 postfix/smtpd[11686]: input attribute name: (end)
Mar 21 14:31:58 raspi01 postfix/smtpd[11686]: abort all milters
Mar 21 14:31:58 raspi01 postfix/smtpd[11686]: milter8_abort: abort milter inet:localhost:12345
Mar 21 14:31:58 raspi01 postfix/smtpd[11686]: milter8_abort: abort milter inet:localhost:54321
Mar 21 14:31:58 raspi01 postfix/smtpd[11686]: disconnect event to all milters
Mar 21 14:31:58 raspi01 postfix/smtpd[11686]: milter8_disc_event: quit milter inet:localhost:12345
Mar 21 14:31:58 raspi01 postfix/smtpd[11686]: milter8_disc_event: quit milter inet:localhost:54321
Mar 21 14:31:58 raspi01 postfix/smtpd[11686]: disconnect from mail.domain_with_error_5.7.0.fr[86.xx.xx.xx]

That is slightly odd. I recommend turning up debug output as more authentication details are shown at SMTPDebug = 4.

One minor thing — don’t set $this->mail->Mailer = 'smtp'; yourself; you’re already calling $this->mail->isSMTP(); which does that for you.

I recommend you avoid $this->mail->SingleTo = true;; it’s deprecated, and you should be sending messages individually yourself.

**I tried everything, but it still failed. Do you have any way to help me?

My file config Mailer

<?php
namespace AppClasses;
use PHPMailerPHPMailerPHPMailer;
class Mail
{
protected $mail;
public function __construct()
{
$this->mail = new PHPMailer;
$this->setUp();
}
public function setUp()
{
$this->mail->isSMTP();
$this->SMTPAuth = true;
$this->mail->SMTPSecure = PHPMailer::ENCRYPTION_STARTTLS;
$this->mail->Host = 'smtp.gmail.com';
$this->mail->Port = 587;
$environment = getenv('APP_ENV');
if($environment === 'local'){$this->mail->SMTPDebug = 4;}
//auth info
$this->mail->Username = 'cokhimoitruongtinphat@gmail.com';
$this->mail->Password = 'xxxx';
$this->mail->isHTML(true);    // Set email format to HTML
//       $this->mail->SingleTo = true; // set multiple user
// send info
$this->mail->setFrom('cokhimoitruongtinphat@gmail.com', 'Mailer');
}
public function send($data)
{
$this->mail->addAddress($data['to'], $data['name']);
$this->mail->Subject = $data['subject'];
$this->mail->Body = make($data['view'], array('data' => $data['body']));
return $this->mail->send();
}
}

File Report Error

2020-07-04 08:17:06 Connection: opening to smtp.gmail.com:587, timeout=300, options=array()
2020-07-04 08:17:06 Connection: opened
2020-07-04 08:17:06 SMTP INBOUND: "220 smtp.gmail.com ESMTP u14sm14743789pfk.211 - gsmtp"
2020-07-04 08:17:06 SERVER -> CLIENT: 220 smtp.gmail.com ESMTP u14sm14743789pfk.211 - gsmtp
2020-07-04 08:17:06 CLIENT -> SERVER: EHLO acme.local
2020-07-04 08:17:06 SMTP INBOUND: "250-smtp.gmail.com at your service, [2402:800:6318:62c2:423:6272:60cf:98f9]"
2020-07-04 08:17:06 SMTP INBOUND: "250-SIZE 35882577"
2020-07-04 08:17:06 SMTP INBOUND: "250-8BITMIME"
2020-07-04 08:17:06 SMTP INBOUND: "250-STARTTLS"
2020-07-04 08:17:06 SMTP INBOUND: "250-ENHANCEDSTATUSCODES"
2020-07-04 08:17:06 SMTP INBOUND: "250-PIPELINING"
2020-07-04 08:17:06 SMTP INBOUND: "250-CHUNKING"
2020-07-04 08:17:06 SMTP INBOUND: "250 SMTPUTF8"
2020-07-04 08:17:06 SERVER -> CLIENT: 250-smtp.gmail.com at your service, [2402:800:6318:62c2:423:6272:60cf:98f9]250-SIZE 35882577250-8BITMIME250-STARTTLS250-ENHANCEDSTATUSCODES250-PIPELINING250-CHUNKING250 SMTPUTF8
2020-07-04 08:17:06 CLIENT -> SERVER: STARTTLS
2020-07-04 08:17:06 SMTP INBOUND: "220 2.0.0 Ready to start TLS"
2020-07-04 08:17:06 SERVER -> CLIENT: 220 2.0.0 Ready to start TLS
2020-07-04 08:17:06 CLIENT -> SERVER: EHLO acme.local
2020-07-04 08:17:07 SMTP INBOUND: "250-smtp.gmail.com at your service, [2402:800:6318:62c2:423:6272:60cf:98f9]"
2020-07-04 08:17:07 SMTP INBOUND: "250-SIZE 35882577"
2020-07-04 08:17:07 SMTP INBOUND: "250-8BITMIME"
2020-07-04 08:17:07 SMTP INBOUND: "250-AUTH LOGIN PLAIN XOAUTH2 PLAIN-CLIENTTOKEN OAUTHBEARER XOAUTH"
2020-07-04 08:17:07 SMTP INBOUND: "250-ENHANCEDSTATUSCODES"
2020-07-04 08:17:07 SMTP INBOUND: "250-PIPELINING"
2020-07-04 08:17:07 SMTP INBOUND: "250-CHUNKING"
2020-07-04 08:17:07 SMTP INBOUND: "250 SMTPUTF8"
2020-07-04 08:17:07 SERVER -> CLIENT: 250-smtp.gmail.com at your service, [2402:800:6318:62c2:423:6272:60cf:98f9]250-SIZE 35882577250-8BITMIME250-AUTH LOGIN PLAIN XOAUTH2 PLAIN-CLIENTTOKEN OAUTHBEARER XOAUTH250-ENHANCEDSTATUSCODES250-PIPELINING250-CHUNKING250 SMTPUTF8
2020-07-04 08:17:07 CLIENT -> SERVER: MAIL FROM:<cokhimoitruongtinphat@gmail.com>
2020-07-04 08:17:07 SMTP INBOUND: "530-5.7.0 Authentication Required. Learn more at"
2020-07-04 08:17:07 SMTP INBOUND: "530 5.7.0 https://support.google.com/mail/?p=WantAuthError u14sm14743789pfk.211 - gsmtp"
2020-07-04 08:17:07 SERVER -> CLIENT: 530-5.7.0 Authentication Required. Learn more at530 5.7.0 https://support.google.com/mail/?p=WantAuthError u14sm14743789pfk.211 - gsmtp
2020-07-04 08:17:07 SMTP ERROR: MAIL FROM command failed: 530-5.7.0 Authentication Required. Learn more at530 5.7.0 https://support.google.com/mail/?p=WantAuthError u14sm14743789pfk.211 - gsmtp
The following From address failed: cokhimoitruongtinphat@gmail.com : MAIL FROM command failed,Authentication Required. Learn more at https://support.google.com/mail/?p=WantAuthError u14sm14743789pfk.211 - gsmtp,530,5.7.0SMTP server error: MAIL FROM command failed Detail: Authentication Required. Learn more at https://support.google.com/mail/?p=WantAuthError u14sm14743789pfk.211 - gsmtp SMTP code: 530 Additional SMTP info: 5.7.0
Email send failed2020-07-04 08:17:07 CLIENT -> SERVER: QUIT
2020-07-04 08:17:07 SMTP INBOUND: "221 2.0.0 closing connection u14sm14743789pfk.211 - gsmtp"
2020-07-04 08:17:07 SERVER -> CLIENT: 221 2.0.0 closing connection u14sm14743789pfk.211 - gsmtp
2020-07-04 08:17:07 Connection: closed

Если отправка сообщений через SMTP не удается, SMTP сервер сообщает код ошибки, по нему можно определить, в чем проблема и как ее исправить. Наиболее распространенные ошибки указаны в списке ниже.

SYMPTOMS

Clients or remote servers sending email via SMTP to the mail server are given
an error that the connecting IP address has been «denied access».

CAUSE

The IP address of the inbound connection has been denied access due to
being listed in the SMTP Access Control properties of the MailEnable
administration program. IP addresses can be added here both manually and
automatically depending on options.

Example error:

530 example.com ESMTP MailEnable Service, Version: 9.00—9.00 denied access
at 01/01/17 17:00:00

RESOLUTION

1. Navigate within the Administration console to the following location:
   Servers->localhost->Services and Connectors, right click on «SMTP» and
   select «Properties» in the popup menu.
2. Navigate to the «Inbound» tab and click on «Access Control».
3. If the Access Control option is set to «Granted access», then ensure the
   IP is not in the list being denied access. If the Access Control option is set
   to «Denied Access» then the connecting IP address needs to be listed
   in order to be allowed access.

MORE INFORMATION

The incoming IP address can automatically be added to the inbound
«Access Control» list if the SMTP security «connection dropping» option is
enabled along with the option to ban. The SMTP service will
drop the connection when the failed number of commands or
recipients is exceeded (during the one SMTP conversation) and add the IP address
to the inbound «Access Control» list.

The SMTP Debug log will have the following line in it when it bans an IP
address:

ME-I0073: IP Address 123.123.123.123 banned.

It is recommended to not enable the autobanning. It is normally better to use
the abuse detection option instead. If you use autobanning do not lower the
value for the failed number of commands to a low number. If an IP address has
been whitelisted in the SMTP settings, it will not be autobanned.