Go Premium for a chance to win a PS4. Enter to Win

x
?
Solved

IMAP issue on SBS2008 server

Posted on 2009-07-06
3
Medium Priority
?
782 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 Worsham
ID: 24787574
0
 
LVL 20

Expert Comment

by:Rick Fee
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 2000 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

Efficient way to get backups off site to Azure

This user guide provides instructions on how to deploy and configure both a StoneFly Scale Out NAS Enterprise Cloud Drive virtual machine and Veeam Cloud Connect in the Microsoft Azure Cloud.

Question has a verified solution.

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

With so many activities to perform, Exchange administrators are always busy in organizations. If everything, including Exchange Servers, Outlook clients, and Office 365 accounts work without any issues, they can sit and relax. But unfortunately, it…
Stellar Exchange Toolkit: this 5 in 1 toolkit comes loaded with mega-software tool. Here’s an introduction to tools’ usage and advantages:
This video shows how to quickly and easily deploy an email signature for all users in Office 365 and prevent it from being added to replies and forwards. (the resulting signature is applied on the server level in Exchange Online) The email signat…
This video shows how to quickly and easily add an email signature for all users on Exchange 2016. The resulting signature is applied on a server level by Exchange Online. The email signature template has been downloaded from: www.mail-signatures…
Suggested Courses

885 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