Problems Emailing Certain Domains using Exchange

[LD71]

Hello,
We are currently using GroupWise 6. We have no problems sending or receiving email from anyone else except for people who have an account with new york state (user@DFA.STATE.NY.US). They also have no problems sending or receiving from anyone else except us. (NYS is using Exchange)

We can send them mail and they receive it, but they can not reply to the message or send us a message directly. We have run every test we can think of but are stumped. The only thing we can think of is that we have an unusual email address since it a .cc account (jobsplus.cc)and think they may be filtering and somehow excluding the .cc on outgoing mail.

I have spoken to some users on their end who say as soon as they hit send on a message to us, it is immediatly rejected back to them.

I asked their tech support to email me a copy of the header of one of the message that was rejected and I have attached it below.

Does anyone have any ideas?

Thanks!

-----Original Message-----
From: System Administrator
Sent: Tuesday, February 18, 2003 4:01 PM
To: c=US;a=
;p=NYSDSS;o=NYSDSSMAILALB;dda:SMTP=lori.desocio@jobsplus.cc;
Subject: Undeliverable: Test 2

Your message did not reach some or all of the intended recipients.

Subject: Test 2
Sent: 02/18/2003 3:55 PM

The following recipient(s) could not be reached:

c=US;a=
;p=NYSDSS;o=NYSDSSMAILALB;dda:SMTP=lori.desocio@jobsplus.cc;
on 02/18/2003 4:01 PM
The recipient name is not recognized
The MTS-ID of the original message is: c=US;a=
;p=NYSDSS;l=EXCHSEN0A1M-030218205524Z-147589

 

[sobak]

I'm far from an exchange expert but it sounds like the issue is at their end. If the message gets bounced back right after sending then the mail never leaves their domain. I've had a few instances where my users have had problems sending to the .cc upper level domain that I had to fix on my GroupWise system. I've done a check on your domain (

http://samspade.org)and

it looks fine, no issues that I can see.

david e
*end users are just like computers, some you can work with...others just need a simple reBOOTing to fix their problems.*

 

[cderow]

I, too, have had this very same issue with other companies running Exchange and I run Groupwise 6. This started out being a problem with one company and then escalated to four different companies, all of which ran Exchange. After working with one of these company's network admins, we couldn't find the problem. Then all of a sudden, the problem went away. Must have been on their end, because I don't remember doing anything to the either the GWIA or the end-users account other than run an analyze fix, check TCP/IP settings, routers, etc. Nothing turned out to be blocking out any email to my domain.

 

[LD71]

Thanks for the responses...I have one question for Sobak...

You said "I've had a few instances where my users have had problems sending to the .cc upper level domain that I had to fix on my GroupWise system"

Can I ask what you did to fix the GroupWise system to be able to send to .cc upperlevel domains?

Thanks again,
Lori

 

[sobak]

Lori,

I use GroupWise-addressing rules in my GWIA; the system was built way before I got here so I really didn't notice any problems until the new upper-level domains came out. I then had my users start telling me they were not able to send to them. With a little investigation I found that the network admin prior to me created addressing rules to define INET traffic. What I did instead of deleting out the addressing rules (and redoing my entire addressing structure) was just add the rules into the GWIA for .cc .us etc. Once I did that then my users had no problem sending to the .cc domain. I didn't post this in my last response because I didn't think most people were using addressing rules for their GWIA.
david e
*end users are just like computers, some you can work with...others just need a simple reBOOTing to fix their problems.*

 

[LD71]

Thanks for the response David. I don't know anything about exchange, but I thought that whatever you did to fix it on GroupWise might also be a potential fix on Exchange.

I will forward this on to the Exchange IT staff.

Lori