.TH "popular-log" "7" "" "" ""
.SH "NAME"
popular-log \- log messages from POPular programs
.SH "DESCRIPTION"
This is a list of all the log messages printed by
.BR pcheckd (8),
.BR pproxy (8),
.BR pserv (8),
and
.BR pdeliver (8) .
.SH "LOG LEVEL"
.TS
l l.
DBG     debug messages
INF     informational messages
ERR     error messages
ADM     admin intervention required
SOS     critical event
BUG     software bug
.TE
.SH "MESSAGE LIST"
.TS
l lw60.
ID	Lvl   Name
\&	Description
_
\fB0001	INF   start
\&	T{
Pserv has started. The server is mostly initialized.
T}
\fB0004	BUG   left_main_loop
\&	T{
Somehow the main loop was terminated. This should never happen.
T}
\fB0005	INF   shutdown_server
\&	T{
The pserv server is shut down.
T}
\fB0006	ADM   dir_access_failed
\&	T{
The opendir() system call on a mailbox directory failed. This probably
means that something is wrong with permissions in the pop spool.
T}
\fB0007	SOS   out_of_memory
\&	T{
Pserv couldn't allocate memory to hold a mail message structure.
T}
\fB0008	ADM   name_too_long
\&	T{
The name of a mailbox directory and file is too long.
T}
\fB0009	ADM   stat_failed
\&	T{
The stat() system call failed for a mail message file. The message
will not be listed. This should never happen and probably means
that somebody tinkered around with a mailbox file by hand and
got the permission wrong.
T}
\fB000a	INF   log_reopen
\&	T{
The logfile will be reopened now. This should be the last message
of the parent process of the server to the log file. (See 000c for
the message in the new log file)
T}
\fB000b	SOS   log_reopen_failed
\&	T{
Reopening of the log file failed for some reason. The old file will
be kept open.
T}
\fB000c	INF   log_reopened
\&	T{

T}
\fB0014	SOS   out_of_memory
\&	T{
Pserv can't allocate memory for a msglist structure.
T}
\fB0018	ERR   unknown_command
\&	T{
The client sent an unknown POP command.
T}
\fB0019	SOS   no_session_found
\&	T{
The pserv parent process got a process id from wait() that he doesn't
know about, i.e. that shouldn't be one of his children. This should
never happen and probably means that there is some serious data
corruption or a bug in the program. pserv will immediately exit.
T}
\fB0020	ADM   child_died
\&	T{
A child of pserv or pproxy died with non-zero exit code. See the
log entries of the child for more details about what happend.
T}
\fB0021	SOS   child_died_signal
\&	T{
A child of pserv or pproxy died because of a signal. This can
either mean that there is a bug in the program of the system
has big problems (like running out of memory).
T}
\fB0022	SOS   out_of_memory
\&	T{
There is no memory to allocate an io context struct. The program is
immediately terminated.
T}
\fB0023	ERR   getpeername_failed
\&	T{
The getpeername() call failed. This probably means that the client
and subsequently the proxy has closed the connection.
T}
\fB0024	ADM   mailbox_too_long
\&	T{
The mailbox name that the proxy sent to the pserv is too long.
T}
\fB0025	ADM   mailbox_too_long
\&	T{
The mailbox name that the proxy sent to the pserv is too long.
T}
\fB0026	ADM   bad_mailbox
\&	T{
The mailbox name that the proxy sent to the pserv has a leading '/'.
T}
\fB0027	ADM   bad_mailbox
\&	T{
The mailbox name that the proxy sent to the pserv has funny
chars in it. Only the following chars are allowed: a-z, A-Z, 0-9,
'.', '_', '-', '+', '/', '=', '%'. Two adjacent dots ("..") are not
allowed.
T}
\fB0028	ADM   id_too_long
\&	T{
The id that the proxy sent to the pserv is too long.
T}
\fB0029	ADM   id_too_long
\&	T{
The id that the proxy sent to the pserv is too long.
T}
\fB0030	ADM   bad_id
\&	T{
The id that the proxy sent to the pserv has funny chars in it. Only
the following chars are allowed: a-z, A-Z, 0-9, '.', '_', '-'.
T}
\fB0031	ADM   flags_too_long
\&	T{
The flags that the proxy sent to the pserv are too long.
T}
\fB0032	ADM   flags_too_long
\&	T{
The flags that the proxy sent to the pserv are too long.
T}
\fB0033	ADM   bad_flags
\&	T{
The flags that the proxy sent to the pserv have funny chars in it.
Only a-z, A-Z, 0-9 are allowed.
T}
\fB0034	INF   login
\&	T{
A new connection from the proxy is coming in and the mailbox name, the
logging id and the flags have been received.
T}
\fB0035	ADM   null_byte_in_input
\&	T{
A null byte was encountered in input from a network socket. This
can never happen in a normal POP3 connection.
T}
\fB0037	ADM   msg_unlink_failed
\&	T{
After the QUIT command has been received, the server tried to
delete a message but failed.
T}
\fB0038	ADM   msg_rename_failed
\&	T{
After the QUIT command has been received, the server tried to
rename a message from the 'new' into the 'cur' directory but
failed.
T}
\fB0039	INF   quit
\&	T{
This message is logged after the client send a QUIT. It contains
statistics about the number of mails in mailbox, the number of new
mails, the number of read mails, and the number of deleted mails.
T}
\fB003a	SOS   socket_call_failed
\&	T{
When trying to open a listening socket, the socket system call
failed.
T}
\fB003b	SOS   setsockopt_failed
\&	T{
When trying to open a listening socket, the setsockopt call to set
SO_REUSEADDR failed.
T}
\fB003c	SOS   bind_failed
\&	T{
When trying to open a listening socket, the bind() failed.
T}
\fB003d	SOS   listen_failed
\&	T{
When trying to open a listening socket, the listen() failed.
T}
\fB003e	ERR   accept_error
\&	T{
The accept() call failed. This probably means that the client closed
the connection before the server could accept it. If this occures only
occasionally, it is harmless. If it occures more often, it might
indicate network problems.
T}
\fB003f	SOS   fork_failed
\&	T{
Pserv tried to fork a child and that failed. This probably means
that the system is overloaded. The connection to the client will
be closed and we try to keep going.
T}
\fB0042	SOS   select_error
\&	T{
The select () syscall in the main loop returned an error that is
not handled. This should never happen.
T}
\fB0047	ERR   unknown_command
\&	T{
An unknown POP3 command was received from the client. The client
got an error message. No action needs to be taken.
T}
\fB0048	ERR   user_name_too_long
\&	T{
The user name that the client sent is too long for some internal
buffer. The buffer should be big enough for any sensible name.
T}
\fB0049	ERR   write_error
\&	T{
An error occurred while writing to the client. This probably means
that the client closed the connection.
T}
\fB004a	ERR   unknown_command
\&	T{
An unknown POP3 command was received from the client. The client
got an error message. No action needs to be taken.
T}
\fB004b	ERR   password_too_long
\&	T{
The password that the client sent is too long for some internal
buffer. The buffer should be big enough for any sensible password.
T}
\fB004c	ADM   pdm_reload_failed
\&	T{
The reloading of a pdm module failed because this module doesn't
support the pdm_reload() function.
T}
\fB004d	SOS   pdm_error
\&	T{
A module returned an internal error while checking a user. This
means that the module is confused, maybe the underlain database
is corrupted. Check for log messages from the module itself to
find out more.
T}
\fB004e	SOS   pdm_error
\&	T{
A module returned an internal error while checking a user. This
means that the module is confused, maybe the underlain database
is corrupted. Check for log messages from the module itself to
find out more.
T}
\fB004f	ERR   readln_timeout
\&	T{
A timeout occurred while waiting for an input line from a socket.
This probably means that the client went away.
T}
\fB0050	ERR   readln_error
\&	T{
An error occurred while waiting for an input line from a socket.
This probably means that the client went away.
T}
\fB0051	ERR   readln_eof
\&	T{
An end-of-file occurred while waiting for an input line from a socket.
This probably means that the client went away.
T}
\fB0052	ERR   readln_too_long
\&	T{
A line was read that is too long. This might indicate an attack. The
buffer is long enough for any reasonable POP3 command etc.
T}
\fB0053	ADM   stat_failed
\&	T{
The stat() of a mail message file failed. A size of 0 will be
used. The quota can't be calculated accurately.
T}
\fB0054	ADM   rename_failed
\&	T{
After the mail message has been written to the 'tmp' directory, it
can't be renamed to the 'new' directory.
T}
\fB0055	INF   delivered
\&	T{
A mail has been delivered successfully.
T}
\fB0056	ADM   opendir_failed
\&	T{
The opendir() system call failed while trying to determine the
mailbox size.
T}
\fB0057	ERR   quota_exceeded
\&	T{
The quota on a mailbox was exceeded. No mail will be delivered.
T}
\fB0058	ERR   quota_exceeded
\&	T{
The quota on a mailbox was exceeded. No mail will be delivered.
T}
\fB0059	SOS   mailboxdir_error
\&	T{
Pdeliver can't change into the mailbox directory.
T}
\fB005a	ADM   open_tmpfile_failed
\&	T{
Opening the tmp file for a new mail message failed.
T}
\fB005b	ADM   fdopen_failed
\&	T{
fdopen() on new tmp file for mail message failed.
T}
\fB005c	ADM   write_mail_failed
\&	T{
A write to the tmp file for a new mail message failed.
T}
\fB005d	ADM   close_failed
\&	T{
The close on the tmp file for a new mail message failed.
T}
\fB005e	INF   debug_type
\&	T{
The debug options were changed through pcontrol. These are the new
options that are used from now on.
T}
\fB005f	INF   shutdown_all_received
\&	T{
The command 'shutdown all' was received from pcontrol. The server
will shut down all it's children and the exit itself.
T}
\fB0060	INF   shutdown_parent_received
\&	T{
The command 'shutdown parent' was received from pcontrol. The server
will shut down itself, but not its children.
T}
\fB0061	ADM   pcontrol_recvfrom_failed
\&	T{
The call to recvfrom() to get a command from pcontrol failed.
T}
\fB0062	ADM   pcontrol_sendto_failed
\&	T{
The call to sendto() to send an answer to pcontrol failed.
T}
\fB0063	ADM   no_mailbox
\&	T{
Changing into mailbox directory failed.
T}
\fB0064	ADM   mkdir_failed
\&	T{
Creation of the mailbox directory failed.
T}
\fB0065	ADM   no_mailbox
\&	T{
Changing into mailbox directory failed.
T}
\fB0066	ADM   mkdir_failed
\&	T{
Creation of the 'new' directory failed.
T}
\fB0067	ADM   mkdir_failed
\&	T{
Creation of the 'cur' directory failed.
T}
\fB0068	ADM   mkdir_failed
\&	T{
Creation of the 'tmp' directory failed.
T}
\fB0069	INF   checking
\&	T{
Checking user in POPular database modules.
T}
\fB006a	INF   result_user_accepted
\&	T{
The user was accepted by a pdm module.
T}
\fB006b	INF   result_user_exists
\&	T{
The user was found by a pdm module but authentication failed.
T}
\fB006c	INF   result_pdm_internal_error
\&	T{
A pdm module returned an internal error.
T}
\fB006d	INF   result_unknown_user
\&	T{
The user was not found by any pdm module.
T}
\fB006e	INF   result_unknown_result_code
\&	T{
An unknown result code was returned by pdm_auth_user().
T}
\fB006f	ADM   unknown_protocol
\&	T{
An unknown protocol identifier was used in the command file. The
program is terminated.
T}
\fB0070	INF   start
\&	T{
Pcheckd has been started and partially initialized.
T}
\fB0072	ADM   invalid_mailbox
\&	T{
The mailbox name that the client sent is invalid. The name is not
allowed to start with a '/'
T}
\fB0073	ERR   opendir_failed
\&	T{
The 'new' directory for the given mailbox can't be opened. This
probably means that the mailbox hasn't been created yet.
T}
\fB0074	ADM   opendir_failed
\&	T{
The 'cur' directory for the given mailbox can't be opened.
T}
\fB0075	ADM   unknown_request
\&	T{
The client sent an unknown request. Allowed are 'L' for load check
and 'M' for mailbox check.
T}
\fB0076	ERR   sendto_failed
\&	T{
Sending the answer of the requested check back to the client
failed.
T}
\fB0077	SOS   select_error
\&	T{
The select () syscall in the main loop returned an error that is
not handled. This should never happen.
T}
\fB0078	INF   shutdown
\&	T{
pcheckd received a QUIT, INT, TER, or PWR signal and is
shutting down.
T}
\fB0079	INF   debug_disabled
\&	T{
pcheckd received a SIGUSR1 and disabled debuglogging.
T}
\fB007a	INF   debug_enabled
\&	T{
pcheckd received a SIGUSR2 and enabled debuglogging.
T}
\fB007c	SOS   no_session_found
\&	T{
The pproxy parent process got a process id from wait() that he doesn't
know about, i.e. that shouldn't be one of his children. This should
never happen and probably means that there is some serious data
corruption or a bug in the program. pproxy will immediately exit.
T}
\fB007d	INF   shutdown_server
\&	T{
The pproxy server is shut down.
T}
\fB0084	INF   open_port
\&	T{
Pproxy has been instructed to listen to a new IP number and port.
T}
\fB0085	SOS   port_open_send_failed
\&	T{
Sending a port open request to the ringd process failed.
T}
\fB0086	SOS   port_open_failed
\&	T{
Opening of the port failed for some reason on the pproxy side.
T}
\fB0087	SOS   listen_failed
\&	T{
The listen() system call on the just opened and bound socket
failed.
T}
\fB0089	SOS   fork_failed
\&	T{
Pproxy tried to fork a child and that failed. This probably means
that the system is overloaded. The connection to the client will
be closed and we try to keep going.
T}
\fB008a	INF   start
\&	T{
PProxy has started and is mostly initialized.
T}
\fB008d	ADM   pidfile_symlink_failed
\&	T{
The symlink to the pidfile failed. The server will continue to run.
T}
\fB008e	SOS   select_error
\&	T{
The select () syscall in the main loop returned an error that is
not handled. This should never happen.
T}
\fB008f	BUG   left_main_loop
\&	T{
Somehow the main loop was terminated. This should never happen.
T}
\fB0096	SOS   backend_socket_call_failed
\&	T{
Creating a socket for a connection to the backend failed.
T}
\fB0097	SOS   connect_to_backend_failed
\&	T{
The connect to a backend failed.
T}
\fB0098	SOS   backend_read_err
\&	T{
A read from a POP3 backend failed.
T}
\fB0099	SOS   backend_not_ready
\&	T{
A POP3 backend sent a -ERR reply on connection.
T}
\fB009a	SOS   backend_read_err
\&	T{
A write to a POP3 backend failed.
T}
\fB009b	SOS   backend_read_err
\&	T{
A read from a POP3 backend failed.
T}
\fB009c	ADM   login_failed
\&	T{
The login to a POP3 backend server failed. The answer to the USER
command was -ERR.
T}
\fB009d	SOS   backend_read_err
\&	T{
A write to a POP3 backend failed.
T}
\fB009e	SOS   backend_read_err
\&	T{
A read from a POP3 backend failed.
T}
\fB009f	ADM   login_failed
\&	T{
The login to a POP3 backend server failed. The answer to the PASS
command was -ERR.
T}
\fB0100	SOS   socket_call_failed
\&	T{
The creation of a UDP socket to talk to the pcheckd on a backend
failed.
T}
\fB0101	SOS   connect_failed
\&	T{
The connect() call on the UDP socket to the pcheckd on a backend
failed.
T}
\fB0102	SOS   buffer_to_small
\&	T{
A buffer for sending a mailbox name to the pcheckd is too small.
T}
\fB0103	SOS   send_failed
\&	T{
The send() call sending a request to the pcheckd failed.
T}
\fB0104	SOS   select_failed
\&	T{
The select () call waiting for answer from pcheckd failed in an
unexpected way.
T}
\fB0105	SOS   recv_failed
\&	T{
Recv() call failed when reading answer from pcheckd.
T}
\fB0106	ERR   check_udp_timeout
\&	T{
Pproxy timed out waiting for an answer from pcheckd.
T}
\fB0107	ERR   timeout
\&	T{
A timeout occurred while proxying data.
T}
\fB0108	INF   quit
\&	T{
The proxy child shuts down after its work is done. The proxied
bytes in both directions are reported.
T}
\fB0109	INF   quit
\&	T{
The client closed the connection while faking a POP3 dialog.
T}
\fB010a	INF   quit
\&	T{
The client send a quit while faking a POP3 dialog.
T}
\fB010c	SOS   out_of_memory
\&	T{
There is not enought memory to allocate an IO context.
T}
\fB010d	SOS   write_to_backend_failed
\&	T{
A write call to the backend failed.
T}
\fB010f	SOS   out_of_memory
\&	T{
There is not enought memory to allocate an IO context.
T}
\fB0110	BUG   illegal_value
\&	T{
The do_pop3_auth() function returned an illegal value.
T}
\fB0111	ERR   getsockname_error
\&	T{
getsockname() returned an error. This probably means that the
client disconnected before we could look at the socket.
T}
\fB0112	ERR   getpeername_error
\&	T{
getpeername() returned an error. This probably means that the
client disconnected before we could look at the socket.
T}
\fB0113	INF   connect
\&	T{
Incoming connection from client.
T}
\fB0114	BUG   unknown_protocol
\&	T{
No protocol information for this virtual server is found. This
should never happen.
T}
\fB0116	SOS   out_of_memory
\&	T{
There is not enought memory to allocate an IO context.
T}
\fB0117	INF   virt_serv_disabled
\&	T{
The virtual server is disabled
T}
\fB0118	ERR   write_error
\&	T{
A write to the client failed.
T}
\fB0119	ERR   write_error
\&	T{
A write to the client failed.
T}
\fB011b	ERR   quit
\&	T{
Client sent QUIT command in authentication phase.
T}
\fB011c	INF   virt_serv_fake
\&	T{
The virtual server is to be faked.
T}
\fB011d	ERR   auth_fail
\&	T{
The authorisation of the user failed because of the client
IP number.
T}
\fB011e	ERR   auth_fail
\&	T{
The authorisation of the user failed because of the protocol
used.
T}
\fB011f	ERR   auth_fail
\&	T{
The authorisation of the user failed because the wrong password
was given.
T}
\fB0120	ERR   auth_fail
\&	T{
The authorisation of the user failed for unknown reasons.
T}
\fB0121	BUG   illegal_auth_result
\&	T{
A PDM module returned an illegal result code.
T}
\fB0122	SOS   unknown_backend
\&	T{
A PDM module told us which backend to use. Unfortunately this
backend is not configured.
T}
\fB0123	INF   user_auth
\&	T{
User was authenticated.
T}
\fB0124	INF   operation
\&	T{
The backend is configured to be faked.
T}
\fB0125	INF   quit
\&	T{
The backend is configured to be offline.
T}
\fB0126	INF   operation
\&	T{
The backend uses POP3 protocol. Proxying will now be started.
T}
\fB0127	INF   operation
\&	T{
The backend pcheckd told us that the mailbox is empty, the
load on the storage server is too high, or the maximum number
of sessions is reached on the storage server or a timeout
occured while waiting for the answer from the pcheckd. The
POP connection will be faked locally.
T}
\fB0128	INF   operation
\&	T{
The backend uses XPOP protocol. Proxying will now be started.
T}
\fB0129	BUG   invalid_value
\&	T{
Invalid value for the backend protocol.
T}
\fB012a	BUG   invalid_value
\&	T{
Invalid value for the backend state.
T}
\fB012b	INF   shutdown_children_received
\&	T{
The command 'shutdown children' was received from pcontrol. The server
will shut down all it's children.
T}
\fB012c	INF   shutdown_children
\&	T{
The pproxy server is shutting down all its children.
T}
\fB012d	INF   shutdown_children
\&	T{
The pserv server is shutting down all its children.
T}
\fB012e	INF   shutdown_delayed
\&	T{
The pproxy server closed all listening ports. After all children have
died, it will close down.
T}
\fB012f	INF   shutdown_delayed_received
\&	T{
The command 'shutdown delayed' was received from pcontrol. The server
will not accept new connections and shut down itself after the last
child has died.
T}
\fB0130	INF   all_children_gone
\&	T{
All children have died and the server got a delayed shutdown
command earlier. It will shutdown now.
T}
\fB0131	INF   all_children_gone
\&	T{
All children have died and the server got a delayed shutdown
command earlier. It will shutdown now.
T}
\fB0132	INF   shutdown_delayed
\&	T{
The pserv server closed the listening ports. After all children have
died, it will close down.
T}
\fB0133	INF   got_term_signal
\&	T{
The child got a TERM or INT signal and will shut down. This signal
was either delivered to the parent between the last check for signals
and the fork, or it was delivered to the child before the child
could change its signal handling to the default behaviour. In any
case, calling exit immediately is the right thing to do here.
T}
\fB0135	SOS   open_statefile
\&	T{
Open of the state file failed. The program will be terminated.
T}
\fB0136	SOS   seek_statefile
\&	T{
Seeking inside the state file failed. The program will be
terminated. Try deleting the state file before restarting.
T}
\fB0137	SOS   write_statefile
\&	T{
Writing to state file failed. The program will be terminated.
Try deleting the state file before restarting.
T}
\fB0138	SOS   mmap_statefile
\&	T{
Mmapping the state file failed. The program will be terminated.
Try deleting the state file before restarting.
T}
\fB0139	ADM   symlink_statefile_failed
\&	T{
The symlinking of the real state file to its symbolical name
failed. The server will still work, but the pstatus program
will not find the state file.
T}
\fB013a	SOS   control_socket_open_failed
\&	T{
Opening of the UNIX domain control socket failed. The program will be
terminated.
T}
\fB013b	SOS   control_bind_failed
\&	T{
Binding the UNIX domain control socket failed. The program will be
terminated.
T}
\fB013c	SOS   control_symlink_failed
\&	T{
Linking the UNIX domain control socket to the canonical name failed.
The programm will be terminated.
T}
\fB0140	ADM   pidfile_open_failed
\&	T{
The opening of the pidfile failed. The server will continue to run.
T}
\fB0141	ADM   unlink_file_in_rundir_failed
\&	T{
An unlink() operation in the run directory failed. The file can
be a pid file, the state file or the control socket.
T}
\fB0142	ADM   unlink_link_in_rundir_failed
\&	T{
An unlink() operation in the run directory failed. The filename is
a link to either a pid file, a state file or a control socket.
T}
\fB0143	SOS   port_open_no_fd
\&	T{
The opening and binding of the port by the ringd process failed
for some reason. The message from the ringd process is printed
with this message.
T}
\fB0144	INF   stat
\&	T{
Statistics from pcheckd: 'requests' is the number of all
requests that pcheckd got, 'mailchecks' is the number of
new format mailcheck requests, 'mailchecks_old' the number
of old format mailcheck requests, 'empty' the number of
requests finding an empty mailbox, 'not_empty' the number of
requests finding a not empty mailbox, 'load_too_high'
the number of requests answered with that message, and
'maxsession_reached' the number of messages send while the
maximum number of pserv sessions was used. The
statistics are logged and cleared on SIGHUP.
T}
\fB0145	SOS   select_error
\&	T{
An error occurred in the select () system call while proxying
data.
T}
\fB0146	ERR   accept_failed
\&	T{
The accept () system call failed for some reason.
T}
\fB0147	ERR   msg_rename_failed
\&	T{
Renaming of a mail file failed, because it is not there. Another
pserv process probably got to this file before we did.
T}
\fB0148	ERR   msg_unlink_failed
\&	T{
Deleting of a mail message failed. Probably another pserv process
was faster.
T}
\fB0149	ADM   config_set
\&	T{
A config variable was set to a new value.
T}
\fB014a	BUG   sigaction_failed
\&	T{
A sigaction () system call failed. This should never happen.
T}
\fB014b	ADM   config_set
\&	T{
A config variable was set to a new value.
T}
\fB014d	ADM   config_set
\&	T{
A config variable was set to a new value.
T}
\fB014e	ADM   server_now_online
\&	T{
The server listens on a port now and accepts connections. You should
see this log message in response to a 'server online' command.
T}
\fB014f	ADM   server_now_offline
\&	T{
The server closed its listening port and doesn't accept any new
connections. You should see this log message in response to a 'server
offline' command.
T}
\fB0150	ADM   config_capa
\&	T{
Capability was configured
T}
\fB0151	ADM   config_capa
\&	T{
Capability was configured
T}
\fB0152	ADM   config_capa
\&	T{
Capability was configured
T}
\fB0153	ADM   config_capa
\&	T{
Capability was configured
T}
\fB0154	ADM   bad_mailbox
\&	T{
The mailbox name that the proxy sent to the pserv has funny
chars in it. Only the following chars are allowed: a-z, A-Z, 0-9,
'.', '_', '-', '+', '/', '=', '%'. Two adjacent dots ("..") are not
allowed.
T}
\fB0155	SOS   fork_failed
\&	T{
The fork () system call in pcheckd failed.
T}
\fB0156	ADM   child_died
\&	T{
A child of pcheckd died with non-zero exit code. See the log entries
of the child for more details about what happened.
T}
\fB0157	ADM   child_died_signal
\&	T{
A child of pcheckd died because of a signal. This can either mean
that there is a bug in the program of the system has big problems
(like running out of memory).
T}
\fB0158	ERR   mailfile_does_not_exist
\&	T{
A mail message file does not exist. This probably means that the
mail has been deleted by another POP session running at the same
time.
T}
\fB0159	ADM   mailfile_open_failed
\&	T{
Opening a mail message file for reading failed.
T}
\fB015a	SOS   mailfile_mmap_failed
\&	T{
The mmap () system call on the mail message file failed.
T}
\fB015b	SOS   mailfile_munmap_failed
\&	T{
The unmap () system call on the mail message file failed.
T}
\fB015d	ERR   write_error
\&	T{
Error writing mail message to proxy socket.
T}
\fB015e	ERR   write_error
\&	T{
Error writing mail message to proxy socket.
T}
\fB015f	ERR   write_error
\&	T{
Error writing mail message to proxy socket.
T}
\fB0160	ADM   config_set
\&	T{
A boolean config variable was set to a new value.
(0=no=off=false, 1=yes=on=true)
T}
\fB0161	ERR   write_error
\&	T{
Error writing mail message to proxy socket.
T}
\fB0162	ADM   msg_size_zero
\&	T{
A mail message has size zero. It will not be listed.
T}
\fB0163	ADM   config_backend_del
\&	T{
A 'backend del' command was executed.
T}
\fB0164	ADM   config_backend_flush
\&	T{
A 'backend flush' command was executed.
T}
\fB0165	ADM   config_backend_conf
\&	T{
A 'backend conf' command was executed.
T}
\fB0166	ADM   config_vserv_conf
\&	T{
A 'vserv conf' command was executed.
T}
\fB0167	ADM   config_vserv_flush
\&	T{
A 'vserv flush' command was executed.
T}
\fB0168	ADM   config_vserv_del
\&	T{
A 'vserv del' command was executed.
T}
\fB0169	ADM   config_capa_load
\&	T{
A 'capa load' command was executed.
T}
\fB016a	ADM   config_capa_del
\&	T{
A 'capa del' command was executed.
T}
\fB016b	ADM   config_pdm_add
\&	T{
A 'pdm add' command was executed.
T}
\fB016c	ADM   config_pdm_del
\&	T{
A 'pdm del' command was executed.
T}
\fB016d	ADM   config_pdm_reload
\&	T{
A 'pdm reload' command was executed.
T}
\fB016e	ADM   config_pdm_flush
\&	T{
A 'pdm flush' command was executed.
T}
\fB016f	BUG   illegal_session_state
\&	T{
The state in sess_ok() has an illegal value. This can never happen.
The server keeps going but might log strange things.
T}
\fB0170	ADM   session_state
\&	T{
The session state is printed. This can be one of 'OK', 'WARN', 'MAX'.
See the documentation for the exact meaning of these messages.
T}
\fB0171	BUG   illegal_load_state
\&	T{
The state in sess_load() has an illegal value. This can never happen.
The server keeps going but might log strange things.
T}
\fB0172	ADM   load_state
\&	T{
The load state is printed. This can be one of 'OK', 'WARN', 'MAX'.
See the documentation for the exact meaning of these messages.
T}
\fB0173	SOS   touch_failed
\&	T{
Creating or 'touching' of a flag file failed.
T}
\fB0174	SOS   unlink_failed
\&	T{
Unlink of a flag file failed.
T}
\fB0177	ERR   auth_fail
\&	T{
The authorisation of the user failed because the user is unknown.
T}
\fB0178	ADM   select_error
\&	T{
The rel_select() call failed.
T}
\fB0179	INF   operation
\&	T{
The backend uses XPOP protocol. Proxying will now be started.
T}
\fB017a	ADM   config_set
\&	T{
A config variable was set to a new value.
T}
\fB017c	ERR   child_died_timeout
\&	T{
A child of pserv or pproxy died because of an ALRM signal. This
means that 'sessiontimeout' (or, for pproxy, 'authtimeout') ran
out.
T}
\fB017d	INF   msg_info
\&	T{
A message was deleted.
T}
\fB017e	INF   msg_info
\&	T{
A message was moved from new to cur.
T}
\fB017f	ERR   too_many_bad_commands
\&	T{
Too many bad commands were received while in auth phase. The server
will close the connection. The number is configured in the
MAX_BAD_COMMANDS define in pconfig.h
T}
\fB0180	ERR   too_many_bad_commands
\&	T{
Too many bad commands were received while in auth phase. The server
will close the connection. The number is configured in the
MAX_BAD_COMMANDS define in pconfig.h
T}
\fB0181	SOS   sock_open_failed
\&	T{
Pproxy tried to open a unix domain socket to talk to the ringd and
this failed
T}
\fB0182	SOS   sock_connect_failed
\&	T{
Pproxy tried to connect to the unix domain socket of the ringd and
this failed
T}
\fB0183	INF   start
\&	T{
ringd has started.
T}
\fB0184	SOS   open_socket
\&	T{
ringd can't open the unix domain socket to listen for commands.
T}
\fB0185	SOS   chown_socket
\&	T{
ringd can't chown its unix domain socket.
T}
\fB0186	INF   quit
\&	T{
ringd go a signal and will quit now.
T}
\fB0187	SOS   socket_max_reached
\&	T{
The maximum number of sockets is reached. If you need more sockets
change RINGD_MAX_SOCK and recompile.
T}
\fB0188	ADM   socket_error
\&	T{
The socket system call returned an error.
T}
\fB0189	ADM   setsockopt_error
\&	T{
The setsockopt system call returned an error.
T}
\fB018a	SOS   bind_error
\&	T{
The bind system call returned an error.
T}
\fB018b	INF   port_list
\&	T{
List of currently opend ports.
T}
\fB018c	ADM   unknown_command
\&	T{
ringd received an unknown command.
T}
\fB018d	ADM   space_char_missing
\&	T{
ringd misses the space char at the 2nd position in the command
string which separates the command from arguments.
T}
\fB018e	ADM   space_char_missing
\&	T{
ringd misses the space char in the command string which separates
the first from the second argument
T}
\fB018f	ADM   port_invalid
\&	T{
The port number given as second argument to a ringd command is
syntactically invalid.
T}
\fB0190	ADM   port_out_of_range
\&	T{
The port number given as second argument to a ringd command is
out of range.
T}
\fB0191	ADM   port_forbidden
\&	T{
The port number given as second argument to a ringd command is
forbidden by configuration (change ALLOWED_PORTS and recompile).
T}
\fB0192	ADM   invalid_ip
\&	T{
The port number given as first argument to a ringd command is
is invalid.
T}
\fB0193	INF   close_port
\&	T{
Pproxy has been instructed to listen to a new IP number and port.
T}
\fB0194	SOS   port_close_send_failed
\&	T{
Sending a port close request to the ringd process failed.
T}
\fB0195	SOS   port_close_failed
\&	T{
Closing of the port failed for some reason on the pproxy side.
T}
\fB0196	SOS   server_method_failed
\&	T{
A SSL*_server_method() call failed. This probably means that there
is something wrong with your openssl library setup.
T}
\fB0199	ERR   tls_init_failed
\&	T{
Initialization of new TLS connection failed (SSL_new call failed).
T}
\fB019a	ERR   tls_set_fd_failed
\&	T{
Initialization of new TLS connection failed (SSL_set_fd call failed).
T}
\fB019b	ERR   tls_accept
\&	T{
Initialization of new TLS connection failed (SSL_accept call failed).
T}
\fB019c	BUG   unknown_protocol
\&	T{
No protocol information for this virtual server is found. This
should never happen.
T}
\fB019d	ADM   key_file_error
\&	T{
The TLS key file could not be opened. (Call to
SSL_CTX_use_RSAPrivateKey_file failed.)
T}
\fB019e	ADM   certificate_file_error
\&	T{
The TLS key file could not be opened. (Call to
SSL_CTX_use_RSAPrivateKey_file failed.)
T}
\fB019f	ERR   tls_init_after_stls_failed
\&	T{
Initialization of new TLS connection after STLS failed. The
connection will be dropped because we can't do anything else
at this point. The +OK was already sent because we had to send
it before initializing TLS on this socket.
T}
\fB0200	INF   switch_to_tls
\&	T{
Connection is switched to TLS after STLS command.
T}
\fB0201	INF   switch_to_tls
\&	T{
Connection is switched to TLS after STLS command.
T}
\fB0202	ERR   tls_init_after_stls_failed
\&	T{
Initialization of new TLS connection after STLS failed. The
connection will be dropped because we can't do anything else
at this point. The +OK was already sent because we had to send
it before initializing TLS on this socket.
T}
\fB0203	SOS   tls_seed_failed
\&	T{
Initialization of the TLS pseudo random number generator failed.
This is serious because it could potentially mean that there is
no security at all.
T}
.TE
.SH "FILES"
.PP
.IP "/var/log/popular/pcheckd"
Log file of the
.BR pcheckd (8)
program
.IP "/var/log/popular/pproxy"
Log file of the
.BR pproxy (8)
program
.IP "/var/log/popular/pserv"
Log file of the
.BR pserv (8)
program
.IP "/var/log/popular/pdeliver"
Log file of the
.BR pdeliver (1)
program
.SH "SEE ALSO"
.PP
pcheckd(8), pdeliver(1), pproxy(8), pserv(8), The POPular Manual
.SH "AUTHOR"
.PP
Jochen Topf jochen@remote\&.org
.PP
\fB
http://www\&.remote\&.org/jochen/mail/popular/
\fR
<URL:http://www\&.remote\&.org/jochen/mail/popular/>
.SH "COPYRIGHT"
.PP
The POPular suite is copyright (C) 1999-2002 by Jochen Topf
jochen@remote\&.org\&.
.PP
This program is free software; you can redistribute it and/or modify
it under the terms of the GNU General Public License as published by
the Free Software Foundation; either version 2 of the License, or
(at your option) any later version\&.
.PP
This program is distributed in the hope that it will be useful,
but WITHOUT ANY WARRANTY; without even the implied warranty of
MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE\&. See the
GNU General Public License for more details\&.
.PP
You should have received a copy of the GNU General Public License
along with this program; if not, write to the Free Software
Foundation, Inc\&., 59 Temple Place, Suite 330, Boston, MA 02111-1307, USA