I got it working.
Reading this page (http://netwinsite.com/zlist/1382.htm), I removed sw_identities.dat and the problem was solved. =)
Frank
From: Frank Bulk
Sent: Tuesday, September 17, 2019 6:48 PM
To: surgemail-list@netwin.co.nz
Subject: RE: [SurgeMail List] How is _user.dat used
Thanks, that was very helpful.
I set this:
pref_reply
username@nethtc.net
allowed_from username@nethtc.net
But my outbound email from SurgeWeb still used a From of
othername@nethtc.net, rather than username@nethtc.net. Which is interesting, because the email composition window in SurgeWeb did show “From:
username@nethtc.net”. Reply to was correct with
username@nethtc.net.
Any ideas what’s going on there?
Frank
yes you can edit the surgeweb _user.dat as needed. There are however two "correct" locations for the file:
1) The _user.dat is actually actively used from the user's surgeweb working folder (find using "tellmail swpath
user@domain.com"), but that is really a cached version.
2) Whenever the one in surgeweb/work is changed it is also uploaded to the mdir/xfile folder (find using "tellmail path
user@domain.com") - note this is a subdirectory of the mdir folder you were looking
Mirrorring gets applied at the mdir/xfile level. At the point of "login to surgeweb" it will check mdir/xfile and if that one is newer than the surgeweb/work folder overwrite
the one in the surgeweb/work folder with the one from mdir/xfile.
You can edit in either location, but beware that someone actively logged in to surgeweb can mean the one mdir/xfile gets overwritten, and that mirrorring can cause the file
in surgeweb/work to get overwritten.
On Tuesday 17/09/2019 at 6:36 pm, Frank Bulk wrote:
I've created a _user.dat file in the customer's mdir directory with two options, but SurgeWeb doesn't seem to use it.
Do I have to turn any other knobs to leverage the settings in that file? Or did I place it in the wrong directory?
Frank
pref_reply username@nethtc.net
allowed_from username@nethtc.net
