Received-SPF: pass (Cache: Last token {+mx} (res=PASS)) client-ip=70.35.205.71; envelope-from=<lyle@lcrcomputer.info>; x-ip-name=ns3.lcrcomputer.net;
X-Received: from ns3.lcrcomputer.net (ns3.lcrcomputer.net [70.35.205.71])
by netwin.co.nz (SurgeMail 7.7d) with ESMTP (TLS) id 6187762-1391920
for <surgemail-list@netwin.co.nz>; Wed, 22 Feb 2023 13:40:30 +0000
X-Return-Path: lyle
X-Default-Received-SPF: pass (skip=loggedin (res=PASS)) x-ip-name=73.211.210.143; envelope-from=<lyle@lcrcomputer.info>;
X-Received: from mail3.lcrcomputer.net (unverified [73.211.210.143])
by ns3.lcrcomputer.net (SurgeMail 7.6h) with ESMTP (TLS) id 404704-1235687
for <surgemail-list@netwin.co.nz>; Wed, 22 Feb 2023 13:40:26 +0000
X-Return-Path: lyle
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=lcrcomputer.info;
s=default; t=1677073229;
bh=TvUeGVLF6OPcza7ntBcpezIe/qAJTgeab9vW5kQeBUU=;
h=Date:Subject:To:From;
b=YeirAGeSNs2i7ttvk7B55WHdQ0tsJ84m5dUeN+VcXyvpTP+t7GQ7faVbIB1q3KgDi
mPRdUfFPygMs1W7t6E0e3KKk1pnX+s331VyJdlcMcwHBhOzfTjUpYo5dnhH4MPc85g
uotrNPkNmmDk+htZPvyJ0IuE6TaZjUYMZWIJgIXA=
X-Default-Received-SPF: pass (skip=forwardok (res=PASS)) x-ip-name=192.168.250.160; envelope-from=<lyle@lcrcomputer.info>;
X-Received: from [192.168.250.160] (unverified [192.168.250.160])
by mail3.lcrcomputer.net (SurgeMail 7.6u) with ESMTP (TLS) id 568823-1794114
for <surgemail-list@netwin.co.nz>; Wed, 22 Feb 2023 07:40:28 -0600
X-Return-Path: lyle
Message-ID: <e9a7048f-4ca5-9da6-ac2a-ed4683907ba9@lcrcomputer.info>
Date: Wed, 22 Feb 2023 07:40:28 -0600
MIME-Version: 1.0
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:102.0) Gecko/20100101
Thunderbird/102.8.0
Subject: Re: [SurgeMail List] Hybrid Mail System (Multiple Delivery)
Content-Language: en-US
To: surgemail-list@netwin.co.nz
References: <CAPKJoo7BD_Tb0ZKXq8k9wj3YiV+BUTXq_Jq-TV3YDV5tGinKYQ@mail.gmail.com>
<96a4a6d6-5c73-2910-67a2-690fb24ef977@netwin.co.nz>
<CAPKJoo6=-13S=xWKjiHuRRghVBRXqML8YCBbZmSPhjuwJXrXkw@mail.gmail.com>
<64e65e84-d384-807c-092c-a231046c3b1e@lcrcomputer.info>
<CAPKJoo7APptVwQSMv1Vxbw+8FfH89s9jP=M00+gM63Tr70B7pw@mail.gmail.com>
From: Lyle Giese
In-Reply-To: <CAPKJoo7APptVwQSMv1Vxbw+8FfH89s9jP=M00+gM63Tr70B7pw@mail.gmail.com>
X-X-Authenticated-User: lyle@lcrcomputer.com
X-X-Qnum: 404704
X-X-Authenticated-User: auth_admin@ns3.lcrcomputer.net
X-Originating-IP: 70.35.205.71
X-Country: code=US country="United States" ip=70.35.205.71
X-Qnum: 6187762
X-Rcpt-To: <surgemail-list@netwin.co.nz>
X-SpamDetect: *****: 5.0 sd=5.0 NoRule 0.04(X-myrbl:Color=white) 0.10(X-SpamContent:clean) 0.90(X-Phrase:isspam) 0.32(FakeURL) 0.37(X-Verify-Helo:+OK) 0.39(genuine) 0.39(dkimok) 0.41(StandardTLD) 0.42(X-NotAscii:utf) 0.48(spfpass) 0.49(X-LangGuess:English) Saned 5.0 sanitym 1.0 -> 5.0 NotSaned s=1.0 was=5.0 Sval 1.0
X-NotAscii: charset=utf-8
X-SpamContent: Clean
X-LangGuess: English
X-FakeURL: netwin.co.nz -> netwinsite.com
X-FakeURL: main.domain -> netwinsite.com
X-FakeURL: main.domain -> netwinsite.com
X-Phrase: IsSpam score=1.00
X-Verify-Helo: +OK ns3.lcrcomputer.net
X-Dmarc: none, from=lyle@lcrcomputer.info, dkim=Good known=True spf=True
Authentication-Results: netwin.co.nz header.from=lcrcomputer.info; dkim=pass (good signature)
X-Encryption: SSL encrypted
X-MyRbl: Color=White Age=458 Spam=0 Notspam=0 Stars=0 Good=11 Friend=14 Surbl=0 Catch=0 r=0 ip=70.35.205.71
X-IP-stats: Incoming Outgoing Last 0, First 769, in=577, out=89, spam=0 Known=true ip=70.35.205.71
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: 8bit
Content-Transfer-Encoding: 8bit
In order to do this in a gateway server, you would have to have
to create a user mailbox(and add all aliases) for EVERY user and
then forward each mail box(with remove) to the server the
mailboxes reside on.
That's a real headache.
In my scenerio, push all mail to server A and if the mailbox does
not exist forward to server B. Exact method is highly dependent on
the software in server A and B, since email from server B needs to
go to server A for users on server A.
Lyle
On 2/21/23 08:10, James Bryan wrote:
If the target server is surgemail or under control then it
will be easy but I need to know the solution if both servers
are not surgemail or in different platforms.
I will be good if we can do in gateway with surgemail only
without any setting on target server
James
I had done this a few years ago as a company I worked for
transitioned from mail server A to Server B.
All incoming mail was pushed to server A and then the
mail for those mailboxes on server B was forwarded from
server A. There are a couple of ways to do that and mostly
depends on the capabilities of the servers involved in
regards to rule/routing capabilities.
But this was a transitioning setup and lastly a month or
two before turning off server A. I would not recommend it
for a permanent solution because of the probable extra
administrative overhead needed.
With Surgemail, you could have mirrored servers where the
mailboxes exist on both servers and the mail clients are
split to look at server A or server B. This would
eliminate the administrative overhead of other solutions.
Lyle Giese
On 2/20/23 22:35, James Bryan wrote:
How about this setting
vdomain name="
email.com"
address="1.1.1.0"
surgewall "1.2.3.4, 5.6.7.8"
Since surgewall will have more than one target ip
server.
Is it possible to add some processes in surgewall to
test/check if user exists in target servers and then
send message to that server
So if both servers 1.2.3.4 and 5.6.7.8 have unique
users and servers are in separate settings then I
think this method should solve this problem.
James
Hi, NEVER setup one domain with two ip addresses
:-), this is the 'wrong' solution to almost any
problem.
The 'domain' IS the mechanism to find the
destination serve - that's it's actual purpose
:-).
Good, now we've clarified that. You do it like
this:
Add a g_gateway rule to send all email to server1
for that domain
Add a g_route rule for each user on server2
or
Add a new domain 's2.domain' and redirect users
that live at server2 to user@s2.domain
then add a rewrite rule to change the destination
from s2.domain to .domain when sent.
(g_send_rewrite) (or configure server2 to accept
s2.domain as an alias)
Then ensure all email users on server1 and
server2 use gateway.server as their outgoing smtp
server and not server1,2
Or you can do something similar on both server1
and server2... each one individually listing the
users to send to the other system (yucky)
All solutions are complicated, messey and bad.
It's very easy to kick yourself in the foot and
end up with a loop or messages bouncing in certain
situations depending on who sends them etc...
Instead, simply establish a second domain name
for the other server, and all these problems go
away. e.g.
user1@main.domain
(server1)
user2@corp.main.domain
(server2)
user3@main.domain
(server1)
user4@corp.main.domain
(server2)
Then on 'server1' add some redirect rules for
'server2' users, just to help with transition.
I know you're probably gonna have to ignore this
advice because of some corporate type decision
that means you have no choice, but I'm giving it
anyway :-) :-).
ChrisP.
On 21/02/2023 8:38 am, James Bryan wrote:
Hi,
Is there any setting of surgemail to do
email gateway solutions where there are more
than one platforms or mail servers combined in
a single domain?
For example
I have email @
email.com
and there have 2 location of server
How to forward / reroute / rewrite email
messages on gateway or server1 or server2 to
transfer messages to a real mailbox on the
server?
Thank you
James