I use Mail.app on 3 machines - all work fine with Sims. Sims runs on a OS 9.1 machine.
>From your logs it looks like you have not authenticated your SMTP session with Sims. also >>>> 18:09:34 4 SMTP-720(eranet.pl) Looking for eranet.pl >>>> 18:10:09 3 SMTP-719(eranet.pl) Failed to verify. Real address is >>>> [192.168.203.16:49155] someone commented that it was taking Sims 35+ seconds to do a lookup. These are 2 different SMTP sessions. It looks like Mail.app always sends as the name of the domain it is sending mail from as the argument to HELO or EHLO. Michael on 3/5/03 7:12 PM, Bill Cole at [EMAIL PROTECTED] wrote: > At 5:50 PM +0100 3/5/03, Krzysztof Szeloch imposed structure on a > stream of electrons, yielding: >> Bill, >> >> The domain assigned to SIMS is bulls.com.pl >> >> I can't send any mail from Mail under Mac OS X through SIMS. Neither >> when I send it as [EMAIL PROTECTED] (one of e-mail accounts) nor >> when I send as [EMAIL PROTECTED] (another identity). >> >> As I mentioned before no problem with sending any mail from the same >> Mac from Eudora 5.2 OSX. >> >> It looks like Mail's bug. Am I right? > > > I think so. it seems to be using a wrong identity in the SMTP HELO > command and it seems to be giving up on getting a response from SIMS > too fast. > > >> Krzysztof >> >> >> >> >> On Wednesday, March 5, 2003, at 06:06 AM, Bill Cole wrote: >> >>> At 6:28 PM +0100 3/4/03, Krzysztof Szeloch imposed structure on a >>> stream of electrons, yielding: >>>> Christian, >>>> >>>> I have increased SIMS' SMTP log sensitivity, and tried to send >>>> something from Mail through SIMS again. >>>> >>>> Here is the the part of the log: >>>> >>> >>> [...] >>> >>>> 18:09:34 5 SMTP-720() Stream Created >>>> 18:09:34 5 SMTP(720) Resolver Created >>>> 18:09:34 4 SMTP Line 720 created for answering >>>> 18:09:34 4 SMTP-720() Got connection from [192.168.203.16:49156] >>>> 18:09:34 4 SMTP(tcp) Connection accepted from >>>> [192.168.203.16:49156], seq=571, 11/12 >>>> 18:09:34 4 SMTP-720([192.168.203.16]) Sending 220-bulls.com.pl >>>> Stalker Internet Mail Server V.1.8b9d14 is ready.\r\n220 ESMTP is >>>> spoken here. You are very welcome\r\n >>>> 18:09:34 5 SMTP-720([192.168.203.16]) OT 116 of 116 bytes sent, Flags=0 >>>> 18:09:34 5 SMTP-720([192.168.203.16]) *Status=22 >>>> 18:09:34 5 SMTP-720([192.168.203.16]) Received 16 bytes >>>> 18:09:34 4 SMTP-720([192.168.203.16]) Input Line: HELO eranet.pl\r >>>> 18:09:34 5 SMTP-720([192.168.203.16]) *Status=21 >>>> 18:09:34 4 SMTP-720(eranet.pl) Looking for eranet.pl >>>> 18:10:09 3 SMTP-719(eranet.pl) Failed to verify. Real address is >>>> [192.168.203.16:49155] >>>> 18:10:09 4 SMTP-719(eranet.pl) Sending 250-bulls.com.pl cannot >>>> verify eranet.pl\r\n250-HELP\r\n250-ETRN\r\n250 EHLO\r\n >>>> 18:10:09 5 SMTP-719(eranet.pl) OT 72 of 72 bytes sent, Flags=0 >>>> 18:10:09 5 SMTP-719([192.168.203.16]) *Status=22 >>>> 18:10:09 3 SMTP-719([192.168.203.16]) Abort Received, reason=54 >>>> 18:10:09 4 SMTP-719([192.168.203.16]) Nothing read - stream broken >>>> 18:10:10 3 SMTP-719([192.168.203.16]) Reading Failed. Error >>>> Code=-25010. Read: >>> >>> [...] >>> >>>> Does it say anything to you? >>> >>> >>> Yes. >>> >>> For some reason, the client is announcing itself as 'eranet.pl' and >>> for some equally unknown reason, SIMS is taking a fairly long time >>> (35 seconds) to check that name for resolution back to the >>> connecting address and coming up without anything. It seems that >>> the client is unwilling to wait that long and is just dropping the >>> connection. >>> >>> There are actually 3 problems here: >>> >>> 1. The client is claiming to be 'eranet.pl' which it clearly is >>> not. This is either a client bug or a problem with the >>> configuration of the machine it is running on. The proper HELO >>> argument is a fully qualified domain name which does in fact >>> identify the machine sending the HELO command. >>> >>> 2. SIMS is failing to resolve eranet.pl and is taking a long time >>> to fail. I can resolve eranet.pl in under a second and I'm on a >>> different continent. This hints at SIMS having very bad DNS at its >>> disposal. >>> >>> 3. The client is giving up on SIMS in less than 35 secconds. This >>> is simply too short a timeout for an SMTP client. SMTP servers may >>> do name resolutions at many points in a transaction, and name >>> resolutions by their nature can stall for fairly long times. Even >>> 60 seconds might be a little too aggressive a timeout, but 35 >>> seconds is silly. >>> -- >>> Bill Cole [EMAIL PROTECTED] >> >> >> ############################################################# >> This message is sent to you because you are subscribed to >> the mailing list <[EMAIL PROTECTED]>. >> To unsubscribe, E-mail to: <[EMAIL PROTECTED]> >> To switch to the DIGEST mode, E-mail to <[EMAIL PROTECTED]> >> To switch to the INDEX mode, E-mail to <[EMAIL PROTECTED]> >> Send administrative queries to <[EMAIL PROTECTED]> ############################################################# This message is sent to you because you are subscribed to the mailing list <[EMAIL PROTECTED]>. To unsubscribe, E-mail to: <[EMAIL PROTECTED]> To switch to the DIGEST mode, E-mail to <[EMAIL PROTECTED]> To switch to the INDEX mode, E-mail to <[EMAIL PROTECTED]> Send administrative queries to <[EMAIL PROTECTED]>
