*This message was transferred with a trial version of CommuniGate(tm) Pro*
Имеем след. ситуацию:
adsl.user и dial-up.user не присутствуют в списке Client IP Addresses.
В свойствах обоих юзеров стоит: AccessModes =
(12,Mail,POP,WebMail,Relay,Mobile,TLS)
У сервера:
AUTH to: "everybody"
When used by an Authenticated Mobile User: Process as a Client Address -
checked
Relay to Any IP Address: If Received from: "Clients" IP Address
Почему в первом случае релей проходит (хотя не должен)? IP у adsl.user
не изменяется.
И второй вопрос - почему клиентское ПО не посылает AUTH для версии
сервера 4.0b6 (в 4.0b5 вроде работало)
16:33:14.48 4 SMTPI-00005([adsl.user]) got connection on [somehost.ip:25]
16:33:14.48 5 SMTPI-00005([adsl.user]) out: 220 somehost.ru ESMTP
CommuniGate Pro 4.0b6 is glad to see you!\r\n
16:33:14.60 5 SMTPI-00005([adsl.user]) inp: HELO user
16:33:14.60 5 SMTPI-00005([adsl.user]) out: 250 somehost.ru we trust you
user\r\n
16:33:14.72 5 SMTPI-00005([adsl.user]) inp: MAIL FROM: <user1@energy.kz>
16:33:14.72 5 SMTPI-00005([adsl.user]) out: 250 user1@somehost.ru sender
accepted\r\n
16:33:14.84 5 SMTPI-00005([adsl.user]) inp: RCPT TO: <remuser@boeing.com>
16:33:14.84 5 SMTPI-00005([adsl.user]) out: 250 remuser@boeing.com will
relay mail from a client address\r\n
16:33:14.96 5 SMTPI-00005([adsl.user]) inp: DATA
19:08:38.32 4 SMTPI-00001([dial-up.user]) got connection on [somehost.ip:25]
19:08:38.32 5 SMTPI-00001([dial-up.user]) out: 220 somehost.ru ESMTP
CommuniGate Pro 4.0b6\r\n
19:08:38.51 5 SMTPI-00001([dial-up.user]) inp: EHLO jscwv8gvj03fui
19:08:38.51 5 SMTPI-00001([dial-up.user]) out: 250-somehost.ru domain
name should be qualified
jscwv8gvj03fui\r\n250-HELP\r\n250-PIPELINING\r\n250-ETRN\r\n250-DSN\r\n250-TURN\r\n250-ATRN\r\n250-SIZE
19:08:38.78 5 SMTPI-00001([dial-up.user]) inp: MAIL FROM:
<user2@somehost.ru>
19:08:38.78 5 SMTPI-00001([dial-up.user]) out: 250 user2@somehost.ru
sender accepted\r\n
19:08:39.00 5 SMTPI-00001([dial-up.user]) inp: RCPT TO: <dio_13@mail.ru> 19:08:39.00 4 SMTPI-00001([dial-up.user]) checking MX-record for mail.ru 19:08:39.14 4 SMTPI-00001([dial-up.user]) checking relay mxs.mail.ru 19:08:39.29 3 SMTPI-00001([dial-up.user]) Recipient dio_13@mail.rurejected: relaying prohibited. You should authenticate first 19:08:39.29 5 SMTPI-00001([dial-up.user]) out: 473 dio_13@mail.ru relaying prohibited. You should authenticate first\r\n 19:08:42.27 5 SMTPI-00001([dial-up.user]) inp: QUIT 19:08:42.27 5 SMTPI-00001([dial-up.user]) out: 221 somehost.ru CommuniGate Pro SMTP closing connection\r\n 19:08:42.27 4 SMTPI-00001([dial-up.user]) closing connection 19:08:42.27 4 SMTPI-00001([dial-up.user]) releasing stream
Тут мы быстро откатились на версию 3.5.9 и сразу же получили AUTH от клиента (за время тестирования изменения в настройках клиентского ПО не проводились) .
19:09:27.78 4 SMTPI-00001([dial-up.user]) got connection on
[somehost.ip], port 25
19:09:27.78 5 SMTPI-00001([dial-up.user]) out: 220 somehost.ru ESMTP
CommuniGate Pro 3.5.9\r\n
19:09:27.98 5 SMTPI-00001([dial-up.user]) inp: EHLO jscwv8gvj03fui
19:09:27.99 5 SMTPI-00001([dial-up.user]) out: 250-somehost.ru domain
name should be qualified
jscwv8gvj03fui\r\n250-HELP\r\n250-PIPELINING\r\n250-ETRN\r\n250-DSN\r\n250-TURN\r\n250-ATRN\r\n250-SIZE
19:09:28.22 5 SMTPI-00001([dial-up.user]) inp: AUTH LOGIN 19:09:28.22 5 SMTPI-00001([dial-up.user]) out: 334 VXNlcuaWtvbm5hbWU6\r\n 19:09:28.40 5 SMTPI-00001([dial-up.user]) inp: YS5Nlcm5huaWtvbGF5ZXY= 19:09:28.40 5 SMTPI-00001([dial-up.user]) out: 334 UGFzc3dvcnaGZkzmQ6\r\n 19:09:28.58 5 SMTPI-00001([dial-up.user]) inp: WXRnaGZkzc3dYmtteWo= 19:09:28.58 2 SMTPI-00001([dial-up.user]) 'user2@somehost.ru' connectedfrom [dial-up.user](temp client)
19:09:28.58 2 SMTPI-00001([dial-up.user]) 'user2@somehost.ru' disconnected ([dial-up.user]) 19:09:28.58 5 SMTPI-00001([dial-up.user]) out: 235 user2@somehost.rurelaying authenticated\r\n
Спасибо.
Николаев Антон. Получено Fri Aug 09 07:50:38 2002
Этот архив был сгенерирован hypermail 2.1.8 : Fri 24 Apr 2015 - 16:12:13 MSK