We set up a VM in Windows Azure cloud service. However, the SMTP is not working. All the messages are queuing in the mailroot\queue folder. Here are some delivery failure message received.
Delivery Status Notification (Failure)
Action: failed
Status: 5.5.0
Diagnostic-Code: smtp;550-5.7.1 [x.x.x.x] The IP you're using to send mail is not authorized to 550-5.7.1 send email directly to our servers. Please use the SMTP relay at your
550-5.7.1 service provider instead.
Delivery Status Notification (Failure)
Action: failed
Status: 5.5.0
Diagnostic-Code: smtp;550 OU-002 (COL0-MC1-F41) Unfortunately, messages from x.x.x.x weren't sent. Please contact your Internet service provider since part of their network is on our block list.
How can it be solved? Please help. Thanks
That looks to me as though the receiving hosts are blocking you from sending to them, probably because your IP is on a blocklist. You can check that on http://mxtoolbox.com/blacklists.aspx
You might want to raise a support ticket with Azure and complain, and/or alternatively ask them for their SMTP server settings, which will relay the mail through their servers (which should never be blocked).
Related
When I try to send a message via smtp, the error message "550 5.7.60 SMTP Client does not have permissions to send as this sender" appears.
If I give myself a send as permission on my own Mailbox, the whole thing works.
I tried to connect via telnet and found that the authentication is NTML.
The Receive connector is configured correct.
I use an Exchange Server 2019.
I am trying to setup Sendinblue and use it as an SMTP server for my marketing and general Odoo 12 email messaging.
I setup every thing in Sendinblue and tested the SMTP Server in Odoo and got a "sucess" message under Settings / Technical / Outgoing Mail Servers.
For this I setup an external smpt server with the following data:
SMTP Server: smtp-relay.sendinblue.com
Email: my sendinblue email
Password: Password provided by sendinblue
Port: 587
Security: TLS (STARTTLS)
I can test the connection with success and set this SMTP Server as the server for sending email campaigns from Email Marketing / Settings / General Settings
Created a test email campaign and tried to send it and test it with no luck.
When Odoo tries to send the message, returns a "not delivered email" message with a unique reference and my local PC name, something like:
989345297097442.1625436965.401543280300903-openerp-reply_to#MYPC-NAME
I confirm sender email is registered and validated in Sendinblue. Using the same email as sender in Odoo.
Tried to do the same with my personal gmail account but even activating less secure apps, no message is sent from my instance.
What could be wrong?
I found the problem.
I had to verify the domain name I use for sending emails from Sendinblue service.
I have done it Senders & API main menu option on "domain" tab.
After verifying my domain name, everything is running fine
My website https://www.smcin.com/ created in drupal 7 and hosted in google cloud console. I am using PHPmailer smtp module to send email through website using port 25. But not mail has been triggered and give error
"test e-mail has NOT been sent to xxxxxxxx#yahoo.com. You should check
the logs for error messages."
On logs only this message has been shown:
MESSAGE: Error sending e-mail (from xxxxxxxx#xxxxxxx.xxx to xxxxxxxx#yahoo.com).
SEVERITY: error.
I also tried other ports (80, 465, 2525 ) and server (gmail, my official webmail) but nothing work.
I wasted lots of time but no solution found.
Your question is unclear as to which Google Cloud Platform service you are using.
Assuming that you're using Compute Engine, please see Sending email from an instance.
NB "Port 25 is always blocked and can't be used"
You should be able to configure it to use e.g. 465.
You may continue to have challenges in showing a good reputation for your instances' IP addresses.
I have a very curious issue with an application. When debugging locally, I can send emails just fine using a client's G Suite email credentials:
<smtp deliveryMethod="Network" from="client#customdomain.com">
<network defaultCredentials="false"
host="smtp.gmail.com"
port="587"
userName="client#customdomail.com"
password="supersecret"
enableSsl="true" />
</smtp>
Now, it's very important to note that the application will send just fine with the credentials when running on localhost using Visual Studio. However, when deploying to LIVE and using the exact same credentials, the application refuses to send and I only get the canned response back saying "Failure Sending mail".
I have enabled "less secure applications" in the settings and have verified the "suspicious activity" from the server's IP address. I can also log in to the Gmail account from the server using RDP and opening Firefox to go to Gmail.com.
No firewall rule has been set to block SMTP or anything on port 587.
UPDATE: the materialized error message is
A connection attempt failed because the connected party did not properly respond after a period of time, or established connection failed because connected host has failed to respond 74.125.192.108:587
74.125.192.108 being smtp.gmail.com's IP Address (or one of them, at least)
UPDATE 2: I can also not get Thunderbird on the remote server to send an email using the supplied credentials, however it can connect via IMAP and download the contents of the inbox just fine.
Well in this very specific case, it was the fault of the Amazon infrastructure this application ran on. Either amazon themselves, or the reseller changed a policy that ended up blocking communications on ports 465, 587 and 993 (and probably others too).
The "solution" was to nag them to sort it out.
I have started to see an intermittant error when sending email via my application.
System.Net.Mail.SmtpException: Service not available, closing transmission channel. The server response was: 4.4.2 service timed out.
Now obviously it's timing out for some reason, but any ideas as to why this is happening now? This is the first time I've seen it happen.
Some things to check:
has anything on the server side changed? Did the admins add some kind of greylisting, perhaps?
what happens if you connect to the server directly via telnet on port 25?
does this occur from other applications, as well (e.g. your desktop E-mail client) ?