masqmail: 4d32eb75d3bc docs/old-manual/install.html

masqmail

view docs/old-manual/install.html @ 139:4d32eb75d3bc

/^\\fB/ in man pages indicates an option this allows automated testing if all config options are documented seems like this is just a hack, but it works ... so what?

author	meillo@marmaro.de
date	Tue, 06 Jul 2010 17:37:18 +0200
parents
children

line source

9 <HTML>

10 <HEAD>

11 <TITLE>MasqMail - Manual

12 </TITLE>

13 </HEAD>

14 <BODY TEXT="#000000" LINK="#0000ff" BGCOLOR="#ffffff">

16 <center>

17 <table width="80%">

18 <tr><td>

19 <table width="100%" bgcolor="#0000aa" cellspacing=0 cellpadding=0>

20 <tr>

21 <td>

22 <a href="manual.html">

23 <img width="20" src = "../images/u_arrow.gif" alt = "manual">

24 </a>

25 </td>

26 <td align=center width="100%">Installation</td>

27 <td>

28 <a href="./options.html">

29 <img width="20" src = "../images/r_arrow.gif" alt = "Options">

30 </a>

31 </td>

32 </tr>

33 </table>

36 You need a user and a group for masqmail to run, I suggest user

37 'mail' and group 'trusted'. Say:

39 <pre>

40 groupadd -g 42 trusted

41 useradd -u 42 -g 42 -d / -s /bin/sh -c "Mail Transfer Agent" mail

42 </pre>

44 If you use other names than mail and trusted use the options

45 described below for configure. The 42 is just a suggestion, you can

46 use any number you like, but preferably one < 100. It does not have

47 to be the same for the user 'mail' and the group 'trusted'.

49 Compliling is a matter of the usual procedure:

51 In the source directory, after unpacking do:

53 <pre>

54 ./configure

55 make

56 make install

57 </pre>

59 Optionally, after you have called make, you can make some tests in

60 the tests directory. Read the README in that directory for

61 instructions.

63 <h4>Additional options for configure:</h4>

65

66 --with-user=USER sets the user as which MasqMail will run. Default is

67 mail. USER has to exist before you 'make install'.

68

69 --with-group=GROUP sets the group as which MasqMail will run. Default

70 is trusted. GROUP has to exist before you 'make install'.

71

72 --with-logdir=LOGDIR sets the directory where MasqMail stores its log

73 files. It will be created if it does not exist. Default is /var/masqmail/.

74

75 --with-spooldir=SPOOLDIR sets the directory where MasqMail stores its

76 spool files. It will be created if it does not exist. Default is

77 /var/spool/masqmail/.

78

79 --enable-auth enables ESMTP AUTH support (disabled by default)

80

81 --disable-pop3 disables pop3 support (enabled by default)

82

84 <h4>After make install</h4>

86

87 You can also use these instructions to omit 'make install' if you do

88 not want to use it.

89

90 Check that 'make install' worked correctly. The following command:

91 <pre>

92 ls -ld /usr/sbin/masqmail /var/masqmail/ /var/spool/masqmail /var/spool/masqmail/input

93 </pre>

94 should give output similar to

95

96 <pre>

97 -rwsr-xr-x 1 root root 86955 Oct 14 14:27 /usr/sbin/masqmail

98 drwxr-xr-x 2 mail trusted 1024 Oct 14 14:29 /var/masqmail/

99 drwxr-xr-x 3 mail trusted 1024 Oct 14 14:27 /var/spool/masqmail

100 drwxr-xr-x 2 mail trusted 1024 Oct 14 18:32 /var/spool/masqmail/input

101 drwxr-xr-x 2 mail trusted 1024 Oct 14 18:32 /var/spool/masqmail/popuidl

102 </pre>

103

104

105 (important is the set-user-id bit for /usr/sbin/masqmail and the

106 ownership of all items).

107

108

109 Edit the configuration files. You can use the files from the

110 examples directory as a template. Copy masqmail.conf to

111 /etc/maqmail.conf, the others to the location given in

112 masqmail.conf.

113

114 If you already have an MTA (eg. sendmail) installed, move that to

115 another location:

116

117 mv /usr/sbin/sendmail /usr/sbin/sendmail.orig

118

119 Then make a link to the new MTA:

120

121 <pre>

122 ln -s /usr/sbin/masqmail /usr/sbin/sendmail

123 </pre>

124

125 Now every mailer that used to call sendmail will now call

126 masqmail. You can now kill your old sendmail if it is running and

127 start masqmail. Usually this is done with the startup scripts. For

128 SuSE this would be (as root):

129

130 <pre>

131 /sbin/init.d/sendmail stop

132 /sbin/init.d/sendmail start

133 </pre>

134

135 or shorter:

136

137 <pre>

138 /sbin/init.d/sendmail restart

139 </pre>

140

141 You can also start it with:

142

143 <pre>

144 /usr/sbin/sendmail -bd -q30m

145 </pre>

146

147 You can also let it be called from inetd (with the -bs option), but

148 this is untested.

149

150 <h4>Configuring for online delivery</h4>

151

152 Now you have to set up the online configuration. The trick is to

153 tell your ip-up script the connection name. You could use the IP

154 number of the far side of the ppp link, but this is a pain and may

155 change each time. But you can give it an additional argument via pppd

156 with ipparam. Somewhere in your dial up script you have a line similar

157 to:

158

159 <pre>

160 /usr/sbin/pppd /dev/ttyS1 connect "/usr/sbin/chat -t 90 -f

161 ${CHATFILE}" -d -d -d user user@somewhere file ${OPTIONS}

162 </pre>

163

164 Just add 'ipparam FastNet' in the command line for pppd if your ISP

165 has the name FastNet. The ip-up script will then get 'FastNet' as a

166 sixth parameter. In your ip-up script you can then call masqmail with

167

168 <pre>

169 /usr/sbin/masqmail -qo $6

170 </pre>

171

172 instead of 'sendmail -q', if you had that in the script

173 before. Masqmail will then read the route configuration specified for

174 the connection name 'FastNet' and deliver the mail destined to the

175 internet. See the <a href="config.html">configuration manual</a> on how

176 to write a route configuration or use one of the examples as a

177 template. I do not know how do configure that for an ISDN adapter,

178 but I am sure you will find something similar in the man

179 pages.

180

181 If you want mail that is received by masqmail from your local

182 net to be delivered immediately using the route configuration, you

183 have two possibilities:

184

185

186 <ul>

187

188 <li>if you are using the masqdialer system, you just have to set the

189 variables online_detect to mserver and

190 mserver_iface to the interface mserver is listening to.</li>

191

192 <li>otherwise you have to add two commands in your ip-up script:

193 echo -n $6 > /tmp/connect_route chmod 644 /tmp/connect_route

194 and you have to remove the file /tmp/connect_route in your

195 ip-down script: rm /tmp/connect_route. Then you have to set

196 online_detect to file and online_file to

197 /tmp/connect_route. </li>

198

199 </ul>

200

201

202 See the route documentation for more.

203 </td></tr>

204

205 <tr><td>

206

207 <hr>

208 <address><a href = "mailto:kurth@innominate.de">Oliver Kurth</a></address>

209 Last modified: Tue May 30 15:19:56 CEST 2000

210

211 This page was created using <a href="http://www.freddyfrog.com/hacks/genpage/">Genpage</a> - Version: 1.0.6

212

213

214 </table>

215 </center>

216

217 </BODY>

218 </HEAD>

219