X-Default-Received-SPF: pass (skip=loggedin (res=PASS)) x-ip-name=115-188-37-143-adsl.sparkbb.co.nz; envelope-from=<surgemail-support@netwinsite.com>;
X-Received: from mail1 (115-188-37-143-adsl.sparkbb.co.nz [115.188.37.143])
by netwin.co.nz (SurgeMail 7.3p) with ESMTP (TLS) id 12454150-1391920
for <surgemail-list@netwin.co.nz>; Wed, 19 Jun 2019 23:21:23 +0000
X-Return-Path: surgemail-support
From: Support ChrisP
To: <surgemail-list@netwin.co.nz>
Subject: Re: [SurgeMail List] old_imaphost not used when user_auto enabled
Date: Wed, 19 Jun 2019 23:21:23 +0000
Message-ID: <5d0ac373.1d72.40d7c700.488cdb4c@netwin.co.nz>
MIME-Version: 1.0
X-Originating-IP: 115.188.37.143
X-Mailer: SurgeWeb - Ajax Webmail Client
X-Rcpt-To: <surgemail-list@netwin.co.nz>
X-SpamDetect: : 0.000000
X-Info: aspam skipped due to (g_smite_skip_relay)
X-Encryption: SSL encrypted
X-IP-stats: Incoming Last 0, First 6, in=63, out=0, spam=0 ip=115.188.37.143
List-Unsubscribe: <mailto:surgemail-list-leave@netwin.co.nz?subject=unsubscribe>
X-Mailing-List: surgemail-list@netwin.co.nz
List-ID: <surgemail-list@netwin.co.nz>
Precedence: bulk
Reply-To: surgemail-list@netwin.co.nz
Content-Transfer-Encoding: quoted-printable
Yes I would expect that to be a problem.
You could use the manual command (if you know the passwords)
Or not use the auto feature as it should create based on the old server...
ChrisP.
On Thursday 20/06/2019 at 3:28 am, Ed Robbins wrote:
Trying to verify some behavior. I need to migrate some users from one set of Surgemail clusters to another and I wanted to do it through the old_imaphost setting within the domain. However, in the tests that I tried, I never saw the new cluster reach out to the old cluster when the user logged in. I suspect it's due to the user_auto feature preceding the behavior of the old_imaphost feature. Can anyone confirm this for me?
Ed