• If you are still using CentOS 7.9, it's time to convert to Alma 8 with the free centos2alma tool by Plesk or Plesk Migrator. Please let us know your experiences or concerns in this thread:
    CentOS2Alma discussion

503 This mail server requires authentication. Please check your mail client settings

B

bizness

Guest
I have tried practically everything but pulling my hair out... which is coming up very soon.

problem is as follows... clients can recieve emails, clients cant send email... when they try and send email, no matter if they have the "my outgoing requires auth...." checked on or off, the result is still the same.....

result:
503 This mail server requires authentication. Please check your mail client settings

some Mailenable logs show as follows.

Relay Denied: Failed to meet all relay criteria.

Though as stated before, the "my server requi...." is checked on correctly....

i setup the same test email on outlook express within the server and tried sending out a email.... relaying went through fine... so problem lies with incoming smtp connections are dropped....

here is a manual smtp test by telneting to the server on port 25....

220 domain.com ESMTP MailEnable Service, Version: 1.73-- ready at 08/04/04 00:35
:47
HELO domain.com
250 Requested mail action okay, completed
MAIL FROM: [email protected]
250 Requested mail action okay, completed
RCPT TO: [email protected]
503 This mail server requires authentication. Please check your mail client settings.
 
In Outlook go to view/change your Email account, click the "More Settings..." button, this is the label for the button on Outlook 2002.

Go to the Outgoing Server tab

Make sure you select
- my outgoing server (SMTP) requieres autentication

Then select radio button
- Use same settings as my incoming mail server....

That should solve your problem... sending email with outlook
 
Thanks for the reply.

Please read the post again and then repost...

As you can see i am going nuts over this problem....

If you check the original post, you will see that it doesnt matter if the outlook or any other email client has authentication turned on or not it still gives the same result.

I use to work as a level 2 tech for Dialtone internet (now, interland) .... I have experience with plesk since version 2.0 came out. Im normally pretty good at catching things because of my experience with 1000's of servers running plesk, however, this is the first plesk server that i have running on windows.

However, as always, any help will be appreciated.
 
I had a similar problem with some domains or email accounts when I was trying to send eMail besides the SMTP authentication on the outlook client, I noticed in mailenable for some reason the domains post office or email accounts were disable....

In C:\Program Files\SWsoft\Plesk\Mail Enable\Bin or you installation path; open MailEnable.msc

Check that all of your Post Offices are enable and also Mailboxes in that domain... I noticed in my case that was reason of the 503 Error... Hopefully this help you out. Good Luck
 
I do not have this problem with my default domain, however, with any additional domain, I have the same problem as above. I have checked "Require SMTP authorization" and made sure to have "use same as login" in both Outlook Express and Microsoft Outlook 2003.
Also, sending email internally doesn't seem to be a problem.
Perhaps there is a bug somewhere??
If only Plesk Tech Support would chime in here!! :(
 
I think I found the problem.
If you go in the MailEnable MMC > Servers > Connectors, right click on the SMTP connector and click on Properties, click the Relay TAB and uncheck Allow Relay for Privileged IP ranges, or add the IP's you want to enable to relay. I disabled it, and it works fine now.

Hope this helps.
-d
 
To solve this SMTP send problem just go to:

Mailenable Administration section> Connectors>SMTP>Relay and just be sure that the "Allow relay for authenticated senders is checked. This will solve the send problem. Just restart SMTP services and you are ready to go:)

Hope this works for all of you.

Regards,
Henry
 
enable authentication for users on the system was checked... the problem lies that for some reason, Mail enable can not read the users at hand.
 
Uncheck the authentication. Apply the change. Go back recheck it. Apply. Restart.

That will fix the problem.
 
Working form me doing this also, Plesk must take note about this for default installations.
 
Originally posted by dennysp
I think I found the problem.
If you go in the MailEnable MMC > Servers > Connectors, right click on the SMTP connector and click on Properties, click the Relay TAB and uncheck Allow Relay for Privileged IP ranges, or add the IP's you want to enable to relay. I disabled it, and it works fine now.

Hope this helps.
-d

Problem solved, Thanks
 
set the defaults to "****"

thank you -- oh, dilligent plesk warriors! you saved the day again. :D

y'know... i'm growing weary of these plesk "default" nightmares. i mean -- I LOVE the features Plesk offers, but... the problems i've encountered with compatability and functionality on windows and now these "default" problems are driving me batty!

in this case -- i understand why you would want to disable relaying by default, but restricting it to IP's??? C'MON! my other major gripe is that i couldn't find this ANYWHERE in the documentation - what's up with that? seems like there should be a HUGE note telling you -- YES, not only is relay disabled by default, but it is also restricted to IP's...

well, guess i'll see you at the next "default" disaster. :p

..k..
 
Originally posted by dennysp
I think I found the problem.
If you go in the MailEnable MMC > Servers > Connectors, right click on the SMTP connector and click on Properties, click the Relay TAB and uncheck Allow Relay for Privileged IP ranges, or add the IP's you want to enable to relay. I disabled it, and it works fine now.

Hope this helps.
-d

If you do this you wont be able to make your servers scripts or components like ASPMAIL send email.

And what's up with some ppl disabling the authentication, wont this make the server open to spammers to use.

I did a complete server reload last week and after that i can send email fine with both "Allow Relay for Privileged IP ranges" and "Authentication" Enabled

-Andres Tinoco
 
this killed my webmails SMTP!

If you do this you wont be able to make your servers scripts or components like ASPMAIL send email.

*good point*, Andres.

And actually, now that you mentioned it, there were also some other problems associated with disabling this option -- I had some clients complaining that could no longer send outbound email via webmail shortly after I made the suggested change.

It seems that by disabling the Privelaged IP ranges, it killed my users ability to send SMTP via webmail -- very strange.

I was able to resolve the problem by re-checking the box for Allow Privelaged IP's and then starting and stopping the SMTP service.

I was concerned that this would again bring up the same problem I was having with Outlook users, but so far all of my test emails have been able to get out.

Its only been about 15 minutes... fingers crossed that it doesn't start tripping out again over the weekend. ;)
 
I tried all the thing but same problem again,
I can solve this problem after checking "Allow relay for local sender addresses". I know it is a big hole for spammers...
 
Back
Top