masqmail-0.2
view tests/relay-to-localhost-mta/README @ 72:ad034b57f3b2
fixed Debian bug 536060 (log files are closed after SIGHUP receival)
Explanation:
When run in daemon mode, first the log files are opened. They get
assigned to the file descriptors 3 and 4 usually. Then std{in,out,err}
are closed. When SIGHUP comes in, all open files are closes and
masqmail reexecutes itself. The new masqmail instance opens the log
files at fd 0 and 1 now, but std{in,out,err} are closed afterwards,
thus the log files are closed.
The fix is to close the log files before std{in,out,err} are closed,
in case the log files have higher fds. After std{in,out,err} were
closed, the log files get opened again, now.
See also: http://bugs.debian.org/536060
| author | meillo@marmaro.de |
|---|---|
| date | Wed, 16 Jun 2010 10:32:20 +0200 |
| parents | |
| children |
line source
1 relay-to-localhost-mta
2 ----------------------
4 Send three mails, using different options, to stdin of masqmail, which
5 relays it per STMP to a local MTA listening at localhost:25.
7 So use it only if you have an MTA running on your box (sendmail,
8 exim, qmail or whatever, or masqmail when you have it already
9 installed).
11 If it works, you should get three mails.
12 Two log files, masqmail.log and debug.log will also be created within
13 this directory. They may give some information if anything went wrong.
15 The scripts assume that your login name corresponds to your mailbox
16 (quite probable) and that your MTA listens on port 25 with the
17 interface which corresponds to the hostname as returned by the shell
18 command "hostname" (without quotes...), also very probable.
20 If the log files reveal that your MTA is not willing to relay, you may
21 have to qualify the hostname. You might want to do this in a way
22 similar to:
24 sed 's/RECV_HOST/foo.example.org/' test.tpl >test