1
<?xml version="1.0" encoding="iso-8859-1"?>
2
1
<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN"
3
2
"http://www.w3.org/TR/html4/loose.dtd">
4
<html xmlns="http://www.w3.org/1999/xhtml">
6
<meta http-equiv="Content-Type" content="text/html; charset=iso-8859-1" />
7
<meta name="MSSmartTagsPreventParsing" content="TRUE" />
5
<meta http-equiv="Content-Type" content="text/html; charset=iso-8859-1">
6
<meta name="MSSmartTagsPreventParsing" content="TRUE">
8
7
<title>Courier FAQ</title>
9
<!-- $Id: FAQ.html,v 1.36 2004/05/08 02:24:22 mrsam Exp $ -->
8
<!-- $Id: FAQ.html,v 1.38 2004/08/07 16:18:10 mrsam Exp $ -->
10
9
<!-- Copyright 2000-2003 Double Precision, Inc. See COPYING for -->
11
10
<!-- distribution information. -->
12
<link rel="icon" href="icon.gif" type="image/gif" />
11
<link rel="icon" href="icon.gif" type="image/gif">
15
<body text="#000000" bgcolor="#FFFFFF" link="#0000EE" vlink="#551A8B"
17
15
<h1>Courier FAQ</h1>
19
17
<p>This is a beginning of a modest FAQ. Contributors:</p>
29
27
<li>Configuration issues
31
29
<li><a href="#configloop">The <code>configure</code> script is stuck in
32
an infinite loop</a><br />
30
an infinite loop</a></li>
35
31
<li><a href="#authlib">What's the deal with authentication modules? Why
36
can't I get OpenLDAP/MySQL/Vpopmail/PAM/whatever working?</a><br />
32
can't I get OpenLDAP/MySQL/Vpopmail/PAM/whatever working?</a></li>
39
33
<li><a href="#gdbmdb">Configuration script reports the following error,
40
34
and stops: "Cannot find either the gdbm or the db library", or it
41
35
fails in the <code>gdbmobj</code> or <code>bdbobj</code>
42
subdirectory</a>.<br />
36
subdirectory</a>.</li>
45
37
<li><a href="#solarisbug">Compilation fails on Solaris in the waitlib
46
subdirectory</a><br />
49
<li><a href="#osx">Compiling Courier-IMAP on OS/X</a><br />
39
<li><a href="#osx">Compiling Courier-IMAP on OS/X</a></li>
52
40
<li><a href="#makefail"><code>make install-strip</code> or <code>make
53
check</code> fails</a><br />
41
check</code> fails</a></li>
56
42
<li><a href="#tru64"><tt>gmake check</tt> fails on Compaq Tru64
60
44
<li><a href="#rpm">I don't know how to build the RPM packages as
64
46
<li><a href="#vpopmail">Problems compiling/linking with
70
52
<li><a href="#esmtptimeout">Why are my e-mails taking so long to
74
54
<li><a href="#esmtperr">Courier delivers ESMTP mail with a strange
75
error message</a><br />
55
error message</a></li>
78
56
<li><a href="#450">Server is not accepting any mail, returns a
79
<code>450 Service unavailable</code> error every time.</a><br />
57
<code>450 Service unavailable</code> error every time.</a></li>
82
58
<li><a href="#relay">How do I enable relaying for an IP address
86
60
<li><a href="#virtual">How do I implement virtual domain
90
62
<li><a href="#linkerr">Courier keeps restarting every minute, and there
91
63
are weird syslog messages about "unsafe" hard links</a></li>
92
64
<li><a href="#backupmx">How to configure Courier to be a backup MX for
96
66
<li><a href="#maxrcpts">Messages with more than 20 recipients are
102
<li><a href="#imapbugs">My IMAP client doesn't work</a><br />
72
<li><a href="#imapbugs">My IMAP client doesn't work</a></li>
105
73
<li><a href="#namespace">Can't create IMAP folders, only subfolders of
109
<li><a href="#imaplogin">Can't login via IMAP</a><br />
75
<li><a href="#imaplogin">Can't login via IMAP</a></li>
112
76
<li><a href="#fam">Repeated messages in syslog: "Failed to create cache
113
77
file: maildirwatch (user) Error: Input/output error Check for proper
114
78
operation and configuration of the File Access Monitor daemon
115
(famd)." How can I solve it?</a><br />
79
(famd)." How can I solve it?</a></li>
118
80
<li><a href="#imapfud">Q: I heard that Courier does not implement IMAP
124
<li><a href="#pop3run">The POP3 server doesn't run at bootup</a><br />
86
<li><a href="#pop3run">The POP3 server doesn't run at bootup</a></li>
127
87
<li><a href="#pop3login">Can't login via POP3</a></li>
339
293
<code>/usr/local/ssl/lib</code>, the <code>gcc</code> compiler needs to have
340
294
the <code>-I/usr/local/ssl/include</code> option for the preprocessor, and
341
295
the <code>-L/usr/local/ssl/lib</code> option for the linker. So, to have the
342
configuration script detect OpenSSL, use the following commands:<br />
296
configuration script detect OpenSSL, use the following commands:</p>
345
297
<pre>CPPFLAGS="-I/usr/local/ssl/include"
346
298
LDFLAGS="-L/usr/local/ssl/lib"
530
482
IMAP clients. Use the following procedure to build the RPMs with different
533
<li>Move the tarball to your <code>SOURCES</code> directory.<br />
485
<li>Move the tarball to your <code>SOURCES</code> directory.</li>
536
486
<li>Extract a single file from the tarball, <code>courier.spec</code>. This
537
file is found at the top level of the source tree.<br />
487
file is found at the top level of the source tree.</li>
540
488
<li>Move <code>courier.spec</code> to your <code>SPECS</code> directory.
541
Edit it and make whatever changes you need to make.<br />
544
<li>Use that spec file to build your RPMs.<br />
489
Edit it and make whatever changes you need to make.</li>
490
<li>Use that spec file to build your RPMs.</li>
547
491
<li>You will have to repeat the procedure when you want to build packages
548
492
from the next release. The spec file is subject to change, and there is
549
493
no guarantee that a spec file from one release will still work for the
697
641
RCPT TO: verbs</p>
699
643
<p><code>[SV]</code> This problem is apparently present in the Microsoft
700
Outlook client too. See item #7 in <a
644
Outlook client too. See item #7 in <a target="_blank"
701
645
href="http://support.microsoft.com/support/kb/articles/Q180/4/84.ASP"><code>http://support.microsoft.com/support/kb/articles/Q180/4/84.ASP</code></a>.
702
646
Note: contrary to the information in that article, this address specification
703
format is REQUIRED by <a href="http://www.rfc-editor.org/rfc/rfc821.txt">RFC
704
821</a>, and Microsoft is simply ignoring another Internet standard, here.</p>
647
format is REQUIRED by <a target="_blank"
648
href="http://www.rfc-editor.org/rfc/rfc821.txt">RFC 821</a>, and Microsoft is
649
simply ignoring another Internet standard, here.</p>
706
651
<p><code>[PP]</code> Solution: The usual solution for a 517 is to tell people
707
652
to explicitly put <> around all E-mail addresses. That is, program
1003
940
<p>A: Check the following</p>
1005
942
<li><code>AUTHMODULES</code> in the <code>imapd</code> configuration file
1009
944
<li>If the <code>authdaemon</code> authentication proxy is used, check the
1010
945
<code>authdaemonrc</code> configuration file. Check that
1011
<code>authdaemond</code> is running.<br />
946
<code>authdaemond</code> is running.</li>
1014
947
<li>Your authentication modules are properly configured. Some
1015
948
authentication modules have additional configuration files
1016
949
(<code>authldap</code> and <code>authmysql</code>). If you're using
1017
950
<code>authpam</code>, you need to configure your PAM library to
1018
951
authenticate the "<em>imap</em>" service. This is a separate task, and is
1019
specific to your PAM library and operating system.<br />
952
specific to your PAM library and operating system.</li>
1022
953
<li>You are using a database-based back-end, such as LDAP or MySQL, and the
1023
back-end server is down.<br />
954
back-end server is down.</li>
1026
955
<li>You're using maildirs. Courier's IMAP server only supports maildirs
1027
956
(<code>$HOME/Maildir</code>), it doesn't support mailbox files.</li>
1081
1004
(<code>authldap</code> and <code>authmysql</code>). If you're using
1082
1005
<code>authpam</code>, you need to configure your PAM library to
1083
1006
authenticate the "<em>pop3</em>" service. This is a separate task, and is
1084
specific to your PAM library and operating system.<br />
1007
specific to your PAM library and operating system.</li>
1087
1008
<li>You are using a database-based back-end, such as LDAP or MySQL, and the
1088
back-end server is down.<br />
1009
back-end server is down.</li>
1091
1010
<li>You're using maildirs. Courier's POP3 server only supports maildirs
1092
1011
(<code>$HOME/Maildir</code>), it doesn't support mailbox files.</li>
1117
1036
<h3><a name="help" id="help">Q: Asking for help on the courier-users and
1118
1037
courier-imap mailing lists</a></h3>
1039
<p>A: The <a target="_blank"
1121
1040
href="http://lists.sourceforge.net/lists/listinfo/courier-users">courier-users</a>
1041
or the <a target="_blank"
1123
1042
href="http://lists.sourceforge.net/lists/listinfo/courier-imap">courier-imap</a>
1124
1043
mailing list should be the first place to look for assistance with resolving
1125
1044
any issues. You only need to observe a few simple rules in order to increase
1126
1045
your chances of getting a quick and helpful response:</p>
1047
<li><a target="_blank"
1129
1048
href="http://lists.sourceforge.net/lists/listinfo/courier-users">Subscribe</a>/<a
1130
1050
href="http://lists.sourceforge.net/lists/listinfo/courier-imap">subscribe</a>
1131
1051
to the mailing list before you ask any questions. If you are not
1132
1052
subscribed, you will not receive any replies that are mailed to the list
1136
<li>Very important: Read <a
1054
<li>Very important: Read <a target="_blank"
1137
1055
href="http://www.catb.org/~esr/faqs/smart-questions.html#intro">http://www.catb.org/~esr/faqs/smart-questions.html#intro</a>
1138
before sending your first question.<br />
1056
before sending your first question.</li>
1141
1057
<li>Do not send HTML E-mail messages, unless you want many people to
1142
1058
automatically delete them, unread. If you are using MS-Outlook, turn off
1143
HTML formatting before sending mail to the list.<br />
1059
HTML formatting before sending mail to the list.</li>
1146
1060
<li>Before sending a question, check it to make sure that your message does
1147
1061
not contain the words "doesn't work." Saying only that something doesn't
1148
1062
work is not very useful in trying to analyze the problem. If something
1149
1063
isn't working correctly, merely stating it will not make much progress.
1150
1064
Be sure to always include in your messages:
1152
<li>The contents of any related configuration files.<br />
1066
<li>The contents of any related configuration files.</li>
1155
1067
<li>What happens, <em>exactly</em>, that makes you think that something
1156
isn't working right.<br />
1068
isn't working right.</li>
1159
1069
<li>The contents of your system log file (syslog, or
1160
<code>/var/log/messages</code>).<br />
1070
<code>/var/log/messages</code>).</li>
1163
1071
<li>Be sure to describe any non-standard modifications to the operating
1164
1072
system you're using, such as a kernel hacked with one of several
1165
1073
varieties of the OpenWall patch, or filesystema mounted with a
1166
1074
no-suid option. Many problems turn out to be unintentional conflicts
1167
1075
with various unexpected side-effects of these custom modifications
1168
(but not after wasting a great deal of time chasing ghosts).<br />
1076
(but not after wasting a great deal of time chasing ghosts).</li>
1173
1079
<li>Do not send large attachments (over 10K bytes is a rule of thumb), to
1174
1080
the list. Put it somewhere - on the web or on a FTP server - and include
1175
a link in your message instead. <br />
1081
a link in your message instead.</li>
1178
1082
<li>Always mention what you've already tried to do in order to fix the
1179
1083
problem. People are more likely to help you if they know that you've made
1180
1084
some effort to figure it out by yourself, and you are only asking for
1181
help after running into a dead end.<br />
1085
help after running into a dead end.</li>
1184
1086
<li>If you do not get an answer in one hour, don't resend your message. If
1185
1087
people open their mailbox and see five copies of the same message,
1186
1088
they'll be ignored. Have patience. Either wait some more, or accept it as
added
removed
courier/doc/FAQ.html
