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.
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 fromHIDDEN@LD.DOMAIN.NAME to
HIDDEN@W.DOMAIN.NAME, it stayed at user@OLD.DOMAIN.NAME. I noticed that
when they log in asHIDDEN@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
LCR Computer Services, Inc.
Last Message | Next Message
Site Map |
Contact Netwin |
POP3 Mail Server |
Linux Webmail |
UnInstall instructions for all products
Copyright © 2017 Netwin Ltd. All rights reserved.