Home

The remote smtp service rejected auth negotiation.

Remote support for technicians in the field with our innovative operational smart glasses. Get live support from your remote staff and save time and money. Troubleshoot in realtime Send Targeted E-Comm and Personalized One-to-One Messages for Mailchimp Users. Reliable, Powerful, and Ideal for Sending Data-Driven Emails. Try for Free SMTP Relay Failure - Messages stuck in Queue folder - The remote SMTP service rejected AUTH negotiation Hello, We have configured SMTP Service on our Windows 2008 R2 server to use smtp.office365.com to send emails and we created an account in Office 365 which is used to send emails and is also configured in the outbound security - > basic. Message delivery to the host '46.105.158.212' failed while delivering to the remote domain 'thedomain.net' for the following reason: The remote SMTP service rejected AUTH negotiation. The problem its i believe i need to use a smarthost in order to send the mail, which its my mail provider smtp server

Remote Support for Operators - Remote Assistance SmartGlasse

The remote SMTP service rejected AUTH negotiation. This seems to be quite a common problem, and from what I can see, the problem is simply down to the fact that if you tell the SMTP VS or Connector to use AUTH when connecting to a smart host, Exchange will not fall back to anonymous delivery if the smart host doesn't support auth I've even completely reinstalled and reconfigured the SMTP relay role in IIS following this procedure: here . I'm getting the following warning in the eventvwr: Message delivery to the host '40.97.153.170' failed while delivering to the remote domain '#####.COM' for the following reason: The remote SMTP service rejected AUTH negotiation. In addition what mail server are you using now? Below is a related thread discussed about the similar issue for your reference: SMTP relay Windows server 2012 rejected auth negotiation Please Note: Since the web site is not hosted by Microsoft, the link may change without notice. Microsoft does not guarantee the accuracy of this information Message delivery to the host '[IP address]' failed while delivering to the remote domain 'outsidedomain' for the following reason: The remote SMTP service rejected AUTH negotiation. Using the same account, sending mail using our .Net app is successful. Investigate the protocol with Wireshark, I found difference between two

Message delivery to the host failed while delivering to the remote domain for the following reason: The remote SMTP service rejected AUTH negotiation. First thought (google), I forgot to give that user Authenticated SMTP permissions in M365. Locate the User, go to Mail > Manage email apps and they actually do have the permissions Message delivery to the host 'xxx.xxx.xxx.xxx' failed while delivering to the remote domain 'examplesite.com' for the following reason: The remote SMTP service rejected AUTH negotiation. These errors will be observed in eventvwr->windows log->system. you can try the below fix to resolve these errors The remote SMTP service rejected AUTH negotiation The remote SMTP service rejected AUTH negotiation spencertaylor (Programmer) (OP) 11 Aug 05 06:55. Any help on this one Installed Exchange 2003 on a tempary box to replace a 2000 server moved mailboxes and all went fin

The remote SMTP service rejected AUTH negotiation. LostinParadise asked on 3/7/2005. Exchange. 5 Comments 1 Solution 2143 Views Last Modified: 10/3/2011. Hi all, My problem seems to have been asked before, but I followed the thread and I still have the problem stuck - the remote smtp service rejected auth negotiation . How do I properly setup IIS5's SMTP service to send email from my development environment? (2) I am trying to send email from an ASP.NET web application using the SmtpClient class. So far I have granted relay access to 127.0.0.1. I am trying to send test emails to my gmail account.. The remote smtp service rejected auth negotiation [SOLVED] SMTP relay Windows server 2012 rejected auth negotiation,. This one means that the receiving server does not need or want to Authenticate you, and you have outbound settings that use credentials

Use the Microsoft 365 admin center to enable or disable SMTP AUTH on specific mailboxes. Open the Microsoft 365 admin center and go to Users > Active users. Select the user, and in the flyout that appears, click Mail. In the Email apps section, click Manage email apps. Verify the Authenticated SMTP setting: unchecked = disabled, checked = enabled We are on: the remote smtp service rejected auth negotiation. Due to the above reasons. The recent uncertainty in the feed in tariff scheme. Bill to show up on their. Russell cooper pools auth negotiation. llc has. Seeing that on the web advertising is aimed. Summary bon hiver prides. Liquid diets generally intended to decreas The remote SMTP service rejected AUTH negotiation, seen in the queue to the new Exchange server from the original server. I am able to move mailboxes between servers without probs, and remotely manage each server. Answer : Problem: The remote SMTP service rejected AUTH negotiation, 1 domain, 2 Exchange 2003 Server The remote SMTP service rejected AUTH negotiation. Since SBC started filtering for Spam I have been unable to send to people at sbcglobal.net and others for that matter due to the fact that I.

This Warning event is logged when Exchange cannot deliver a message to a remote host. The event description should specify the reason for the failure. Some common reasons for this Warning event include the following: The connection was dropped by the remote host. The remote SMTP service rejected AUTH negotiation. 2 days ago users stopped being able to send e-mail. It all went into the queue and the SMTP connector showed The remote SMTP service rejected AUTH negotiation.. We have pop3 connector configured. Verizon required secure connection to smtp so set it up under advanced > outbound security > basic. I've rebooted with no avail It show me The remote SMTP service rejected AUTH negotiation. (b) When I create sevamandir@sevamandir.org as local id and try to send mail from that id it works but other id is not able to send mails. (d) When I select Anonymous Access then it start sending mails to some domain but not in rediff and other thing it deliver. SMTP - The remote SMTP service rejected AUTH negotiation. 2 days ago users stopped being able to send e-mail. It all went into the queue and the SMTP connector showed The remote SMTP service rejected AUTH negotiation.. We have pop3 connector configured

SMTP Relay Failure - Messages stuck in Queue folder - The remote SMTP service rejected AUTH negotiation Hello, We have configured SMTP Service on our Windows 2008 R2 server to use smtp.office365.com to send emails and we created an account in Office 365 which is used to send emails and is also configured in the outbound security - > basi The remote SMTP service rejected AUTH negotiation GODADDY! - 14.Jan.2012 10:57:55 PM jaysonk . Posts: 3 Joined: 14.Jan.2012 Status: offline: Hello Everyone, So the exchange 2003 server that you have will not connect to godaddy. You have set these up 10,000 time before and you, for the life of you, cannot get your message store to connect to. In the Add New Account dialog box, enter the Name, email address and password. Check the option 'Require logon using SPA'. Click on 'More Settings' and choose ' Advanced ' tab. In the 'Outgoing server (SMTP)', choose ' TLS ' under 'Use the following type of encrypted connection'. Use SSL authentication for SMTP server Enable SMTP Server. (Server Manager->Features-> Enable SMTP Server) Now it's time to actually configure the SMTP Relay for Office 365. Start->Administrative Tools->Internet Information Services (IIS) 6.0 Manager. Click on the '+' next to your host name. Right-click on the [SMTP Virtual Server] and select Properties

The Remote Smtp Service Rejected Auth Negotiation Office 365 They are two B260 f... 8 months ago IT Pro PowerShell experience PowerShell Conference EU 2016 - [image: banner240x240_eng_360] Last year I took part in PowerShell Community Konferenz that took place From the Support Center, you can also search the Microsoft Product Support Knowledge. EXCH 2003: The remote SMTP service rejected AUTH negotiation. tglaze asked on 2/2/2004. Exchange. 11 Comments 1 Solution 4357 Views Last Modified: 8/13/2012. The above message is being displayed in the additional que information box of the queue in ESM. As far as I can tell, no outgoing email is being sent. Incoming email is AOK Turn up logging on the SMTP Send Connector. To enable logging on a send connector, log into the Exchange Admin Center (EAC) and select the Mail Flow tab and Send Connectors sub-tab. Double click the send connector named Outbound to Office 365 and select Verbose under the General tab. Click Save. To perform this same action through the Exchange. Message delivery to the host ' [ip address of recipient domain]' failed while delivering to the remote domain ' [recipient domain]' for the following reason: The remote SMTP service rejected AUTH negotiation. The SMTP verb which caused the error is 'AUTH' Message delivery to the host '[some IP Like]' failed while delivering to the remote domain 'test.com' for the following reason: The remote server did not respond to a connection attempt. We are using IIS 6 for our SMTP, we don't use Exchange or Outlook or Lotus Notes for our outbound email

We are currently using port 25 with anonymous access using the smtp.comcast.net smarthost. My initial thought was that port 25 was being blocked, but I was able to telnet from the server to the smtp server without an issue, meaning its not being blocked In SBS20003, the SMTP connector has been told to forward all email to another server. The outbound security is set to basic auth with the correct user name and password set. The queue status information on this connector states The remote SMTP service rejected the AUTH negotiation

Transactional Email Service - Use API or SMTP - Free Demo

  1. Local time 6:21 AM aest 11 July 2021 Membership 890,022 registered members 9,603 visited in past 24 hrs Big numbers 3,749,437 threads 69,387,857 posts 4,866 wiki topic
  2. Message delivery to host 'ipnumber' failed while delivering to the remote domain 'domainname' for the following reason. The remote SMTP service rejected AUTH negotiation. I can find instructions for exchange server, but not for just the SMTP server
  3. SMTP Server: smtp.gmail.com. SMTP Port: 465. Use SSL. Username: my.email@gmail.com. Pass: (it's correct!) Send Test Email. I happened to check my email after attempting to get this working, and there was an email from Google with the heading Suspicious sign in prevented and the message Someone recently tried to use an application to sign in.
  4. created a connector in the Office 365 exchange mail flow to allow connection using the external address of the SMTP server. added our external IP address to the acceptable addresses for the domain. tried just creating a txt file and putting in in the C:\inetpub\mailroot\Pickup folder. If it is an outside address it goes through, no issue

SMTP Relay Failure - Messages stuck in Queue folder - The

  1. inal features of an O365 account so that it can be used from another application
  2. I'm not really sure what Exchange organisation is I'm afraid :( All I'm trying to do is get our server to send emails so our website can send emails for forgotten passwords, newsletters etc. Currently we use google apps to receive email for address xyz@scirra.com, we just want now to set our own SMTP server to send emails to people now but they always fail and don't send
  3. To set up a smart host: In IIS Manager, right-click the SMTP virtual server, and then click Properties. Click the Delivery tab, and click Advanced. In the Smart host box, type the name of the smart host server. You can type a string to represent a name or enter an IP address
  4. Select SMTP Server and continue through wizard. Configure the SMTP Service. Go to Start. Select Internet Information Services (IIS) 6.0 Manager. Right-click on SMTP Virtual Server #1. Select Properties. Click on the Access tab. Click on Relay - add your local network, then select OK. Click on the Delivery tab
  5. istration Console. Click on the Ad
  6. SMTP Response codes and troubleshooting tips. Response codes. Each SMTP call you make returns a response. 200 responses are usually success responses, and 400 responses are usually deferrals. SendGrid continues to retry resending 400 messages for up to 72 hours.500 responses are hard failures that are not retried by our servers. This table has possible response codes with example errors and a.
  7. The upper status box should read, Retry, Remote delivery. The lower box should read, The remote SMTP service rejected AUTH negotiation. This resolution addresses two types of delivery methods. Follow these steps to change the SMTP virtual server: Open Exchange System Manager. Expand ServerName, expand Protocols, and then expand SMTP. Right.

When I highlight the Default SMTP Virtual Server SmallBusiness SMTP connector - mail.domainname.com, the message in Additional queue information says The remote server did not respond to a connection attempt. We get the following Event warning in the Application events: I cannot telnet mail.domainname.com 25, but It does connect with port 26 Username and password is correct and I even tried the one I use on my own server, but no luck. The only difference on this server compared to my own is that they have separate ISP for POP and SMTP. Any suggestions as to what I'm doing wrong? Thanks, Rayne

If you can't configure the anonymous relay, please take a look at Using an SMTP server that requires authentication. In my TFS server, I added an SMTP service which uses a smart HTTP host to send mail. The SMTP service on my machine users anonymous authentication with Outbound Security set to use Integrated Windows Authentication The remote SMTP service rejected AUTH negotiation. Any help would be great. markm75 -> RE: Exchange 2007 with Exchange 2003.. migrated mailboxes wont receive email from outside world or email (28.Sep.2007 8:03:52 AM Join Stack Overflow to learn, share knowledge, and build your career Event Id: 4006: Source: MSExchangeTransport: Description: Message delivery to the host SmartHost failed while delivering to the remote domain SmartHostFQDN for the following reason: The remote SMTP service rejected AUTH negotiation. However, when trying to send mail it fails. In the queue under the SMTP connection addition information it says: The remote SMTP service rejected AUTH negotiation.. To check I entered the details correctly I ran telnet and connected to my ISP's SMTP server and tested the authentication manually which worked fine

SMTP relay Windows server 2012 rejected auth negotiatio

The remote SMTP service rejected AUTH negotiation

  1. Select Relay > Only the List Below, and then specify the IP address of the devices relaying through this SMTP server. On the Delivery tab, select Outbound Security, and then do the following: Select Basic Authentication. Enter the credentials of the Office 365 user who you want to use to relay SMTP mail
  2. If you install a local IIS SMTP Relay Server, it will be able to route mail to Office 365 or other destinations, such as hotmail.com, microsoft.com, etc. Mail to domains not hosted on Office 365 will be delivered directly from the IIS SMTP server to the final destination, it will not pass through the Office 365 SMTP servers
  3. AUTH Authenticated SMTP RFC 255. STARTTLS is the SMTP service that starts TLS negotiations between the SMTP servers. You try to send an encrypted e-mail to a remote SMTP server called.

Everytime we send mail it hangs out in the retry cue with the message The remote SMTP service rejected AUTH negotiation. So I thought, okay, maybe I need to set it up on the SMTP Virtual Server instead. So I added the smart host there, setup the outbound port to 587. Then I set the basic authentication username/password to the correct on and. I'm assuming that my ptr records are setup correctly because it's only the Microsoft SMTP server that doesn't work, my MailEnable server works without having to change any settings except allowing 127.0.0.1 to relay. I think I am going to give up on the Microsoft SMTP server and just go back to using the MailEnable one. It just works SMTP-AUTH is configured for this connection, AUTH LOGIN was advertised by the remote server, but an attempt to do AUTH LOGIN was rejected. Deferral: Connected to {IP} but authentication was rejected (username)./Remote host said: {MESSAGE} SMTP-AUTH is configured for this connection, and the username was rejected as part of AUTH LOGIN attempt.

To connect to an SMTP server by using Telnet on port 25, you need to use the fully-qualified domain name (FQDN) (for example, mail.contoso.com) or the IP address of the SMTP server. If you don't know the FQDN or IP address, you can use the Nslookup command-line tool to find the MX record for the destination domain Exchange servers require authentication to route internal user messages between servers. The issue can be caused by one of the following reasons: The Exchange server is experiencing Time synchronization issues. There is a replication issue between the domain controllers. The Exchange server is experiencing Service Principal Name (SPN) issues SMTP2GO means rock solid reliability. An outgoing email service needs to be carefully set up and properly maintained to be capable of performing. No more downtime. Our redundant, multi data center. infrastructure means emails. will still be sent even during. a major internet outage

Mail relay to Office 365 from IIS SMTP Relay - Microsoft

  1. Join over 35,000 people and businesses using SMTP2GO. Get started with our free plan for up to 1,000 emails per month
  2. mutual_auth Use only mechanisms that authenticate both the client and the server to each other. Mail relay authorization options to know are: [From the SASL_READ] With permit_sasl_authenticated the Postfix SMTP server can allow SASL-authenticated SMTP clients to send mail to remote destinations. Examples
  3. The lower box should read, The remote SMTP service rejected AUTH negotiation. RESOLUTION; This resolution addresses two types of delivery methods. Using DNS for Delivery By default, Anonymous access is the default setting for sending SMTP mail by using DNS to all Internet domains. To resolve this behavior
  4. This issue occurs because the certificate isn't enabled for the SMTP service and Exchange Server doesn't check whether the certificate is enabled for the SMTP service when it's associated with the send connector
  5. I have found this is a common issue. You set up an Exchange Online Hybrid or Exchange Online Protection (EOP) stand alone service and follow all the instructions for the creating of the connectors needed, only to find that your emails queue in your Exchange Server

The remote SMTP service does not support TLS - Microsoft Q&

There are many options being suggested such as to change the ports for the smtp server, to enable allow less secure apps option in Security settings tab etc. One solution which works, is to enable Gmail's Two step authentication for the AuthUser, generate an app specific password, and use this password as the Gmail password when setting up. If you have an on-premises non-Exchange server, application or device that relays email through your Office 365 tenant either by SMTP AUTH client submission or by using a certificate based inbound connector, make sure these servers or devices or applications support TLS 1.2. If they do not support TLS 1.2, the TLS negotiation will fail, and a. After I go to settings -> accounts and import and click add another email address under the send email as section, on the next screen I enter the email address (myname@mydomainname.com) and click next, it brings me to the next screen to configure it and auto-populates the SMTP server field with: smtp.mydomainname.com, the user name as. Re: Send Mail (SMTP) through Office 365 with MFA. Option 2 will work externally. You need to make sure your certificates for the connector contain your domain, or it will be treated as external email relaying. Option 3 is better. Option 2 is not there for allow mass marketing emails

IIS SMTP service relay to Exchang

  1. The IIS SMTP mail relay includes a built-in supports in the TLS protocol and gives that we have created all the required configuration setting that described in the article - xxx, the communication channel between the IIS SMTP mail relay and the Office 365 EOP server which represented by the host name: smtp.office365.com created
  2. Basically, Exim will deny the message if the session sends data before the SMTP banner or if remote client sends data out of sync. This is caused by Exim being more compliant to the SMTP RFC, it will drop the connection if this results. This issue has been addressed and patched by the AtMail Webmail client
  3. SMTP server cannot email outside LAN. There are a lot of variables in my question, so I'll try to be as concise as possible: Objective: To setup a local SMTP server for our other servers to connect to a local IP address to mail out. We're moving to Google Apps email, and smtp.gmail.com won't work for us for the applications we're running
  4. Select the option of SMTP Server (The reset of the installation process is just next, next, etc.) Step 2: IIS SMTP Service. By default, the IIS SMTP service is not started, and the startup type is: manual. We will need to change the default setting to - Automatic
  5. The SMTP Mail Server you specified, doesn't have a valid certificate or doesn't have a certificate at all. The certificate that the SMTP Mail Server provides to Gmail during the connection, doesn't contain the domain name, that Gmail uses to connect to the SMTP Mail Server. 7. When you see the next screen: 1

Navigating Microsoft 365 and Authenticated SMTP - Cireso

Select Manual setupor additional server types, and then click Next. Select POP or IMAP, and then click Next. Enter your name and email address, and then select POP3 for the Account Type. Enter your Incoming mail server and Outgoing mail server (SMTP) details, enter your logon information, and then click Next On that page, there is a section that talks about SSL certificates currently in use by the server (see ssl-1.png) The certificate you choose for mail must be valid (i.e. not expired) and must work for whatever server address you are going to specify for people enter enter as the SMTP server address The mail server will respond with 235 Authentication successful. Getting this far indicates that your connection to smtp.sendgrid.net over the chosen port is open and that your API key is valid. Next, add the email that you're sending from using the SMTP MAIL FROM command and press Enter Basic Authentication and Exchange Online - February 2021 Update. Feb 04 2021 09:00 AM. We previously announced we would begin to disable Basic Auth for five Exchange Online protocols in the second half of 2021. Due to the pandemic and the effect it has on priorities and work patterns, we are announcing some important changes to our plan to.

How to troubleshoot and resolve SMTP relay related error

These IMAP servers have come into existence after this Sugar code was written. As part of the automated phpunit codeception tests #3600 , you must add a live connection test to real email accounts hosted on each type of supported IMAP server. The automated test must try to connect, and fail when the connect fails Code. Description. 1. The specified client is not registered. 2. Parameter is invalid. 3. The Web service or WS scan function is disabled. 4. The device is not connected to the network The Authentication Service Extension 1. The name of this [SMTP] service extension is Authentication. 2. The EHLO keyword value associated with this extension is AUTH. 3. The AUTH EHLO keyword contains as a parameter a space-separated list of the names of available [SASL] mechanisms In addition, you can use client access filters to limit user to specific domains or IP address ranges. SMTP Authentication, or SMTP AUTH (RFC 2554) is the preferred method of providing SMTP relay server security. SMTP AUTH allows only authenticated users to send mail through the MTA. For more information, see Enabling Authenticated SMTP SMTPD(8) SMTPD(8) NAME smtpd - Postfix SMTP server SYNOPSIS smtpd [generic Postfix daemon options] sendmail -bs DESCRIPTION The SMTP server accepts network connection requests and performs zero or more SMTP transactions per connection. Each received message is piped through the cleanup daemon, and is placed into the incoming queue as one single queue file

The remote SMTP service rejected AUTH negotiation

A remote computer is the one which has no physical presence; it can be accessed only through some sort of a computer network. The Remote Host is the computer hosting the network which hosts the remote computer and the remote client is the user of the remote client on the network Setting up qmail-remote for SMTP Authentication. There are two Use Cases to consider allowing qmail-remote to support SMTP Authentication:. A local user on the system using Authentication: Since no user-interface exists to specify an userid and the uid is not available anymore for qmail-remote the authentication information needs to be bound the the sending address: 'Mail From: ' SMTP, or Simple Mail Transfer Protocol, is the service that controls how your emails move across networks. By interacting with the Mail Transfer Agent (MTA), it ensures your communications reach their intended address mySMTP is a cloud-based SMTP service. The remote SMTP service rejected AUTH negotiation Hello, We have configured SMTP. Note: Starting from v5.0beta2 SSTP does not require certificates to operate and can use any available authentication type. This feature will work only between two MikroTik routers, as it is not in accordance with Microsoft standard. Otherwise to establish secure tunnels mschap authentication and client/server certificates from the same chain should be used As shown in the diagram above, the before-queue filter sits between two Postfix SMTP server processes. The before-filter Postfix SMTP server accepts connections from the Internet and does the usual relay access control, SASL authentication, TLS negotiation, RBL lookups, rejecting non-existent sender or recipient addresses, etc

Solved: The remote SMTP service rejected AUTH negotiation

The TeamViewer remote connectivity cloud platform enables secure remote access to any device, across platforms, from anywhere, anytime.. TeamViewer connects computers, smartphones, servers, IoT devices, robots — anything — with fast, high performance connections through our global access network even in outer space or low bandwidth environments Require that a remote SMTP client introduces itself with the HELO or EHLO command before sending the MAIL command or other commands that require EHLO negotiation. smtpd_delay_reject = yes It allows Postfix to log recipient address information when rejecting a client name/address or sender address, so that it is possible to find out whose mail. Turning off EHLO on the SMTP Server. Without EHLO you also lose: NOTARY. TLS negotiation. Preemptive controls on message sizes. With EHLO, the remote SMTP client determines if you have a limit and stops trying to send a message that exceeds the limit as soon as it sees this response

stuck - the remote smtp service rejected auth negotiation

.NET Components MailBee.NET Objects .NET email components: SMTP, POP3, IMAP, Security, AntiSpam, Outlook, Address Validator, PDF MailBee.NET Queue Easy-to-use .NET service to deliver e-mails in the background: ActiveX Components MailBee Objects ActiveX email components: SMTP, POP3, IMAP, S/MIME MailBee Message Queue Queue-based background sending of email SMTP: Rebex.Net.SmtpException: An existing connection was forcibly closed by the remote host. Negotiation failed. The connection was closed by the server. Rebex.Net.Ftp Exception:An existing connection was forcibly closed by the remote host. Rebex.Net.SftpException: The connection was closed by the server Jeremy Faircloth, in Enterprise Applications Administration, 2014. Simple Mail Transfer Protocol. Many enterprise applications use SMTP for sending various emails from the application. In some cases the enterprise application will have a remote SMTP server set up and in others it will rely on a local SMTP server to accept the message and relay it to the next SMTP server in line

My understanding is that SMTP is a little different because it needs to cater for both server to server communications (servers address each other by their real names, and the self-signed certs are used for TLS) and client to server communications, as well as other scenarios like hybrid mail flow, partner connections, and so on, that all might. Remote SMTP server is sending email where in SMTP connection is providing some fake non local email address but in message content there is FROM and TO set to my client address. This scenario is producing message which is being passed to main SM server to my client mailbox which looks like it has been sent from himself to himself The access rights granted to this name on the remote server should allow your server to use the ATRN command. The CommuniGate Pro SMTP module uses the AUTH CRAM-MD5 authentication method to send passwords in an encrypted form. If the remote server does not support the CRAM-MD5 method, the clear-text AUTH LOGIN method is used negotiation method for the user and the server to negotiate changes to the terminal provided in the NVT. Typically the client and the server stays in the NVT just as long as it takes to negotiate some terminal type to be emulated. [Fei96] 1.3 Options The TELNET has a set of options and these options can be negotiated through a simpl Connection to the SMTP server failed due to no response from SMTP. This could be because a server other than the SMTP server has been specified, or the specified SMTP server port number is incorrect. Check the SMTP server name, port number, or the SMTP server port number. SMTPC: failed to connect smtp server. Connection to the SMTP server failed