Email Problem

[Marty]

I moved an account yesterday from one server to another. Now the customer, using outlook, can receive mail and can login to webmail and the control panel, but when he sends mail it rejects his password only on send. He is using the same password for pop access and smtp send access, so I am stumped. Why would it reject only when he goes to send? This not a port 25 problem, this is a failed authentication error. Neither server uses the maildir format.

 

[hicom]

1) Reset the password for start

2) did you remove the old account on the old server ? Sometimes DNS act funny, they'd be receiving POP3 from one IP and sending SMTP on another IP and accessing HTTP to one of those IPs!! Until full propogation has been made (sometimes 3 days) it is hard to tell.

3) also try to check in his SMTP Authentication that he is using the full e-mail address unless he is trying to check the default mail account

 

[Marty]

1) Reset the password for start

Did that, didn't help

2) did you remove the old account on the old server ? Sometimes DNS act funny, they'd be receiving POP3 from one IP and sending SMTP on another IP and accessing HTTP to one of those IPs!! Until full propogation has been made (sometimes 3 days) it is hard to tell.

No, it is not deleted, but the same password exists on both servers and can be used to login to webmail for that account. Only SMTP authentication fails. POP does not fail.

3) also try to check in his SMTP Authentication that he is using the full e-mail address unless he is trying to check the default mail account

He is using the cpanel username and password because it is the default account, and as I said this username and password also works for cpanel and webmail and pop access, just not for smtp sending.

I got the username and password from the client and tried it myself as well, and it does not work for smtp auth, just for pop and cpanel and webmail.

 

[hicom]

check the domain is listed in /etc/localdomains and post the full EXIM error message with the before and after line here.

 

[Marty]

check the domain is listed in /etc/localdomains and post the full EXIM error message with the before and after line here.

It is in localdomains, and here is a sample of the failures in the exim log:

2006-07-17 19:40:19 fixed_plain authenticator failed for ([192.168.1.100]) [69.21.88.85]:4504 I=[69.72.168.85]:2525: 535 Incorrect authentication data (set_id=bnewton)
2006-07-17 19:40:20 fixed_login authenticator failed for ([192.168.1.100]) [69.21.88.85]:4504 I=[69.72.168.85]:2525: 535 Incorrect authentication data (set_id=bnewton)
2006-07-17 19:40:26 fixed_plain authenticator failed for ([192.168.1.100]) [69.21.88.85]:4504 I=[69.72.168.85]:2525: 535 Incorrect authentication data (set_id=bnewton)
2006-07-17 19:40:26 fixed_login authenticator failed for ([192.168.1.100]) [69.21.88.85]:4504 I=[69.72.168.85]:2525: 535 Incorrect authentication data (set_id=bnewton)

 

[hicom]

This seems something wrong in your Exim config file, is this the only domain on the server ? Any others having issues sending/receiving ?

I'd suggest you remove any additional EXIM entries that were added, reset exim config file (remember do proper backups) and then restart exim.

Does it work if you disable SMTP authentication ?

 

[Marty]

There over 50 other accounts on the server and this is the only account having problems.

By the way, thanks for all the responses. Your questions are at least making me think. The exim config on this server is identical to the exim config on the server it was moved from.

 

[Marty]

Any other ideas anyone?

 

[nettigritty]

the same error occurs when an account is in demo mode or if the username / domain name exists in /etc/demousers and /etc/demodomains

 

[Fernis]

I am having the same email problem as stated above. The client tells me that he can receive emails, but when he sends email using outlook it errors out mentioning a demo account. How can I tell if an account is in demo mode other than looking in the /etc/demodomains & users file?

Is this a cPanel bug that creates some accounts in demo mode?

 

[Jack21]

1st : Try to delete and recreate the email settings, making sure that you are using the correct procedure.
2nd : Even if the above step fails to solve the problem, then try to disable the firewall or any antivirus which scan your outgoing emails...just for testing purposes.

Please try these steps and see if it solves your problem or not.

 

[Fernis]

Remove the account and domain from /etc/demodomains & users file fixed the problem for me.

 

[gfisch]

same problem here

I am having the same problem. Just one account on a server with 200 domains.
Just started this morning. My demodomains and demousers are blank.

2007-05-30 12:02:04 fixed_login authenticator failed for ([192.168.1.100]) [63.250.114.248]:54618 I=[69.90.92.10]:25: 535 Incorrect authentication data ([email protected])

 

[cybra]

Same issue

I am having the same problem - There is only one domain on my server, and only one user cannot send mail (receives mail fine). I have the same error in my exim_rejectlog:

fixed_login authenticator failed for (XXX) [xx.xx.xx.xx]: 535 Incorrect authentication data ([email protected])

I made sure demo mode was disabled, demousers and demodomains are blank, and when I try this email account from home using Thunderbird I can connect and send fine. I can NOT send mail with this one account using either Outlook or Outlook Express. I've reset the password, changed the password, deleted and recreated the email account, etc.

Is there ANYTHING else I can check?

Thanks!

Angela

 

[4u123]

Having this same problem.

Moved accounts to a new server - just one domain cant send mail, it keeps asking for the username and password. The same issue happens for newly created email accounts on their domain. it isnt in demousers or demodomains and is in localdomains.

so bumpety bump!

 

[nettigritty]

Having this same problem.

Moved accounts to a new server - just one domain cant send mail, it keeps asking for the username and password. The same issue happens for newly created email accounts on their domain. it isnt in demousers or demodomains and is in localdomains.

so bumpety bump!

try a /scripts/upcp --force