gerland@ubvms.cc.buffalo.edu (Jim Gerland - Manager, User Support Services) (01/18/90)
I have the following line in my NEWS_ADDRESS.CNF file: *@* "in%""\001@\002""" and I thought that would handle any and all non-local addresses, but... when I tried to REPLY to user@node.UUCP it did not build the correct address, so I added the line: *@*.* "in%""\001@\002.\003""" and it built the correct address. QUESTION: Do I need to add *@*.*.* [...] to get any and all combinations? Thanks, Jim...
gih900@CSC.DNET (Geoff Huston) (01/22/90)
>I have the following line in my NEWS_ADDRESS.CNF file: > >*@* "in%""\001@\002""" > >and I thought that would handle any and all non-local addresses, but... > >when I tried to REPLY to user@node.UUCP it did not build the correct address, >so I added the line: > >*@*.* "in%""\001@\002.\003""" > >and it built the correct address. > >QUESTION: Do I need to add *@*.*.* [...] to get any and all combinations? With V5.9, the mail address is NOT passed through the DCL parser - Therefore I would've thought the entry *@* in%"\001@\002" whould do what you want. Geoff Huston
asleeman@peace.waikato.ac.nz (Andrew Sleeman (Computer Services)) (01/25/90)
In article <23.25b463b3@ubvms.cc.buffalo.edu> gerland@ubvms.cc.buffalo.edu (Jim Gerland - Manager, User Support Services) writes: >I have the following line in my NEWS_ADDRESS.CNF file: > >*@* "in%""\001@\002""" > The examples given in the NEWS_ADDRESS.CNF are a little misleading and should really be changed or removed from the distribution for the assistance novice networkers like myself. Try the following. Trust me, I know not what I'm doing. *@* in%"\001@\002" >Thanks, >Jim... Not a problem. Andrew ...