Email Account Creation Problem

[queueless]

This is definitely a stumper. Here's my problem.

I'm currently migrating domains to a Plesk system. I'm trying to run the following command to add an email account:

/usr/local/psa/bin/mail -c spam@domainname.org -mailbox true -passwd RjEE.S5NWLLU6 -passwd_type encrypted

The password used here is already crypted so I have no clue what it actually is. This is the error I get from the 'mail' command.

An error occured during mailname creation: Unable to update the mail name properties:
The password is incorrect, use at least 5 characters. The password should not contain mail name as its part.
Only Latin characters, no dictionary words (optional).

What gives?

 

[queueless]

Ok I just noticed the fact that in the poppasswd file there is a domain that has an account called 'spam'. Can 2 different domains not have the same account name?

i.e.

bob@domain1.com
bob@domain2.com

 

[Who-m3]

Admin Control Panel -> Server -> Mail -> Use of User@Domain accounts only. This will allow you to create the same user@domain1 and user@domain2 accounts w/o any problems. While using the "simple" login format, this is not possible if using the same password. This is also a security risk, as it notifies your customers that someone ELSE has the same password set on an account similar. I highly recommend switching your setting to the use of User@Domain accounts.

Side note: Using any external e-mail programs, such as Outlook, etc., this will require you to change your login name from "user" to "user@domain". Please be aware it is a case sensitive username.

 

[queueless]

Thanks for the reply. I had found that after posting my problem. It seemed to fix the problem I was having.

 

[slowburn]

We are having a very similar problem with migration. However, as we are migrating hundreds of domains to PSA, it is not feasable to do this: Admin Control Panel -> Server -> Mail -> Use of User@Domain accounts only.

The issue for us isn't with duplicate passwords. It's with being able to have bob@domain1 and bob@domain2 after a migration. Currently it works fine by manually creating the domains and email accounts. The migration appears to be breaking things.

I expect there is something the migration manager is adding to the PSA database somewhere, but I can't find it.

Any ideas?

 

[queueless]

While it may seem that the problem is not related to the passwords, it really is. I don't know exactly why this is the case, but it is.

I can't remember exactly the option, or where it is, as I havn't worked with the plesk interface for a few months; however, there is an option in the mail configuration that is basically along the lines of 'short logins' or 'long logins'.

"Short" logins will allow users to authenticate with only their username (minus the domain).

"Long" will require a fully quallified login, i.e. bob@domain.com

While "short" logins is enabled, no 2 domains can have the same username and the same password. Oddly, two different domains can have the same user with different passwords.

If you change your plesk settings so that users have to authenticate with "user@domain.com", you shouldn't have any further problems.

This is what fixed the problem I was having.

[Edit]

I can't tell you anything about any 'migration' tools out there. I wrote my own migration scripts for a client that was migrating more than 500 domains from another webhosting company. The tools provided by plesk had a reputation for not being up for the task.

Also, after reading your post again, I don't see how the number of domains being added would affect the option of requiring the 'long' email usernames. In most shared hosting systems, that is how it works anyway.

 

[slowburn]

The reason this is such a problem for us is that we are migrating hundreds of domains. As each domain has multiple email accounts, every email client will have to be manually configured. In our case that runs us into the thousands.

The problem is directly related to the fact that the migration utility creates "crypt" type passwords in the database. At least with the RaQ3 migration. Though, from what I can gather from other forum posts it may happen even with plesk to plesk migrations. If there is a crypt password associated with an account, an account with the same name can no longer be used in any other domain.

Identical account/password pairs can not be used across domains even if the password type is plain. But that has been know for some time. There are work arounds that are faily reasonable for that.

I can verify that "Only use of full POP3/IMAP mail accounts names is allowed" works around the problem. For some it is a good work around. In our case it certainly isn't.

Obviously, I have done a lot more testing since my original message. By the way, a password does not have to be unique. Many accounts can use the same password. You just can't have the same account/password pair.

 

[queueless]

Well, unfortunately the only current solution to your problem is to turn on 'long' email account names.

The only other solution would be to change the passwords to something you know to be uniqe per account. This, too, would require email client changes.

I still don't understand why it would be you that has to manually configure these email clients. Obviously you will be sending a blanket announcement to your clients. This announcement can include this change.

If you get support requests about it, it is a simple matter of a canned response.

At this point, I don't see any other option for you, as this was the same problem we faced.