PDA

View Full Version : Email problems after 8.4.0 update


fdoibz
5th May 2008, 11:55 AM
After 8.4.0 update all domain's email accounts are not working.
I've tried mchk with no success, also reinstalling 8.3.0 qmail and courier-imap RPMs.
Nothing seems to work, any ideas?

websitesource
5th May 2008, 12:59 PM
We've been having this same problem on our servers since upgrading over the weekend. I have narrowed it down to the fact that the servers are ONLY accepting full email address authentication, and not username authentication. I have double checked all our settings and the control panel indicates that it should be configured for both types of authentication. It looks like the setting just isn't getting properly applied in the configuration somewhere.

Peace,
Kelly Shutt
Alentus

fdoibz
5th May 2008, 01:12 PM
Thanks for your comments!

One question,
Does your poppasswd keeps blank after mchk? because mine is staying blank.
I have enabled Only use of full POP3/IMAP mail accounts names.
Have you tried anything else?

sidhe
5th May 2008, 01:26 PM
I have the same problem. Smtp authentication is accepting only full email addresses as login. Second issue that I have noticed is that when I switch on the message submission and configure Thunderbird for port 587 it does not work with SSL only with TLS, but maybe this issue concerns the client not the server ...

Brujo
5th May 2008, 01:51 PM
@websitesource

just one question did you switched the function from full/short to full only accepted with OK and then back to use full & short again ?

I had a simmilar issue with the RBL Blacklists, it was enabled in Plesk, but not knwon in the config files after switch on/off it comes back to normal behavior and works as expected...

sidhe
5th May 2008, 01:58 PM
I've tried switching it off and on again just a minute ago, but it doesn't work :(

Brujo
5th May 2008, 02:00 PM
@sidhe
as i remember thats "normal" that submission works only with TLS and it has nothing to do with 8.4

Brujo

sidhe
5th May 2008, 02:06 PM
Oh, ok thnx, I didn't know that ... still short usernames are not working :/

websitesource
5th May 2008, 03:39 PM
Yes, I did try switching the authentication settings but it had no effect. Yes, the poppasswd file is blank, even after running mchk. I think maybe something in the new version isn't updating the config files correctly.

Peace,
Kelly Shutt
Alentus

matrujillo
5th May 2008, 04:53 PM
some idea to solve this issue ? :S

matrujillo
5th May 2008, 08:22 PM
ok i am still doing tests on my server, does somebody has another port open besides the 25 port for smtp ?

I have another port open (26) and it does not work on this one only. Can anybody hlp me please....?

fdoibz
5th May 2008, 08:32 PM
Parallels support solved my issue reinstalling some base and qmail RPMs that didn't upgrade well. I'm not really sure how, but my e-mail service is back online now.

matrujillo
5th May 2008, 08:49 PM
Ok I solve my problem, in plesk 8.4.0 add a new line on

/etc/xinetd.d/smtp_psa

env = SMTPAUTH=1 SHORTNAMES=1

On the config of my other port, I add the new line to fix it.

buttter
5th May 2008, 09:53 PM
Well, same problem, upgraded to 8.4 and now some of my client canīt send by SMTP (587), error 553...

As well the updater doesnīt show any upgrade or info.

Any fix?

When I was updating to 8.4, I needed to update about 3 times the spamassasin module, I dont know why it appears again and again.. and then no update, and no SMTP working well.

I got the same lines as Trujillo added before, and still the same error 553... help!

dellison1226
6th May 2008, 12:16 AM
I am also having the same problems. Unable to login using Horde webmail and pop accounts. Also unable to create test account and login. Regardless I get the login failed page or username and password incorrect for pop accounts.

I have also tried the command /usr/local/psa/admin/bin/mchk -v with no success. Domains work fine except email. Please help!

Thank you,
David

Geoff Riley
6th May 2008, 04:02 AM
I managed to get almost everything working with emails after a traumatic Saturday, but I've not real idea as to which of the atempts at repair actually did the trick: I re-applied various RPMs over and over.

For a long time I was getting the dreaded wrong user in the queue problem that I managed to sort out with a cronjob doing a chown -R every couple of minutes.

SpamAssassin is resolutely not working though and so I'm drowning in spam again... I'm going to attempt to get greylisting back running today to get at least that 'protection' back on line.

This is proving very frustrating: particularly when there doesn't seem to be any indication as to why 8.4 was pulled off... I only did the upgrade because I was sick of being constantly told that there were 'new' updates for 8.3 but on arriving at the updater finding nothing to be updated. Really regretting that decision now. :(

rogerp
7th May 2008, 03:55 PM
Our site got upgraded to 8.4 today (we're still looking into exactly how this happened) and we're experiencing the same Horde and pop mail problems mentioned earlier. Can anyone offer any guidance on how to proceed (i.e. fix it or maybe rollback)? Unfortunately you are talking to an applications guy here; our web guru is on extended leave and checking in intermittently. It may be that he did the upgrade but we can't contact him via email as it's broken! What a fabulous pickle.

Thanks

Roger

dzappone
8th May 2008, 12:32 AM
I've got the same problems - no one can send or receive email on my server. I've got a half dozen clients that are very irritated right now. This is a major bug with 8.4 in my opinion. Considering that in the forums this is the issue with the most posts and view I'd view it as the biggest issue with 8.4.

I updated because of the enhanced spam protection that was being offered - but I think not being able to get email is a bit excessive as far as spam reduction goes. ;-)

Can we get please get a response from Parallels about this? Is this issue being addressed? Please help!

For what it's worth I'm running Plesk on Ubuntu 7.10.

tavhane
8th May 2008, 12:48 AM
Yes, this problem major bug. Please fix parallels. My server Plesk on Ubuntu 7.10

SliderMKH6
8th May 2008, 06:30 AM
I got the same Problem with an RedHat5 System and Plesk8.4!

eilko
8th May 2008, 06:49 AM
Do these problems occure with the Plesk version that was pulled or with the Plesk 8.4.0 for Linux/Unix build 84080425.19 release that is available now at http://download1.parallels.com/Plesk/Plesk8.4/plesk-8.4.0-for-rpm-based-os.html ?

SliderMKH6
8th May 2008, 06:53 AM
v8.4.0_build84080425.19 I cant send E-Mail or get E-Mail. That dont work!

rogerp
8th May 2008, 07:34 AM
Our problems are with 8.4.0-ubuntu7.10.build84080425.19

SliderMKH6
8th May 2008, 08:13 AM
Red Hat 5

v8.4.0_build84080425.19

I can't send email or receive ... dont work for me! please fix it now!!!

dzappone
8th May 2008, 08:53 AM
For me it was the pulled version when I ran the upgrade.

Plesk Control Panel version: psa v8.4.0_build84080425.19 os_Ubuntu 7.10
Operating system: Linux 2.6.22-14-server

tavhane
8th May 2008, 09:15 AM
8.4.0-ubuntu7.10.build84080425.19

SliderMKH6
8th May 2008, 09:20 AM
In Plesk 8.3 the Mail System was running perfect but now i cant send or get new mails. He do nothing. All is running!

Red Hat 5 ... v8.4.0_build84080425.19

Parallels PLEASE ANSWER what is the Problem!!!!! and answer on my Mails!!!!!!

dzappone
8th May 2008, 10:09 AM
I think we'd all like to know the answer to that. Of course Plesk support seems to be notorius for not responding on the forums. One wonders if they have even read this. Maybe I'll call them today. I'd be happy to work with Parallels on this to provide technical details of what is going on, as anyone here would as well, I imagine.

dzappone
8th May 2008, 01:46 PM
By the way I don't know what errors others are getting but when I hit the pop server using Evolution from the server itself I get the following:

Error sending password: -ERR Login failed

And for SMTP I get:

Bad authentication response from server

Using Thunderbird from the server I get:

POP: Sending of password did not succeed. Mail server mail.mydomain.com responded: Login failed.

SMTP: Sending of message failed. (Plus a bunch more text going on about how the SMTP server isn't responding properly, etc.)

And telneting yields the following.

telnet localhost 110
Trying 127.0.0.1...
Connected to ip6-localhost.
Escape character is '^]'.
+OK Hello there. <26808.1210266129@localhost.localdomain>
user username@mydomain.com
+OK Password required.
pass ********
-ERR Login failed.
^]

And for what its worth I tried mchk, and reinstalling psa-qmail, psa-qmail-rblsmtpd, psa-courier-imap with no change in behaviour. And of course the poppasswd file is empty which, not having worked with it I don't know that it should have anything it it but it sure seems like it is supposed to.

IMAP doesn't work either.

martijnbakker
8th May 2008, 02:04 PM
Also problems here, when i use -Rt0 its gives the error.

rying 127.0.0.1...
Connected to localhost.
Escape character is '^]'.
/usr/bin/env: invalid option -- R
Try `/usr/bin/env --help' for more information.

This error occurs right after the update. When i remove the option, its working. But i need that option :)

martijnbakker
8th May 2008, 04:00 PM
Ok -Rt0 doenst work anymore, but --Rt0 does for me.

SliderMKH6
8th May 2008, 04:24 PM
Red Hat 5

Maillog


May 8 22:12:02 km11223 qmail-queue-handlers[3469]: Handlers Filter before-queue for qmail started ...
May 8 22:12:02 km11223 qmail-queue-handlers[3469]: from=#@[]
May 8 22:12:02 km11223 qmail-queue-handlers[3469]: to=postmaster@xxx.de
May 8 22:12:02 km11223 qmail-queue-handlers[3469]: hook_dir = '/var/qmail//handlers/before-queue'
May 8 22:12:02 km11223 qmail-queue-handlers[3469]: recipient[3] = 'postmaster@xxx.de'
May 8 22:12:02 km11223 qmail-queue-handlers[3469]: handlers dir = '/var/qmail//handlers/before-queue/recipient/postmaster@xxx.de'
May 8 22:12:02 km11223 qmail-queue-handlers[3469]: starter: submitter[3470] exited normally
May 8 22:12:02 km11223 qmail: 1210277522.089271 bounce msg 14747128 qp 3469
May 8 22:12:02 km11223 qmail: 1210277522.089403 end msg 14747128
May 8 22:12:02 km11223 qmail: 1210277522.089874 new msg 14747124
May 8 22:12:02 km11223 qmail: 1210277522.090070 info msg 14747124: bytes 1996 from <#@[]> qp 3470 uid 2522
May 8 22:12:02 km11223 qmail: 1210277522.094335 starting delivery 30: msg 14747124 to local 1-postmaster@xxx.de
May 8 22:12:02 km11223 qmail: 1210277522.094495 status: local 1/10 remote 0/20
May 8 22:12:02 km11223 qmail: 1210277522.094769 new msg 14747127
May 8 22:12:02 km11223 qmail: 1210277522.094966 info msg 14747127: bytes 1994 from <#@[]> qp 3468 uid 2522
May 8 22:12:02 km11223 qmail-local-handlers[3471]: Handlers Filter before-local for qmail started ...
May 8 22:12:02 km11223 qmail-local-handlers[3471]: from=#@[]
May 8 22:12:02 km11223 qmail-local-handlers[3471]: to=postmaster@xxx.de
May 8 22:12:02 km11223 qmail: 1210277522.099930 starting delivery 31: msg 14747127 to local 1-postmaster@xxx.de
May 8 22:12:02 km11223 qmail: 1210277522.100089 status: local 2/10 remote 0/20
May 8 22:12:02 km11223 qmail-local-handlers[3471]: cannot reinject message to 'postmaster@xxx.de'
May 8 22:12:02 km11223 qmail-local-handlers[3474]: Handlers Filter before-local for qmail started ...
May 8 22:12:02 km11223 qmail: 1210277522.104297 delivery 30: failure: This_address_no_longer_accepts_mail./
May 8 22:12:02 km11223 qmail: 1210277522.104563 status: local 1/10 remote 0/20
May 8 22:12:02 km11223 qmail: 1210277522.104689 triple bounce: discarding bounce/14747124
May 8 22:12:02 km11223 qmail: 1210277522.104819 end msg 14747124
May 8 22:12:02 km11223 qmail-local-handlers[3474]: from=#@[]
May 8 22:12:02 km11223 qmail-local-handlers[3474]: to=postmaster@xxx.de
May 8 22:12:02 km11223 qmail-local-handlers[3474]: cannot reinject message to 'postmaster@xxx.de'
May 8 22:12:02 km11223 qmail: 1210277522.111961 delivery 31: failure: This_address_no_longer_accepts_mail./
May 8 22:12:02 km11223 qmail: 1210277522.112255 status: local 0/10 remote 0/20
May 8 22:12:02 km11223 qmail: 1210277522.112384 triple bounce: discarding bounce/14747127
May 8 22:12:02 km11223 qmail: 1210277522.112505 end msg 14747127


Problem: E-Mails sending and receiving don't work!

Solution: unknown!

martijnbakker
8th May 2008, 04:46 PM
Whats in the log files about delivering mail to others than the postmaster? I got the same messages, but thats because i dont have a postmaster account. Whats the error for sending mail ?

dzappone
8th May 2008, 05:57 PM
I filtered the maillog for "pop" and got a whole lotta this:


May 8 15:02:18 <servername> pop3d: Connection, ip=[72.XX.XX.XXX]
May 8 15:02:23 <servername> pop3d: IMAP connect from @ [72.XX.XX.XXX]ERR: LOGIN FAILED, ip=[72.XX.XX.XXX]
May 8 15:02:38 <servername> pop3d: IMAP connect from @ [72.XX.XX.XXX]ERR: LOGIN FAILED, ip=[72.XX.XX.XXX]
May 8 15:02:43 <servername> pop3d: IMAP connect from @ [72.XX.XX.XXX]ERR: LOGIN FAILED, ip=[72.XX.XX.XXX]
May 8 15:02:48 <servername> pop3d: IMAP connect from @ [72.XX.XX.XXX]ERR: LOGIN FAILED, ip=[72.XX.XX.XXX]


and these:


May 8 15:03:16 <servername> spamd[5653]: auto-whitelist: open of auto-whitelist file failed: locker: safe_lock: cannot create tmp lockfile /var/qmail/popuser/.spamassassin/auto-whitelist.lock.$


With <servername> being my servername and the ip address being the ip address I was connecting from.

DCoats
8th May 2008, 06:53 PM
I'm getting
IMAP connect from @ [x.x.x.x]checkmailpasswd: unable to open mail authentication database: No such file or directory

who knows where the database is specified?

dzappone
8th May 2008, 07:45 PM
It should be /var/qmail/users/cdb.

Which is the qmail user database containing salted md5 encrypted passwords. Then there's the poppasswd which I believe should be empty and is where the account info goes temporarily until compiled into cdb. More or less.

DCoats
8th May 2008, 09:56 PM
thanks, but on freebsd its /usr/local/psa/qmail/users/cdb and my question was really where is that path specified, because it obviously does exist, something calling the wrong path.

insanetwork
8th May 2008, 11:33 PM
Insanetwork.NET
www.insanetwork.net

i modify in the /etc/services


comment the port submission 587 tcp and udp , and the port 25 or 26 use change service smtp to submission and alias change mail to msa , note only use one port for use submission service and now working protect mail and yo port select.

dzappone
9th May 2008, 12:37 AM
I don't think that really addresses the issue at hand. Unless I'm missing something entirely. It seems the problem is not the ports but rather the fact that password are being rejected. The poppaswd which the courier-imap service is configured to use is empty. Hence no one is able to authenticate their logins and send or recieve email.

Also when I run /usr/local/psa/admin/bin/mchk -v (any options actually) I get the following about 5 times

mchk: Maildir subfolder 'cur' stat failed
System error 5: Input/output error

cgavage
9th May 2008, 03:26 AM
Same problem... under ubuntu... Seems to be related to auth_psa module for courier...

cgavage
9th May 2008, 06:14 AM
It's our first major issue with Plesk product, but I'm really disappointed to see the no-reactivity. I submitted the bug on the bugreport system, by support form, and on all available emails ;)

No reactivity, no automatic reply... really bad conclusion for me about a commercial product.

akxak
9th May 2008, 06:44 AM
One solution... as swsoft obvious and as usual does NOT respond:

I restored

/usr/lib/courier-imap/authlib/authpsa

from my backup (plesk 8.3.0). which has here (Suse 10.1) 80160 bytes instead of 37736 of the new version and the IMAP/POP3 problem is gone.

Either the database update failed during the upgrade for which I have indication or the new authpsa is as such broken.

At least IMAP works again.

This does NOT solve the problem with SMTP-authentication which remains broken here as well as the Plesk Control Panel not working at all.

cgavage
9th May 2008, 07:03 AM
Tested with backup of previous release (ubuntu), not working :(

dzappone
9th May 2008, 09:41 AM
Same here. I also was looking through the pop3d.rc and imapd.rc files and noticed that they point to authdaemond which they startup and which doesn't seem to exist.

DCoats
9th May 2008, 09:47 AM
I finally got it working after checking /var/db/pkg/ for all psa relevent packages, found some still at 8.3, after insuring all plesk packages were 8.4 versions and restarting psa, my mail functions work properly.

Rimheden
9th May 2008, 10:35 AM
Plesk 8.4.0 writes to the wrong path when it changes this configuration option: /usr/lib/courier-imap/etc/courier-imap, but the real configuration files are located in /etc/courier-imap (at least on our system).

To fix this problem manually, edit /etc/courier-imap/pop3d and /etc/courier-imap/pop3d and add the following line to the bottom of the files:

SHORTNAMES=1

Then restart courier-imap to get your short usernames working again.

martijnbakker
9th May 2008, 11:31 AM
Ok -Rt0 doenst work anymore, but --Rt0 does for me.

Ok, it works, but give not any functionality, someone know how to fix this ? Sending mail via qmail smtp is very very slow with connecting.

dzappone
9th May 2008, 02:21 PM
Would it be asking to much for some sort of reply to this issue? Is it even being looked into? Do you like having customers? It really shouldn't take this long to get a response and I'll be damned if I'm going to pay $150.00/hour for support for a software bug that was introduced in an upgrade. What's going on? Anyone? Anyone? Bueller? Anyone?

Please note that while I am serious about wanting some sort of response this post should not be construed as angry or threatening in any way. I am however trying to get your attention. It's been five business days since the first post and I think we'd all like to know if there is some progress being made here. I don't know if the problem is in the upgraded software or the upgrade process itself but I do believe the onus is on Parallels to address the issue whether by a new patch or a solution.

I think it's pretty clear here that we have tried pretty much everything we can and to no effect. I also understand that at least one person here submitted a bug report. I would to but I can't seem to locate a bug submission form.

robharris
9th May 2008, 02:30 PM
Plesk 8.4 writes to the wrong file. It writes the configuration to /usr/lib/courier-imap/etc/courier-imap
but the real configuration files are located in /etc/courier-imap

Switch on the short usernames setting in Plesk, check what changed in the files in the incorrect path and find that it simply adds a line:

SHORTNAME=1

to the bottom of the file. Then apply this to the real configuration files, restart the mail server and now it works.

Rob Harris
http://ashopcart.com
http://ashopsoftware.com
http://ashopwebhosting.com

martijnbakker
9th May 2008, 02:41 PM
Would it be asking to much for some sort of reply to this issue? Is it even being looked into? Do you like having customers? It really shouldn't take this long to get a response and I'll be damned if I'm going to pay $150.00/hour for support for a software bug that was introduced in an upgrade. What's going on? Anyone? Anyone? Bueller? Anyone?

Please note that while I am serious about wanting some sort of response this post should not be construed as angry or threatening in any way. I am however trying to get your attention. It's been five business days since the first post and I think we'd all like to know if there is some progress being made here. I don't know if the problem is in the upgraded software or the upgrade process itself but I do believe the onus is on Parallels to address the issue whether by a new patch or a solution.

I think it's pretty clear here that we have tried pretty much everything we can and to no effect. I also understand that at least one person here submitted a bug report. I would to but I can't seem to locate a bug submission form.

Already tried to get back to 8.3? I think thats a solution while there's no new update from Parralels.

SliderMKH6
9th May 2008, 02:57 PM
Plesk 8.4 writes to the wrong file. It writes the configuration to /usr/lib/courier-imap/etc/courier-imap
but the real configuration files are located in /etc/courier-imap

Switch on the short usernames setting in Plesk, check what changed in the files in the incorrect path and find that it simply adds a line:

SHORTNAME=1

to the bottom of the file. Then apply this to the real configuration files, restart the mail server and now it works.

Rob Harris
http://ashopcart.com
http://ashopsoftware.com
http://ashopwebhosting.com


yes and E-Mail Forwarding dont work :P or? Because i have send a mail to my box but he dont forward it but in horde i can see the mail lol :P

dzappone
9th May 2008, 03:02 PM
Already tried to get back to 8.3? I think thats a solution while there's no new update from Parralels.

It would be a solution if I had a backup from the past month that wasn't corrupt.

I'm guessing the autoinstaller would possibly allow one to install version 8.3 instead but I'm hesitant to try that.

I guess I'll back up all the sites and setting and reinstall 8.3 if that's the case. But Parallels should really at least let us know they are aware of the problem.

martijnbakker
9th May 2008, 05:47 PM
Yeah, your right about it, but make backup of your /etc/ vhosts qmail and mysql ? And then remove completly psa ? Dunnow what system you have installed it on ?

In debian you can change in the sources.list of apt the version to 8.3 and then update and install.

Shephard
9th May 2008, 07:46 PM
Sorry for the offtopic here, but may someone of you have a look at my issue? http://forum.swsoft.com/showthread.php?t=52731 Thanks and sorry again

paco68
10th May 2008, 09:02 AM
Plesk 8.4.0 writes to the wrong path when it changes this configuration option: /usr/lib/courier-imap/etc/courier-imap, but the real configuration files are located in /etc/courier-imap (at least on our system).

To fix this problem manually, edit /etc/courier-imap/pop3d and /etc/courier-imap/pop3d and add the following line to the bottom of the files:

SHORTNAMES=1

Then restart courier-imap to get your short usernames working again.

I restarted my VPS from Virtuozzo and now it's OK !!!

sergius
10th May 2008, 10:29 AM
After 8.4.0 update all domain's email accounts are not working.
I've tried mchk with no success, also reinstalling 8.3.0 qmail and courier-imap RPMs.
Nothing seems to work, any ideas?

Hello fdoibz,

Thank you for the report.
Please try to run mchk tool w/ option v

mchk -v

dzappone
10th May 2008, 11:21 AM
Hello fdoibz,

Thank you for the report.
Please try to run mchk tool w/ option v

mchk -v

I don't know about fdoibz but when I run mchk -v it gives me error messages and doesn't help at all. There error messages are:

mchk: Maildir subfolder 'cur' stat failed
System error 5: Input/output error

Although the first time I ran it there were no error messages but it didn't fix the problem.

I've also tried reinstalling the psa-qmail and psa-courier-imap packages using apt. Switching from full mail names to both short and full mail names and back.

I've tried turning off every extra mail option there is - anti-virus, spam, etc in the event one of them was interfering.

I've looked through every configuration file I could find related to email for anything that looked out of place - based on research in these forums for similar issues - everything seems to pointing in to the correct files and locations. The pop3d and imapd files both point to /etc/qmail/users/poppasswd for the location of passwords - the file is empty (which seems to be the problem) and mchk -v doesn't fix it.

This is using psa v8.4.0_build84080425.19 os_Ubuntu 7.10

The problems remains:

1. Can't check email via pop: -ERR login failed.
2. Can't check email via imap: a001 NO Login failed.
3. Can't send email via SMTP: 535 auth failure.

Email seems to be recieved from remote servers.

Please help.

Much thanks in adavance.

dzappone
10th May 2008, 12:08 PM
I forgot to mention that the mail log is full of errors like these:

May 8 15:02:18 <servername> pop3d: Connection, ip=[72.XX.XX.XXX]
May 8 15:02:23 <servername> pop3d: IMAP connect from @ [72.XX.XX.XXX]ERR: LOGIN FAILED, ip=[72.XX.XX.XXX]
May 8 15:02:38 <servername> pop3d: IMAP connect from @ [72.XX.XX.XXX]ERR: LOGIN FAILED, ip=[72.XX.XX.XXX]
May 8 15:02:43 <servername> pop3d: IMAP connect from @ [72.XX.XX.XXX]ERR: LOGIN FAILED, ip=[72.XX.XX.XXX]
May 8 15:02:48 <servername> pop3d: IMAP connect from @ [72.XX.XX.XXX]ERR: LOGIN FAILED, ip=[72.XX.XX.XXX]

and these

May 8 15:03:16 <servername> spamd[5653]: auto-whitelist: open of auto-whitelist file failed: locker: safe_lock: cannot create tmp lockfile /var/qmail/popuser/.spamassassin/auto-whitelist.lock.$

Where <servername> being my servername and the ip address being the ip address I was connecting from.

tavhane
10th May 2008, 01:52 PM
I run mhck -v no error messages but all domain's email accounts are not working.

dash
10th May 2008, 04:06 PM
Sirs,

There are several problems and solutions mixed in this thread.
Let's try to summarize them to a sequence of steps and hope that it will be helpful for the majority.

1) reinstall psa-qmail and courier-imap (psa-courier-imap) packages. I mean exactly packages from Plesk 8.4.0 distribution. Do not try to use packages from previous Plesk versions.

2) run /usr/local/psa/admin/sbin/mail_auth_dump utility

3) If you use authorization as a relay option:
In CP go to Server->Mail page. set "relaying" = closed. Click "OK" button. After that go to the page again, set desired authorization options and click OK button.

4) If you use "short names", check that there is a "SHORTNAMES=1" line in your /etc/courier-imap/imapd, imapd-ssl, pop3d, pop3d-ssl files. If it's missing, add it to the end of each file and restart courier-imap service.

5) run /usr/local/psa/admin/sbin/mchk -v

dzappone
10th May 2008, 05:46 PM
Sirs,

There are several problems and solutions mixed in this thread.
Let's try to summarize them to a sequence of steps and hope that it will be helpful for the majority.

1) reinstall psa-qmail and courier-imap (psa-courier-imap) packages. I mean exactly packages from Plesk 8.4.0 distribution. Do not try to use packages from previous Plesk versions.

2) run /usr/local/psa/admin/sbin/mail_auth_dump utility

3) If you use authorization as a relay option:
In CP go to Server->Mail page. set "relaying" = closed. Click "OK" button. After that go to the page again, set desired authorization options and click OK button.

4) If you use "short names", check that there is a "SHORTNAMES=1" line in your /etc/courier-imap/imapd, imapd-ssl, pop3d, pop3d-ssl files. If it's missing, add it to the end of each file and restart courier-imap service.

5) run /usr/local/psa/admin/sbin/mchk -v

Made absolutely no difference for me. Seems like a reasonable summary of steps. Question: what exactly does mail_auth_dump do? When I use mail_auth_view (which I am guessing show's the same data that mail_auth_dump manipulates I get no results returned - in fact it looks like this:


+--------------------------------------+-----+--------------------------------------+
| address |flags| password |
+--------------------------------------+-----+--------------------------------------+
+--------------------------------------+-----+--------------------------------------+
Flags
A - account disabled
D - domain disabled
E - password encrypted

105547111
11th May 2008, 01:30 AM
I have got problems with users trying to send mail. They have to use full names@domain not just short names.

This makes me think there is another set of files elsewhere for smtp, smtps, imap and imaps but for sending, as short works for incoming but not outgoing.

Any idea's where to look? Its not /etc/courier-imap as this is incoming.

dash
11th May 2008, 02:17 AM
Made absolutely no difference for me. Seems like a reasonable summary of steps. Question: what exactly does mail_auth_dump do? When I use mail_auth_view (which I am guessing show's the same data that mail_auth_dump manipulates I get no results returned - in fact it looks like this:


+--------------------------------------+-----+--------------------------------------+
| address |flags| password |
+--------------------------------------+-----+--------------------------------------+
+--------------------------------------+-----+--------------------------------------+
Flags
A - account disabled
D - domain disabled
E - password encrypted


mail_auth_dump utility gets data about mail-users and passwords from mysql database and map it into the file(/var/lib/plesk/mail/auth/passwd.db), which is used by all plesk mail-auth utilities.
mail_auth_view allows to view auth-data from this file.
mail_auth_dump is called during upgrade. but maybe upgrade on your server was failed for some reason before this call.
Try to run mail_auth_dump and after that run mail_auth_view to check that auth-file was created successfully.

dash
11th May 2008, 02:26 AM
I have got problems with users trying to send mail. They have to use full names@domain not just short names.

This makes me think there is another set of files elsewhere for smtp, smtps, imap and imaps but for sending, as short works for incoming but not outgoing.

Any idea's where to look? Its not /etc/courier-imap as this is incoming.

Is there env = SHORTNAMES=1 SMTPAUTH=1 line in your /etc/xinetd.d/smtp_psa, smtps_psa ?

paco68
11th May 2008, 03:54 AM
I have got problems with users trying to send mail. They have to use full names@domain not just short names.

This makes me think there is another set of files elsewhere for smtp, smtps, imap and imaps but for sending, as short works for incoming but not outgoing.

Any idea's where to look? Its not /etc/courier-imap as this is incoming.

Restart your VPS or Server!

dzappone
11th May 2008, 08:31 AM
Try to run mail_auth_dump and after that run mail_auth_view to check that auth-file was created successfully.

Cool, thanks for the info.

No it's not creating the auth file. It still shows the same empty table. Now how could that be failing and what file is is the auth file?

As a site note I do not (and I don't know if I should) have a /etc/xinetd.d/smtp_psa, smtps_psa file either.

dash
11th May 2008, 09:43 AM
Cool, thanks for the info.

No it's not creating the auth file. It still shows the same empty table. Now how could that be failing and what file is is the auth file?

As a site note I do not (and I don't know if I should) have a /etc/xinetd.d/smtp_psa, smtps_psa file either.

What OS do you use?
Are there any errors during mail_auth_dump running in console?

dzappone
11th May 2008, 11:08 AM
What OS do you use?
Are there any errors during mail_auth_dump running in console?

I've got:

Plesk Control Panel version: psa v8.4.0_build84080425.19 os_Ubuntu 7.10
Operating system: Linux 2.6.22-14-server

And no errors running mail_auth_dump in the console. In fact the timestamp of the files (assign, cdb, poppasswd) all seem to get updated but the contents don't change - file size remains the same - poppasswd is empty. The passwd.db seems to be updating just fine when changes are made to passwords.

It seems there is some sort of disconnect somewhere - but I have no idea.

Thanks for all the help and suggestions.

105547111
11th May 2008, 12:07 PM
Is there env = SHORTNAMES=1 SMTPAUTH=1 line in your /etc/xinetd.d/smtp_psa, smtps_psa ?

Unfortunately YES :(

service submission
{
socket_type = stream
protocol = tcp
wait = no
disable = no
user = qmaild
instances = UNLIMITED
env = SUBMISSION=1 SMTPAUTH=1
server = /var/qmail/bin/tcp-env
server_args = -Rt0 /var/qmail/bin/qmail-smtpd /var/qmail/bin/smtp_auth /var/qmail/bin/true /var/qmail/bin/cmd5checkpw /var/qmail/bin/true
}

service smtps
{
socket_type = stream
protocol = tcp
wait = no
disable = no
user = root
instances = UNLIMITED
env = SMTPAUTH=1 SHORTNAMES=1
server = /var/qmail/bin/tcp-env
server_args = -Rt0 /usr/sbin/rblsmtpd -r bl.spamcop.net -r sbl-xbl.spamhaus.org /var/qmail/bin/relaylock /var/qmail/bin/qmail-smtpd /var/qmail/bin/smtp_auth /var/qmail/bin/true /var/qmail/bin/cmd5checkpw /var/qmail/bin/true
}

service smtp
{
socket_type = stream
protocol = tcp
wait = no
disable = no
user = root
instances = UNLIMITED
env = SMTPAUTH=1 SHORTNAMES=1
server = /var/qmail/bin/tcp-env
server_args = -Rt0 /usr/sbin/rblsmtpd -r bl.spamcop.net -r sbl-xbl.spamhaus.org /var/qmail/bin/relaylock /var/qmail/bin/qmail-smtpd /var/qmail/bin/smtp_auth /var/qmail/bin/true /var/qmail/bin/cmd5checkpw /var/qmail/bin/true
}


only thing weird is submission has 1 space between fields on the env line the others have more than one???

dzappone
11th May 2008, 06:39 PM
I did a clean install on a new system twice - Ubuntu 7.10 and Plesk 8.4. It has the exact same problem. No email users can authenticate. I'd say there's a bug with 8.4 or the 8.4 install on at least Ubuntu 7.10 and probably some other distros as well.

intelitech
11th May 2008, 07:54 PM
This smtp auth issue was driving me crazy for the past several hours. The passwords would not get accepted as if they were wrong. Did all fixes described here to no avail. I got and untarred full 8.4 distribution package and force installed psa-qmail and spam-assasin and rblsmtpd, etc. Nothing worked. Then I noticed that "Real-time Blackhole List client for qmail" changed to "not up to date" in the autoupdater. Auto Installed it and issue got resolved. Don't know if it was new update from Parallels or I did unintentional reinstall of "Real-time Blackhole List client for qmail" or could be something else.

Hope this info helps someone.

Mike.
Intelitech.nu

dash
11th May 2008, 11:35 PM
I've got:

Plesk Control Panel version: psa v8.4.0_build84080425.19 os_Ubuntu 7.10
Operating system: Linux 2.6.22-14-server

And no errors running mail_auth_dump in the console. In fact the timestamp of the files (assign, cdb, poppasswd) all seem to get updated but the contents don't change - file size remains the same - poppasswd is empty. The passwd.db seems to be updating just fine when changes are made to passwords.

It seems there is some sort of disconnect somewhere - but I have no idea.

Thanks for all the help and suggestions.

The passwd.db is the only significant file.
Reapply Mail options on Server->Mail page. I mean change it, press OK, after that set it again as necessary and press OK again.
Check you seperserver file:
If you use Debian or Ubuntu it's a /etc/inetd.conf
If you use rpm based systems it's /etc/xinet.d/smtp_psa, smtps_psa
You are interested in
SHORTNAMES=1, if you use shortnames
SMTPAUTH=1, if you use smtp auth
POPAUTH=1, if you use "smtp after pop"

Check /etc/courier-imap/imapd, imapd-ssl, pop3d, pop3d-ssl
You are interested in SHORTNAMES=1, if you use shortnames

RESTART ALL NECESSARY SERVICES:
/etc/init.d/psa restart

jstapels
12th May 2008, 12:20 AM
I'm having the same problem as many others. I upgraded to Ubuntu 7.10 and suddenly noone can authenticate to IMAP. I have tried many/all the steps outlined in this thread to no avail. I hope that Plesk takes a look at this problem quickly as my customers are very unhappy.

For the record, my poppasswd file is blank, but I know in past versions of plesk that it was not.

jstapels
12th May 2008, 01:22 AM
UPDATE: I found that running the Plesk 8.3 version of mchk -v as well as restoring the 8.3 version of authpsa solved my problem. For those that don't have proper backups (like me!), I was able to extract the old versions using the 8.3 deb files found here: http://autoinstall.plesk.com/PSA_8.3.0/dist-deb-Ubuntu-7.10-i386/base/

the mchk tool is in the psa_8.3.0-ubuntu7.10.build83071218.20_i386.deb

the authpsa file is in the psa-courier-imap-add_8.3.0-ubuntu7.10.build83071218.20_i386.deb

This is clearly a hack. I only hope that the Plesk team resolves this issue quickly.

dzappone
12th May 2008, 01:22 AM
The passwd.db is the only significant file.
Reapply Mail options on Server->Mail page. I mean change it, press OK, after that set it again as necessary and press OK again.
Check you seperserver file:
If you use Debian or Ubuntu it's a /etc/inetd.conf
If you use rpm based systems it's /etc/xinet.d/smtp_psa, smtps_psa
You are interested in
SHORTNAMES=1, if you use shortnames
SMTPAUTH=1, if you use smtp auth
POPAUTH=1, if you use "smtp after pop"

Check /etc/courier-imap/imapd, imapd-ssl, pop3d, pop3d-ssl
You are interested in SHORTNAMES=1, if you use shortnames

RESTART ALL NECESSARY SERVICES:
/etc/init.d/psa restart

Ok, having done all that it still is not working. I'm using Ubuntu 7.10. I've tried with shortnames and full. I've tried all authentication options. I've tried pop, pop w/ssl, imap and imap w/ssl.

The imapd, imapd-ssl, pop3d and pop3d-ssl file all have these lines at the end:


MAILDIRPATH=Maildir
AUTHMODULES="authpsa"
MAILPASSWD="/var/qmail/users/poppasswd"


The pop3d file also has this line - though if I comment it out it makes no difference.

POP3DHOSTNAME=localhost.localdomain

Leading me to think that the password file is /var/qmail/users/poppasswd which is empty and remains empty regardless of mail_auth_dump or mchk -v being run. It would seem based on those config settings that poppasswd is where authpsa is looking to authenticate passwords against. It's empty so it's failing is my thought - if the passwd.db is the only significant file then I'm not sure why pop3d points to poppasswd unless that's change and it should be pointing elsewhere. I'm pretty sure that the blank poppasswd is the root of this evil. I could be wrong but that's certainly what all signs point to.

Thanks again for the suggestions.

dzappone
12th May 2008, 01:23 AM
UPDATE: I found that running the Plesk 8.3 version of mchk -v as well as restoring the 8.3 version of authpsa solved my problem. For those that don't have proper backups (like me!), I was able to extract the old versions using the 8.3 deb files found here: http://autoinstall.plesk.com/PSA_8.3.0/dist-deb-Ubuntu-7.10-i386/base/

the mchk tool is in the psa_8.3.0-ubuntu7.10.build83071218.20_i386.deb

the authpsa file is in the psa-courier-imap-add_8.3.0-ubuntu7.10.build83071218.20_i386.deb

This is clearly a hack. I only hope that the Plesk team resolves this issue quickly.

Thanks for the tip - I'll try it first thing tomorrow.

sergius
12th May 2008, 08:07 AM
Thanks for the tip - I'll try it first thing tomorrow.

Hello dzappone,

Could you please post here about result tomorrow?

sergius
12th May 2008, 08:42 AM
Hello dzappone,

Could you please post here about result tomorrow?

Excuse me. Please do not try to fix the issue by tools from previous Plesk versions - this is a risk.

dzappone, could you send me PM w/ credentials for access to your problem server?

DCoats
12th May 2008, 08:48 AM
Sergius, any Idea why with freebsd5.5 that the domainkeys being enabled for any domain would not allow any mail to be sent to the server from outside clients?
May 9 15:16:09 vortex qmail-remote-handlers[88732]: domainkeys-handler exited with status 31
May 9 15:16:09 vortex qmail-remote-handlers[88732]: call_handlers: stop call handlers because handler 'dd51-domainkeys' not PASS (31)
May 9 15:16:09 vortex qmail-remote-handlers[88732]: call_handlers: stop call handlers from dir '/usr/local/psa/qmail//handlers/before-remote/global'
May 9 15:16:09 vortex qmail: 1210360569.172809 delivery 713: failure: handlers_permanentfail/

Then ofcourse the mail bounces back with "handlers permanentfail"

dzappone
12th May 2008, 11:25 AM
Excuse me. Please do not try to fix the issue by tools from previous Plesk versions - this is a risk.

dzappone, could you send me PM w/ credentials for access to your problem server?

Have done so. I realize the risk of using tools from previous versions but if I cannot get this fixed by any other means I may have to do so. Please keep me appraised via PM of the status if possible. I have warned all my clients against making changes to their sites until further notice.

Thanks for the help.

LiquidD
12th May 2008, 11:39 AM
This is what i did. I upgraded to Plesk 8.4 (Fedora Core is the OS) and was getting the

"553 sorry, that domain isn't in my list of allowed rcpthosts (#5.7.1)" error in Outlook...Everyone was.

Everything was working fine up until the upgrade, so I knew there was an authentication issue somewhere.

I went to /etc/xinetd.d/smtp_psa and verified this:
"env = SMTPAUTH=1 SHORTNAMES=1"

I remembered that I created a smtp_psa_alt file for my alternate port. Inside that file, I looked for the following:
"env = SMTPAUTH=1 SHORTNAMES=1"
But it WAS NOT there. So I added it under "instances = UNLIMITED"

Restarted xinetd.d and I can send without the error. Nothing in Outlook or Plesk was changed except that file.

I assume that if you change the Relay options the ALT file will not update itself. This "env" must be new to this file??

Nonetheless, I hope this works for someone out there.

To update:
I found out later that clients somehow stopped getting mail as the email would bounce back the the sender would get a 553 error. I used this command and all is working now.

/usr/local/psa/admin/bin/mchk --with-spam

Hopefully all these problems will stop.

jstapels
12th May 2008, 02:19 PM
Excuse me. Please do not try to fix the issue by tools from previous Plesk versions - this is a risk.


I agree and stated that my fix was a "hack". But without any developers around, what else can we do? On Ubuntu 7.10, the upgrade to 8.4 left all my users unable to access their email via Pop and IMAP. Since this problem has been ongoing and I didn't have a clear solution I had to do something before my paying clients decided to go elsewhere.

For my server, it was clear that that my cdb file did not contain ANY password information. (I used the cdbdump tool to verify this). I tried all of the suggestions listed in this thread but none of them worked for me. So I decided to install the 8.3 version of mchk and when I ran it, it generated the poppasswd file with the password information.

Unfortunately, the cdb file still didnt have password information in it. I suspect the 8.4 version of authpsa was coded to use passwords stored in the cdb file rather than poppasswd. So I installed the 8.3 version of authpsa and my users could start accessing their mail again.

So, if I had to guess, I would imagine that one of the 8.4 deb files for Ubuntu 7.10 did not get built with the proper library. I cannot allow access to my system if someone from Plesk wants to debug, but I am more than willing to provide information and feedback.

dellison1226
12th May 2008, 02:41 PM
I have been having the same problems with POP and Horde webmail access all last week. Today the update is once again available and this time the update worked. All email pop and webmail are now working.

tavhane
12th May 2008, 04:18 PM
I try all tips but mails not worked. not worked. not workd!!!!!!!!!!!!!

buttter
12th May 2008, 05:54 PM
This did the trick, I have an alternative port too, and in the smtp_psa file the "env =" wasnīt there.

Thanks man!

(Using Red Hat PSA 8.4)


This is what i did. I upgraded to Plesk 8.4 (Fedora Core is the OS) and was getting the

"553 sorry, that domain isn't in my list of allowed rcpthosts (#5.7.1)" error in Outlook...Everyone was.

Everything was working fine up until the upgrade, so I knew there was an authentication issue somewhere.

I went to /etc/xinetd.d/smtp_psa and verified this:
"env = SMTPAUTH=1 SHORTNAMES=1"

I remembered that I created a smtp_psa_alt file for my alternate port. Inside that file, I looked for the following:
"env = SMTPAUTH=1 SHORTNAMES=1"
But it WAS NOT there. So I added it under "instances = UNLIMITED"

Restarted xinetd.d and I can send without the error. Nothing in Outlook or Plesk was changed except that file.

I assume that if you change the Relay options the ALT file will not update itself. This "env" must be new to this file??

Nonetheless, I hope this works for someone out there.

To update:
I found out later that clients somehow stopped getting mail as the email would bounce back the the sender would get a 553 error. I used this command and all is working now.

/usr/local/psa/admin/bin/mchk --with-spam

Hopefully all these problems will stop.

calderwood
12th May 2008, 08:21 PM
Sirs,

There are several problems and solutions mixed in this thread.
Let's try to summarize them to a sequence of steps and hope that it will be helpful for the majority.

1) reinstall psa-qmail and courier-imap (psa-courier-imap) packages. I mean exactly packages from Plesk 8.4.0 distribution. Do not try to use packages from previous Plesk versions.

2) run /usr/local/psa/admin/sbin/mail_auth_dump utility

3) If you use authorization as a relay option:
In CP go to Server->Mail page. set "relaying" = closed. Click "OK" button. After that go to the page again, set desired authorization options and click OK button.

4) If you use "short names", check that there is a "SHORTNAMES=1" line in your /etc/courier-imap/imapd, imapd-ssl, pop3d, pop3d-ssl files. If it's missing, add it to the end of each file and restart courier-imap service.

5) run /usr/local/psa/admin/sbin/mchk -v

Where do we get these packages to re-install????

calderwood
12th May 2008, 08:31 PM
Should say - is there an updated RPM file for this? Re-installing the same probably makes no difference.

calderwood
12th May 2008, 08:56 PM
It appears that the error is in the email boxes using redirect or groups with an email address that uses domain keys, such as Google or Yahoo - they are rejecting the keys and sending back a response which generates another redirect, etc.

105547111
12th May 2008, 09:38 PM
I still cant use shortnames for sending email, but short is ok for incoming. So smtp has issues accepting short login names despite the /etc/xinet.d/ files have the short in them :(

Monica
13th May 2008, 04:09 AM
Hello all.
See the hotfix for mail issues after upgrade:
http://kb.parallels.com/en/5256

Crashys
13th May 2008, 04:15 AM
Just tried that mail_fix...

root@els:~# sh mail_fix.sh
root@els:~#

Nothing happens... still with problem

Monica
13th May 2008, 04:24 AM
the script lauches mchk in daemon mode, probably it is worth waiting for a little bit, check whether mchk is running with "ps aux".

Crashys
13th May 2008, 04:34 AM
the script lauches mchk in daemon mode, probably it is worth waiting for a little bit, check whether mchk is running with "ps aux".

After i run the script and do a "top" i see sometimes apear the 'mchk' command, but now that i believe its finished my problem with the mail remains... :|

105547111
13th May 2008, 05:00 AM
Hi Monica,

I applied the patch and certainly sending email using IMAPS on my iphone I get failed authentication if I use short name for sending.

If I change sending back to full name I can send mail.

Incoming mail is still fine using short.

Thanks!

(PS I did restart both qmail and imap)

Monica
13th May 2008, 05:09 AM
Parallels support keeps on working on this... Let us wait.

105547111
13th May 2008, 05:11 AM
No problems I just wanted to provide some feedback. I look forward to the fix once it comes.

I assume this existing hotfix is not a problem and wont inevitably break something?

Just thinking aloud, people having this short name on sending and it wont work, are you also using domainkeys on sending email? I am.

Thanks!

105547111
13th May 2008, 05:59 AM
Hey I found the FIX and thought I would share..

look at:

/etc/xinet.d/submission_psa

I found mine was missing SHORTNAMES=1

I edited it restarted xinetd (/etc/init.d/xinetd restart) and it works shortnames..

So plesk needs a hotfix to properly set shortnames=1 inside the submission_psa

I also noticed if I just say OK in the plesk gui toi the mail options, only smtp_psa and smtps_psa get the timestamp changed, submission_psa is not written to at all.

I also ticked off submission, then OK and then set back to on and OK. All I see is the filename gets renamed, but the timsstamp and contents do not get modified.

So there is a bug in plesk not generating the submission_psa on any mail changes!

calderwood
13th May 2008, 06:25 AM
Hello all.
See the hotfix for mail issues after upgrade:
http://kb.parallels.com/en/5256

There is way more happening with this upgrade than covered by the hotfix. Here are my logs:

May 13 06:20:51 ip-208-109-248-176 qmail: 1210674051.768310 status: local 0/10 r emote 9/20
May 13 06:20:51 ip-208-109-248-176 qmail: 1210674051.768346 delivery 3651: failu re: 64.202.189.86_failed_after_I_sent_the_message./Remote_host_said:_554_Message _refused./
May 13 06:20:51 ip-208-109-248-176 qmail: 1210674051.768377 status: local 0/10 r emote 8/20
May 13 06:20:51 ip-208-109-248-176 qmail: 1210674051.768408 new msg 9670400
May 13 06:20:51 ip-208-109-248-176 qmail: 1210674051.768439 info msg 9670400: by tes 3060 from <> qp 25913 uid 2522
May 13 06:20:52 ip-208-109-248-176 qmail: 1210674052.173833 starting delivery 36 52: msg 9670809 to remote postmaster@ip-208-109-248-176.ip.secureserver.net
May 13 06:20:52 ip-208-109-248-176 qmail: 1210674052.173918 status: local 0/10 r emote 9/20
May 13 06:20:52 ip-208-109-248-176 qmail-queue[26188]: mail: all addreses are un checkable - need to skip scanning (by deny mode)
May 13 06:20:52 ip-208-109-248-176 qmail-queue[26188]: scan: the message(drweb.t mp.wdZLeg) sent by #@[] to postmaster@ip-208-109-248-176.ip.secureserver.net sho uld be passed without checks, because contains uncheckable addresses
May 13 06:20:54 ip-208-109-248-176 qmail-queue-handlers[26189]: Handlers Filter before-queue for qmail started ...
[root@ip-208-109-248-176 ~]# tail /usr/local/psa/var/log/maillog
May 13 06:21:42 ip-208-109-248-176 qmail-queue[26438]: mail: all addreses are uncheckable - need to skip scanning (by deny mode)
May 13 06:21:42 ip-208-109-248-176 qmail-queue[26438]: scan: the message(drweb.tmp.XW8rIh) sent by to drweb-daemon@ip-208-109-248-176.ip.secureserver.net should be passed without checks, because contains uncheckable addresses
May 13 06:21:42 ip-208-109-248-176 qmail-queue-handlers[26443]: Handlers Filter before-queue for qmail started ...
May 13 06:21:42 ip-208-109-248-176 qmail-local-handlers[26439]: from=downeds2@gurukun.net
May 13 06:21:42 ip-208-109-248-176 qmail-local-handlers[26439]: to=mickey4741@funataglance.com
May 13 06:21:42 ip-208-109-248-176 qmail-queue-handlers[26443]: from=
May 13 06:21:42 ip-208-109-248-176 qmail-queue-handlers[26443]: to=drweb-daemon@ip-208-109-248-176.ip.secureserver.net
May 13 06:21:42 ip-208-109-248-176 qmail-queue-handlers[26443]: hook_dir = '/var/qmail//handlers/before-queue'
May 13 06:21:42 ip-208-109-248-176 qmail-queue-handlers[26443]: recipient[3] = 'drweb-daemon@ip-208-109-248-176.ip.secureserver.net'
May 13 06:21:42 ip-208-109-248-176 qmail-queue-handlers[26443]: handlers dir = '/var/qmail//handlers/before-queue/recipient/drweb-daemon@ip-208-109-248-176.ip.secureserver.net'

Crashys
13th May 2008, 10:14 AM
New changes on the KB adding:

If it does not help and you get "no such user" error in /usr/local/psa/var/log/maillog, for example during IMAP connections, make sure that all Plesk packages were upgraded to the Plesk 8.4 build (build84080*). Because Plesk 8.4 uses new optimized mail authorization mechanism that may not work with the old packages. On RPM based OSes you can check it with the command like:
# rpm -qa | grep psa | grep -v 840

Didn't work for me. (System Ubuntu 7.10)... keep losing clients... lost 3 clients already. :|

adriman
13th May 2008, 11:07 AM
I can help you with this issue
My resume: http://www.odesk.com/users/~~9625e914c41aa8a5

!!! for all that have CentOS !!!!!!!!!!!
step 1: check installed rpm after plesk update
rpm -qa | grep psa | grep qmail

psa-qmail-rblsmtpd-0.70-cos4.build84080425.21
psa-qmail-1.03-cos4.build84080425.21

if you have other output than myne download new rpms from official site

STEPT 2:
you have to install this psa-qmail-1.03-cos4.build84080425.21.i586.rpm
and this psa-qmail-rblsmtpd-0.70-cos4.build84080425.21.i586.rpm

rpm -U psa-qmail-rblsmtpd-0.70-cos4.build84080425.21.i586.rpm #update
rpm -U psa-qmail-rblsmtpd-0.70-cos4.build84080425.21.i586.rpm #update rbl

if you het message that you have the latest version but it's not true uninstall previous version

rpm -e --nodeps your_previous_version
also with rbl
and install the new one
rpm -i psa-qmail-rblsmtpd-0.70-cos4.build84080425.21.i586.rpm
also with rbl RPM

STEP 3:
after that edit /etc/xinetd.dsmtp_psa

service smtp
{
socket_type = stream
protocol = tcp
wait = no
disable = no
user = root
instances = UNLIMITED
env = SMTPAUTH=1 SHORTNAMES=1
server = /var/qmail/bin/tcp-env
server_args = -Rt0 /var/qmail/bin/relaylock /var/qmail/bin/qmail-smtpd /var/qmail/bin/smtp_auth /var/qmail/bin/true /var/qmail/bin/cmd5checkpw /var/qmail/bin/true
}

STEP 4:
restart qmail, restart courier-imap
and have fun :)

Crashys
13th May 2008, 11:09 AM
I can help you with this issue

!!! for all that have CentOS !!!!!!!!!!!
step 1: check installed rpm after plesk update
rpm -qa | grep psa | grep qmail

psa-qmail-rblsmtpd-0.70-cos4.build84080425.21
psa-qmail-1.03-cos4.build84080425.21

if you have other output than myne download new rpms from official site

STEPT 2:
you have to install this psa-qmail-1.03-cos4.build84080425.21.i586.rpm
and this psa-qmail-rblsmtpd-0.70-cos4.build84080425.21.i586.rpm

rpm -U psa-qmail-rblsmtpd-0.70-cos4.build84080425.21.i586.rpm #update
rpm -U psa-qmail-rblsmtpd-0.70-cos4.build84080425.21.i586.rpm #update rbl

if you het message that you have the latest version but it's not true uninstall previous version

rpm -e --nodeps your_previous_version
also with rbl
and install the new one
rpm -i psa-qmail-rblsmtpd-0.70-cos4.build84080425.21.i586.rpm
also with rbl RPM

STEP 3:
after that edit /etc/xinetd.dsmtp_psa

service smtp
{
socket_type = stream
protocol = tcp
wait = no
disable = no
user = root
instances = UNLIMITED
env = SMTPAUTH=1 SHORTNAMES=1
server = /var/qmail/bin/tcp-env
server_args = -Rt0 /var/qmail/bin/relaylock /var/qmail/bin/qmail-smtpd /var/qmail/bin/smtp_auth /var/qmail/bin/true /var/qmail/bin/cmd5checkpw /var/qmail/bin/true
}

STEP 4:
restart qmail, restart courier-imap
and have fun :)

I dont have CentOS so this can't help me... i have Ubuntu... :|

dzappone
13th May 2008, 12:00 PM
Just wanted to say thanks for all the help. The email authentication has been restored.

For those who are curious as to the problem it is this (at least on Ubuntu):


Mail_auth_dump utility from Plesk 8.4.0 does not work with latest libdb4.4 package from gutsy-updates

As a result mail-auth database /var/lib/plesk/auth/passwd.db was empty and authentication was failed.

I rebuilt mail_auth_dump with latest libdb4, uploaded it on your server. Looks like mail auth works fine now.

<snip>

As I wrote on forum, /var/lib/plesk/auth/passwd.db is the only significant data-file.


And it does work fine. The problem is likely to appear only for those who have the latest updats to Ubuntu 7.10. If you haven't applied the most recent updates your email may still be working fine.

I imagine a hotfix is on it's way.

joeybutterface
13th May 2008, 12:13 PM
Does this fix address the mail redirect bug others are reporting?

(if you don't know what I'm talking about: create a new email account, no mailbox, and redirect it to a yahoo/gmail/hotmail account - now try sending a message to that account)

cgavage
13th May 2008, 12:18 PM
After i run the script and do a "top" i see sometimes apear the 'mchk' command, but now that i believe its finished my problem with the mail remains... :|

Still the problem after to have executed the fix.

dzappone
13th May 2008, 01:44 PM
Does this fix address the mail redirect bug others are reporting?

(if you don't know what I'm talking about: create a new email account, no mailbox, and redirect it to a yahoo/gmail/hotmail account - now try sending a message to that account)

Well I don't know if it fixes it or not. I created new email account, no password, no mailbox with a redirect. It would not redirect to my gmail account but it would to my Yahoo! account.

jstapels
13th May 2008, 02:41 PM
This hotfix still did not solve my POP/IMAP authentication issues.

Edit: For the record, I'm NOT using shortnames... I have this problem using longnames.

tavhane
13th May 2008, 06:19 PM
Yes, hotfix not solved POP/IMAP authentication issues.

dzappone
13th May 2008, 06:53 PM
@jstapels, @tavhane

There are apparently two authentication issues. One involving short names and one involving the mail_auth_dump utility.

The hotfix does not solve the mail_auth_dump authentication issue on Ubuntu 7.10 with the latest Ubuntu patches.

The mail_auth_dump utility from Plesk 8.4.0 does not work with latest libdb4.4 package from gutsy-updates (Ubuntu 7.10.) This leaves the /var/lib/plesk/auth/passwd.db empty and authentication will fail. I think if you have not applied the latest updates to Ubuntu you may not be encountering authentication issues.

You can run mail_auth_view (/opt/psa/admin/sbin/mail_auth_view on Debian based dsitros.) If the results do not include any email address/password combinations this is most likely the problem you are having.

You will need a rebuilt mail_auth_dump with latest libdb4 package on your server for email authentication to function correctly. I believe it was stated somewhere in this thread that Plesk uses new mail authentication routines in 8.4.0.

I don't know what Parallels process is for releasing patches but I do know they are aware of the problem and I imagine will issue a patch or hotfix shortly but considering how many Linux distros are supported for Plesk it may take some time.

tavhane
13th May 2008, 09:41 PM
I need reinstall plesk 8.3. how to do?

jstapels
14th May 2008, 12:33 AM
@dzappone

Thanks for the update, much appreciated :).

buttter
14th May 2008, 01:06 AM
Hi all, got some problems, the IMAP works fine, but when i try to send by SMTP always is requesting for user/pass in outlook, I tried all, all! the fixes and advices in this forum and nothing works, I look in the outlook log, and I find this:

2008.05.13 23:57:57 SMTP : Connected to host
2008.05.13 23:57:57 SMTP : <rx> 220 domain.com ESMTP
2008.05.13 23:57:57 SMTP : [tx] EHLO CCPC
2008.05.13 23:57:57 SMTP : <rx> 250-domain.com
2008.05.13 23:57:57 SMTP : <rx> 250-AUTH=LOGIN CRAM-MD5 PLAIN
2008.05.13 23:57:57 SMTP : <rx> 250-AUTH LOGIN CRAM-MD5 PLAIN
2008.05.13 23:57:57 SMTP : <rx> 250-STARTTLS
2008.05.13 23:57:57 SMTP : <rx> 250-PIPELINING
2008.05.13 23:57:57 SMTP : <rx> 250 8BITMIME
2008.05.13 23:57:57 SMTP : Authorizing to server
2008.05.13 23:57:57 SMTP : [tx] AUTH LOGIN
2008.05.13 23:57:57 SMTP : <rx> 334 (encrypted user)
2008.05.13 23:57:57 SMTP : [tx] (pass)
2008.05.13 23:57:57 SMTP : <rx> 334 (pass)
2008.05.13 23:57:57 SMTP : [tx] *****
2008.05.13 23:57:57 SMTP : <rx> unable to open mail authentication database: Permission denied

So I guess the problem is a chmod or permision problem in some file for auth... could somebody give me an advise?

Thanks in advance!

dash
14th May 2008, 02:07 AM
One more IMPORTANT note for Ubuntu 7.10 i386 users only:
mail_auth_dump utility does not work correctly with package libdb4.4 = 4.4.20-8.1ubuntu3.1 from gutsy-updates repository.
As a result main mail-auth data file /var/lib/plesk/mail/auth/passwd.db is not created/updated

To solve the issue:
1) check what exactly libdb4.4 version do you have installed:
# apt-cache policy libdb4.4
libdb4.4:
Installed: 4.4.20-8.1ubuntu3.1 <<<<<<<<
Candidate: 4.4.20-8.1ubuntu3.1

2) If you have exactly 4.4.20-8.1ubuntu3.1 installed -> downgrade libdb4.4 package to 4.4.20-8.1ubuntu3 release from gutsy/main repository:

#apt-get install libdb4.4=4.4.20-8.1ubuntu3

3) regenerate mail-auth data file /var/lib/plesk/mail/auth/passwd.db:
# /usr/local/psa/admin/sbin/mail_auth_dump

4) check that auth data is up2date:
# /usr/local/psa/admin/sbin/mail_auth_view

Official update is comming soon.

tavhane
14th May 2008, 02:57 AM
thank you very much dash :( thank you! thank you! thank you! god bless youuuuu!

jstapels
14th May 2008, 11:56 AM
@dash: Thanks!!! You're my hero of the month!

buttter
14th May 2008, 08:43 PM
Well I have checked with mozilla thunderbird and it can send SMTP messages! but I see and it uses the HELO command and not the EHLO, any advise?? I need working the EHLO command because all my clients use Outlook or Entourage... please help!



Hi all, got some problems, the IMAP works fine, but when i try to send by SMTP always is requesting for user/pass in outlook, I tried all, all! the fixes and advices in this forum and nothing works, I look in the outlook log, and I find this:

2008.05.13 23:57:57 SMTP : Connected to host
2008.05.13 23:57:57 SMTP : <rx> 220 domain.com ESMTP
2008.05.13 23:57:57 SMTP : [tx] EHLO CCPC
2008.05.13 23:57:57 SMTP : <rx> 250-domain.com
2008.05.13 23:57:57 SMTP : <rx> 250-AUTH=LOGIN CRAM-MD5 PLAIN
2008.05.13 23:57:57 SMTP : <rx> 250-AUTH LOGIN CRAM-MD5 PLAIN
2008.05.13 23:57:57 SMTP : <rx> 250-STARTTLS
2008.05.13 23:57:57 SMTP : <rx> 250-PIPELINING
2008.05.13 23:57:57 SMTP : <rx> 250 8BITMIME
2008.05.13 23:57:57 SMTP : Authorizing to server
2008.05.13 23:57:57 SMTP : [tx] AUTH LOGIN
2008.05.13 23:57:57 SMTP : <rx> 334 (encrypted user)
2008.05.13 23:57:57 SMTP : [tx] (pass)
2008.05.13 23:57:57 SMTP : <rx> 334 (pass)
2008.05.13 23:57:57 SMTP : [tx] *****
2008.05.13 23:57:57 SMTP : <rx> unable to open mail authentication database: Permission denied

So I guess the problem is a chmod or permision problem in some file for auth... could somebody give me an advise?

Thanks in advance!

buttter
17th May 2008, 01:22 AM
Well, for anyone interested we reinstalled the qmail-psa RPM and the SMTP_AUTH now works =)

jdstevens
17th May 2008, 07:52 PM
Well, for anyone interested we reinstalled the qmail-psa RPM and the SMTP_AUTH now works =)

This worked well for me also. Outgoing mail would not be delivered except locally because of authentication issues.

On Centos 4 in /root/psa/PSA_8.4.0/dist-rpm-CentOS-4.2-i386/base

rpm -ivh --force psa-qmail-1.03-cos4.build84080425.21.i586.rpm

fixed the authentication problem. Outgoing email to "foreign" servers began working correctly.

I had run the mail_fix.sh script with no apparent positive results. I don't know if it contributed to the solution.

neph
26th May 2008, 06:17 AM
I've reinstalled psa-qmail on Fedora Core 4, but I can only send mails.. Not receiving. When I try to send email from gmail, I get "Not accepting emails anymore" message.

Any help please? :/

neph
27th May 2008, 04:12 AM
Hello fdoibz,

Thank you for the report.
Please try to run mchk tool w/ option v

mchk -v

1.

[root@srv1 etc]# /usr/local/psa/admin/sbin/mchk -v
mail_auth_dump: Unable to clear mail authentication database: DB_RUNRECOVERY: Fatal error, run database recovery

System error 2: No such file or directory
mchk: /usr/local/psa/admin/bin/mail_auth_dump execution failed:
mail_auth_dump: Unable to clear mail authentication database: DB_RUNRECOVERY: Fatal error, run database recovery

System error 2: No such file or directory
mchk: /usr/local/psa/admin/bin/mail_auth_dump execution failed:
mail_auth_dump: Unable to clear mail authentication database: DB_RUNRECOVERY: Fatal error, run database recovery

System error 2: No such file or directory
mchk: unable to open mail authentication database: DB_RUNRECOVERY: Fatal error, run database recovery

System error 2: No such file or directory
mchk: unable to open mail authentication database: DB_RUNRECOVERY: Fatal error, run database recovery

System error 2: No such file or directory
mchk: unable to set password
System error 2: No such file or directory
mchk: unable to set password
System error 2: No such file or directory
[root@srv1 etc]#

2. Same error occured with mail_auth_dump

3. I still cant see any updates in "Updater"

any help guys? :/ (I've reinstalled psa-qmail, but its still rejecting mails..)

neph
28th May 2008, 05:06 AM
c'mon guys, your online support form is NOT WORKING, and nobody's answering here..

we need that mail issue fixed asap, thousands of our users are pissed already!

Blackbit
28th May 2008, 06:19 AM
This is a very critical issue, as no incoming e-mails are processed!

mail_auth_dump: Unable to clear mail authentication database: DB_RUNRECOVERY: Fatal error, run database recovery

System error 2: No such file or directory
mail_auth_dump: Unable to clear mail authentication database: DB_RUNRECOVERY: Fatal error, run database recovery

System error 2: No such file or directory

Blackbit
28th May 2008, 06:24 AM
...and saw this with strace when i run mail_auth_dump:

stat("/var/lib/plesk/mail/auth/DB_CONFIG", 0x7fff46195e70) = -1 ENOENT (No such file or directory)
open("/var/lib/plesk/mail/auth/DB_CONFIG", O_RDONLY) = -1 ENOENT (No such file or directory)
stat("/var/lib/plesk/mail/auth/__db.001", 0x7fff46195df0) = -1 ENOENT (No such file or directory)
open("/var/lib/plesk/mail/auth/__db.001", O_RDWR) = -1 ENOENT (No such file or directory)
open("/var/lib/plesk/mail/auth/__db.001", O_RDWR) = -1 ENOENT (No such file or directory)
open("/var/lib/plesk/mail/auth/__db.001", O_RDWR) = -1 ENOENT (No such file or directory)
stat("/var/lib/plesk/mail/auth/__db.001", 0x7fff46195f50) = -1 ENOENT (No such file or directory)

How can we restore/create these db-files?

Blackbit
28th May 2008, 06:26 AM
Backup your files in /var/lib/plesk/mail/auth
Remove all files in /var/lib/plesk/mail/auth
Run /usr/local/psa/admin/sbin/mail_auth_dump

Run /usr/local/psa/admin/sbin/mchk

Gorlist
29th May 2008, 03:47 AM
Ignoring my other post (http://forum.swsoft.com/showthread.php?t=53084) - I assume this is related to the same issue of SMTP authentication not functioning correctly?

I could disable RBL but rather not.

UnityWeb
30th May 2008, 04:53 PM
Reporting, Ubuntu 7.10 Plesk 8.4

Got mail checking working by adding the 'shortnames' trick above, but 'mail_auth_dump' and 'mchk' still report errors (and panics)


mail_auth_dump: Unable to commit changes to mail authentication database: DB_RUNRECOVERY: Fatal error, run database recovery
mchk: /opt/psa/admin/bin/mail_auth_dump execution failed:
not a restored transaction
PANIC: Invalid argument
mail_auth_dump: Unable to commit changes to mail authentication database: DB_RUNRECOVERY: Fatal error, run database recovery
mchk: /opt/psa/admin/bin/mail_auth_dump execution failed:
not a restored transaction
PANIC: Invalid argument
mail_auth_dump: Unable to commit changes to mail authentication database: DB_RUNRECOVERY: Fatal error, run database recovery


Also downgraded libdb4.4 ... nothing

What's the 'database recovery' thing ?

Official 'mail_fix.sh' doesn't work eighter

Clueless ... Thanks again Plesk !

robca
1st June 2008, 04:42 PM
My problem is solved by editing my clamav config...
Removed following options:

#ArchiveMaxCompressionRatio 300
#ArchiveBlockMax no

llaann
22nd June 2008, 03:39 AM
Greetings to all!!!
In advance I am sorry for the English.
Reading a forum I so anywhere also have not found the decision apropos poppasswd. Why it is empty in version 8.4.0 support keyweb cannot help.
Whether module replacement authpsa from version 8.3 will help?
And in general somebody knows where passwords are stored? In poppasswd they simply are not present, then where they are?!
Thanks, friends!
Help me pls!!!!!!

2tonecafe
25th June 2008, 09:06 PM
Post #123 (Blackbit)


Backup your files in /var/lib/plesk/mail/auth
Remove all files in /var/lib/plesk/mail/auth
Run /usr/local/psa/admin/sbin/mail_auth_dump

#This command didn't work for me
Run /usr/local/psa/admin/sbin/mchk

At the end I restarted the smtp service
service qmail restart

And all was well and the email flows!

Thanks Blackbit....
I had to do this on 2 servers

weelk
27th June 2008, 06:58 AM
Hi all.

I'm new to Plesk and Virtuozzo. Got a VPS recently and from very beginning there is a problem with sending or receiving more than 10 emails in one go. They getting bounced back or disappeared completely. Can anyone help.

Thanks

Hultenius
29th June 2008, 11:59 AM
I've just upgraded one server (CentOS 4) from Plesk 8.3 to Plesk 8.4.

One mayor problem is that I can't use Outlook/Outlook Express to send mail over SSL (port 465) anymore! I get a SSL certificate warning (which is normal) but then the authentication won't let me thru (both short and full username tested). This error message could be found in /var/log/message:
smtp_auth: smtp_auth: FAILED: info - no such user from *@* [IP]

There is no problem with Thunderbird, just Outlook/Outlook Express. Does anyone have the same problem?

This is a big issue since my customer has been told to use port 465 and i know alot of them are using Outlook/Outlook Express. I won't upgrade another server until this has been solved.

Netcontac
6th July 2008, 03:08 PM
I have the SMTP problem but only with a couple of domains and some networks

I had read all the comments and my problem looks similar except it is not all the time.

The e-mails sent from certain networks fail if the recipient is not in my VServer, geting error 550 in Microsoft products and 571 in Thunderbird. It started a week ago, after upgrading to psa v8.4.0_build84080514.18 os_CentOS 4.2

Even the same message sent in one single movement to many addresses succeed with those of my VServer and fails with the rest.

Such problem only occurs in some networks with Win XP/Vista but in others everything goes find. I mean, in the network of a client, all the machines with Outlook failed, but those in other site do not, trying with addresses of their contact lists as well as new ones.

The auth credentials are:
user: name@domain.com
password: *****

Please let me know if it may be the same upgrade issue, I am indeed concern about a propagation to the rest of my domains.

datahaus
8th July 2008, 02:00 PM
i had alot of problems with short mailbox names and some hackers could use the server as open mail relay, after hours of investigating it seems the "-Rt0" caused the problems in /etc/xinetd.d/smtp_psa (and /etc/xinetd.d/smtps_psa) ...

server_args = -Rt0 /usr/sbi...

try to remove that if it is there and restart xinetd with "service xinetd restart"

inunisonltd
15th July 2008, 10:56 AM
Forgive me, I'm like PLESK stupid and qmail iliterate. Our server was upgraded to PLESK 8.4 and now I have users who send email (using outlook) and outlook sends it but it never hits our server, and they never get an error or bounce. It just goes into some black hole somewhere. Then I have users who used to get newsletters and now they don't, I look at the maillog and the newsletter never reaches us. I even white listed the email address it comes from and nothing. I have ran mchk -v from an ssh prompt as root, and it just sits there and does whatever, then my session times out after about an hour. Can anybody help with this. I'm losing customers left and right.

Thanks,

Bryan

martijnbakker
15th July 2008, 11:13 AM
Hi Bryan, Are u using SpamAssassin or something? In SA there is a bug, which is fixed in a newer version, but not in the one thats Plesk using at the moment. Its because they are sending with outlook 2007 and are being blocked because it dont like the new version and deleted it (for the users which have a score of 2,5 and deletion is on).

Meaby this is the problem(one we've got with outlook), otherwise : Try to find out your server log files (/var/log/mail.info / mail.err), for errors and to check if the mails reach the server for sure. Meaby you can post some in here and we can help you ;)

inunisonltd
22nd September 2008, 09:53 AM
I posted under another Title with similar problems. What I ended up doing was turning off the checking of Black Lists. This allowed all the mail that was not coming in to get to our server. Appears these people were all black listed by at least one listing. There is no way I can possibly check all my customers customers IP addresses. So I turned it off and so far so good. But, I will check into the version of SA, and this outlook issue you mentioned. Thanks for the Heads up.