Solved

IMAP issue on SBS2008 server

Posted on 2009-07-06
3
732 Views
Last Modified: 2012-06-22
Having an issue with sending e-mails via imap on an SBS 2008 server.  I can login to the account just fine (using outlook 2k7).

I get the following error message when trying to send: "send error 421 4.3.2 service not available closing transmission channel"

Outlook web access and exchange outlook clients work fine.  Imap was working fine 2 or so weeks ago.

Have tried restarting services, etc.

0
Comment
Question by:tcsnetwork
3 Comments
 
LVL 29

Expert Comment

by:Michael W
ID: 24787574
0
 
LVL 20

Expert Comment

by:EndureKona
ID: 24787600
When you attempting to send your using (generally, might be using 587 or others) port 25.   can you telnet to port 25 on the sbs server from that workstation?  

Example:

  Open the      cmd prompt.
Type      telnet server.com 25
Type HELO      server.com
Type MAIL      FROM:you@mydomain.com
You may      get a message saying "250 ok"
Type RCPT      TO:joe@somedomain.com
again, You      may get a message saying "250 ok"
To write      the message, type DATA, followed by your message.
To end the      message, put a period on a new line by itself and press Enter.
Type QUIT      to exit Telnet.
 
0
 
LVL 27

Accepted Solution

by:
shauncroucher earned 500 total points
ID: 24788196
Could be a firewall preventing SMTP connection to your Exchange server. Test with telnet and if you get this error straight away I would look for a firewall blocking the port. From the transient failure code you have given, it could well be a firewall that is causing port 25 blocking.

If not then check the settings on the Receive connector. If you are using the Default Connector, this will be listening on port 25 by default and is probably the one you are using.

Check that Exchange Users are allowed to authenticate, and that the server accepts authentication in a form the client will present to it.

Get-ReceiveConnector De* | fl Auth*,Perm* will give you a list of accepted authentication mechanisms and a list of users who can use the connector.

Make sure the email client is set to send authentication credentials to the SMTP Receive connector. If the client is sending Basic authentication, make sure the receive connector is set to allow this (perhaps without TLS if your client does not support TLS).

Shaun
0

Featured Post

Ransomware-A Revenue Bonanza for Service Providers

Ransomware – malware that gets on your customers’ computers, encrypts their data, and extorts a hefty ransom for the decryption keys – is a surging new threat.  The purpose of this eBook is to educate the reader about ransomware attacks.

Question has a verified solution.

If you are experiencing a similar issue, please ask a related question

We are happy to announce a brand new addition to our line of acclaimed email signature management products – CodeTwo Email Signatures for Office 365.
Follow this checklist to learn more about the 15 things you should never include in an email signature from personal quotes, animated gifs and out-of-date marketing content.
This tutorial will walk an individual through the steps necessary to join and promote the first Windows Server 2012 domain controller into an Active Directory environment running on Windows Server 2008. Determine the location of the FSMO roles by lo…
This tutorial will show how to configure a new Backup Exec 2012 server and move an existing database to that server with the use of the BEUtility. Install Backup Exec 2012 on the new server and apply all of the latest hotfixes and service packs. The…

920 members asked questions and received personalized solutions in the past 7 days.

Join the community of 500,000 technology professionals and ask your questions.

Join & Ask a Question

Need Help in Real-Time?

Connect with top rated Experts

13 Experts available now in Live!

Get 1:1 Help Now