Relaying Mail

Jeffrey Lee

unread,

Jun 29, 2005, 7:04:50 PM6/29/05

to

What is the easiest way to migrate a domain to another server?

I would like to catch all mail going to domain.com and send it to the
respective accounts at stmp.otherdomain.com until the dns changes
take effect. This way no one loses email.

Thanks,
Jeff

#############################################################
This message is sent to you because you are subscribed to
the mailing list <CGat...@mail.stalker.com>.
To unsubscribe, E-mail to: <CGateP...@mail.stalker.com>
To switch to the DIGEST mode, E-mail to <CGatePr...@mail.stalker.com>
To switch to the INDEX mode, E-mail to <CGatePr...@mail.stalker.com>
Send administrative queries to <CGatePro...@mail.stalker.com>

Fred Skrotzki

unread,

Jun 29, 2005, 7:45:40 PM6/29/05

to

better way is to decrease the TTL on the domain in question a few days before hand, then with say a 5 minute ttl you just switch it and away you go.

Other way is assuming the users exist already on new server is to insert the new mx value in DNS with lower number then current so as soon as the new system is up it starts using that one.

Otherwise you can just use router record to forward all e-mail from your current server to the new one.

<*@example.com> = *%examp...@newmail.example.com.smtp

JORGE RUBEN MACIAS LOPEZ

unread,

Jun 29, 2005, 11:10:26 PM6/29/05

to

Hi guys

I'm trying to set an AXIS 210 Network Camera to relay its
emails notifications using one of our CGPro serves, but so
far I've been unable to make it work. The Camera only asks
the ip address of the smtp server, and whether it needs to
authenticate, case in which one has to fill the login,
password and the weakest auth method allowed (one of plain,
login, carm-md5 and digest-md5).

I get the following in cgpro log:

21:44:06.08 5 SMTP connection request from
[201.128.51.243:2455], socket=15
21:44:06.08 4 SMTPI-17112([201.128.51.243]) got connection
on [207.249.74.204:25]
21:44:06.08 5 SMTPI-17112([201.128.51.243]) out: 220
mexis.net ESMTP CommuniGate Pro 4.3.5\r\n
21:44:06.12 5 SMTPI-17112([201.128.51.243]) inp: EHLO
AxisProduct.gateway.2wire.net
21:44:06.12 5 SMTPI-17112([201.128.51.243]) out:
250-mexis.net we trust you
AxisProduct.gateway.2wire.net\r\n250-DSN\r\n250-SIZE\r\n250-STARTTLS\r\n250-AUTH=LOGIN\r\n250-AUTH
LOGIN PLAIN CRAM-MD5
DIGEST-MD5\r\n250-ETRN\r\n250-TURN\r\n250-ATRN\r\n250-NO-SOLICITING\r\n250-8BITMIME\r\n250-HELP\r\n250-P
21:44:06.16 5 SMTPI-17112([201.128.51.243]) inp: AUTH
DIGEST-MD5
21:44:06.16 4 SMTPI-17112([201.128.51.243])
SASL-0(DIGEST-MD5) out:
nonce="17112a1120099445amexis.net",qop="auth",algorithm=md5-sess
21:44:06.16 5 SMTPI-17112([201.128.51.243]) out: 334
bm9uY2U9IjE3MTEyYTExMjAwOTk0NDVhbWV4aXMubmV0Iixxb3A9ImF1dGgiLGFsZ29yaXRobT1tZDUtc2Vzcw==\r\n
21:44:06.28 5 SMTPI-17112([201.128.51.243]) inp:
dXNlcm5hbWU9ImptYWNpYXNsQG1leGlzLm5ldCIsIG5vbmNlPSIxNzExMmExMTIwMDk5NDQ1YW1leGlzLm5ldCIsIGNub25jZT0iOTk0MmI3NjlkZjRjYmI4NyIsIG5jPTAwMDAwMDAxLCBxb3A9YXV0aCwgZGlnZXN0LXVyaT0iU01UUC8yMDcuMjQ5Ljc0LjIwNCIsIHJlc3BvbnNlPTk0ODVjMmI5ZWExMzk3ZWM0ZDcwYzFhNGQwMGU
21:44:06.28 4 SMTPI-17112([201.128.51.243])
SASL-0(DIGEST-MD5) inp: username="axi...@mexis.net",
nonce="17112a1120099445amexis.net",
cnonce="9942b769df4cbb87", nc=00000001, qop=auth,
digest-uri="SMTP/207.249.74.204",
response=9485c2b9ea1397ec4d70c1a4d00e89e3, maxbuf=2738,
authzid="axis01@mexis.n
21:44:06.28 1 ACCOUNT(axis01) incorrect password. Login
attempt(SMTP) from [201.128.51.243]
21:44:10.28 5 SMTPI-17112([201.128.51.243]) out: 535 (515)
incorrect password or account name\r\n
21:44:10.31 3 SMTPI-17112([201.128.51.243]) read failed.
Error Code=connection closed by peer
21:44:10.31 4 SMTPI-17112([201.128.51.243]) closing
connection
21:44:10.31 4 SMTPI-17112([201.128.51.243]) releasing
stream

the account being used is axis01, I've tried with and
without @mexis.net and I've tried choosing the 4 different
options for the weakest method, but it seems the Axis devie
always ends using DIGEST-MD5, I've tried using an account
which has a clear text password in cpgro and also with
encrypted passwords, but I get the same result.

This problem occurs with CGP 4.3.5 and also with 4.1.8, in
either case we are not advertising msn or kerberos methods.
From Thunderbird I can authenticate with no problem, and
seeing in the logs I find I end up using an CRAM-MD5
method, so maybe this is some weird issue with DIGEST-MD5?

Any ideas?

Thanks,

Jorge