www.novell.com/documentation
Multi-System Administration Guide
GroupWise 2012
January 24, 2012
Legal Notices
Novell,Inc.makesnorepresentationsorwarrantieswithrespecttothecontentsoruseofthisdocumentation,andspecifically
disclaimsanyexpressorimpliedwarrantiesofmerchantabilityorfitnessforanyparticularpurpose.Further,Novell,Inc.
reservestherighttorevisethispublicationandtomakechangestoitscontent,at
anytime,withoutobligationtonotifyany
personorentityofsuchrevisionsorchanges.
Further,Novell,Inc.makesnorepresentationsorwarrantieswithrespecttoanysoftware,andspecificallydisclaimsany
expressorimpliedwarrantiesofmerchantabilityorfitnessforanyparticularpurpose.Further,Novell,Inc.reservestheright
to
makechangestoanyandallpartsofNovellsoftware,atanytime,withoutanyobligationtonotifyanypersonorentityof
suchchanges.
AnyproductsortechnicalinformationprovidedunderthisAgreementmaybesubjecttoU.S.exportcontrolsandthetrade
lawsofothercountries.Youagreeto
complywithallexportcontrolregulationsandtoobtainanyrequiredlicensesor
classificationtoexport,re‐export,orimportdeliverables.Youagreenottoexportorre‐exporttoentitiesonthecurrentU.S.
exportexclusionlistsortoanyembargoedorterroristcountriesasspecifiedintheU.S.
exportlaws.Youagreetonotuse
deliverablesforprohibitednuclear,missile,orchemicalbiologicalweaponryenduses.SeetheNovellInternationalTrade
ServicesWebpage(http://www.novell.com/info/exports/)formoreinformationonexportingNovellsoftware.Novellassumes
noresponsibilityforyourfailuretoobtainanynecessaryexportapprovals.
Copyright©2003‐2012
Novell,Inc.Allrightsreserved.Nopartofthispublicationmaybereproduced,photocopied,storedon
aretrievalsystem,ortransmittedwithouttheexpresswrittenconsentofthepublisher.
Novell, Inc.
1800 South Novell Place
Provo, UT 84606
U.S.A.
www.novell.com
OnlineDocumentation:ToaccesstheonlinedocumentationforthisandotherNovellproducts,andtogetupdates,seethe
Novell
DocumentationWebsite(http://www.novell.com/documentation).
Novell Trademarks
ForNovelltrademarks,seetheNovellTrademarkandServiceMarklist(http://www.novell.com/company/legal/trademarks/
tmlist.html).
Third-Party Materials
Allthird‐partytrademarksarethepropertyoftheirrespectiveowners.
Contents 3
Contents
About This Guide 5
Part I Connecting to Other GroupWise Systems 7
1 Understanding Connection Options 9
1.1 Connection Methods Supported by the Various GroupWise Versions. . . . . . . . . . . . . . . . . . . . . . . . .9
1.2 External System Links . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .10
1.3 Dynamic Internet Links. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .10
1.4 Direct Links . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .10
2 Using External System Links 13
3 Using Dynamic Internet Links 15
3.1 MTA Version Requirements. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .15
3.2 Installing the GroupWise Internet Agent . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .15
3.3 Setting Up Internet-Style Addressing. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .16
3.4 Adding MTA Resource Records to DNS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .16
3.4.1 Creating the Address ("A") Record . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .16
3.4.2 Creating the Service ("SRV") or Text ("TXT") Record . . . . . . . . . . . . . . . . . . . . . . . . . . . . .17
3.5 Configuring the MTA’s Server for DNS Lookups . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .18
3.5.1 Configuring Windows Server 2008 for DNS Lookups . . . . . . . . . . . . . . . . . . . . . . . . . . . . .18
3.5.2 Configuring Windows Server 2003 for DNS Lookups . . . . . . . . . . . . . . . . . . . . . . . . . . . . .18
3.6 Enabling MTAs to Perform DNS Lookups . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .19
3.6.1 Enabling DNS Lookups for All MTAs. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .19
3.6.2 Enabling/Disabling DNS Lookups for Individual MTAs . . . . . . . . . . . . . . . . . . . . . . . . . . . .20
3.7 Message Flow through a Dynamic Internet Link . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .21
3.7.1 Stage 1: GroupWise Client in the Sending System . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .21
3.7.2 Stage 2: GroupWise Client in the Sending System . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .21
3.7.3 Stage 3: GroupWise MTA in the Sending System. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .22
3.7.4 Stage 4: GroupWise MTA in the Sending System. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .22
3.7.5 Stage 5: GroupWise MTA in the Sending System. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .22
3.7.6 Stage 6: GroupWise MTA in the Sending System. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .22
3.7.7 Stage 7: GroupWise Internet Agent in the Sending System . . . . . . . . . . . . . . . . . . . . . . . .22
3.7.8 Stage 8: GroupWise Internet Agent in the Sending System . . . . . . . . . . . . . . . . . . . . . . . .23
3.7.9 Stage 9: GroupWise MTA in the Sending System. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .23
3.7.10 Stage 10: GroupWise MTA in the Sending System. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .23
3.7.11 Stage 11: GroupWise MTA in the Receiving System . . . . . . . . . . . . . . . . . . . . . . . . . . . . .23
3.7.12 Stage 12: Both GroupWise MTAs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .23
4 Using Direct Links 25
4.1 Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .25
4.2 Creating an External Domain. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .26
4.3 Linking to the External Domain . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .27
4.4 Checking the Link Status of the External Domain . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .28
4.5 Sending Messages Between Systems. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .29
4.6 Exchanging Information Between Systems . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .29
4 Contents
4.7 Message Flow Between External Domains . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .29
5 Using Gateway Links 31
6 Synchronizing External GroupWise Systems 33
Part II Merging GroupWise Systems 37
7 Why Merge GroupWise Systems? 39
8 Planning the Merge 41
8.1 Understanding the Merge Process. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .41
8.2 Planning Administrator Rights . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .43
8.3 Determining Which GroupWise Objects Are No Longer In Use. . . . . . . . . . . . . . . . . . . . . . . . . . . . .43
8.4 Planning the Location of the Domain Database Backup Directories . . . . . . . . . . . . . . . . . . . . . . . . .44
8.5 Planning GroupWise System Connections . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .44
8.5.1 External Domains . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .45
8.5.2 Linking the Domains . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .46
8.5.3 Releasing the Secondary Domains in Site #2 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .47
8.6 Planning to Merge Additional GroupWise Systems . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .47
8.6.1 Merging in One Session . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .48
8.6.2 Merging at Different Times . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .48
8.7 Merge Planning Worksheet . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .49
9 Preparing for the Merge 55
9.1 Setting Up Administrator Rights. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .55
9.2 Deleting Unused GroupWise Objects . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .55
9.3 Verifying That UNC Paths Are Correct. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 55
9.4 Resolving Pending Operations. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .56
10 Merging the GroupWise Systems 57
10.1 Creating External Domains for Both Systems . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .57
10.1.1 Creating Site #1 External Domains in Site #2 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .58
10.1.2 Creating Site #2 External Domains in Site #1 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .59
10.2 Configuring Links Between Site #2 Domains and Site #1 Secondary Domains. . . . . . . . . . . . . . . . .59
10.3 Checking Links to External Domains for Both Systems. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .60
10.3.1 Checking Links to Site #1 External Domains in Site #2. . . . . . . . . . . . . . . . . . . . . . . . . . . .60
10.3.2 Checking Links to Site #2 External Domains in Site #1. . . . . . . . . . . . . . . . . . . . . . . . . . . .60
10.4 Creating Temporary Holding Directories . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .61
10.5 Releasing Site #2 Secondary Domains . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .61
10.6 Sending Site #2 Databases to the Site #1 Administrator . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .62
10.7 Receiving Site #2 Databases at Site #1. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .62
10.8 Merging a Site #2 Domain into Site #1. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .63
10.9 Merging the Next GroupWise System . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .63
10.10 Sending the Merged Site #2 Databases to Site #2 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .64
10.11 Restarting the GroupWise Agents . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .64
10.12 Testing the Merged System . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .64
About This Guide 5
About This Guide
ThisNovellGroupWise2012Multi‐SystemAdministrationGuidehelpsyouconnectyourGroupWise
systemtootherGroupWisesystemsornon‐GroupWisemessagingsystems,andhelpsyoumerge
yourGroupWisesystemwithanotherGroupWisesystemtocreateonesystem.Theguideisdivided
intothefollowingsections:
Part I,“ConnectingtoOtherGroupWise
Systems,”onpage 7
Part II,“MergingGroupWiseSystems,”onpage 37
Fortroubleshootingassistance,see:
GroupWise2012Troubleshooting1:ErrorMessages
GroupWise2012Troubleshooting2:SolutionstoCommonProblems
GroupWise2012Troubleshooting3:MessageFlowandDirectoryStructure
NovellSupportandKnowledgebase(http://www.novell.com/support)
TosearchtheGroupWisedocumentationfromtheNovellSupportWeb
site,clickAdvanced
Search,selectDocumentationintheSearchIndrop‐downlist,selectGroupWiseintheProducts
drop‐downlist,typethesearchstring,thenclickSearch.
GroupWiseSupportForums(http://forums.novell.com/forumdisplay.php?&f=356)
GroupWiseSupportCommunity(http://www.novell.com/support/products/groupwise)
GroupWiseCoolSolutions(http://www.novell.com/coolsolutions/gwmag/index.html)
Audience
ThisguideisintendedfornetworkadministratorswhoinstallandadministerGroupWise.
Feedback
Wewanttohearyourcommentsandsuggestionsaboutthismanualandtheotherdocumentation
includedwiththisproduct.PleaseusetheUserCommentfeatureatthebottomofeachpageofthe
onlinedocumentation.
Additional Documentation
ForadditionalGroupWisedocumentation,seethefollowingguidesattheNovellGroupWise2012
documentationWebsite(http://www.novell.com/documentation/groupwise2012):
InstallationGuide
ServerMigrationGuide
AdministrationGuide
Multi‐SystemAdministrationGuide
InteroperabilityGuide
TroubleshootingGuides
6 GroupWise 2012 Multi-System Administration Guide
GroupWiseUserFrequentlyAskedQuestions(FAQ)
GroupWiseUserGuides
GroupWiseUserQuickStarts
I
Connecting to Other GroupWise Systems 7
I
Connecting to Other GroupWise
Systems
Chapter 1,“UnderstandingConnectionOptions,”onpage 9
Chapter 2,“UsingExternalSystemLinks,”onpage 13
Chapter 3,“UsingDynamicInternetLinks,”onpage 15
Chapter 4,“UsingDirectLinks,”onpage 25
Chapter 5,“UsingGatewayLinks,”onpage 31
Chapter 6,“SynchronizingExternalGroupWiseSystems,”onpage 33
8 GroupWise 2012 Multi-System Administration Guide
1
Understanding Connection Options 9
1
Understanding Connection Options
WhenconnectingyourGroupWise2012systemwithanotherGroupWise6.x,7,8,or2012system,
youcanchoosefromseveralconnectionmethods.Tohelpyouchoosethebestmethodforyour
system,thefollowingsectionsprovidebriefsummaries:
Section 1.1,“ConnectionMethodsSupportedbytheVariousGroupWiseVersions,”onpage 9
Section 1.2,
“ExternalSystemLinks,”onpage 10
Section 1.3,“DynamicInternetLinks,”onpage 10
Section 1.4,“DirectLinks,”onpage 10
DependingontheversionsofthetwoGroupWisesystemsyouaretryingtoconnect,someofthe
methodsmightnotbeavailable.Forinformationaboutmethodsavailableforthetwosystemsyou
areconnecting,see
Section 1.1,“ConnectionMethodsSupportedbytheVariousGroupWise
Versions,”onpage 9.
1.1 Connection Methods Supported by the Various GroupWise
Versions
ThefollowingchartliststheGroupWise6.x,7,8,and2012versionsandthemethodsthatcanbeused
whenconnectingsystemsthataretheseversions:
KEY
D = Direct Link
G = Gateway Link
I = Dynamic Internet Link
E = External System Link
Tousethechart,locateyoursystem’sversioninthefirstcolumn,thenreadacrosstherowuntilyou
reachtheversionofthesystemyouareconnectingto.Themethodslistedarethemethodssupported
whenconnectingthetwosystems.
GroupWise
Version
6.x 7 8 2012
6.x D G I D G I D G I D I
7 D G I D G I D G I D I
8 D G I D G I D G I E D I E
2012 D I D I D I E D I E
10 GroupWise 2012 Multi-System Administration Guide
IMPORTANT:AGroupWisesystem’sversionisdeterminedbytheversionoftheMessageTransfer
Agent(MTA)runninginthesystem.IfyoursystemincludesmultipleversionsoftheMTA,
determinewhichMTAwillbeusedwhenconnectingtotheothersystemandusethatMTA’sversion
whenreadingthetable.
1.2 External System Links
BeforeGroupWise8,ifyouwantedusersinyourGroupWisesystemtobeabletoexchangemessages
convenientlywithusersinanotherGroupWisesystem,youneededtosetupexternaldomains,
externalpostoffices,andexternalusers,orusedynamicInternetlinks,asdescribedinlatersections.
StartingwithGroupWise8,
youcansetupanInternetdomaininGroupWisetorepresenttheother
GroupWisesystem.Asaresult,messagesareroutedtotheotherGroupWisesystembasedonlinks
setupintheLinkConfigurationTool,ratherthanthroughtheInternetAgent(GWIA).
ForinformationaboutconnectingGroupWisesystemsviaexternal
systemlinks,seeChapter 2,
“UsingExternalSystemLinks,”onpage 13.
1.3 Dynamic Internet Links
ThedynamicInternetlinkcapabilityoftheGroupWiseMessageTransferAgent(MTA)enablesitto
useDomainNameService(DNS)toassociatethedomainnameinanInternet‐styleaddress(for
example,jsmith@novell.com)toanMTAassignedtoreceivemessagesforthatdomainname.After
theaddresshasbeenresolved,the
sendingMTAusestheGroupWiseMessageTransferProtocol
(GWMTP)toconnectwithandtransfermessagestothedestinationMTA.
BecausemessagesaretransferreddirectlyfromoneMTAtoanother,noGroupWiseclient
functionalityislost.UserscanperformBusySearches,retractsentmessages,andseethestatusof
theiroutgoingmessages,
justasiftherecipientwereinthesameGroupWisesystem.Inaddition,
usersareabletousewell‐knownInternet‐styleaddresssyntax(forexample,[email protected]).
Administratively,usingdynamicInternetlinksenablesyoutoavoiddefiningusersfromother
GroupWisesystemsinyourGroupWisesystem.Aslongasthesender
knowstherecipient’sInternet‐
styleaddress,andtherecipient’sdomainnameisregisteredinDNSandassociatedwithanMTA,the
messageisproperlyroutedtotherecipient.
ForinformationaboutconnectingGroupWisesystemsviadynamicInternetlinks,seeChapter 3,
“UsingDynamicInternetLinks,”onpage 15.
1.4 Direct Links
ThedirectlinkcapabilityoftheMTAenablesittouseamappedorUNCpathtoaccessadomain
directoryinanotherGroupWisesystemortouseTCP/IPtoconnecttothedomain’sMTA.Thisisthe
samefunctionalitythatenablestwodomainsinthesameGroupWisesystemtobe
connected.
BecausemessagesaretransferreddirectlyfromoneMTAtoanother,noGroupWiseclient
functionalityislost.
Understanding Connection Options 11
Administratively,youcanusetheExternalSystemSynchronizationfeaturetoexchangeinformation
betweenthetwosystemsandenableuserstoselectaddressesfromtheAddressBook,oryoucan
choosetonotexchangeinformationandrequireuserstoenterafully‐qualifiedaddress
(
userID.post_office.domain
or
user@internet_domain
).
ForinformationaboutconnectingGroupWisesystemsviadirectlinks,seeChapter 4,“UsingDirect
Links,”onpage 25.
12 GroupWise 2012 Multi-System Administration Guide
2
Using External System Links 13
2
Using External System Links
TosetupanInternetdomainthatrepresentsanexternalGroupWisesystem:
1 InConsoleOne,clickTools>GroupWiseSystemOperations>InternetAddressing.
2 OntheInternetDomainstab,clickCreate.
3 SpecifytheInternetdomainnamefortheexternalGroupWisesystem,thenprovidea
descriptionifdesired.
4 SelectUsedforExternalGroupWiseSystemsOnly,thenclickOK.
14 GroupWise 2012 Multi-System Administration Guide
3
Using Dynamic Internet Links 15
3
Using Dynamic Internet Links
YoucanconnecttwoGroupWisesystemsthroughdynamicInternetlinks.DynamicInternetlinks
enableaGroupWiseMessageTransferAgent(MTA)touseDomainNameService(DNS)and
GroupWiseMessageTransferProtocol(GWMTP)tosendmessagesfromonesystemtoanther.Foran
overviewofdynamicInternetlinks,seeChapter 1,“UnderstandingConnection
Options,”onpage 9.
TousedynamicInternetlinks,completethetasksinthefollowingsections:
Section 3.1,“MTAVersionRequirements,”onpage 15
Section 3.2,“InstallingtheGroupWiseInternetAgent,”onpage 15
Section 3.3,“SettingUpInternet‐StyleAddressing,”onpage 16
Section 3.4,“AddingMTAResourceRecordstoDNS,”onpage 16
Section 3.5,“ConfiguringtheMTA’s
ServerforDNSLookups,”onpage 18
Section 3.6,“EnablingMTAstoPerformDNSLookups,”onpage 19
Section 3.7,“MessageFlowthroughaDynamicInternetLink,”onpage 21
3.1 MTA Version Requirements
TousedynamicInternetlinkstoconnectyourGroupWisesystemwithanotherGroupWisesystem,
bothGroupWisesystemsmusthaveatleastonedomainthatisrunningoneofthefollowingversions
oftheGroupWiseMTA:
GroupWise6.x
GroupWise7
GroupWise8
GroupWise2012
3.2 Installing the GroupWise Internet Agent
BeforeconfiguringyourGroupWisesystemtousedynamicInternetlinks,youneedtomakesure
thattheGroupWiseInternetAgent(GWIA)hasbeeninstalled.DynamicInternetlinksrequireyour
GroupWisesystemtouseInternet‐styleaddressing,whichisonlyavailableifyou’veinstalledthe
GWIAandcreatedoneormoreInternet
domainsforyourGroupWisesystem.
TheonlyrequirementfordynamicInternetlinksisthattheGWIAbeinstalled,sothataGWIAobject
iscreatedinNovelleDirectory.TheGWIAdoesnotactuallyneedtobeconfiguredcorrectlyortobe
running.However,ifthereareGroupWisesystemsthatyouneed
toconnecttobutcannotdoso
throughdynamicInternetlinks,youcanusetheGWIAtoconnecttothosesystemswhileusing
dynamicInternetlinkstoconnecttosupportedGroupWisesystems.
16 GroupWise 2012 Multi-System Administration Guide
Forinformationaboutinstalli ngtheGWIA,see“InstallingtheGroupWiseInternetAgent”inthe
GroupWise2012InstallationGuide.
3.3 Setting Up Internet-Style Addressing
DynamicInternetlinksrequireyourGroupWisesystemtobeconfiguredtouseInternet‐style
addressing(
user@internet_domain
)ratherthanstandardGroupWiseaddressing
(
userID.post_office.domain
).IfyouhavenotenabledInternet‐styleaddressinganddefinedat
leastoneInternetdomainforyourGroupWisesystem,see“ConfiguringInternetAddressing”inthe
GroupWise2012AdministrationGuide.
TheInternetdomainsyouestablishwhensettingupInternet‐styleaddressing(forexample,
novell.com
,
groupwise.novell.com
,and
support.novell.com
)arethekeytoenablingdynamic
Internetlinks.EachMTAthatwillreceivemessagesmustbedefinedinDNSandassociatedwiththe
Internetdomain(ordomains)thatitwillreceivemessagesfor.ThisallowsMTAsinotherGroupWise
systemstoroutemessagesthatcontainyourInternetdomainnamesto
theappropriateMTAsinyour
system.
3.4 Adding MTA Resource Records to DNS
InorderforyourGroupWisesystemtoreceivemessagesfromanotherGroupWisesystemthrougha
dynamicInternetlink,youneedtocreateaDNS resourcerecordforatleastoneofyourMTAs.The
resourcerecordenablestheMTA’saddress,alongwiththeInternetdomainnamesassociatedwithit,
tobe
broadcastthroughouttheInternet.
YouneedtocreatethefollowingresourcerecordsinDNS:
Anaddress(ʺAʺ)recordthatmapstheMTAserver’shostnametoitsIPaddress.
Aservice(ʺSRVʺ)recordoratext(ʺTXTʺ)recordthatmapstheInternetdomainname
tothehost
nameorIPaddressassignedtotheMTA’sserver.
YoucanuseyourtoolofchoicetomodifyDNS.Thefollowingsectionsexplaintheinformat ion
requiredandprovidesamplerecords.
Section 3.4.1,“CreatingtheAddress(ʺAʺ)Record,”onpage 16
Section 3.4.2,“CreatingtheService(ʺSRVʺ)or
Text(ʺTXTʺ)Record,”onpage 17
3.4.1 Creating the Address ("A") Record
YoucancreateanʺAʺrecordtomapyourMTAserver’sfully‐qualifiedhostnametoitsIPaddress.
Doingsoenablesyoutousetheserver’sfully‐qualified hostnameintheservice(ʺSRVʺ)ortext
(ʺTXTʺ)recordratherthantheIPaddress.TheʺAʺrecord
isrequiredifyouplantouseaʺSRVʺ
record.
ThefollowingtextshowssampleʺAʺrecords.
;
; Address ("A") records
;
localhost IN A 172.0.0.1
corp.serv.novl IN A 172.16.5.18
gwdev.serv.novl IN A 172.16.5.19
gwsup.serv.novl IN A 172.16.5.20
Using Dynamic Internet Links 17
HostName(column1):UsethehostnameassignedtotheMTA’sserver.Intheaboveexample,
corp
,
gwdev
,and
gwsupport
arethehostnamesassignedtothreeMTAservers.
Class(column2):UseINtorepresenttheInternet.
Type(column3):UseAtospecifyanaddressrecord.
IPAddress(column4):UsetheIPaddressassignedtotheMTA’sserver.
3.4.2 Creating the Service ("SRV") or Text ("TXT") Record
YoucanuseeitherservicerecordsortextrecordstomapyourInternetdomainnamestoMTAs.The
followingtextshowssampleʺSRVʺandʺTXTʺrecords:
;
; Service ("SRV") records
;
gwmtp.tcp.novell.com 172800 IN SRV 1 0 7100 corp.serv.novl
gwmtp.tcp.groupwise IN SRV 1 1 7100 corp.serv.novl
gwmtp.tcp.groupwise IN SRV 1 2 7100 gwdev.serv.novl
gwmtp.tcp.support 172800 IN SRV 1 0 7100 gwsup.serv.novl
gwmtp.tcp.support 172800 IN SRV 2 0 7100 corp.serv.novl
;
; Text ("TXT") records
;
gwmtp.tcp.novell.com 172800 IN TXT "1 0 7100 corp.serv.novl"
gwmtp.tcp.groupwise IN TXT "1 1 7100 corp.serv.novl"
gwmtp.tcp.groupwise IN TXT "1 2 7100 gwdev.serv.novl"
gwmtp.tcp.support 172800 IN TXT "1 0 7100 gwsup.serv.novl"
gwmtp.tcp.support 172800 IN TXT "2 0 7100 corp.serv.novl"
Service.Protocol.Name(column1):Theservicemustbespecifiedas
gwmtp
.Theprotocolmustbe
specifiedas
tcp
.ThenamecorrespondstotheInternetdomainnameyouwantassociatedwiththe
MTA.Intheabovesample,
novell.com
,
groupwise.novell.com
,and
support.novell.com
arethe
InternetdomainnamesdefinedinGroupWise.
TimetoLive(column2):TTL(timetolive)istheamountoftimetherecordiscachedinmemoryso
itdoesnotneedtobelookedupagain.TTLisspecifiedinseconds.Intheabovesample,172800
represents2days.
Ifyoudon’tspecifyaTTL,therecordisnotcached.
Class(column3):Enter
IN
torepresenttheInternet.
Type(column4):Enter
SRV
tospecifyaservicerecord.Enter
TXT
tospecifyatextrecord.
Priority(column5):IfanInternetdomainnameisassociatedwithtwodifferentMTAs,thehostwith
thelowestvalueisalwayscontactedfirst.Forexample,ahostwithpriority1iscontactedbeforea
hostwithpriority2.IftworecordswiththesameInternet
domainnamehavethesamepriority,the
weightnumberisused.Intheaboveexample,thetwo
groupwise.novell.com
recordshavethe
samepriority,sothe weightwouldbeused.
Weight(column6):Theweightnumberspecifieshowtoallocateconnectionsamonghostswith
equalpriorities.Inthe
groupwise.novell.com
recordabove,the
corp.serv.novl
hostandthe
gwdev.serv.novl
hosthaveequalpriorities,butthe
corp.serv.novl
hosthasaweightof1andthe
gwdev.serv.novl
hosthasaweightof2.Thismeansthat1outof3timesthe
corp.serv.novl
host
wouldbecontactedfirst,and2outof3times,the
gwdev.serv.novl
hostwouldbe contactedfirst.
Port(column7):TheportnumberspecifiestheTCPportonwhichtheMTAlistensforincoming
messages.ThedefaultportnumberfortheMTAis7100.
18 GroupWise 2012 Multi-System Administration Guide
Host(column8):Thehostspecifiesthefully‐qualifiedhostnameorIP addressoftheMTA’sserver.
Foraservicerecord,youmustspecifythehostname.Foratextrecord,youcanspecifyeitherthe
server’shostnameorIPaddress.Ifyouuseahostname,itmust
bemappedtoanIPaddressthrough
anDNSʺAʺrecord.Intheaboveexample,
corp.serv.novl
,
gwdev.serv.novl
,and
gwsup.serv.novl
areallhostnamesthataremappedtoIPaddressesthroughʺAʺrecordsinDNS.
3.5 Configuring the MTA’s Server for DNS Lookups
InorderforanMTAinyourGroupWisesystemtousedynamicInternetlinkstosendmessages,you
mustmakesuretheMTA’sserverisproperlyconfiguredforDNSlookups.Basicconfiguration
informationisprovidedbelow.ConsultyourDNSdocumentationformoredetailedinformation
aboutconfiguringaserverforDNSlookups.
Section 3.5.1,“ConfiguringWindowsServer2008forDNSLookups,”onpage 18
Section 3.5.2,“ConfiguringWindowsServer2003forDNSLookups,”onpage 18
3.5.1 Configuring Windows Server 2008 for DNS Lookups
1 ClicktheStart>ControlPanel>Viewnetworkstatusandtasks>LocalAreaConnection.
2 IntheLocalAreaConnectiondialogbox,clickPropertiestodisplaytheLocalAreaConnection
Propertiesdialogbox.
3 InthelistontheNetworkingtab,selectInternetProtocol,thenclickPropertiestodisplaythe
InternetProtocol(TCP/IP)Propertiesdialogbox.
4 ClickAdvancedtodisplaytheAdvancedTCP/IPSettingsdialogbox.
5 ClicktheDNStab,thenmakesuretheIPaddressofatleastoneDNSnameserverislistedinthe
DNSServerAddresseslist,thenclickOK.
6 ClickOKtosaveanychangesyouhavemade.
ConsultyourDNSdocumentationformoredetailedinformationaboutconfiguringaWindows
workstationorserverforDNSlookups.
3.5.2 Configuring Windows Server 2003 for DNS Lookups
1 ClicktheStart>ControlPanel>NetworkConnections>LocalAreaConnection.
2 IntheLocalAreaConnectiondialogbox,clickPropertiestodisplaytheLocalAreaConnection
Propertiesdialogbox.
3 InthelistontheGeneraltab,selectInternetProtocol(TCP/IP),thenclickPropertiestodisplaythe
InternetProtocol(TCP/IP)Propertiesdialogbox.
4 ClickAdvancedtodisplaytheAdvancedTCP/IPSettingsdialogbox.
5 ClicktheDNStab,thenmakesuretheIPaddressofatleastoneDNSnameserverislistedinthe
DNSServerAddresseslist,thenclickOK.
ConsultyourDNSdocumentationformoredetailedinformationaboutconfiguringaWindows
workstationorserverforDNSlookups.
Using Dynamic Internet Links 19
3.6 Enabling MTAs to Perform DNS Lookups
AfteryouhaveperformedthenecessaryconfigurationtoenableanMTA’sservertoallowDNS
lookups,asdescribedinSection 3.5,“ConfiguringtheMTA’sServerforDNSLookups,”onpage 18,
youmustconfiguretheMTAtoperformDNSlookups.
Bydefault,yourGroupWisesystemisconfigurednottoallowMTAstoperform
DNSlookups.You
canretainthesystemdefaultofnoDNSlookups,thenenableDNSlookupsforindividualMTAs.Or
youcanenableDNSlookupsforallMTAsinyourGroupWisesystem,thenselectivelydisableDNS
lookupsforindividualMTAs.TheapproachyoutakedependsonhowmanyMTAsyou
want
enabledcomparedtothenumberyouwantdisabled.
Section 3.6.1,“EnablingDNSLookupsforAllMTAs,”onpage 19
Section 3.6.2,“Enabling/DisablingDNSLookupsforIndividualMTAs,”onpage 20
3.6.1 Enabling DNS Lookups for All MTAs
ToconfigureyourGroupWisesystemsoallMTAsperformDNSlookups(providedtheirserversare
enabledforDNSlookups):
1 InConsoleOne,clicktheToolsmenu>GroupWiseSystemOperations>SystemPreferencestodisplay
theGroupWiseSystemPreferencesdialogbox.
2 ClicktheRoutingOptionstab.
3 EnabletheAllowMTAs toSen dDirectlytoOtherGroupWiseSystemsoption
Iftheoptionisdimmed,youhavenotdefinedanInternetdomainyet.See“ConfiguringInternet
Addressing”in“InternetAgent”intheGroupWise2012AdministrationGuide.
4 ClickOK.
20 GroupWise 2012 Multi-System Administration Guide
3.6.2 Enabling/Disabling DNS Lookups for Individual MTAs
IfyouhaveusedtheGroupWiseSystemPreferencestoenableallMTAstoperformDNSlookupsin
ordertosendmessagesdirectlytootherGroupWisesystems,asdescribedin“EnablingDNS
LookupsforAllMTAs”onpage 19,youcandisableDNSlookupsforindividualMTAs.
Ifyouhaven’tusedtheGroupWise
SystemPreferencestoenableallMTAstoperformDNSlookups,
youcanenableDNSlookupsforindividualMTAs.
1 InConsoleOne,right‐clicktheMTAobject,thenclickProperties.
2 ClickGroupWise>RoutingOptionstodisplaytheRoutingOptionspage.
3 SelecttheOverrideboxtotheleftoftheAllowMTAtoSendDirectlytoOtherGroupWiseSystems
option.
4 SelectordeselectAllowMTAtoSendDirectlytoOtherGroupWiseSystemsasneededforthisMTA.
5 ClickOK.
Page is loading ...
Page is loading ...
Page is loading ...
Page is loading ...
Page is loading ...
Page is loading ...
Page is loading ...
Page is loading ...
Page is loading ...
Page is loading ...
Page is loading ...
Page is loading ...
Page is loading ...
Page is loading ...
Page is loading ...
Page is loading ...
Page is loading ...
Page is loading ...
Page is loading ...
Page is loading ...
Page is loading ...
Page is loading ...
Page is loading ...
Page is loading ...
Page is loading ...
Page is loading ...
Page is loading ...
Page is loading ...
Page is loading ...
Page is loading ...
Page is loading ...
Page is loading ...
Page is loading ...
Page is loading ...
Page is loading ...
Page is loading ...
Page is loading ...
Page is loading ...
Page is loading ...
Page is loading ...
Page is loading ...
Page is loading ...
Page is loading ...
Page is loading ...
/
