[xmail] Re: config files discussion
Jeffrey Laramie wrote: On Tuesday 20 February 2007 12:32, Davide Libenzi wrote: On Tue, 20 Feb 2007, Dave Henderson wrote: Davide, Thanks for your reply. I can see your points. It was just a question I had as it seems alot of the daemons I use, use the apache style or a single config file method. The daemons also don't lock the files when reading them, they just read them upon startup (of course) and re-read them automatically within a certain period of time (to check for any changes made to them). I suppose both styles have their strengths and weaknesses. In either case, thanks for the reply. I'm not an heavy Apache user (actually, I use thttpd ;) but IIRC Apache is going in the exact opposite direction (splitting configs). In recent openSUSE releases httpd.conf is nothing more than comments and Include statements. All the actual configuration is divided up amongst the Included config files and directories. Most of the user configuration is in vhost containers that each have a vhostname.conf file in the vhosts.d directory. It takes a little getting used to but the design is actually very nice once you see how it works. Jeff - To unsubscribe from this list: send the line unsubscribe xmail in the body of a message to [EMAIL PROTECTED] For general help: send the line help in the body of a message to [EMAIL PROTECTED] That's what my apache (and UnrealIRCd) config looks like too. But this will definately make updates from the CONTROL interface much harder, probably impossible for Davide. I agree with Francis Clement that it would be easier if most of the current command-line options were in the SERVER.tab or some other config file. Ivo - To unsubscribe from this list: send the line unsubscribe xmail in the body of a message to [EMAIL PROTECTED] For general help: send the line help in the body of a message to [EMAIL PROTECTED]
[xmail] Small GLST bug maybe?
Hello all, I decided to give glst a try. Mostly out of curiosity 'cause I don't receive that much spam at all... yet... :( First, it took me a while to figure out how to pass the --cfg parameter to the glst binary but I've got that figured out now. At first I tried this in my filters.pre-data.tab: !aex /data/MailRoot/bin/glst --cfg /etc/glst.conf --mfile @@FILE But now I know I had to set it up like this: !aex /data/MailRoot/bin/glst --cfg /etc/glst.conf --mfile @@FILE The errors (-97) went away but I didn't get the impression the filter was working properly because all mail kept coming in without any delay. I checked the filters logfile and it said: [EMAIL PROTECTED] [EMAIL PROTECTED] xxx.xxx.xxx.xxx xxx.xxx.xxx.xxx 2007-02-21 22:25:46 pre-data 0 0 /data/MailRoot/bin/glst;--cfg;/etc/glst.conf;--mfile;/tmp/msrv8b40c.4140b.tmp; Looks ok... right? I mean, a first-time user wouldn't notice anything wrong with that. At least I see a 0 now where it used to be -97. I dumped the database I created by running glst manually once or twice and it didn't list the emails that had come in. So I was sure something had to be wrong. I then deleted the databases to see what would happen but the filters logfile still didn't show any errors but the database wasn't re-created either... I then changed to permissions on the directory (I have xmail running as user mail) where the database resides and pronto, it works! Maybe it's an idea to let glst return some kind of return code when it can't access or create the database... Anyway, keep up the good work! -- Best regards, Henri mailto:[EMAIL PROTECTED] - To unsubscribe from this list: send the line unsubscribe xmail in the body of a message to [EMAIL PROTECTED] For general help: send the line help in the body of a message to [EMAIL PROTECTED]
[xmail] Re: Small GLST bug maybe?
On Wed, 21 Feb 2007, Henri van Riel wrote: Hello all, I decided to give glst a try. Mostly out of curiosity 'cause I don't receive that much spam at all... yet... :( First, it took me a while to figure out how to pass the --cfg parameter to the glst binary but I've got that figured out now. At first I tried this in my filters.pre-data.tab: !aex /data/MailRoot/bin/glst --cfg /etc/glst.conf --mfile @@FILE But now I know I had to set it up like this: !aex /data/MailRoot/bin/glst --cfg /etc/glst.conf --mfile @@FILE The errors (-97) went away but I didn't get the impression the filter was working properly because all mail kept coming in without any delay. I checked the filters logfile and it said: [EMAIL PROTECTED] [EMAIL PROTECTED] xxx.xxx.xxx.xxx xxx.xxx.xxx.xxx 2007-02-21 22:25:46 pre-data 0 0 /data/MailRoot/bin/glst;--cfg;/etc/glst.conf;--mfile;/tmp/msrv8b40c.4140b.tmp; Looks ok... right? I mean, a first-time user wouldn't notice anything wrong with that. At least I see a 0 now where it used to be -97. I dumped the database I created by running glst manually once or twice and it didn't list the emails that had come in. So I was sure something had to be wrong. I then deleted the databases to see what would happen but the filters logfile still didn't show any errors but the database wasn't re-created either... I then changed to permissions on the directory (I have xmail running as user mail) where the database resides and pronto, it works! Maybe it's an idea to let glst return some kind of return code when it can't access or create the database... GLST defaults to 0 as generic error code in case something happen. In that way messages can go through w/out causing any problems. You can use the generr command line or config option to change it. - Davide - To unsubscribe from this list: send the line unsubscribe xmail in the body of a message to [EMAIL PROTECTED] For general help: send the line help in the body of a message to [EMAIL PROTECTED]
[xmail] SMTP error: 451 Requested action aborted: (-100) local error in processing
Hello all, I just installed XMailserver on a brand new machine running Fedora Core 6. I now get this error when trying to connect via SMTP: === 220 server.name.test [EMAIL PROTECTED] [XMail 1.24 ESMTP Server] service ready; Thu, 22 Feb 2007 00:25:04 +0100 HELO something 451 Requested action aborted: (-100) local error in processing === I have done a couple of other successful XMailserver installations in the past and haven't seen this error before. Does anyone know what could be causing this? Thanks! Sincerely, Bart Mortelmans - To unsubscribe from this list: send the line unsubscribe xmail in the body of a message to [EMAIL PROTECTED] For general help: send the line help in the body of a message to [EMAIL PROTECTED]
[xmail] Re: SMTP error: 451 Requested action aborted: (-100) local error in processing
On Thu, 22 Feb 2007, Bart Mortelmans wrote: Hello all, I just installed XMailserver on a brand new machine running Fedora Core 6. I now get this error when trying to connect via SMTP: === 220 server.name.test [EMAIL PROTECTED] [XMail 1.24 ESMTP Server] service ready; Thu, 22 Feb 2007 00:25:04 +0100 HELO something 451 Requested action aborted: (-100) local error in processing === I have done a couple of other successful XMailserver installations in the past and haven't seen this error before. Does anyone know what could be causing this? Duh!?! -100 is ERR_SHMAT and is never used in 1.24!?! - Davide - To unsubscribe from this list: send the line unsubscribe xmail in the body of a message to [EMAIL PROTECTED] For general help: send the line help in the body of a message to [EMAIL PROTECTED]
[xmail] Re: SMTP error: 451 Requested action aborted: (-100) local error in processing
Duh!?! -100 is ERR_SHMAT and is never used in 1.24!?! Regretfully, this is what I'm getting as a result. I did a normal compilation from the source (make -f Makefile.lnx). The only strange thing I can think of (different from what I'm used to) is that this server uses RAID 0 for the partition mounted under /. In debug modus, I just see this: SMAIL thread [00] started SMAIL thread [01] started SMAIL thread [02] started SMAIL thread [03] started SMAIL thread [04] started SMAIL thread [05] started SMAIL thread [06] started SMAIL thread [07] started SMAIL thread [08] started SMAIL thread [09] started SMAIL thread [10] started SMAIL thread [11] started SMAIL thread [12] started SMAIL thread [13] started SMAIL thread [14] started [XMail 1.24 CTRL Server] started [XMail 1.24 CTRLS Server] started SMAIL thread [15] started [XMail 1.24 POP3 Server] started [XMail 1.24 POP3S Server] started [XMail 1.24 ESMTP Server] started [XMail 1.24 ESMTPS Server] started [XMail 1.24 PSYNC Server] started [XMail 1.24 FINGER Server] started LMAIL thread [00] started LMAIL thread [01] started LMAIL thread [02] started SMTP client connection from [192.168.1.116] SMTP client exit [192.168.1.116] This is the script I use to start it with: #!/bin/sh XMAIL_ROOT=/var/MailRoot XMAIL_CMD_LINE=-Pl -Sl -Cl -Ll -Mm -Ql --debug -Md PATH=$XMAIL_ROOT/bin:/usr/local/sbin:/usr/local/bin:/sbin:/bin:/usr/sbin:/usr/bin NAME=XMail DESC=XMail server set -e ulimit -c 2 MAIL_ROOT=$XMAIL_ROOT export MAIL_ROOT MAIL_CMD_LINE=$XMAIL_CMD_LINE export MAIL_CMD_LINE export LD_ASSUME_KERNEL=2.6.19 /var/MailRoot/bin/XMail -Pl -Sl -Cl -Ll -Mm -Ql --debug -Md I'll try some more things, but am unsure where to look... Sincerely, Bart Mortelmans - To unsubscribe from this list: send the line unsubscribe xmail in the body of a message to [EMAIL PROTECTED] For general help: send the line help in the body of a message to [EMAIL PROTECTED]
[xmail] Re: SMTP error: 451 Requested action aborted: (-100) local error in processing
On Thu, 22 Feb 2007, Bart Mortelmans wrote: Duh!?! -100 is ERR_SHMAT and is never used in 1.24!?! Ok, it's not ERR_SHMAT but ERR_NO_ROOT_DOMAIN_VAR. You're missing the RootDomain server.tab variable. I made a script to extract error codes, and that's the output ... - Davide 0 -- ERR_SUCCESS 1 -- ERR_SERVER_SHUTDOWN 2 -- ERR_MEMORY 3 -- ERR_NETWORK 4 -- ERR_SOCKET_CREATE 5 -- ERR_TIMEOUT 6 -- ERR_LOCKED 7 -- ERR_SOCKET_BIND 8 -- ERR_CONF_PATH 9 -- ERR_USERS_FILE_NOT_FOUND 10 -- ERR_FILE_CREATE 11 -- ERRDUMMY 12 -- ERR_USER_NOT_FOUND 13 -- ERR_USER_EXIST 14 -- ERR_WRITE_USERS_FILE 15 -- ERR_NO_USER_PRFILE 16 -- ERR_FILE_DELETE 17 -- ERR_DIR_CREATE 18 -- ERR_DIR_DELETE 19 -- ERR_FILE_OPEN 20 -- ERR_INVALID_FILE 21 -- ERR_FILE_WRITE 22 -- ERR_MSG_NOT_IN_RANGE 23 -- ERR_MSG_DELETED 24 -- ERR_INVALID_PASSWORD 25 -- ERR_ALIAS_FILE_NOT_FOUND 26 -- ERR_ALIAS_EXIST 27 -- ERR_WRITE_ALIAS_FILE 28 -- ERR_ALIAS_NOT_FOUND 29 -- ERR_SVR_PRFILE_NOT_LOCKED 30 -- ERR_GET_PEER_INFO 31 -- ERR_SMTP_PATH_PARSE_ERROR 32 -- ERR_BAD_RETURN_PATH 33 -- ERR_BAD_EMAIL_ADDR 34 -- ERR_RELAY_NOT_ALLOWED 35 -- ERR_BAD_FORWARD_PATH 36 -- ERR_GET_SOCK_INFO 37 -- ERR_GET_SOCK_HOST 38 -- ERR_NO_DOMAIN 39 -- ERR_USER_NOT_LOCAL 40 -- ERR_BAD_SERVER_ADDR 41 -- ERR_BAD_SERVER_RESPONSE 42 -- ERR_INVALID_POP3_RESPONSE 43 -- ERR_LINKS_FILE_NOT_FOUND 44 -- ERR_LINK_EXIST 45 -- ERR_WRITE_LINKS_FILE 46 -- ERR_LINK_NOT_FOUND 47 -- ERR_SMTPGW_FILE_NOT_FOUND 48 -- ERR_GATEWAY_ALREADY_EXIST 49 -- ERR_GATEWAY_NOT_FOUND 50 -- ERR_USER_NOT_MAILINGLIST 51 -- ERR_NO_USER_MLTABLE_FILE 52 -- ERR_MLUSER_ALREADY_EXIST 53 -- ERR_MLUSER_NOT_FOUND 54 -- ERR_SPOOL_FILE_NOT_FOUND 55 -- ERR_INVALID_SPOOL_FILE 56 -- ERR_SPOOL_FILE_EXPIRED 57 -- ERR_SMTPRELAY_FILE_NOT_FOUND 58 -- ERR_DOMAINS_FILE_NOT_FOUND 59 -- ERR_DOMAIN_NOT_HANDLED 60 -- ERR_BAD_SMTP_RESPONSE 61 -- ERR_CFG_VAR_NOT_FOUND 62 -- ERR_BAD_DNS_RESPONSE 63 -- ERR_SMTPGW_NOT_FOUND 64 -- ERR_INCOMPLETE_CONFIG 65 -- ERR_MAIL_ERROR_LOOP 66 -- ERR_EXTALIAS_FILE_NOT_FOUND 67 -- ERR_EXTALIAS_EXIST 68 -- ERR_WRITE_EXTALIAS_FILE 69 -- ERR_EXTALIAS_NOT_FOUND 70 -- ERR_NO_USER_DEFAULT_PRFILE 71 -- ERR_FINGER_QUERY_FORMAT 72 -- ERR_LOCKED_RESOURCE 73 -- ERR_NO_PREDEFINED_MX 74 -- ERR_NO_MORE_MXRECORDS 75 -- ERR_INVALID_MESSAGE_FORMAT 76 -- ERR_SMTP_BAD_MAIL_FROM 77 -- ERR_SMTP_BAD_RCPT_TO 78 -- ERR_SMTP_BAD_DATA 79 -- ERR_INVALID_MXRECS_STRING 80 -- ERR_SETSOCKOPT 81 -- ERR_CREATEEVENT 82 -- ERR_CREATESEMAPHORE 83 -- ERR_CLOSEHANDLE 84 -- ERR_RELEASESEMAPHORE 85 -- ERR_BEGINTHREADEX 86 -- ERR_CREATEFILEMAPPING 87 -- ERR_MAPVIEWOFFILE 88 -- ERR_UNMAPVIEWOFFILE 89 -- ERR_SEMGET 90 -- ERR_SEMCTL 91 -- ERR_SEMOP 92 -- ERR_FORK 93 -- ERR_SHMGET 94 -- ERR_SHMCTL 95 -- ERR_SHMAT 96 -- ERR_SHMDT 97 -- ERR_OPENDIR 98 -- ERR_STAT 99 -- ERR_SMTP_BAD_CMD_SEQUENCE 100 -- ERR_NO_ROOT_DOMAIN_VAR 101 -- ERR_NS_NOT_FOUND 102 -- ERR_NO_DEFINED_MXS_FOR_DOMAIN 103 -- ERR_BAD_CTRL_COMMAND 104 -- ERR_DOMAIN_ALREADY_HANDLED 105 -- ERR_BAD_CTRL_LOGIN 106 -- ERR_CTRL_ACCOUNTS_FILE_NOT_FOUND 107 -- ERR_SPAMMER_IP 108 -- ERR_TRUNCATED_DGRAM_DNS_RESPONSE 109 -- ERR_NO_DGRAM_DNS_RESPONSE 110 -- ERR_EMPTY_DNS_RESPONSE 111 -- ERR_BAD_SMARTDNSHOST_SYNTAX 112 -- ERR_MAILBOX_SIZE 113 -- ERR_DYNDNS_CONFIG 114 -- ERR_PROCESS_EXECUTE 115 -- ERR_BAD_MAILPROC_CMD_SYNTAX 116 -- ERR_NO_MAILPROC_FILE 117 -- ERR_DNS_RECURSION_NOT_AVAILABLE 118 -- ERR_POP3_EXTERNAL_LINK_DISABLED 119 -- ERR_BAD_DOMAIN_PROC_CMD_SYNTAX 120 -- ERR_NOT_A_CUSTOM_DOMAIN 121 -- ERR_NO_MORE_TOKENS 122 -- ERR_SELECT 123 -- ERR_REGISTER_EVENT_SOURCE 124 -- ERR_NOMORESEMS 125 -- ERR_INVALID_SEMAPHORE 126 -- ERR_SHMEM_ALREADY_EXIST 127 -- ERR_SHMEM_NOT_EXIST 128 -- ERR_SEM_NOT_EXIST 129 -- ERR_SERVER_BUSY 130 -- ERR_IP_NOT_ALLOWED 131 -- ERR_FILE_EOF 132 -- ERR_BAD_TAG_ADDRESS 133 -- ERR_MAILFROM_UNKNOWN 134 -- ERR_FILTERED_MESSAGE 135 -- ERR_NO_DOMAIN_FILTER 136 -- ERR_POP3_RETR_BROKEN 137 -- ERR_CCLN_INVALID_RESPONSE 138 -- ERR_CCLN_ERROR_RESPONSE 139 -- ERR_INCOMPLETE_PROCESSING 140 -- ERR_NO_EXTERNAL_AUTH_DEFINED 141 -- ERR_EXTERNAL_AUTH_FAILURE 142 -- ERR_MD5_AUTH_FAILED 143 -- ERR_NO_SMTP_AUTH_CONFIG 144 -- ERR_UNKNOWN_SMTP_AUTH 145 -- ERR_BAD_SMTP_AUTH_CONFIG 146 -- ERR_BAD_EXTRNPRG_EXITCODE 147 -- ERR_BAD_SMTP_CMD_SYNTAX 148 -- ERR_SMTP_AUTH_FAILED 149 -- ERR_BAD_SMTP_EXTAUTH_RESPONSE_FILE 150 -- ERR_SMTP_USE_FORBIDDEN 151 -- ERR_SPAM_ADDRESS 152 -- ERR_SOCK_NOMORE_DATA 153 -- ERR_BAD_TAB_INDEX_FIELD 154 -- ERR_FILE_READ 155 -- ERR_BAD_INDEX_FILE 156 -- ERR_INDEX_HASH_NOT_FOUND 157 -- ERR_RECORD_NOT_FOUND 158 -- ERR_HEAP_ALLOC 159 -- ERR_HEAP_FREE 160 -- ERR_RESOURCE_NOT_LOCKED 161 -- ERR_LOCK_ENTRY_NOT_FOUND 162 -- ERR_LINE_TOO_LONG 163 -- ERR_MAIL_LOOP_DETECTED 164 -- ERR_FILE_MOVE 165 -- ERR_INVALID_MAILDIR_SUBPATH 166 -- ERR_SMTP_TOO_MANY_RECIPIENTS 167 -- ERR_DNS_CACHE_FILE_FMT 168 -- ERR_DNS_CACHE_FILE_EXPIRED 169 -- ERR_MMAP 170 -- ERR_NOT_LOCKED 171 -- ERR_SMTPFWD_FILE_NOT_FOUND 172 -- ERR_SMTPFWD_NOT_FOUND 173 -- ERR_USER_BREAK 174 -- ERR_SET_THREAD_PRIORITY
[xmail] Re: SMTP error: 451 Requested action aborted: (-100) local error in processing
I originally copied and pasted my server.tab from one terminal screen to an open vi in an other, assuming tabs would remain real tabs. It turns out that that isn#39;t the case and that tabs are translated to a couple of spaces with such a copy-paste... I changed the spaces into tabs and now get the expected 250-response... Thanks! Sincerely, Bart Mortelmans - Oorspronkelijk bericht Afzender: xmail@xmailserver.org Naar: xmail@xmailserver.org xmail@xmailserver.org Onderwerp: [xmail] Re: SMTP error: 451 Requested action aborted: (-100) localerror in processing Datum: 22/02/07 02:20 On Thu, 22 Feb 2007, Bart Mortelmans wrote: Duh!?! -100 is ERR_SHMAT and is never used in 1.24!?! Ok, it#39;s not ERR_SHMAT but ERR_NO_ROOT_DOMAIN_VAR. You#39;re missing the RootDomain server.tab variable. I made a script to extract error codes, and that#39;s the output ... - Davide 0 -- ERR_SUCCESS 1 -- ERR_SERVER_SHUTDOWN 2 -- ERR_MEMORY 3 -- ERR_NETWORK 4 -- ERR_SOCKET_CREATE 5 -- ERR_TIMEOUT 6 -- ERR_LOCKED 7 -- ERR_SOCKET_BIND 8 -- ERR_CONF_PATH 9 -- ERR_USERS_FILE_NOT_FOUND 10 -- ERR_FILE_CREATE 11 -- ERRDUMMY 12 -- ERR_USER_NOT_FOUND 13 -- ERR_USER_EXIST 14 -- ERR_WRITE_USERS_FILE 15 -- ERR_NO_USER_PRFILE 16 -- ERR_FILE_DELETE 17 -- ERR_DIR_CREATE 18 -- ERR_DIR_DELETE 19 -- ERR_FILE_OPEN 20 -- ERR_INVALID_FILE 21 -- ERR_FILE_WRITE 22 -- ERR_MSG_NOT_IN_RANGE 23 -- ERR_MSG_DELETED 24 -- ERR_INVALID_PASSWORD 25 -- ERR_ALIAS_FILE_NOT_FOUND 26 -- ERR_ALIAS_EXIST 27 -- ERR_WRITE_ALIAS_FILE 28 -- ERR_ALIAS_NOT_FOUND 29 -- ERR_SVR_PRFILE_NOT_LOCKED 30 -- ERR_GET_PEER_INFO 31 -- ERR_SMTP_PATH_PARSE_ERROR 32 -- ERR_BAD_RETURN_PATH 33 -- ERR_BAD_EMAIL_ADDR 34 -- ERR_RELAY_NOT_ALLOWED 35 -- ERR_BAD_FORWARD_PATH 36 -- ERR_GET_SOCK_INFO 37 -- ERR_GET_SOCK_HOST 38 -- ERR_NO_DOMAIN 39 -- ERR_USER_NOT_LOCAL 40 -- ERR_BAD_SERVER_ADDR 41 -- ERR_BAD_SERVER_RESPONSE 42 -- ERR_INVALID_POP3_RESPONSE 43 -- ERR_LINKS_FILE_NOT_FOUND 44 -- ERR_LINK_EXIST 45 -- ERR_WRITE_LINKS_FILE 46 -- ERR_LINK_NOT_FOUND 47 -- ERR_SMTPGW_FILE_NOT_FOUND 48 -- ERR_GATEWAY_ALREADY_EXIST 49 -- ERR_GATEWAY_NOT_FOUND 50 -- ERR_USER_NOT_MAILINGLIST 51 -- ERR_NO_USER_MLTABLE_FILE 52 -- ERR_MLUSER_ALREADY_EXIST 53 -- ERR_MLUSER_NOT_FOUND 54 -- ERR_SPOOL_FILE_NOT_FOUND 55 -- ERR_INVALID_SPOOL_FILE 56 -- ERR_SPOOL_FILE_EXPIRED 57 -- ERR_SMTPRELAY_FILE_NOT_FOUND 58 -- ERR_DOMAINS_FILE_NOT_FOUND 59 -- ERR_DOMAIN_NOT_HANDLED 60 -- ERR_BAD_SMTP_RESPONSE 61 -- ERR_CFG_VAR_NOT_FOUND 62 -- ERR_BAD_DNS_RESPONSE 63 -- ERR_SMTPGW_NOT_FOUND 64 -- ERR_INCOMPLETE_CONFIG 65 -- ERR_MAIL_ERROR_LOOP 66 -- ERR_EXTALIAS_FILE_NOT_FOUND 67 -- ERR_EXTALIAS_EXIST 68 -- ERR_WRITE_EXTALIAS_FILE 69 -- ERR_EXTALIAS_NOT_FOUND 70 -- ERR_NO_USER_DEFAULT_PRFILE 71 -- ERR_FINGER_QUERY_FORMAT 72 -- ERR_LOCKED_RESOURCE 73 -- ERR_NO_PREDEFINED_MX 74 -- ERR_NO_MORE_MXRECORDS 75 -- ERR_INVALID_MESSAGE_FORMAT 76 -- ERR_SMTP_BAD_MAIL_FROM 77 -- ERR_SMTP_BAD_RCPT_TO 78 -- ERR_SMTP_BAD_DATA 79 -- ERR_INVALID_MXRECS_STRING 80 -- ERR_SETSOCKOPT 81 -- ERR_CREATEEVENT 82 -- ERR_CREATESEMAPHORE 83 -- ERR_CLOSEHANDLE 84 -- ERR_RELEASESEMAPHORE 85 -- ERR_BEGINTHREADEX 86 -- ERR_CREATEFILEMAPPING 87 -- ERR_MAPVIEWOFFILE 88 -- ERR_UNMAPVIEWOFFILE 89 -- ERR_SEMGET 90 -- ERR_SEMCTL 91 -- ERR_SEMOP 92 -- ERR_FORK 93 -- ERR_SHMGET 94 -- ERR_SHMCTL 95 -- ERR_SHMAT 96 -- ERR_SHMDT 97 -- ERR_OPENDIR 98 -- ERR_STAT 99 -- ERR_SMTP_BAD_CMD_SEQUENCE 100 -- ERR_NO_ROOT_DOMAIN_VAR 101 -- ERR_NS_NOT_FOUND 102 -- ERR_NO_DEFINED_MXS_FOR_DOMAIN 103 -- ERR_BAD_CTRL_COMMAND 104 -- ERR_DOMAIN_ALREADY_HANDLED 105 -- ERR_BAD_CTRL_LOGIN 106 -- ERR_CTRL_ACCOUNTS_FILE_NOT_FOUND 107 -- ERR_SPAMMER_IP 108 -- ERR_TRUNCATED_DGRAM_DNS_RESPONSE 109 -- ERR_NO_DGRAM_DNS_RESPONSE 110 -- ERR_EMPTY_DNS_RESPONSE 111 -- ERR_BAD_SMARTDNSHOST_SYNTAX 112 -- ERR_MAILBOX_SIZE 113 -- ERR_DYNDNS_CONFIG 114 -- ERR_PROCESS_EXECUTE 115 -- ERR_BAD_MAILPROC_CMD_SYNTAX 116 -- ERR_NO_MAILPROC_FILE 117 -- ERR_DNS_RECURSION_NOT_AVAILABLE 118 -- ERR_POP3_EXTERNAL_LINK_DISABLED 119 -- ERR_BAD_DOMAIN_PROC_CMD_SYNTAX 120 -- ERR_NOT_A_CUSTOM_DOMAIN 121 -- ERR_NO_MORE_TOKENS 122 -- ERR_SELECT 123 -- ERR_REGISTER_EVENT_SOURCE 124 -- ERR_NOMORESEMS 125 -- ERR_INVALID_SEMAPHORE 126 -- ERR_SHMEM_ALREADY_EXIST 127 -- ERR_SHMEM_NOT_EXIST 128 -- ERR_SEM_NOT_EXIST 129 -- ERR_SERVER_BUSY 130 -- ERR_IP_NOT_ALLOWED 131 -- ERR_FILE_EOF 132 -- ERR_BAD_TAG_ADDRESS 133 -- ERR_MAILFROM_UNKNOWN 134 -- ERR_FILTERED_MESSAGE 135 -- ERR_NO_DOMAIN_FILTER 136 -- ERR_POP3_RETR_BROKEN 137 -- ERR_CCLN_INVALID_RESPONSE 138 -- ERR_CCLN_ERROR_RESPONSE 139 -- ERR_INCOMPLETE_PROCESSING 140 -- ERR_NO_EXTERNAL_AUTH_DEFINED 141 -- ERR_EXTERNAL_AUTH_FAILURE 142 -- ERR_MD5_AUTH_FAILED 143 -- ERR_NO_SMTP_AUTH_CONFIG 144 -- ERR_UNKNOWN_SMTP_AUTH 145 -- ERR_BAD_SMTP_AUTH_CONFIG 146 -- ERR_BAD_EXTRNPRG_EXITCODE 147 -- ERR_BAD_SMTP_CMD_SYNTAX 148 -- ERR_SMTP_AUTH_FAILED 149 -- ERR_BAD_SMTP_EXTAUTH_RESPONSE_FILE 150 -- ERR_SMTP_USE_FORBIDDEN 151 -- ERR_SPAM_ADDRESS 152 -- ERR_SOCK_NOMORE_DATA
