I have problem with checking existing of gmail account. For connecting to smtp server i use openssl for Windows. After run i writing next line to connect to server:
s_client -starttls smtp -crlf -connect smtp.gmail.com:587
After connect, i login on server using auth login.
After this i starting to create new mail:
C:mail from:<somegmail#gmail.com>
S:250 2.1.0 OK w7sm27345781wiz.0
C:rcpt to:<incorrectEmail#asas.com> //input incorrect email
S:250 2.1.0 OK w7sm27345781wiz.0
But after input incorrect email server must return error:
550-5.1.1 The email account that you tried to reach does not exist...
Why server not return error?
The sending server accepts your message, for sending, but does not check if the destination is actually valid at this time. That is why you have a success message.
The server is basically telling you: "Ok I have your message and will try to deliver it"
It will be later, when the gmail.com server talks with the asas.com server, that the asas.com server will give an error, at which time you will receive a bounce email from Gmail
Related
Can someone help me out to this below issue. We done change smtp to office365 but after change the smtp host, we start getting below issue
Transaction failed. The server response was: 5.2.0 STOREDRV.Submission.Exception:SendAsDeniedException.MapiExceptionSendAsDenied; Failed to process message due to a permanent exception with message Cannot submit message.
The email address used in the SMTP protocol (MAIL From:<salesperson1#contoso.com>) must be identical to your office365 account name, i.e. "salesperson1#contoso.com".
Source: check this Microsoft support page, related to printers and scanners:
"Your printer or application must send email from the same address that you entered logon credentials for during email setup. If the printer or application tries to send email from a different account, this results in an error similar to:
5.7.60 SMTP; Client does not have permissions to send as this sender.
For example, if you entered login credentials for sales#contoso.com in your application settings, but the application tries to send emails from salesperson1#contoso.com, this is not supported. For this scenario, use Microsoft 365 or Office 365 SMTP relay instead."
In our case, the address mismatch causes office365.com to reply with the following error message:
554 5.2.0 STOREDRV.Submission.Exception:SendAsDeniedException.MapiExceptionSendAsDenied; Failed to process message due to a permanent exception with message Cannot submit message.
and has been resolved as described.
If using Asp.net/c#, then ensure the sender id used in NetworkCredential is similar to the from email address as below:
MailServer.Credentials = new System.Net.NetworkCredential(SenderId, SenderPass);
MailAddress from = new MailAddress(SenderId);
I don't know if I am asking this in the right place.
I have an SSL cert for my website, and I am trying to setup a mail server (same domain) using the same cert.
I am using Postfix and Dovecot. When I try logging in from Evolution mail client, I get an error "Peer failed to perform TLS handshake". When I try an online service to verify I get "Recipient address rejected: User unknown in local recipient table."
I guess my actual question is, can I actually use the same SSL cert for my website and my email server?
What do I do to debug next?
You can use a certificate you have for the web server also for your mail server as long as it matches the hostname you use to access your mail server. Of course the certificate need to properly setup at the mail server, i.e. include the necessary intermediate certificates similar to how it is (hopefully) setup on the web server.
I am using Postfix and Dovecot.
This means you need to take care of multiple configurations, both for SMTP in Postfix and IMAP/POP3 (whatever you use) in Dovecot. And in all cases the certificates subject/SAN must match the hostname you use to connect to the server.
When I try logging in from Evolution mail client, I get an error "Peer failed to perform TLS handshake".
There are not enough information about this setup to find out what exactly is causing the TLS error. It is not even clear if the error is caused when retrieving mail (IMAP/POP3, i.e. Dovecot) or while sending (Postfix).
When I try an online service to verify I get "Recipient address rejected: User unknown in local recipient table."
This has nothing to do with TLS at all. The test server simply tried to use a recipient which your mail server (Postfix) will not accept.
What do I do to debug next?
The next steps would probably be to check if the certificate matches the names you use in the first place and to look into log files for error messages or warnings. Following steps depend on what the result of these steps is.
I have just installed VestaCP on a fresh CentOS VPS.
I have set up email for one domain. All mail sent to that domain bounces with the error 550 smtp auth requried
I have commented out the following;
deny message = smtp auth requried
from exim.conf
I have turned off anti-spam.
I still get the bounce with this message.
Specifically, if I send an email from a gmail account google responds:
Technical details of permanent failure:
Google tried to deliver your message, but it was rejected by the server for the recipient domain foobar.tld by mail.foobar.tld. [x.x.x.x].
The error that the other server returned was:
550 smtp auth requried
Any experience with this? I have seen the problem on a number of threads but have not found a solution.
I partially solved the problem. It only occurred when sending mail to the smtp server from a domain that was hosted on the same server for web but not for email. When I sent email from a domain that had nothing to do with any domains hosted on the same server as the exim instance, then it got through. I still can't send email from the domain that was causing the problem and I would like to, but I can work around it.
So to be clear in case anyone reads this:
domain1 web is hosted on server1
domain1 email is hosted on google's servers
domain2 is hosted on server1 for web and email
exim is running on server1
when I send email from thunderbird via google's server from email#domain1 to and email#domain2 the exim instance asks google's smtp server for authentication even though the mail is being delivered to a mailbox in its list of domains it can deliver to on the same physical server where it is running.
I suspect that it is suspicious of the from address, which it shouldn't be since the mx records indicate that it does not host mail for that domain.
I have exim on server №1 (1.1.1.1). A mailbox info was created, and email was sending and receiving successfully. But when I perform sending from server №2 (2.2.2.2), using an email and password for authentication, the mail server does not let me, giving the following error:
H=mailer.server2.com (1.1.1.1) [2.2.2.2] rejected MAIL : Access denied
- Invalid HELO name (See RFC2821 4.1.3)
How can I adjust the resolution to be sent from any server with any HELO №2 (2.2.2.2)?
Ubuntu was installed on all servers.
It seems that there is an issues with your mail client setting, Please try to update SMTP authentication setting on your mail client and check this again.
I have problem sending emails, i checked the email sending error logs, and I found this:
RCPT RCPT TO:
503 This mail server requires authentication when attempting to send to a non-local e-mail address. Please check your mail client settings or contact your administrator to verify that the domain or address is defined for this server.
And this:
Sending unsolicited commercial or bulk e-mail to Microsoft's computer network is prohibited. Other restrictions are found at http://privacy.msn.com/Anti-spam/. Violations will result in use of equipment located in California and other states.
And following I dont understand what it means:
DATA DATA 354+Start+mail+input;+end+with+.
RCPT RCPT TO: 250 Requested mail action okay, completed
and some others...
This SMTP server requires authentication. Depending on your provider, you either need to specify username/password or, if your host uses POP-before-SMTP auth, you need to check your email first and that action adds you to an authenticated list for some time so you can send replies.
This error means you need to authenticate against your SMTP server before sending out emails.