It's not working. It is staying at all lower case via Surgeweb. I have
a test account setup you can play with.
I will submit that info via the Privileged Access Form. Let me know if
you have any questions or problems accessing the system.
Lyle Giese
LCR Computer Services, Inc.
On 10/19/15 17:14, Surgemail Support (Marijn) wrote:
>
> Surgeweb should use the primary domain as specified in surgemail.ini
> as it's primary domain, and this should be used in the from address etc.
>
> I just confirmed that from an existing account / domain, changing the
> vdomain in the surgemail.ini vdomain section propagates it
> successfully to the surgeweb login. This included the picking up the
> capitalisation as specified in the vdomain line.
>
> There are two possible complicating factors:
> 1) You can explicitly specify the from address which may be happening,
> if so in _user.dat. This is disabled by default though as it is not
> generally needed.
> 2) If using the multiple accounts feature some information about each
> login is stored in the sw_identities.dat file which may not be getting
> updated on unusual usage scenarios like renaming domains.
>
> Try removing (or renaming) sw_identities.dat to see if this resolves
> your issues. You will have to remove the one in the surgeweb work
> folder (find using "tellmail sw_pathHIDDEN@omain") and the surgemail
> xfile folder (find using "tellmail pathHIDDEN@omain").
>
> The other thing to check is _user.dat. Other than that surgeweb should
> not be "tied to a particular domain" at all.
>
> Let us know if you need further help.
>
> Marijn
>
>
>
>
> On Sunday 18/10/2015 at 2:48 am, Lyle Giese wrote:
>>
>> On 10/14/15 20:11, Surgemail Support wrote:
>>>
>>> On 10/14/2015 2:30 PM, surgemailHIDDEN@etwinsite.com wrote:
>>>>
>>>> In the posted FAQ's I found this:
>>>>
>>>> Stop SurgemailMake a backup of nwauth.* and surgemail.ini
>>>> If using nwauth, then Run ./nwauth -rename old.domain.name
>>>> new.domain.name If not using nwauth change the domain names in
>>>> your database!Edit surgemail.ini and change the vdomain
>>>> name="OLD.DOMAIN.NAME" TO "NEW.DOMAIN.NAME"And add 'host_alias
>>>> "old.domain.name" if desired.What about the email in the directory
>>>> old.domain.name? Do we rename the email store directory from
>>>> old.domain.name to new.domain.name also?
>>>>
>>>> Lyle Giese
>>>> LCR Computer Services, Inc.
>>>>
>>>>
>>>>
>>>>
>>>
>>> There is no need to rename the email store itself, it can stay as
>>> the old file path as long as mailbox_path setting in that domain
>>> still points to it.
>>>
>>> Or you can rename it, and adjust mailbox_path to the new name.
>>>
>>> Both options will work.
>>>
>>> ChrisP.
>>>
>>>
>> Ok, the reason we did the rename was to make NEW.DOMAIN.NAME the
>> primary address that will be used when sending via Surgeweb. After
>> the rename, the From in Surgeweb did not change from
>>HIDDEN@LD.DOMAIN.NAME to user@NEW.DOMAIN.NAME, it stayed at
>>HIDDEN@LD.DOMAIN.NAME. I noticed that when they log in as
>>HIDDEN@EW.DOMAIN.NAME, Surgeweb did create new caching directories on
>> the server under NEW.DOMAIN.NAME
>>
>> Second issue that came up is the owner doesn't want NEW.DOMAIN.NAME,
>> but New.Domain.Name. They want specific capitalization in their From
>> address and they use Surgeweb exclusively. They don't use any other
>> email clients.
>>
>> Thanks,
>> Lyle Giese
>> LCR Computer Services, Inc.
>>
>>
>
>
>
>
|
