Well, the issue has been solved (and it wasn't vpopmail at all).
There was a slight disconnect between the client and me, so while I saw
the box, it was misspelled on the system (missing an "e") causing the
problem.
Yet another example for the box labeled "check the obvious things first".
*sigh*
Yes. The problem user is the top user in the file.
Oddly enough, vuserinfo is currently showing the user as existing.
I also checked one of the old domains that hasn't been touched since the
upgrade, and the vpasswd format was the same as I indicated. (We were
running 5.2.1)
- Michael
Rick M
Michael Johnson wrote:
Checked against a domain added just yesterday, and the entries match in
fields:
_boxname_:_cryptpass_:1:0:_comment_:_directorypath_:_quota_:_clearpass_
___
Check the vpasswd file. Most likely you are miss
Checked against a domain added just yesterday, and the entries match in fields:
_boxname_:_cryptpass_:1:0:_comment_:_directorypath_:_quota_:_clearpass_
___
Michael Johnson 626-852-9696 Ext. 103
System A
Michael Johnson wrote:
I just encountered a strange problem with a user account that vpopmail
seems to think doesn't exist (sometimes).
I was previously on vpopmail 5.2 and just upgraded to 5.4 recently. I'm
not sure if that might be part of the problem.
One of my clients had sent up a mailb
I just encountered a strange problem with a user account that vpopmail seems to
think doesn't exist (sometimes).
I was previously on vpopmail 5.2 and just upgraded to 5.4 recently. I'm not sure
if that might be part of the problem.
One of my clients had sent up a mailbox and then added a sepa
