Community Discussions and Support
User do not exist

My Pegasus lived on a freenas window share with all my other files, videos, movies and so on.
I upgraded from freenas to truenas and also acquired drives with more storage.
Before doing anything, I backed the whole server up to a 10TB drive. everything, directory by directory, with verification.
removed old drives, installed new drives. Installed truenas. And got a new window share up and running.
I copied everything back to the new window share.


Before i started, Pegasus ran ok. After finishing, I got this message: User do not exists.
HELP!


Here is a part of a file.


[Pegasus Mail for Windows - Run Info]
Program version = Version 4.80.1028, Jan 16 2022
Language resources = Standard UK English resources (EN,0,LL)
Time and date run ended = Sat, 16 Aug 2025 21:05:49
Running in standalone mode? = Y
Internal username = Admin
Working home mailbox location = \TRUENAS\Arkana\New Pegasus\MAIL\Admin
New mailbox location = \TRUENAS\Arkana\New Pegasus\MAIL\Admin
LAN-based SMTP gateway status = Disabled, not preferred, not 'use always'.
MHS status = Disabled, not preferred, not 'use always'.
MHS directory path = /
MHS operating mode = SMF-70


[Pegasus Mail for Windows - Identities]


Help.


My Pegasus lived on a freenas window share with all my other files, videos, movies and so on. I upgraded from freenas to truenas and also acquired drives with more storage. Before doing anything, I backed the whole server up to a 10TB drive. everything, directory by directory, with verification. removed old drives, installed new drives. Installed truenas. And got a new window share up and running. I copied everything back to the new window share. Before i started, Pegasus ran ok. After finishing, I got this message: User do not exists. HELP! Here is a part of a file. --- [Pegasus Mail for Windows - Run Info] Program version = Version 4.80.1028, Jan 16 2022 Language resources = Standard UK English resources (EN,0,LL) Time and date run ended = Sat, 16 Aug 2025 21:05:49 Running in standalone mode? = Y Internal username = Admin Working home mailbox location = \\TRUENAS\Arkana\New Pegasus\MAIL\Admin New mailbox location = \\TRUENAS\Arkana\New Pegasus\MAIL\Admin LAN-based SMTP gateway status = Disabled, not preferred, not 'use always'. MHS status = Disabled, not preferred, not 'use always'. MHS directory path = / MHS operating mode = SMF-70 [Pegasus Mail for Windows - Identities] --- Help.

A couple issues I would check? Why do you have a space in the path?


What is the contents of your PMAIL.CFG file in the PMAIL/Programs directory.
Note that is a binary file so don't edit with a regular text editor. PCONFIG32.exe is program is used.
type command can be used to just look at basic info.
Might see
C:\PMAIL\MAILC:\PMAIL\MAIL
or
C:\PMAIL\MAIL~NC:\PMAIL\MAIL~N


Might need to have your nas path, but dodn't know if it would use that path, and the space might cause wierd issues.


Also, what does the PMAIL.USR file in the PMAIL/MAIL directory have?


A couple issues I would check? Why do you have a space in the path? What is the contents of your PMAIL.CFG file in the PMAIL/Programs directory. Note that is a binary file so don't edit with a regular text editor. PCONFIG32.exe is program is used. type command can be used to just look at basic info. Might see C:\PMAIL\MAILC:\PMAIL\MAIL or C:\PMAIL\MAIL\~NC:\PMAIL\MAIL\~N Might need to have your nas path, but dodn't know if it would use that path, and the space might cause wierd issues. Also, what does the PMAIL.USR file in the PMAIL/MAIL directory have?

mikes@guam.net

Last I know, Pegasus Mail would not work with UNC paths. That may have changed though. Was a UNC path to your mailbox location working under freenas? You should be able to tell by looking in the backed up PMAIL.INI file.


How did you change the mailbox path from freenas to truenas?


Finally, the space in the directory name "New Pegasus" may be causing a problem. Try using "New_Pegasus" instead. A directory rename here will require that you run PCONFIG32.EXE to specify the new mailbox path as mentioned by @msetzerii.

In summary, these are the things I suggest:


  • map a drive to \TRUENAS\Arkana
  • rename "New Pegasus" to "New_Pegasus"
  • run PCONFIG32.EXE to set the Home mailbox root directory to: <drive:>\New_Pegasus\MAIL\ ~N NOTE: There should not be a space between the backslash and the tilde. For some strange reason, this forum removes the backslash character when it is followed by a tilde.

It should look like this except the drive letter should be yours: 68bc1937cba9f


Last I know, Pegasus Mail would not work with UNC paths. That may have changed though. Was a UNC path to your mailbox location working under freenas? You should be able to tell by looking in the backed up PMAIL.INI file. How did you change the mailbox path from freenas to truenas? Finally, the space in the directory name &quot;New Pegasus&quot; may be causing a problem. Try using &quot;New_Pegasus&quot; instead. A directory rename here will require that you run PCONFIG32.EXE to specify the new mailbox path as mentioned by @msetzerii. In summary, these are the things I suggest: - map a drive to \TRUENAS\Arkana - rename &quot;New Pegasus&quot; to &quot;New_Pegasus&quot; - run PCONFIG32.EXE to set the Home mailbox root directory to: &lt;drive:&gt;\New_Pegasus\MAIL\ ~N NOTE: There should not be a space between the backslash and the tilde. For some strange reason, this forum removes the backslash character when it is followed by a tilde. It should look like this except the drive letter should be yours: ![68bc1937cba9f](serve/attachment&amp;path=68bc1937cba9f)

I just tested using PCONFIG32 to set the home mailbox path to a path that contained a space. There were no errors. The path shows correctly in PMAIL.CFG. What I recall about directory/filename issues and UNC vs mapped drive paths goes back a number of Pegasus Mail versions when I was administering a shared installation of Pegasus Mail that resided on a Windows 2008 server. At that time, UNC paths and long filenames in paths caused problems. I am now curious whether either of these are true today. I will try to get an answer.


I just tested using PCONFIG32 to set the home mailbox path to a path that contained a space. There were no errors. The path shows correctly in PMAIL.CFG. What I recall about directory/filename issues and UNC vs mapped drive paths goes back a number of Pegasus Mail versions when I was administering a shared installation of Pegasus Mail that resided on a Windows 2008 server. At that time, UNC paths and long filenames in paths caused problems. I am now curious whether either of these are true today. I will try to get an answer.
live preview
enter atleast 10 characters
WARNING: You mentioned %MENTIONS%, but they cannot see this message and will not be notified
Saving...
Saved
With selected deselect posts show selected posts
All posts under this topic will be deleted ?
Pending draft ... Click to resume editing
Discard draft