Unable to setup IMAP account in outlook 2013

Question asked by Jon Eastwood - 4/1/2015 at 2:12 AM

Unanswered

I have a client who reported they were unable to setup an IMAP account on outlook 2013.

It gets as far as doing a connection test. The incoming test completes ok but the outgoing fails with the following message

"Send test email message: cannot send the message. Verify the email address in your account properties. The server responded: 544 sending address not accepted due to spam filter."

Outlook won't let them disable the "test settings" checkbox so they can't create the account.

Both incoming and outgoing servers are correct as they can log into webnmail

If they turn on authentication for outgoing mail it just keeps asking for the password.

Any advice?

They tried the same for POP3 and it worked fine?

What are they doing wrong or what is wrong with my server IMAP settings

6 Replies

Reply to Thread

Employee Replied

4/1/2015 at 8:39 AM

Employee Post

Jon, can you verify that the following option is unchecked under SystemAdmin | Protocol Settings | SMTP In | "Disable AUTH LOGIN method for SMTP authenication". Also, are you able to telnet using the user's credentials?

Jon Eastwood Replied

4/1/2015 at 8:47 AM

yes that is unchecked, could you let me know what the user would need to do for telnet, what the commands would be please?

Employee Replied

4/1/2015 at 8:53 AM

Employee Post

Use "telnet [server address] 25". After the SMTP welcome message type "EHLO". You should see a Hello message, size, the "AUTH LOGIN CRAM-MD5", "8BITMIME", "OK", etc. Make sure the CRAM-MD5 has "AUTH LOGIN" present before it. I'm assuming since you have the checkbox unchecked, it should show properly.

CCWH Replied

4/1/2015 at 2:56 PM

This could be that they are not selecting My Server requires Outgoing Authentication.

Scarab Replied

4/1/2015 at 5:02 PM

I suspect that the "sending address not accepted due to spam filter" is the biggest clue as to the problem. On your Smartermail Server go to SECURITY > ADVANCED SETTINGS > SMTP BLOCKING. It sounds like you have an address (or wildcard address) that is configured that is blocking that particular user from sending.

For example, we accidentally blocked a sender named specialist@domain.tld because we had a wildcard address of *cialis*@* to block male-enhancement spam.

Pro-tip The easiest way to find a SMTP Blocked wildcard address is to search (F7) for just a few letters in the first part of their email address.

Jon Eastwood Replied

4/2/2015 at 5:34 AM

thanks for all the help and advice

Fix was much simpler :-0

Users password had been blocked for SMTP as it violated the password compliance riles so the server blocked them for SMTP outbound email

Back to Community Threads

Please leave this box unchecked

6 Replies

Reply to Thread

Tags

Related Knowledge Base Articles