6 This directory contains a modified version of the rpcomp program, used
7 with the Internet remote-printing experiment. More info on the experiment
8 can be found in /mrose/tpc on ftp.ics.uci.edu.
10 The xrpcomp program (it's a shell script) is like rpcomp, except that it
11 will look in X.500 if no fax recipients are found in the .rpdb file.
12 It still uses .rpdb to extract the originator information.
14 There are a couple of things in rp500.c you will want to tailor to use
17 DAPUSER This is the user the rp500 program, called from
18 xrpcomp will bind to the directory as. It can
21 DEFAULT_BASE This is the search base rp500 will use when looking
22 in the directory for fax recipients.
25 Where to find the ldapfilter.conf file. Should
26 make setting this automatic, but for now...
28 PHONE_PREFIX The prefix of phones in your local area. If
29 rp500 finds a fax number in the directory that is
30 not fully qualified, it will append as many of
31 these digits as necessary to make it fully
32 qualified. NB it assumes US-format numbers.
35 The host running the default ldap server to
40 The rp500 program knows a little about the US phone number format, in
41 an attempt to deal with (evil) people who have not put fully qualified
42 international format (e.g. +1 ... ) phone numbers in their entry. If
43 your users do not have US-format phone numbers, you'll need to take a
44 look at the fax2email() routine in rp500.c and change it around a bit.
52 This directory also contains the fax500 program. fax500 is just like
53 mail500, except that it looks up the facsimileTelephoneNumber
54 attribute, constructs an appropriate "remote-printer@blah.tpc.int"
55 address, and send the mail there. For example, the facsimile number
56 "+1 313 555 1212" corresponds to the address
57 "remote-printer@2.1.2.1.5.5.5.3.1.3.1.tpc.int." For a complete
58 explanation of the Internet remote-printing experiment, look in
59 /mrose/tpc on ftp.ics.uci.edu, or send mail to tpc-faq@town.hall.org.
61 The general idea is that you can set things up so that mail sent to
62 "user@fax.domain" will get printed on the user's fax machine, if
63 they've entered a fax number in their X.500 entry.
65 NOTE: you will need to modify faxtotpc.c if you have any "abbreviated"
66 phone number capabilities. For example, our telephone switches allow
67 you to dial only the last 5 digits of campus telephone numbers. People,
68 therefore, tend to list the last 5 digits of their fax numbers. The
69 routine "munge_phone()" takes care of fixing up abbreviated phone
70 numbers. You may need to write your own code.
72 fax500 is not yet complete. In particular, the following work still needs
75 - If the group entry itself has a fax number, don't send to all the members'
76 individual fax numbers. Instead, just send to the group's fax number.
77 - The -h flag for fax500 defines both the host name and the search base.
78 This causes problems because the host name we want is "fax.umich.edu"
79 but we need to search "umich.edu." The workaround is to add an
80 Associated Domain corresponding to the domain you want for your fax
81 service to each X.500 group which is to be accessible.
82 - We're working toward mail500 and fax500 being the same binary. Depending
83 on what argv[0] is, you'll get different behavior. Although this
84 binary should work just like mail500 if you name it "mail500" it's
86 - fax500 currently assumes that incoming messages are plain text, and
87 therefore constructs a destination address like
88 "remote-printer.user_name@2.1.2.1.5.5.5.3.1.3.1.tpc.int". If
89 the message is already MIME-compliant with an "application/remote-printing"
90 content type, we lose, since the remote-printing software assumes
91 that anything other than "remote-printer" on ther lhs of the address
92 means the message is plain text. Not sure about the solution to this.
93 - Regarding group support - typically, when we collect all the fax numbers
94 for a group, we'll end up either with (a) people who haven't registered
95 fax numbers, or (b) "email-only" group members who do not have entries
96 in X.500 (they only have an email address associated with the group).
97 The question is: what do you do with faxes for these folks? You could
98 (1) bounce to the sender (current behavior) or you could (2) send
99 email to the members with no fax numbers, informing them that someone
100 tried to send them a fax. I tend to prefer solution (2) for case (a),
101 and solution (1) for case (b).
102 - A configuration file-driven "munge_phone()" would be nice.