Re: [Exim] Exim and Exchange

Page principale
Supprimer ce message
Répondre à ce message
Auteur: Bob Franklin
Date:  
À: JAC Software
CC: exim-users
Sujet: Re: [Exim] Exim and Exchange
On Tue, 25 Jun 2002, JAC Software wrote:

>     I'll see if I can get someone with an Exim box to run the -v option,
> but otherwise I guess I will just have to keep searching.


Doing a quick test from one of our mail gateways gives the same error:


exim@vimg1% exim -f r.c.franklin@??? -v unknown-person@???
From: r.c.franklin@???
To: unknown-person@???
Subject: Test message

This is a test message related to the problem reported on exim-users.
.
LOG: 0 MAIN
<= r.c.franklin@??? U=exim P=local S=393
Exim version 3.36 debug level 1 uid=<UID> gid=<GID>
probably ndbm
delivering message 17MUh0-0001PM-00
exim@vimg1% Connecting to mail.mgr.com.au [203.48.133.10.25] ... connected
SMTP<< 220 mgrsr02.mgr.com.au Microsoft ESMTP MAIL Service, Version:
5.0.2195.2966 ready at Tue, 25 Jun 2002 00:21:27 +1000
SMTP>> EHLO vimg1.rdg.ac.uk

  SMTP<< 250-mgrsr02.mgr.com.au Hello [134.225.112.81]
         250-TURN
         250-ATRN
         250-SIZE
         250-ETRN
         250-PIPELINING
         250-DSN
         250-ENHANCEDSTATUSCODES
         250-8bitmime
         250-BINARYMIME
         250-CHUNKING
         250-VRFY
         250-X-EXPS GSSAPI NTLM LOGIN
         250-X-EXPS=LOGIN
         250-AUTH GSSAPI NTLM LOGIN
         250-AUTH=LOGIN
         250-X-LINK2STATE
         250-XEXCH50
         250 OK

SMTP>> MAIL FROM:<r.c.franklin@???> SIZE=1426
SMTP>> RCPT TO:<unknown-person@???>
SMTP>> DATA

SMTP<< 250 2.1.0 r.c.franklin@???....Sender OK
SMTP<< 250 2.1.5 unknown-person@???
SMTP<< 354 Start mail input; end with <CRLF>.<CRLF>
SMTP>> writing message and terminating "."

SMTP<< 500 5.3.3 Unrecognized command
SMTP>> QUIT

LOG: 0 MAIN
** unknown-person@??? R=smtp_internet T=remote_smtp: SMTP error
from remote mailer after end of data: host mail.mgr.com.au
[203.48.133.10]: 500 5.3.3 Unrecognized command


... so I guess the problem is somewhere during the DATA portion of the
transfer. I've done a snoop and can't spot anything untoward - the DATA
portion seems to transfer and then you get this error back at the end,
after the terminating '.' is sent.

I can't seem to get the same error by using telnet and sending similar
lines manually - so I'm probably missing out something subtle in the lines
sent.

- Bob


--
 Bob Franklin <r.c.franklin@???>          +44 (0)118 931 6630
 Systems and Communications, IT Services, The University of Reading, UK