Received-SPF: pass (Last token {include:_netblocks.google.com} (res=PASS)) client-ip=209.85.128.175; envelope-from=<farmv52@gmail.com>; x-ip-name=mail-yw1-f175.google.com;
X-Received: from mail-yw1-f175.google.com (mail-yw1-f175.google.com [209.85.128.175])
by netwin.co.nz (SurgeMail 7.7d) with ESMTP (TLS) id 6189720-1391920
for <surgemail-list@netwin.co.nz>; Wed, 22 Feb 2023 15:38:30 +0000
X-Return-Path: farmv52
X-Received: by mail-yw1-f175.google.com with SMTP id 00721157ae682-536bbef1c5eso115800307b3.9
for <surgemail-list@netwin.co.nz>; Wed, 22 Feb 2023 07:38:30 -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=7m95CawFBbw87FR6+NjP9oyH44531ifdy9iqvs+pPA4=;
b=U/1rdQ0d+mX3Jk33KRpMCbyDH3ZfrO5JGZdTgRqdbc5oRWSctkoXfR12oWAXN1XL3r
xxYJzJGnO34kWBgbLnn/IsrBwTXYJMzLcmJ70jIz3jcruO5CjFtjM9PRn5JoqDxntQPv
D74FI/6JVawr6Kvfzw9mEAZIMC+eQ7acMeBpCNCzL0DaPPO2dBPh6KG7Uo9D4vyDxzle
2aFgI4RdqK3rSCYsgipHQt1U8cvYyCLBDZtz/gxuoWZLkrgRoXbsDflpxkHpbgFLU007
rMTe/JpIeRyS4sPd9NO87/2ztrDnhk6/dcQgAgUYBNxuYjmOoQSCVvzgRuGKy3cbrAEd
uG5A==
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=7m95CawFBbw87FR6+NjP9oyH44531ifdy9iqvs+pPA4=;
b=nHeu4xDt/q0vN0bH2ZeF8V6KiOZJR1WcgIWxyAh8bGz2rt4IScaJhbNb5PB6l7q+sS
JEiadDFanJ0CktAqtdxmcwi+bc5YxjDZUUlLmG7zIVQYx91GYk+z6oncsfBz5u0aEwix
MZH5/GNpjCqp+3Zo2yM618A1RwJamgF3/McoBYHXHp2Uz+sB0S4NIRcgjyuKKTcjocC4
VUaTssV9ZCfWWFmc5sgRf/ij/CrN4WpvHcTiA3wrAao5SrXT++CdNzNikvefmq43zVB/
oiORX2TVHCZtHk04awV0cxWR4D5K2/xa+gdq/Sxun0NgATNeypYIq+kQaUrw+gC0JAxU
q42g==
X-Gm-Message-State: AO0yUKVRxX8tnWt4TpDCsZQeu+GjHC5Est5UKwAbX1mCV99a1MPO6zVs
AtJ68NwNrBJw+lI/2Kr+Bz2Zf5r8SyvBnFIb7n+JpJHsUP+uGY7XZkV1Jw==
X-Google-Smtp-Source: AK7set9c1DtglWJhO5CLDaJayu7dJnRRMYzHz2mXWhkavfPl4fqksRa/JpH/x3TIwtTBoQLLrVMaqJUhY00H4jT5KFg=
X-Received: by 2002:a81:af50:0:b0:533:9ffb:cb12 with SMTP id
x16-20020a81af50000000b005339ffbcb12mr917489ywj.10.1677080309072; Wed, 22 Feb
2023 07:38:29 -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> <CAPKJoo7APptVwQSMv1Vxbw+8FfH89s9jP=M00+gM63Tr70B7pw@mail.gmail.com>
<e9a7048f-4ca5-9da6-ac2a-ed4683907ba9@lcrcomputer.info>
In-Reply-To: <e9a7048f-4ca5-9da6-ac2a-ed4683907ba9@lcrcomputer.info>
From: James Bryan
Date: Wed, 22 Feb 2023 15:38:17 +0000
Message-ID: <CAPKJoo4QGOk-tGqqCoR3ZDtS_7hYws-qkKE=EgDFLn0t5TbyUg@mail.gmail.com>
Subject: Re: [SurgeMail List] Hybrid Mail System (Multiple Delivery)
To: surgemail-list@netwin.co.nz
X-Originating-IP: 209.85.128.175
X-Country: code=US country="United States" ip=209.85.128.175
X-Qnum: 6189720
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.69(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 3.5 -> 5.0 NotSaned s=3.5 was=5.0 Sval 3.5
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-yw1-f175.google.com
X-Dmarc: none, from=farmv52@gmail.com, dkim=Good known=True spf=True
Authentication-Results: netwin.co.nz header.from=gmail.com; dkim=pass (good signature)
X-Encryption: SSL encrypted
X-MyRbl: Color=Yellow Age=2010 Spam=193 Notspam=177 Stars=9974 Good=160513 Friend=191613 Surbl=293 Catch=19 r=0.012 ip=209.85.128.175
X-IP-stats: Incoming Last 26, First 25, in=1, out=0, spam=0 ip=209.85.128.175
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
Let me explain with process diagram (Remote server Mail1 and Mail2 is not surgemail and has different platform)
First one is show when incoming
email to
user2@email.com then surgemail will verify both servers if use
exists and send a message to Mail2 that they have a user2 account.
The second will show when incoming email to non-exist email account, surgemail needs to verify both servers if all servers return non-exist accounts then reject to sender.
Surgewall will normally forward incoming message to one of servers in the list if it connectable, try the next one if have more than one.
So It need to add new surgewall option for this mode and add some extra function to verify account in all servers and reject only if all server return non-exist account and once it found server that they have account and send it later to that one.
This might be a feature request.
James
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