• Introducing WebPros Cloud - a fully managed infrastructure platform purpose-built to simplify the deployment of WebPros products !  WebPros Cloud enables you to easily deliver WebPros solutions — without the complexity of managing the infrastructure.
    Join the pilot program today!
  • Support for BIND DNS has been removed from Plesk for Windows due to security and maintenance risks.
    If a Plesk for Windows server is still using BIND, the upgrade to Plesk Obsidian 18.0.70 will be unavailable until the administrator switches the DNS server to Microsoft DNS.

Plesk Refuses Mail from authenticated users ESMTP

M

marco114

Guest
I have a new problem all of the sudden and I am not sure why it happened but when my users on my server send WITH Authentication the server is refusing mail and without it will work (if the POP option is on)..

Is there something I can check why?

In the logs it says something about relay lock but that seems generic.

Maybe it got confused who could and can't send mail.

Is anyone willing to help me real quick?

AIM: mrmacnut

thanks
marc


update: log file:

/usr/local/psa/var/log/maillog:

ep 21 16:37:16 sh1 relaylock: /var/qmail/bin/relaylock: mail from xxx.xxx.xxx.xxx (userhostname.com)

update:
I stopped qmail & xinetd
I backed up the qmail queues
I forced qmail to rebuild using the

rpm -Uvh --force psa-qmail....

still not working..

any other ideas?
 
SOLUTION.

My solution is fixed for now, here is what to do:
TURN OFF POP LOCK TIME and force all users to use SMTP Authentication.

The problem if you care, I think this is a bug or procedural problem, and I've searched and a lot of people have this issue.

I attemtped to explain this issue to SWSoft Support but they didn't understand why this could be an issue.

Under the conditions:

MAIL SERVER Settings:
POP3 Lock Time is ON (set to 120 minutes)
and SMTP Auth is ON

Perform these steps:

1. Login and CHECK mail with POP3 (you will then be authorized to send mail without Password)
2. Create new message and send WITH SMTP authentication ON in email client.

The server will reply with this error: (DOMAIN has substituted the real domain).

$ telnet mail.DOMAIN.com 25
Trying 64.100.100.100...
Connected to mail.DOMAIN.com.
Escape character is '^]'.
220 mail.DOMAIN.com ESMTP
auth login
503 you are already authenticated <<- this is a major problem!

If a user is already authenticated with POP3 Lock time, and then attempts to use SMTP Authentication method like all customers are TOLD to do.. qmail gives an error. Since MOST of my clients use this method (SMTP), and then I turned ON POP 3 lock time to help out customers who always forget to set the method of SMTP Auth, this started happening.

When POP3 lock time is on and user checks mail (POP Mail), the server authenticates them for the lock period so they can relay without SMTP authentication. However, then they try using the SMTP Auth Method, the email client throws an error.

In my opinion, even if the user IS authenticated with POP3 lock time, they should still be allowed to use SMTP with the password and Qmail should ignore the POP3 lock. The behavior inherently causes problems. In fact, if you have POP3 Lock Time checked, you're simply asking for problems.

Since most users end up being authenticated with POP3 lock time, any user that has SMTP Auth really can never send.

Thanks
Marc Pope
Falcon Internet
 
Back
Top