Tek-Tips is the largest IT community on the Internet today!

Members share and learn making Tek-Tips Forums the best source of peer-reviewed technical information on the Internet!

  • Congratulations strongm on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!

Hi All, Here is the setup: 1 LAN w

Status
Not open for further replies.

KenB

MIS
Aug 30, 1999
242
US
Hi All,
Here is the setup: 1 LAN with a Firewall, 2 Companies share the LAN, Company A has a NW 5.0 50 user running on Server A w/GroupWise 5.5 SP5, Company B has a NW 5.0 SBS 10 user Server w GroupWise 5.5 SP5 the Company Trees are seperate as are the GroupWise systems. Because the Firewall will only allow a passthrough to one SMTP Gateway the GWIA is set up on Server A (this was the original Server as Server B came later) and has been working fine. Because of the Independant nature of Company B I set up the New server for them last November and started moving all of their resources to the new server, the last thing to move was the E-mail.
I followed the recomendations of Novell and linked the Domain's together using External Domains and Syncronized the two systems. New GW user accounts were setup on Server B all of the old mail was archived and moved to the new system, the FID was changed and the Mailbox's could Unarchive what was needed. The old GW user accounts were deleted from Server A and the new accounts can send/receive E-mail.
Now the problem: none of the users can reply to New messages received from the Internet, everything else works fine. The reply message tags the To: address (user@company.com) with this From: address (Server_A:user@company.com)which causes the message to bounce at the gateway and come back as undeliverable. I have searched the Novell Knowledge Base and tried all of the recomended fixes but the Reply problem still exists.
Any help would be greatly appreciated.

TIA
Ken
 
Is it just users on server b that have the reply problem or the ones on server A as well? An addressing rule might do the trick. You could add a rule that takes server_a:* and replaces it with %1. I'm not 100% sure of the syntax, but think that should work.
 
It's just the users who were moved from server a to server b.

Ken
 
Status
Not open for further replies.

Part and Inventory Search

Sponsor

Back
Top