[xmail] Re: xmail DNS problem : First sample
-Message d'origine- De : [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] la part de Davide Libenzi Envoyé : dimanche 28 mai 2006 18:17 À : xmail@xmailserver.org Objet : [xmail] Re: xmail DNS problem : First sample On Sun, 28 May 2006, Rob Arends wrote: So Davide, can you explain When the TTL expires and Xmail tries the A record, why then for ALL the retries, does xmail attempt to send to the same server? If the xmail re-resolved the domain for each retry, wouldn't it get the correct MX, now that the SmartDNShost has cached either NS/MX for the domain. I totally understand xmail can't do much if the smartdnshost can't resolve the MX, however usually it can on the second attempt, so xmail should be able to send the email on the second try. The A-record try is *always* a fallback, and it *never* cached, and this is a fact. So if XMail continue to try to the A record, it means that the network condition that stops it to resolve the MX persist. - Davide For the sample I provided (ifrance.com), the mail was still in xmail queue and at time I run'd the nslookup from the xmail server itself to find the mx, and I got a valid 'authoritive' response with the mx entry with no timeout, but at next retry the mail delivery attempt was done on the A record ... The same think for many others mails waiting for a good mx entry in the xmail queue ... My xmail server is definitively not lucky on mx lookups (with or without smartdnshost ...) ! I will get a try on Tom Banting patch ASAP ... Francis - 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] What triggers SMTP=EERRS?
Davide, I need some clarification as to the SMTP log entry SMTP=EERRS. When does it occur? I have the server. tab setting as follows: SERVER.TAB SMTP-MaxErrors2 So I expect that when the sender gets the RCPT TO wrong twice, that the EERRS will be triggered. I thought I'd see two RCPT=EAVAIL, then an EERRS. I didn't expect the EIPMAP and the EERRS. Can you tell me if there are any other causes for EERRS to be triggered? -- Additional info. I have today's log that shows in part, one EIPMAP, then an EERRS. These are consecutive log entries. (I've removed null columns and the 1st 2 columns to save space and aligned others for ease of reading) [sorry if yours wraps] 221.145.206.167 2006-05-29 09:13:55 YOUR-OUQL80EY5G [EMAIL PROTECTED] SNDRIP=EIPMAP (list.dsbl.org.) 0 221.145.206.167 2006-05-29 09:13:55 YOUR-OUQL80EY5G SMTP=EERRS 0 221.145.206.167 2006-05-29 09:14:05 YOUR-OUQL80EY5G [EMAIL PROTECTED]SNDRIP=EIPMAP (list.dsbl.org.) 0 221.145.206.167 2006-05-29 09:14:05 YOUR-OUQL80EY5G SMTP=EERRS 0 221.145.206.167 2006-05-29 09:14:08 YOUR-OUQL80EY5G.b250.com [EMAIL PROTECTED] SNDRIP=EIPMAP (list.dsbl.org.) 0 221.145.206.167 2006-05-29 09:14:08 YOUR-OUQL80EY5G.b250.com SMTP=EERRS 0 221.145.206.167 2006-05-29 09:14:12 YOUR-OUQL80EY5G.uml2o.net [EMAIL PROTECTED] SNDRIP=EIPMAP (list.dsbl.org.) 0 221.145.206.167 2006-05-29 09:14:12 YOUR-OUQL80EY5G.uml2o.net SMTP=EERRS 0 221.145.206.167 2006-05-29 09:14:14 YOUR-OUQL80EY5G.d2atn.net [EMAIL PROTECTED] SNDRIP=EIPMAP (list.dsbl.org.) 0 221.145.206.167 2006-05-29 09:14:14 YOUR-OUQL80EY5G.d2atn.net SMTP=EERRS 0 221.145.206.167 2006-05-29 09:14:19 YOUR-OUQL80EY5G [EMAIL PROTECTED]SNDRIP=EIPMAP (list.dsbl.org.) 0 221.145.206.167 2006-05-29 09:14:19 YOUR-OUQL80EY5G SMTP=EERRS 0 - I'm in the process of writing a log scanner (in Perl), that will run once a minute to look how many SMTP=EERRS occurred per IP in the last 2 minutes. If there are more than 2 per IP, then add the IP to spammers.tab for a month. That should cater for 4 RCPT=EAVAIL errors in my setup. Values and duration may change but that's the outline. I find that I get a barrage of RCPT=EAVAIL for about 5 minutes, then it moves to a new IP, for about 30-60 mins each day around 1am. I'm also thinking that counting SNDRIP=EIPMAP and adding them to spammers.tab will help reduce the constant dns lookups, and drop the connection quicker. Does anyone know of a better way to track SMTP rejections that don't progress to the pre-data filter stage? - apart from a log scanner. Rob :-) - 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: Blacklist effectiveness...
John, but giving the sequence of servers, it might shadow spamcop... It does; first hit stops the rest. So you are best to move your dnsbl.sorbs.net. To the beginning, then followed by bl.spamcop.net. at least. Saves the DNS lookups. Rob :-) -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Jorn Hass Sent: Monday, 29 May 2006 9:03 PM To: xmail@xmailserver.org Subject: [xmail] Blacklist effectiveness... Hi all. For those that are interested, I did some quick reports for the last 7 days, plus today: Rejects per blacklist: 15 (relays.ordb.org.) 62 (sbl-xbl.spamhaus.org.) 1870 (bl.spamcop.net.) 7501 (dnsbl.sorbs.net.) I have only added sbl-xbl.spamhaus.org today, and have already hit 62 counts. From this, it looks as if dnsbl.sorbs.net is the most effective, but giving the sequence of servers, it might shadow spamcop... From my server.tab: CustMapsList relays.ordb.org.:1,sbl-xbl.spamhaus.org.:1,rhsbl.sorbs.net..:1,zombie.dnsbl ..sorbs.net.:1,dnsbl.sorbs.net.:0,bl.spamcop.net.:0 Top 114 IPs that have 20 or more rejects over the last 7 days... A very common pattern is the 20 or 50 refusal runs every so often. 20 125.181.107.209 (bl.spamcop.net.) 20 200.113.104.224 (dnsbl.sorbs.net.) 20 201.24.104.74 (dnsbl.sorbs.net.) 20 203.171.241.20 (bl.spamcop.net.) 20 211.222.179.141 (blacklist.is.co.za.) 20 213.54.155.128 (dnsbl.sorbs.net.) 20 218.155.182.188 (blacklist.is.co.za.) 20 218.80.66.251 (blacklist.is.co.za.) 20 219.248.127.162 (blacklist.is.co.za.) 20 222.253.77.163 (bl.spamcop.net.) 20 59.158.117.4 (bl.spamcop.net.) 20 59.38.66.249 (dnsbl.sorbs.net.) 20 65.185.148.24 (dialups.blacklist.is.co.za.) 20 66.168.86.99 (dnsbl.sorbs.net.) 20 66.27.199.1 (dnsbl.sorbs.net.) 20 66.30.42.20 (dnsbl.sorbs.net.) 20 67.162.166.169 (dnsbl.sorbs.net.) 20 67.172.173.73 (dnsbl.sorbs.net.) 20 69.34.54.115 (dnsbl.sorbs.net.) 20 71.251.130.114 (dnsbl.sorbs.net.) 20 80.143.244.51 (dnsbl.sorbs.net.) 20 80.146.85.179 (dnsbl.sorbs.net.) 20 80.213.1.233 (dnsbl.sorbs.net.) 20 81.157.163.141 (dnsbl.sorbs.net.) 20 81.190.177.87 (dnsbl.sorbs.net.) 20 82.35.29.170 (dnsbl.sorbs.net.) 20 82.78.137.205 (bl.spamcop.net.) 20 83.18.201.146 (bl.spamcop.net.) 20 83.213.213.119 (bl.spamcop.net.) 20 83.28.246.43 (dnsbl.sorbs.net.) 20 83.32.17.80 (dnsbl.sorbs.net.) 20 84.10.140.16 (dnsbl.sorbs.net.) 20 84.120.106.55 (dnsbl.sorbs.net.) 20 84.122.253.99 (bl.spamcop.net.) 20 84.130.102.252 (dnsbl.sorbs.net.) 20 84.130.223.27 (dnsbl.sorbs.net.) 20 84.133.23.38 (dnsbl.sorbs.net.) 20 85.176.105.109 (dnsbl.sorbs.net.) 20 85.180.189.50 (dnsbl.sorbs.net.) 20 86.63.102.63 (bl.spamcop.net.) 20 87.49.44.158 (dnsbl.sorbs.net.) 20 87.89.33.1 (dnsbl.sorbs.net.) 21 81.109.72.142 (dnsbl.sorbs.net.) 22 217.98.8.10 (dnsbl.sorbs.net.) 22 24.62.255.214 (blacklist.is.co.za.) 25 12.218.33.45 (dialups.blacklist.is.co.za.) 25 58.187.32.167 (dnsbl.sorbs.net.) 25 68.200.19.216 (dnsbl.sorbs.net.) 25 71.65.63.13 (dnsbl.sorbs.net.) 25 82.83.207.136 (dnsbl.sorbs.net.) 31 62.117.26.170 (dnsbl.sorbs.net.) 38 12.21.179.250 (bl.spamcop.net.) 39 217.125.183.59 (dnsbl.sorbs.net.) 40 67.167.207.216 (dnsbl.sorbs.net.) 40 71.253.207.166 (dnsbl.sorbs.net.) 50 12.226.114.115 (dialups.blacklist.is.co.za.) 50 162.84.209.229 (dnsbl.sorbs.net.) 50 195.13.38.168 (bl.spamcop.net.) 50 200.210.49.160 (dnsbl.sorbs.net.) 50 200.79.53.50 (dnsbl.sorbs.net.) 50 200.89.246.11 (dnsbl.sorbs.net.) 50 201.127.120.154 (dnsbl.sorbs.net.) 50 201.240.61.88 (dnsbl.sorbs.net.) 50 203.203.113.195 (dnsbl.sorbs.net.) 50 207.118.218.49 (dnsbl.sorbs.net.) 50 213.98.23.3 (dialups.blacklist.is.co.za.) 50 217.73.101.30 (bl.spamcop.net.) 50 218.238.159.51 (dnsbl.sorbs.net.) 50 218.59.137.178 (dnsbl.sorbs.net.) 50 219.128.166.225 (dnsbl.sorbs.net.) 50 24.128.43.101 (dnsbl.sorbs.net.) 50 24.148.182.177 (dnsbl.sorbs.net.) 50 24.15.145.84 (dnsbl.sorbs.net.) 50 24.3.79.31 (dnsbl.sorbs.net.) 50 24.82.117.184 (dialups.blacklist.is.co.za.) 50 59.16.18.102 (dnsbl.sorbs.net.) 50 61.117.53.100 (dnsbl.sorbs.net.) 50 61.7.3.190 (bl.spamcop.net.) 50 62.131.251.73 (bl.spamcop.net.) 50 65.31.87.197 (dnsbl.sorbs.net.) 50 66.30.19.233 (dnsbl.sorbs.net.) 50 70.107.22.240 (dnsbl.sorbs.net.) 50 70.31.77.89 (bl.spamcop.net.) 50 70.74.116.173 (dnsbl.sorbs.net.) 50 71.110.236.250 (dnsbl.sorbs.net.) 50 71.125.217.222 (dnsbl.sorbs.net.) 50 71.247.235.84 (dnsbl.sorbs.net.) 50 71.52.59.181 (dnsbl.sorbs.net.) 50 76.0.204.145 (bl.spamcop.net.) 50 80.129.204.204 (dnsbl.sorbs.net.) 50 80.143.35.99 (dnsbl.sorbs.net.) 50 80.239.46.169 (bl.spamcop.net.) 50 80.53.6.26 (bl.spamcop.net.) 50 80.55.103.54 (dnsbl.sorbs.net.) 50 80.55.188.78 (bl.spamcop.net.) 50 80.57.239.189 (dnsbl.sorbs.net.) 50 81.192.66.238 (dnsbl.sorbs.net.) 50 81.219.220.137 (bl.spamcop.net.) 50 82.160.72.2 (dnsbl.sorbs.net.) 50
[xmail] Re: xmail DNS problem : First sample
On Mon, 29 May 2006, CLEMENT Francis wrote: For the sample I provided (ifrance.com), the mail was still in xmail = queue and at time I run'd the nslookup from the xmail server itself to find = the mx, and I got a valid 'authoritive' response with the mx entry with no timeout, but at next retry the mail delivery attempt was done on the A record ... The same think for many others mails waiting for a good mx entry in the xmail queue ... My xmail server is definitively not lucky on mx lookups (with or = without smartdnshost ...) ! The TTL for that record was 86400. This means that if XMail find his own cached copy to be expired, and another server in your network still has cached a copy that is not expired, you'll continue to get positive lookups for a whole day. - 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: What triggers SMTP=EERRS?
On Mon, 29 May 2006, Rob Arends wrote: Davide, I need some clarification as to the SMTP log entry SMTP=EERRS. When does it occur? I have the server. tab setting as follows: SERVER.TAB SMTP-MaxErrors 2 So I expect that when the sender gets the RCPT TO wrong twice, that the EERRS will be triggered. I thought I'd see two RCPT=EAVAIL, then an EERRS. The number of errors is not only recipient errors, but any kind of SMTP command error (wrong sequence, command not available, etc...). - 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: MAIL FROM with spaces in local part
On Mon, 29 May 2006, Manuel Martin wrote: Xmail accepts the following, while e. g. MS Exchange rejects it: MAIL FROM:bla [EMAIL PROTECTED] I wonder if this is too lenient from Xmail's part, although I cannot = cite a RFC which forbids spaces in the local part (perhaps someone else can). White space is not allowed in that form. I did a poll a looong time ago, and users preferred a more tollerant approach on address format at that time. I already have planned strictier address checks. - 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: Cannot find environment variable: MAIL_ROOT
On Sun, 28 May 2006, Chris Lori wrote: ls -l /usr/sbin/sendmail* lrwxrwxrwx2 root root 27 Mar 9 14:32 /usr/sbin/sendmail - /usr/sbin/sendmail.xmail.sh lrwxrwxrwx1 root root 21 Aug 8 2004 /usr/sbin/sendmail.orig - /etc/alternatives/mta -rwsr-xr-x1 root root11160 Sep 14 2003 /usr/sbin/sendmail.xmail -rwxr-xr-x1 root root 105 Sep 14 2003 /usr/sbin/sendmail.xmail.sh the cat of sendmail.xmail.sh is: #!/bin/sh if [ -z $MAIL_ROOT ]; then export MAIL_ROOT=/var/MailRoot fi /usr/sbin/sendmail.xmail $* What else should I be looking for? Looks fine. Did you say you are able to send messages by uses XMail's sendmail from the command line? - 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: What triggers SMTP=EERRS?
Great! So why do I get: YOUR-OUQL80EY5G [EMAIL PROTECTED] SNDRIP=EIPMAP (list.dsbl.org.) 0 YOUR-OUQL80EY5G SMTP=EERRS 0 I expect that the IPMAP kicked them off before they could do Command errors. Given they are from the same IP address. Any thoughts Davide? Rob :-) -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Davide Libenzi Sent: Tuesday, 30 May 2006 1:53 AM To: xmail@xmailserver.org Subject: [xmail] Re: What triggers SMTP=EERRS? On Mon, 29 May 2006, Rob Arends wrote: Davide, I need some clarification as to the SMTP log entry SMTP=EERRS. When does it occur? I have the server. tab setting as follows: SERVER.TAB SMTP-MaxErrors 2 So I expect that when the sender gets the RCPT TO wrong twice, that the EERRS will be triggered. I thought I'd see two RCPT=EAVAIL, then an EERRS. The number of errors is not only recipient errors, but any kind of SMTP command error (wrong sequence, command not available, etc...). - 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] - 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: What triggers SMTP=EERRS?
I think this normal if you set 'list.dsbl.org:0' (:0 mode) in the CustMapsList (the connection is kept alive but only authenticated users can send mail ) So you permit xmail to wait for a possible authentication command (login, ) from the client after the helo/ehlo stage, and if the client don't auth at all and try 'mail from' directly (or any others commands), then this is a protocol violation as xmail only want an auth as the next command send by the client and finaly you have a EERRS error in the log. Right Davide ? Do you think xmail, in future version, could avoid writing this 'EERRS' entry then previous one was 'EIPMAP' ? Not a very important request at all ;) Francis -Message d'origine- De : [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] la part de Rob Arends Envoyé : lundi 29 mai 2006 18:18 À : xmail@xmailserver.org Objet : [xmail] Re: What triggers SMTP=EERRS? Great! So why do I get: YOUR-OUQL80EY5G [EMAIL PROTECTED] SNDRIP=EIPMAP (list.dsbl.org.) 0 YOUR-OUQL80EY5G SMTP=EERRS 0 I expect that the IPMAP kicked them off before they could do Command errors. Given they are from the same IP address. Any thoughts Davide? Rob :-) -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Davide Libenzi Sent: Tuesday, 30 May 2006 1:53 AM To: xmail@xmailserver.org Subject: [xmail] Re: What triggers SMTP=EERRS? On Mon, 29 May 2006, Rob Arends wrote: Davide, I need some clarification as to the SMTP log entry SMTP=EERRS. When does it occur? I have the server. tab setting as follows: SERVER.TAB SMTP-MaxErrors 2 So I expect that when the sender gets the RCPT TO wrong twice, that the EERRS will be triggered. I thought I'd see two RCPT=EAVAIL, then an EERRS. The number of errors is not only recipient errors, but any kind of SMTP command error (wrong sequence, command not available, etc...). - 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] - 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] - 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: Blacklist effectiveness...
FYI - Spamcop's BL is very heavy with false positives. Not to say it can't be useful as part of a scoring system, but if you use it directly to reject mail, you're *going* to lose legitimate mail... Jorn Hass wrote: Hi all. For those that are interested, I did some quick reports for the last 7 days, plus today: Rejects per blacklist: 15 (relays.ordb.org.) 62 (sbl-xbl.spamhaus.org.) 1870 (bl.spamcop.net.) 7501 (dnsbl.sorbs.net.) I have only added sbl-xbl.spamhaus.org today, and have already hit 62 counts. From this, it looks as if dnsbl.sorbs.net is the most effective, but giving the sequence of servers, it might shadow spamcop... From my server.tab: CustMapsList relays.ordb.org.:1,sbl-xbl.spamhaus.org.:1,rhsbl.sorbs.net..:1,zombie.dnsbl.sorbs.net.:1,dnsbl.sorbs.net.:0,bl.spamcop.net.:0 Top 114 IPs that have 20 or more rejects over the last 7 days... A very common pattern is the 20 or 50 refusal runs every so often. 20 125.181.107.209 (bl.spamcop.net.) 20 200.113.104.224 (dnsbl.sorbs.net.) 20 201.24.104.74 (dnsbl.sorbs.net.) 20 203.171.241.20 (bl.spamcop.net.) 20 211.222.179.141 (blacklist.is.co.za.) 20 213.54.155.128 (dnsbl.sorbs.net.) 20 218.155.182.188 (blacklist.is.co.za.) 20 218.80.66.251 (blacklist.is.co.za.) 20 219.248.127.162 (blacklist.is.co.za.) 20 222.253.77.163 (bl.spamcop.net.) 20 59.158.117.4 (bl.spamcop.net.) 20 59.38.66.249 (dnsbl.sorbs.net.) 20 65.185.148.24 (dialups.blacklist.is.co.za.) 20 66.168.86.99 (dnsbl.sorbs.net.) 20 66.27.199.1 (dnsbl.sorbs.net.) 20 66.30.42.20 (dnsbl.sorbs.net.) 20 67.162.166.169 (dnsbl.sorbs.net.) 20 67.172.173.73 (dnsbl.sorbs.net.) 20 69.34.54.115 (dnsbl.sorbs.net.) 20 71.251.130.114 (dnsbl.sorbs.net.) 20 80.143.244.51 (dnsbl.sorbs.net.) 20 80.146.85.179 (dnsbl.sorbs.net.) 20 80.213.1.233 (dnsbl.sorbs.net.) 20 81.157.163.141 (dnsbl.sorbs.net.) 20 81.190.177.87 (dnsbl.sorbs.net.) 20 82.35.29.170 (dnsbl.sorbs.net.) 20 82.78.137.205 (bl.spamcop.net.) 20 83.18.201.146 (bl.spamcop.net.) 20 83.213.213.119 (bl.spamcop.net.) 20 83.28.246.43 (dnsbl.sorbs.net.) 20 83.32.17.80 (dnsbl.sorbs.net.) 20 84.10.140.16 (dnsbl.sorbs.net.) 20 84.120.106.55 (dnsbl.sorbs.net.) 20 84.122.253.99 (bl.spamcop.net.) 20 84.130.102.252 (dnsbl.sorbs.net.) 20 84.130.223.27 (dnsbl.sorbs.net.) 20 84.133.23.38 (dnsbl.sorbs.net.) 20 85.176.105.109 (dnsbl.sorbs.net.) 20 85.180.189.50 (dnsbl.sorbs.net.) 20 86.63.102.63 (bl.spamcop.net.) 20 87.49.44.158 (dnsbl.sorbs.net.) 20 87.89.33.1 (dnsbl.sorbs.net.) 21 81.109.72.142 (dnsbl.sorbs.net.) 22 217.98.8.10 (dnsbl.sorbs.net.) 22 24.62.255.214 (blacklist.is.co.za.) 25 12.218.33.45 (dialups.blacklist.is.co.za.) 25 58.187.32.167 (dnsbl.sorbs.net.) 25 68.200.19.216 (dnsbl.sorbs.net.) 25 71.65.63.13 (dnsbl.sorbs.net.) 25 82.83.207.136 (dnsbl.sorbs.net.) 31 62.117.26.170 (dnsbl.sorbs.net.) 38 12.21.179.250 (bl.spamcop.net.) 39 217.125.183.59 (dnsbl.sorbs.net.) 40 67.167.207.216 (dnsbl.sorbs.net.) 40 71.253.207.166 (dnsbl.sorbs.net.) 50 12.226.114.115 (dialups.blacklist.is.co.za.) 50 162.84.209.229 (dnsbl.sorbs.net.) 50 195.13.38.168 (bl.spamcop.net.) 50 200.210.49.160 (dnsbl.sorbs.net.) 50 200.79.53.50 (dnsbl.sorbs.net.) 50 200.89.246.11 (dnsbl.sorbs.net.) 50 201.127.120.154 (dnsbl.sorbs.net.) 50 201.240.61.88 (dnsbl.sorbs.net.) 50 203.203.113.195 (dnsbl.sorbs.net.) 50 207.118.218.49 (dnsbl.sorbs.net.) 50 213.98.23.3 (dialups.blacklist.is.co.za.) 50 217.73.101.30 (bl.spamcop.net.) 50 218.238.159.51 (dnsbl.sorbs.net.) 50 218.59.137.178 (dnsbl.sorbs.net.) 50 219.128.166.225 (dnsbl.sorbs.net.) 50 24.128.43.101 (dnsbl.sorbs.net.) 50 24.148.182.177 (dnsbl.sorbs.net.) 50 24.15.145.84 (dnsbl.sorbs.net.) 50 24.3.79.31 (dnsbl.sorbs.net.) 50 24.82.117.184 (dialups.blacklist.is.co.za.) 50 59.16.18.102 (dnsbl.sorbs.net.) 50 61.117.53.100 (dnsbl.sorbs.net.) 50 61.7.3.190 (bl.spamcop.net.) 50 62.131.251.73 (bl.spamcop.net.) 50 65.31.87.197 (dnsbl.sorbs.net.) 50 66.30.19.233 (dnsbl.sorbs.net.) 50 70.107.22.240 (dnsbl.sorbs.net.) 50 70.31.77.89 (bl.spamcop.net.) 50 70.74.116.173 (dnsbl.sorbs.net.) 50 71.110.236.250 (dnsbl.sorbs.net.) 50 71.125.217.222 (dnsbl.sorbs.net.) 50 71.247.235.84 (dnsbl.sorbs.net.) 50 71.52.59.181 (dnsbl.sorbs.net.) 50 76.0.204.145 (bl.spamcop.net.) 50 80.129.204.204 (dnsbl.sorbs.net.) 50 80.143.35.99 (dnsbl.sorbs.net.) 50 80.239.46.169 (bl.spamcop.net.) 50 80.53.6.26 (bl.spamcop.net.) 50 80.55.103.54 (dnsbl.sorbs.net.) 50 80.55.188.78 (bl.spamcop.net.) 50 80.57.239.189 (dnsbl.sorbs.net.) 50 81.192.66.238 (dnsbl.sorbs.net.) 50 81.219.220.137 (bl.spamcop.net.) 50 82.160.72.2 (dnsbl.sorbs.net.) 50 82.216.127.121 (dnsbl.sorbs.net.) 50 83.113.56.109 (dnsbl.sorbs.net.) 50 83.27.247.68 (dnsbl.sorbs.net.) 50
[xmail] Re: Cannot find environment variable: MAIL_ROOT
I don't think I did say. However, I did try it last night, and it was successful. It may have to do with the webapp, I'll try posting a question on their forums. Chris Davide Libenzi wrote: On Sun, 28 May 2006, Chris Lori wrote: ls -l /usr/sbin/sendmail* lrwxrwxrwx2 root root 27 Mar 9 14:32 /usr/sbin/sendmail - /usr/sbin/sendmail.xmail.sh lrwxrwxrwx1 root root 21 Aug 8 2004 /usr/sbin/sendmail.orig - /etc/alternatives/mta -rwsr-xr-x1 root root11160 Sep 14 2003 /usr/sbin/sendmail.xmail -rwxr-xr-x1 root root 105 Sep 14 2003 /usr/sbin/sendmail.xmail.sh the cat of sendmail.xmail.sh is: #!/bin/sh if [ -z $MAIL_ROOT ]; then export MAIL_ROOT=/var/MailRoot fi /usr/sbin/sendmail.xmail $* What else should I be looking for? Looks fine. Did you say you are able to send messages by uses XMail's sendmail from the command line? - 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] - 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]
