Dennis, I wouldn't worry about any problems you have with anything at Allegiance Telecom. They are a communications conglomerate that tried to purchase and merge a bunch of small and local telephone and internet service providers who were all doing very well independently. They promised to maintain the service levels of all the companies they bought, promised to hold the prices, etc, etc, etc, etc.
They then doubled and tripled the prices, closed all of the local offices, virtually eliminated customer service, lost most of the customer base they purchased with the small local companies they bought and ran the company into bankruptcy. They still have a bunch of DNS servers and validation servers sitting all over the country that are havens for spammers, thousands of cancelled accounts that are still active and people who used to pay for those accounts can still access their e-mail and web sites they were once paying for. All of the companies that Allegiance once purchased to merge together, along with XO communications, are now owned by Quest Communications, the former aggregator who is now the new owner of the "baby bell" that services the Seattle Washington area. You probably guessed it as well - they just raised all the rates of all the services they provide - once again. I'm in the process of moving a major cable television client from XO communications, because XO could neither get the client's telephone numbers into the national directory database nor make changes to the hunt groups at the client's offices because they said it would take at least 35 days before the order got entered into the system and they refused to give us a due date. We then ordered replacement services from another provider that we have a great relationship with and asked for the existing telephone numbers to be ported to the new provider and the local offices sat on the order, telling us they could not do anything for "a couple of weeks" and wouldn't give us a due date. So much for customer service and so much for having any kind of a record of what they own, where it's located and how it's configured. When it comes to either taking pity on them for a malconfigured server or host, or attempting to get the problem resolved, you will have better luck if you go outside and talk to your car. Bruce Barnes Chicago IL -----Original Message----- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] Behalf Of Tom Kemp Sent: Wednesday, February 18, 2004 09:42 To: [EMAIL PROTECTED] Subject: RE: [IMail Forum] Repost: One domain will not receive our mail Importance: High I had this issue with one domain....algxmail.com. I never was able to resolve it. I, like you, don't believe that it is at my end. I suspected that it was the services that Allegiance used for hosting their email. They used the services of iPlanet.com. If I telneted into these servers...any of the 4 they used, I would have intermittent success with ehlo ahd helo messages getting responses. Dennis T. Kemp II (Tom) Program Manager MCSE/CNA/A+ Control Concepts, Inc. [EMAIL PROTECTED] ICQ#: 157741210 For additional contact information, click below: https://www.cardscan.net/v/?id=98303ssF0Qrf3FdboKaCbijB7g= 703-876-6418 Fax#: 703-876-6416 -----Original Message----- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] Behalf Of James P. Bednarz Sent: Wednesday, February 18, 2004 10:07 AM To: [EMAIL PROTECTED] Subject: [IMail Forum] Repost: One domain will not receive our mail Had internet connection issues... Not sure if this made it to the forum... Folks, I hope you can help. This ones got me twisted in knots. I have Win 2k3 Server IMAIL 8.05 hf1 DNS running on same box Small office, 130 accounts. I have had no problems with any other mail except for one domain. This one domain 99% bounces back after 20 tries. About 1% of the time gets through but usually after 16 to 18 tries. Of course they say it's us, and we say it's them. I have my server running behind a firewall NAT'd to a public address. They can send mail to us with no problems. We cannot send to them. >From my router outside my firewall, I can telnet into their smtp server and any others. From mail server, I cannot telnet into this particular smtp server. However I can telnet into any others (as many that allow that) By this I conclude that port is not blocked in my firewall. Plus, that would cause all mail to fail. No? I can traceroute to it. DNS appears to resolve it correctly. I am getting MX connect fail errors in my log for this address. Why only this address? If I were having problems with dns wouldn't all of my mail get returned? I checked the ip addresses in my registry and everything seems to be in order. Is it because I am running from behind the firewall rather than in the DMZ? Again, if that were the case why would only 1 stinking e-mail get hung up? Arrrrrgh. I am lost. Here is some log for ya.... 02:17 14:53 SMTPD(0020021E) [192.168.0.230] connect 192.168.0.142 port 4570 02:17 14:53 SMTPD(0020021E) [192.168.0.142] EHLO dionysis 02:17 14:53 SMTPD(0020021E) [192.168.0.142] MAIL FROM: <[EMAIL PROTECTED]> 02:17 14:53 SMTPD(0020021E) [192.168.0.142] RCPT TO: <[EMAIL PROTECTED]> 02:17 14:53 SMTPD(0020021E) [192.168.0.142] C:\IMAIL\spool\D71510020021e2e7d.SMD 758 02:17 14:53 SMTP-(08A006A1) processing C:\IMAIL\spool\Q71510020021e2e7d.SMD 02:17 14:53 SMTP-(08A006A1) [x] looking up theirdomain.com in HOSTS and MX 02:17 14:53 SMTP-(08A006A1) Info - DNS Cache full, deleting last item (somethingelse.gov) 02:17 14:53 SMTP-(08A006A1) Info - Adding theirdomain.com to DNS cache - TTL = 3600 02:17 14:53 SMTP-(08A006A1) Trying theirdomain.com (0) 02:17 14:53 SMTP-(08A006A1) [x] Connecting socket to service <SMTP> on host <theirdomain.com> using protocol <tcp> 02:17 14:53 SMTP-(08A006A1) Info - Found theirdomain.com in DNS Cache 02:17 14:54 SMTP-(08A006A1) MX connect fail "xxx.xxx.xxx.xxx" 02:17 14:54 SMTP-(08A006A1) MX connect fail "xxx.xxx.xxx.xxx" 02:17 14:54 SMTP-(08A006A1) Info - Adding theirdomain.com to temporary skip list 02:17 14:54 SMTP-(08A006A1) requeuing C:\IMAIL\spool\Q71510020021e2e7d.SMD R0 T1 02:17 14:54 SMTP-(08A006A1) finished C:\IMAIL\spool\Q71510020021e2e7d.SMD status=3 James P. Bednarz - PC Systems Coordinator Kaestle Boos Associates, Inc. Teamwork Rules! To Unsubscribe: http://www.ipswitch.com/support/mailing-lists.html List Archive: http://www.mail-archive.com/imail_forum%40list.ipswitch.com/ Knowledge Base/FAQ: http://www.ipswitch.com/support/IMail/ To Unsubscribe: http://www.ipswitch.com/support/mailing-lists.html List Archive: http://www.mail-archive.com/imail_forum%40list.ipswitch.com/ Knowledge Base/FAQ: http://www.ipswitch.com/support/IMail/ To Unsubscribe: http://www.ipswitch.com/support/mailing-lists.html List Archive: http://www.mail-archive.com/imail_forum%40list.ipswitch.com/ Knowledge Base/FAQ: http://www.ipswitch.com/support/IMail/
