Okay, let's see if I can address a few gaps in my plea. Wasn't it SIMS Discussions [EMAIL PROTECTED] who once said...
>From: Global Homes Webmaster <[EMAIL PROTECTED]> >Subject: Re: Slightly OT: Network resources needed for dying mail > > >On 09/17/02 at 14:23, NetHead wrote: > >> I've posted a couple of questions about this before. We have a company in >> the UK with which we need to exchange e-mail. We can receive mail from >> them just fine. However, any e-mail addressed to them from within our >> network will fail. > >Fail how? Does SIMS bounce the messages? Does the UK server bounce them? In >either case, what does the bounce message say? Does SIMS accept messages >and then fail to transmit them without bouncing? If so, does SIMS log any >error(s)? The first thing you need to determine is where the failure is >occuring. Is it on your server, on the destination server, your network, >their network, or somewhere in the 'net in between? Okay, to be more specific, we cannot make a connection to their mail server from behind our isp's router. Telnet on port 25 will not connect; SMTP will not connect; nothing will connect if I am behind my isp's router. Sounds almost like it's their router doesn't it? But it is only items addressed to "pecandeluxe.co.uk" or "legend.co.uk" (which is the host for "pecandeluxe.co.uk") that fail. I can reach you guys here at "stalker.com"; I can even reach another "uk" domain, "eclipse.co.uk". Hmmmm.... SIMS eventually "gives up" trying to deliver the mail with the following error: -----begin message snippet----- Failed to deliver your message to [EMAIL PROTECTED]: SMTP: Connection is broken Cannot speak with 'mx.legend.co.uk' for 16 hours. Reporting-MTA: dns; pecandeluxe.com Final-Recipient: rfc822; [EMAIL PROTECTED] Action: failed Status: 5.0.0 -----end message snippet----- > [snip] >> I don't really think this forum is the proper place to address this issue >> any further. > >Why not? It seems on-topic to me -- it involves a question of getting mail >to be delivered by a SIMS server. Whether or not the failure is SIMS' >fault, SIMS is still a part of the equation and if you can find a solution >it might benefit others on the list. I felt this might not be the place because I've pretty well ruled out SIMS as being the problem. The problem seems to lie with the "foreign" isp (as best we can tell), but they deny that they are the problem. I'm hoping to find some tool or resource that might help me diagnose the "path" of the mail, determine where it is stalling and why. I'm certainly willing to discuss this in the list... I just didn't want to be a "burden" to the group. > >> But I could use some recommendations as to a good place to >> seek help. [snip] >> Or if you know of a network "tool" >> that would allow me to test the connections and determine what the source >> of the block is, I'd be grateful. > >Turn SIMS' SMTP logging all the way up to 'All Info', then try to send a >message to the 'problem' server and see what SIMS logs. That should tell >you 1) whether SIMS can make a connection to the UK server to begin with >and 2) if so, where in the SMTP exchange things go awry (if that's where >the problem lies). I have had logging up all the way for some time. No help there that I can see. -----begin log snippet----- 08:26:49 5 SYSTEM Line Read: To: "AMK" <[EMAIL PROTECTED]>, <[EMAIL PROTECTED]>, "'SH (E-mail)'" <[EMAIL PROTECTED]> 08:26:49 5 SYSTEM Line Read: cc: "'JM (E-mail)'" <[EMAIL PROTECTED]>, "'E (E-mail)'" <[EMAIL PROTECTED]>, "'N (E-mail)'" <[EMAIL PROTECTED]> 08:26:49 4 SMTP Line 4967 created for pecandeluxe.co.uk, [S.0000015506] 08:26:49 4 SMTP-967(pecandeluxe.co.uk) Got 1 relay(s) 08:26:49 5 SMTP-967(pecandeluxe.co.uk) *Status=7 08:26:49 4 SMTP-967(pecandeluxe.co.uk) Looking for mx.legend.co.uk. 08:26:49 5 SMTP-967(pecandeluxe.co.uk) *Status=9 08:26:49 5 SMTP-967(pecandeluxe.co.uk) *Status=8 08:30:35 3 SMTP-967(pecandeluxe.co.uk) Failed to connect to [212.69.225.52:25]. reason=60 08:30:35 5 SMTP-967(pecandeluxe.co.uk) *Status=9 08:30:35 5 SMTP-967(pecandeluxe.co.uk) *Status=7 08:30:35 3 SMTP-967(pecandeluxe.co.uk) No relay address is accessable. Error Code=-25010 08:30:35 5 SMTP-967(pecandeluxe.co.uk) *Status=2 -----end log snippet----- If anybody sees something here, please speak up. >You might also want to try to telnet to port 25 on the >UK machine from your SIMS server and see if you can conduct an SMTP >conversation manually. If the other server will accept messages, but not >deliver them to their recipients, then the problem is on the other end. If >you can get the cooperation of the UK server's admin, you might ask what >their server logs show. > I'm sorry I failed to mention that I have made numerous attempts to connect to port 25 on their mail server via telnet. They all fail after a period of time... several minutes at least. Similar to what happens with the email; SIMS makes a valiant attempt to speak with the server and then gives up. I have had the same result with various machines (including the SIMS server). I have even disconnected my entire network, hooked a single machine to my isp's router, and STILL a telnet connection will not go through. What is very odd is that if I get out from behind my isp's router, say via a dial-up connection (or if one of you were to try it from your location), then the telnet connection goes through. It is something about the specific path from our router to Legend's mail server. But neither our isp nor Legend can determine what the problem is. Heck, they both deny that there is a problem on there respective ends. >------------------------------ > >Date: Tue, 17 Sep 2002 22:21:56 -0500 >Subject: Re: Slightly OT: Network resources needed for dying mail >From: Larry Stone <[EMAIL PROTECTED]> > > >On 9/17/02 2:23 PM, NetHead at [EMAIL PROTECTED] wrote: > >> Or if you know of a network "tool" >> that would allow me to test the connections and determine what the source >> of the block is, I'd be grateful. > >I'll echo the Telnet suggestion. In case you don't know how to do it, Telnet >to port 25 at the destination and then go through SMTP dialogue seeing what >sort of response you get at each point. >HELO your host name >MAIL FROM:<sender@yourdomainname> >RCPT TO:<recipient@theirdomainname> >DATA >type some text ending with just a period on one line >. >QUIT See the notes about the telnet problems above. Is there some way, if I make a telnet connection via dial-up, that I can query there SMTP server to see why it is rejecting e-mail from our mail server? I'm not very versed in much telnet syntax. I can make connections and that's about it. Thanks for the responses, though. On one final note, I got a phone call from another local SIM user who suggested that I set up a "routing" to use another mail server to pass the message to "pecandeluxe.co.uk". Either I'm too stupid to figure it out or the documentation for SIMS is lacking in this area. I tried a couple of the mail-exchangers that my isp has. I set up a routing in SIMS like this: "[EMAIL PROTECTED]" But I get this response: -----begin error message----- Failed to deliver your message to [EMAIL PROTECTED]: SMTP: Address rejected by host Host 'anotherhost.myisp.com' says: 553 <[EMAIL PROTECTED]>... Not server for myispsmailexchanger.myisp.com -----end error message----- Perhaps someone could enlighten me as to the right way to set up such a scheme? Thanks, again, all. Sorry this is so looooonng (re: recent complaints about quoted material), but I didn't see any other way to communicate all of this. ================================================ | Doug Starkey | | Network Administrator | | Pecan Deluxe Candy Company | | 2570 Lone Star Drive | | Dallas, TX 75212-6308 | | e-mail: [EMAIL PROTECTED] | | voice: 214-631-3669 Ext. 108 | | fax: 214-631-5833 | ================================================ ############################################################# 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]>
