Received-SPF: pass (Last token {include:_netblocks.google.com} (res=PASS)) client-ip=209.85.219.182; envelope-from=<farmv52@gmail.com>; x-ip-name=mail-yb1-f182.google.com;
X-Received: from mail-yb1-f182.google.com (mail-yb1-f182.google.com [209.85.219.182])
by netwin.co.nz (SurgeMail 7.7d) with ESMTP (TLS) id 6166351-1391920
for <surgemail-list@netwin.co.nz>; Tue, 21 Feb 2023 14:10:31 +0000
X-Return-Path: farmv52
X-Received: by mail-yb1-f182.google.com with SMTP id i7so5383608ybu.6
for <surgemail-list@netwin.co.nz>; Tue, 21 Feb 2023 06:10:31 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;
d=gmail.com; s=20210112;
h=to:subject:message-id:date:from:in-reply-to:references:mime-version
:from:to:cc:subject:date:message-id:reply-to;
bh=Bk/Hr4KJWCbr1rAUaGhnI3X5mEGSt6tnJQ1h9azOKkE=;
b=NU2ViQhth8hlqUFJQeKs7+Fb36letN172a5p2nMdnLq67EsI6LgIAikgIMOq44dd3q
cSkEgIzcmibT8JGNK/fbPm/Vdi+Uyh/li+y0gpXgUmtAPHExwXOVY/qEN9/O/GW+lMn3
3gHExvrQCNCjz41Pd94lsgYp4tKJrlifZPPfNzfxuuodasj4EqeK2qjhwPFosM2DErsL
VAaLOP+pl5JzuiEqFcaEfZWGaxbZVQV7PFAgO8PDSkw31ULymtQMArVJPNIkSROQQvKB
jx0fdSpKpMsfhPUL8OIp7qYGRyoOT0H6KXQx3Dqa9tjELHFrACz7Ul4/KbsAtPPZxyB9
icaQ==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;
d=1e100.net; s=20210112;
h=to:subject:message-id:date:from:in-reply-to:references:mime-version
:x-gm-message-state:from:to:cc:subject:date:message-id:reply-to;
bh=Bk/Hr4KJWCbr1rAUaGhnI3X5mEGSt6tnJQ1h9azOKkE=;
b=kg/1sgBOA+C851fsnuN1sSRaixPcUQQpcOOAg5MCUSqozbSND/oW3EwOp8VeVM6lwq
qgrFhUQE7jHJb2quKgaB8SSrBrQJnhiAHmxmZg1ObZO+sLWkTeWweCjaoCb3l4/gyGnP
4ERM/RDXh6Y6VVPo3ujBAKyFuFzq8G4/h/LZgTKiJs5CjR9TRykLcdp+Rm/alN42cynb
+Q/T0dtGlKeqRt+cClqoWSzpExsD/egS49w4JRzd/OIYLwlsbav8cRrxDqpoJo2p9TeS
68iy0HaB3uCtaVJBT5F4PY+sZDv7KXxo8ZvKDa95SFhmUFJbSuEg8u0wg69dIrpc/CxQ
uN7g==
X-Gm-Message-State: AO0yUKU6ainuUpf3aGmzveam9pfzECkOYg5iN8ut86g8dx5COOr/TTxp
NV4DutV7w3uz7myJJLMH0REc7XdQsY+HB6TBA2giAGOd6h2HgIILmIM=
X-Google-Smtp-Source: AK7set/iGyDksCbeGRbPpGwFgaia0yBwHcDo4GIhWf11uvsXjnJqgupMcMgpTgtIJ5lCJ97+Sfcx82NI7zkZlwDZ7rg=
X-Received: by 2002:a5b:ec3:0:b0:861:a3bc:3a24 with SMTP id
a3-20020a5b0ec3000000b00861a3bc3a24mr33255ybs.238.1676988631096; Tue, 21 Feb
2023 06:10:31 -0800 (PST)
MIME-Version: 1.0
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>
In-Reply-To: <64e65e84-d384-807c-092c-a231046c3b1e@lcrcomputer.info>
From: James Bryan
Date: Tue, 21 Feb 2023 14:10:18 +0000
Message-ID: <CAPKJoo7APptVwQSMv1Vxbw+8FfH89s9jP=M00+gM63Tr70B7pw@mail.gmail.com>
Subject: Re: [SurgeMail List] Hybrid Mail System (Multiple Delivery)
To: surgemail-list@netwin.co.nz
X-Originating-IP: 209.85.219.182
X-Country: code=US country="United States" ip=209.85.219.182
X-Qnum: 6166351
X-ORBS-Stamp: hostkarma_yellow, hostkarma_quitok
X-Rcpt-To: <surgemail-list@netwin.co.nz>
X-SpamDetect: *****: 5.0 sd=5.0 NoRule 0.90(X-Phrase:isspam) 0.10(X-myrbl:Color=yellow) 0.21(genuine_gmail) 0.26(free_email) 0.28(X-ORBS-Stamp:yellow) 0.71(BContent2) 0.32(FakeURL) 0.37(X-Verify-Helo:+OK) 0.39(genuine) 0.39(dkimok) 0.41(StandardTLD) 0.42(X-NotAscii:utf) 0.53(From: ends in numbers) 0.48(spfpass) 0.49(X-LangGuess:English) Saned 5.0 sanitym 4.2 -> 5.0 NotSaned s=4.2 was=5.0 Sval 4.2
X-NotAscii: charset=utf-8
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 mail-yb1-f182.google.com
X-Dmarc: none, from=farmv52@gmail.com, dkim=Good known=False spf=True
Authentication-Results: netwin.co.nz header.from=gmail.com; dkim=pass (good signature)
X-Encryption: SSL encrypted
X-MyRbl: Color=Yellow Age=1635 Spam=468 Notspam=358 Stars=27532 Good=214010 Friend=318428 Surbl=340 Catch=49 r=0.016 ip=209.85.219.182
X-IP-stats: Catcher Incoming Last 5, First 689, in=20, out=0, spam=0 ip=209.85.219.182
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
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