Re: master mail problems -- help needed
On Sat, Nov 26, 2005 at 04:39:46PM +0100, Jeroen van Wolffelaar wrote: When an exim mailserver is really bogged down under mail load, attempts can be made even less often. It's ben pointed out to me that my mail through master is also bouncing at times. I also have an IPv6 MX, so it could be related. However, another datapoint (and relevant to the above): top - 07:38:12 up 293 days, 15:52, 8 users, load average: 5.92, 5.39, 5.12 Tasks: 288 total, 6 running, 280 sleeping, 1 stopped, 1 zombie Cpu(s): 29.9% user, 18.9% system, 0.5% nice, 50.7% idle Mem: 2069780k total, 1981968k used,87812k free, 268648k buffers Swap: 284k total,35744k used, 1964340k free, 1132708k cached PID USER PR NI VIRT RES SHR S %CPU %MEMTIME+ COMMAND 18353 clamav16 0 19560 18m 9672 R 33.9 0.9 12:20.88 clamd 18120 clamav16 0 19560 18m 9672 R 30.9 0.9 55:56.78 clamd 18360 clamav16 0 19560 18m 9672 R 30.9 0.9 2:33.51 clamd 31657 clamav15 0 19560 18m 9672 R 30.9 0.9 8:39.73 clamd 8251 clamav15 0 19560 18m 9672 R 14.7 0.9 0:02.64 clamd 14004 wouter16 0 1416 1416 1060 R 10.3 0.1 0:00.15 top 13930 Debian-e 10 0 3184 3176 2820 S 4.4 0.2 0:00.06 exim4 14010 root 11 0 3184 3176 3036 S 4.4 0.2 0:00.05 exim4 4562 root 9 0 31148 30m 8564 S 1.5 1.5 279:23.32 named 18357 clamav 9 0 19560 18m 9672 S 1.5 0.9 27:43.19 clamd 12311 www-data 9 0 4936 4160 3968 S 1.5 0.2 0:00.02 apache 12826 www-data 9 0 000 Z 1.5 0.0 0:00.02 apache defunct 14030 root 16 0 3164 3156 3036 S 1.5 0.2 0:00.01 exim4 14031 Debian-e 16 0 3232 3224 3052 D 1.5 0.2 0:00.01 exim4 1 root 8 0 472 440 420 S 0.0 0.0 243:01.96 init 2 root 9 0 000 S 0.0 0.0 0:01.57 keventd 3 root 19 19 000 S 0.0 0.0 0:13.91 ksoftirqd_CPU0 4 root 19 19 000 S 0.0 0.0 0:14.97 ksoftirqd_CPU1 5 root 9 0 000 S 0.0 0.0 3029:45 kswapd 6 root 9 0 000 S 0.0 0.0 60:08.08 bdflush That's on master. I've been watching it for about 5 minutes, and never saw the load drop below 3.80-ish. Could it be that master is simply imploding on the amount of mail received? -- .../ -/ ---/ .--./ / .--/ .-/ .../ -/ ../ -./ --./ / -.--/ ---/ ..-/ .-./ / -/ ../ --/ ./ / .--/ ../ -/ / / -../ ./ -.-./ ---/ -../ ../ -./ --./ / --/ -.--/ / .../ ../ --./ -./ .-/ -/ ..-/ .-./ ./ .-.-.-/ / --/ ---/ .-./ .../ ./ / ../ .../ / ---/ ..-/ -/ -../ .-/ -/ ./ -../ / -/ ./ -.-./ / -./ ---/ .-../ ---/ --./ -.--/ / .-/ -./ -.--/ .--/ .-/ -.--/ .-.-.-/ / ...-.-/ -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: master mail problems -- help needed
Wouter Verhelst [EMAIL PROTECTED] writes: That's on master. I've been watching it for about 5 minutes, and never saw the load drop below 3.80-ish. Could it be that master is simply imploding on the amount of mail received? It's always been like that (if not worse). -- ,''`. : :' :Romain Francoise [EMAIL PROTECTED] `. `' http://people.debian.org/~rfrancoise/ `- -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: master mail problems -- help needed
On Thu, Dec 08, 2005 at 03:00:58PM +0100, Romain Francoise wrote: Wouter Verhelst [EMAIL PROTECTED] writes: That's on master. I've been watching it for about 5 minutes, and never saw the load drop below 3.80-ish. Could it be that master is simply imploding on the amount of mail received? It's always been like that (if not worse). Not that I recall. But then, I'm not really all that familiar with master, so let's assume it's indeed something else. The fact that my primary MX is only available through IPv6, and that this is the case for other people who're having problems too might then be a better chance at being the problem. -- .../ -/ ---/ .--./ / .--/ .-/ .../ -/ ../ -./ --./ / -.--/ ---/ ..-/ .-./ / -/ ../ --/ ./ / .--/ ../ -/ / / -../ ./ -.-./ ---/ -../ ../ -./ --./ / --/ -.--/ / .../ ../ --./ -./ .-/ -/ ..-/ .-./ ./ .-.-.-/ / --/ ---/ .-./ .../ ./ / ../ .../ / ---/ ..-/ -/ -../ .-/ -/ ./ -../ / -/ ./ -.-./ / -./ ---/ .-../ ---/ --./ -.--/ / .-/ -./ -.--/ .--/ .-/ -.--/ .-.-.-/ / ...-.-/ -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: master mail problems -- help needed
On Thu, Dec 08, 2005 at 09:30:52PM +0100, Wouter Verhelst wrote: The fact that my primary MX is only available through IPv6, and that this is the case for other people who're having problems too might then be a better chance at being the problem. My primary MX is IPv6-only, too. I don't have detected a problem yet :) -- Lionel -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: master mail problems -- help needed
* Lionel Elie Mamane: On Thu, Dec 08, 2005 at 09:30:52PM +0100, Wouter Verhelst wrote: The fact that my primary MX is only available through IPv6, and that this is the case for other people who're having problems too might then be a better chance at being the problem. My primary MX is IPv6-only, too. I don't have detected a problem yet :) Do you receive lots of mail from master.debian.org, and would you notice the bounces? Mail from Debian mailing lists come directly from murphy.debian.org, which does not seem to have the problem. You also have one IPv4-only MX, which might be enough to prevent the Exim bug[1] from occurring. [1] I'm not sure if it's a Exim's fault, it's only a hunch. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: master mail problems -- help needed
On Thu, Dec 08, 2005 at 10:33:54PM +0100, Florian Weimer wrote: * Lionel Elie Mamane: On Thu, Dec 08, 2005 at 09:30:52PM +0100, Wouter Verhelst wrote: The fact that my primary MX is only available through IPv6, and that this is the case for other people who're having problems too might then be a better chance at being the problem. My primary MX is IPv6-only, too. I don't have detected a problem yet :) Do you receive lots of mail from master.debian.org, I don't think so. and would you notice the bounces? I wouldn't get bounces, people sending me mail on [EMAIL PROTECTED] would. You also have one IPv4-only MX, No, I don't. -- Lionel -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: master mail problems -- help needed
* Lionel Elie Mamane: You also have one IPv4-only MX, No, I don't. But Exim 4 thinks so: [EMAIL PROTECTED] router = dnslookup, transport = remote_smtp host capsaicin.mamane.lu [2001:888:19f0::2] MX=9 host capsaicin.mamane.lu [2001:888:19f0:2::2] MX=9 host quorn.mamane.lu [213.84.114.29] MX=10 host tofu.mamane.lu [2001:888:19f0:0:210:5aff:fe45:9b17] MX=11 host a.mx.conuropsis.org [2001:838:300:241::2]MX=30 host a.mx.conuropsis.org [217.115.192.216]MX=30 My local BIND omits a few records from the answer to mamane.lu/IN/MX to bring it below the 512 byte limit (it may do so, after all it's just the addtitional section). I would have thought that Exim queried for records if necessary, but this seems to be wrong. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: master mail problems -- help needed
On Thu, Dec 08, 2005 at 11:57:58PM +0100, Florian Weimer wrote: * Lionel Elie Mamane: You also have one IPv4-only MX, No, I don't. But Exim 4 thinks so: [EMAIL PROTECTED] router = dnslookup, transport = remote_smtp host capsaicin.mamane.lu [2001:888:19f0::2] MX=9 host capsaicin.mamane.lu [2001:888:19f0:2::2] MX=9 host quorn.mamane.lu [213.84.114.29] MX=10 host tofu.mamane.lu [2001:888:19f0:0:210:5aff:fe45:9b17] MX=11 host a.mx.conuropsis.org [2001:838:300:241::2]MX=30 host a.mx.conuropsis.org [217.115.192.216]MX=30 I see. My local BIND omits a few records from the answer to mamane.lu/IN/MX to bring it below the 512 byte limit (it may do so, after all it's just the addtitional section). I would have thought that Exim queried for records if necessary, but this seems to be wrong. Well, I've dropped tofu from the MX list now, so maybe quorn's record will make it back in (after TTL expires)? -- Lionel -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: master mail problems -- help needed
On Thu, Dec 08, 2005 at 10:33:54PM +0100, Florian Weimer wrote: * Lionel Elie Mamane: On Thu, Dec 08, 2005 at 09:30:52PM +0100, Wouter Verhelst wrote: The fact that my primary MX is only available through IPv6, and that this is the case for other people who're having problems too might then be a better chance at being the problem. My primary MX is IPv6-only, too. I don't have detected a problem yet :) Do you receive lots of mail from master.debian.org, and would you notice the bounces? Mail from Debian mailing lists come directly from murphy.debian.org, which does not seem to have the problem. You also have one IPv4-only MX, which might be enough to prevent the Exim bug[1] from occurring. [1] I'm not sure if it's a Exim's fault, it's only a hunch. I've filed #342619 on the strong suspicion something fishy is going on in exim, even though I don't know for sure what's going on exactly. --Jeroen -- Jeroen van Wolffelaar [EMAIL PROTECTED] (also for Jabber MSN; ICQ: 33944357) http://Jeroen.A-Eskwadraat.nl -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: master mail problems -- help needed
* Stephen Gran: No noticable time difference between the two, either. So, I don't think this is the real problem. You could be right. The problem is still present, unfortunately. One more data point: A couple of seconds before the last bounce was generated, murphy (which is on the same network as master) successfully delivered mail to mail.enyo.de. It doesn't seem to be related to connectivity issues on my part. postmaster@ has been contacted, I'm waiting for log excerpts from DSA. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: master mail problems -- help needed
On Sat, Nov 26, 2005 at 02:00:48PM +0100, Florian Weimer wrote: From time to time, master seems to bounce mail routed to mail.enyo.de with the following error message: [EMAIL PROTECTED] retry time not reached for any host after a long failure period Is anybody experiencing a similar problem? I tried to debug it myself, using the information I could access on master, but I couldn't gather enough evidence to present to the postmasters so far. But other DD's can also only do a limited amount of research, the only way to really find out is asking a postmaster -- this isn't a prosecution, so 'evidence' is not needed, I'd say (though, a copy of one bounce message with full headers would be the minimum I'd expect, because otherwise debugging is close to impossible). In general, this failure means that for 4 consecutive days the a connection attempt that happens roughly every 8 hours fails (connection refused, a timeout, HELO refused, stuff like that). Are you sure that this condition can never have happened? I see you only have one MX, for increased reliability and for cases when for example there's a routing problem somewhere between master and that one single MX, add a backup MX. When an exim mailserver is really bogged down under mail load, attempts can be made even less often. IIRC, when there are no prolonged connectivity problems, the error message is characteristic of a broken Exim retry configuration (no retry section at all, or something like that), but master's configuration seems to be fine in this regard. The host mail.enyo.de had some intermittent connectivity problems during the past few weeks (downtimes of about one hour every couple of days, nothing which should cause Exim to run past its configured retry limit). But this has been fixed, and the sporadic bounces continued. The other problem is a certain sluggishness when one of those botnets attempts to send spam to hundreds of message IDs, but these attacks last a couple of minutes only, and master should be able to cope with that. I'd really look into a secondary MX, but if it's indeed only there two problems at the frequency you say, it shouldn't really be possible that this is the cause. This problem has gained some unexpected urgency because I was kicked off the PTS due to these bounces (I think so, I haven't been shown one of the PTS bounces). On the other hand, it rules out my .procmailrc on master as an error source (because PTS mail gets sent to [EMAIL PROTECTED] directly). There is no automatic bounce handling for the PTS, that's still on the TODO... --Jeroen -- Jeroen van Wolffelaar [EMAIL PROTECTED] (also for Jabber MSN; ICQ: 33944357) http://Jeroen.A-Eskwadraat.nl -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: master mail problems -- help needed
This one time, at band camp, Florian Weimer said: From time to time, master seems to bounce mail routed to mail.enyo.de with the following error message: [EMAIL PROTECTED] retry time not reached for any host after a long failure period Is anybody experiencing a similar problem? I tried to debug it myself, using the information I could access on master, but I couldn't gather enough evidence to present to the postmasters so far. IIRC, when there are no prolonged connectivity problems, the error message is characteristic of a broken Exim retry configuration (no retry section at all, or something like that), but master's configuration seems to be fine in this regard. You want to try /usr/sbin/exim4 -brt deneb.enyo.de You'll get an answer back that looks something like F,2h,15m; G,16h,1h,1.5; F,4d,6h; This means retry every 15min for the first 2 hours, then go into a 'growth algorithm' period where you retry starting at 1hour, then multiply by 1.5 until 16 hours have elapsed (so first every hour, then 1.5 hours, then 2.25 hours, etc) then finally every 6 hours until 4 days have elapsed, then bounce the mail. Once you know the retry rules, try /usr/sbin/exinext [EMAIL PROTECTED] That will tell you what's recorded in the retry database currently. It's fairly self explanatory, and you'll get something that looks like: Transport: gateway1.att.net [204.127.134.23] error 0: SMTP error from remote mailer after initial connection: host gateway1.att.net [204.127.134.23]: 450 busy - please try later first failed: 26-Nov-2005 15:35:16 last tried: 26-Nov-2005 15:35:16 next try at: 26-Nov-2005 15:50:16 Transport: gateway2.att.net [12.102.240.23] error 0: SMTP error from remote mailer after initial connection: host gateway2.att.net [12.102.240.23]: 450 busy - please try later first failed: 25-Nov-2005 04:44:32 last tried: 26-Nov-2005 15:35:16 next try at: 26-Nov-2005 21:35:16 I am guessing that you'll find that your host should have been tried and wasn't. The host mail.enyo.de had some intermittent connectivity problems during the past few weeks (downtimes of about one hour every couple of days, nothing which should cause Exim to run past its configured retry limit). But this has been fixed, and the sporadic bounces continued. The other problem is a certain sluggishness when one of those botnets attempts to send spam to hundreds of message IDs, but these attacks last a couple of minutes only, and master should be able to cope with that. I am guessing here, since I don't really have any way to check, but I assume that the problem is related to master's large queue. If exim encounters a host down state, it records it in the retry database. The host state will be updated, but only when the queue finally reaches it after the retry timer expires. If the queue takes forever to process, it's possible for host states to last longer than they should. Good luck, and hope that helps, -- - | ,''`.Stephen Gran | | : :' :[EMAIL PROTECTED] | | `. `'Debian user, admin, and developer | |`- http://www.debian.org | - signature.asc Description: Digital signature
Re: master mail problems -- help needed
* Stephen Gran: Once you know the retry rules, try /usr/sbin/exinext [EMAIL PROTECTED] That will tell you what's recorded in the retry database currently. exinext ist not SUID, and I haven't got sufficient permission on master to access the retry database: [pid 29063] open(/var/spool/exim4/db/retry.lockfile, O_RDONLY|O_LARGEFILE) = -1 EACCES (Permission denied) It would be interesting to see if the output contains an record, though. The information for the A record should have been cleared because I've successfully received mail since the last bounce. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: master mail problems -- help needed
* Jeroen van Wolffelaar: I tried to debug it myself, using the information I could access on master, but I couldn't gather enough evidence to present to the postmasters so far. But other DD's can also only do a limited amount of research, the only way to really find out is asking a postmaster -- this isn't a prosecution, so 'evidence' is not needed, I'd say (though, a copy of one bounce message with full headers would be the minimum I'd expect, because otherwise debugging is close to impossible). The trouble is that I lack a recent bounce message because I thought the problem was on my side (my .procmailrc script). The PTS unsubscription told me that I was wrong. In general, this failure means that for 4 consecutive days the a connection attempt that happens roughly every 8 hours fails (connection refused, a timeout, HELO refused, stuff like that). Are you sure that this condition can never have happened? Yes, some mail went through smoothly during about the same time. This should clear the hint in Exim's retry database. I see you only have one MX, for increased reliability and for cases when for example there's a routing problem somewhere between master and that one single MX, add a backup MX. Hmm, speaking of MXes, mail delivery over IPv6 seems to be enabled on master: router = dnslookup, transport = remote_smtp host mail.enyo.de [2001:14b0:202:1::a7] MX=10 host mail.enyo.de [212.9.189.167] MX=10 But master does not seem to have IPv6 connectivity. Maybe this is causing the problems, but this would also mean that Exim itself is buggy. It probably makes sense to disable IPv6 support in Exim on master, independently of my current problem. I'm going to suggest this to postmaster@ once I figured out a good way to implement this. When an exim mailserver is really bogged down under mail load, attempts can be made even less often. As far as I know, the mail server still responds with the RFC limits, which are also obeyed by Exim. I'd really look into a secondary MX, Or more powerful hardware on the primary MX, or more efficient software, I know. but if it's indeed only there two problems at the frequency you say, it shouldn't really be possible that this is the cause. Exactly my line of thought. This problem has gained some unexpected urgency because I was kicked off the PTS due to these bounces (I think so, I haven't been shown one of the PTS bounces). On the other hand, it rules out my .procmailrc on master as an error source (because PTS mail gets sent to [EMAIL PROTECTED] directly). There is no automatic bounce handling for the PTS, that's still on the TODO... The removal wasn't automatic. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: master mail problems -- help needed
This one time, at band camp, Florian Weimer said: * Stephen Gran: Once you know the retry rules, try /usr/sbin/exinext [EMAIL PROTECTED] That will tell you what's recorded in the retry database currently. exinext ist not SUID, and I haven't got sufficient permission on master to access the retry database: [pid 29063] open(/var/spool/exim4/db/retry.lockfile, O_RDONLY|O_LARGEFILE) = -1 EACCES (Permission denied) It would be interesting to see if the output contains an record, though. The information for the A record should have been cleared because I've successfully received mail since the last bounce. Sorry, I thought that you had access enough to check those things. Then you are just going to have to contact a postmaster and ask them to run it for you and see what's going on. If you are in group adm, you can use exigrep to find out status of messages (it produces quite a bit of output, though) /usr/sbin/exigrep [EMAIL PROTECTED] /var/log/exim4/mainlog* Will tell you about _all_ the logged tries for all messages to you - that might be an unacceptable load and an unaceptable amount to wade through, however. It does at least sort output by message, and makes it easier it easier to visualize than a plain grep. Good luck, -- - | ,''`.Stephen Gran | | : :' :[EMAIL PROTECTED] | | `. `'Debian user, admin, and developer | |`- http://www.debian.org | - signature.asc Description: Digital signature
Re: master mail problems -- help needed
This one time, at band camp, Florian Weimer said: Hmm, speaking of MXes, mail delivery over IPv6 seems to be enabled on master: router = dnslookup, transport = remote_smtp host mail.enyo.de [2001:14b0:202:1::a7] MX=10 host mail.enyo.de [212.9.189.167] MX=10 But master does not seem to have IPv6 connectivity. Maybe this is causing the problems, but this would also mean that Exim itself is buggy. It probably makes sense to disable IPv6 support in Exim on master, independently of my current problem. I'm going to suggest this to postmaster@ once I figured out a good way to implement this. I doubt that's the problem. This is from my logs: 2005-08-10 13:33:46 1E2uSY-0005KV-1Q = [EMAIL PROTECTED] H=lobefin.net (www.lobefin.net) [216.158.52.108] U=Debian-exim P=asmtp X=TLS-1.0:RSA_AES_128_CBC_SHA:16 A=plain_server:steve S=2386 [EMAIL PROTECTED] 2005-08-10 13:33:46 1E2uSY-0005KV-1Q IPv6 socket creation failed: Address family not supported by protocol 2005-08-10 13:33:46 1E2uSY-0005KV-1Q mail.enyo.de [2001:14b0:202:1::a7]: Address family not supported by protocol 2005-08-10 13:33:47 1E2uSY-0005KV-1Q = [EMAIL PROTECTED] R=dnslookup T=remote_smtp H=bugs.debian.org [140.211.166.43] QT=1s DT=1s 2005-08-10 13:33:49 1E2uSY-0005KV-1Q = [EMAIL PROTECTED] R=dnslookup T=remote_smtp H=mail.enyo.de [212.9.189.167] QT=3s DT=3s 2005-08-10 13:33:49 1E2uSY-0005KV-1Q Completed I have IPv6 support in kernel and exim, but no IPv6 connectivity, so it falls back to IPv4 without any noticable delay. -- - | ,''`.Stephen Gran | | : :' :[EMAIL PROTECTED] | | `. `'Debian user, admin, and developer | |`- http://www.debian.org | - signature.asc Description: Digital signature
Re: master mail problems -- help needed
* Stephen Gran: It probably makes sense to disable IPv6 support in Exim on master, independently of my current problem. I'm going to suggest this to postmaster@ once I figured out a good way to implement this. I doubt that's the problem. This is from my logs: 2005-08-10 13:33:46 1E2uSY-0005KV-1Q = [EMAIL PROTECTED] H=lobefin.net (www.lobefin.net) [216.158.52.108] U=Debian-exim P=asmtp X=TLS-1.0:RSA_AES_128_CBC_SHA:16 A=plain_server:steve S=2386 [EMAIL PROTECTED] 2005-08-10 13:33:46 1E2uSY-0005KV-1Q IPv6 socket creation failed: Address family not supported by protocol 2005-08-10 13:33:46 1E2uSY-0005KV-1Q mail.enyo.de [2001:14b0:202:1::a7]: Address family not supported by protocol 2005-08-10 13:33:47 1E2uSY-0005KV-1Q = [EMAIL PROTECTED] R=dnslookup T=remote_smtp H=bugs.debian.org [140.211.166.43] QT=1s DT=1s 2005-08-10 13:33:49 1E2uSY-0005KV-1Q = [EMAIL PROTECTED] R=dnslookup T=remote_smtp H=mail.enyo.de [212.9.189.167] QT=3s DT=3s 2005-08-10 13:33:49 1E2uSY-0005KV-1Q Completed I have IPv6 support in kernel and exim, Are you sure? IPv6 socket creation failed: Address family not supported by protocol suggests something else. but no IPv6 connectivity, master has even got an IPv6 routing table and the kernel assumes it can reach IPv6 hosts with site-local addresses (fe80::/64): [EMAIL PROTECTED]:~$ ip -f inet6 route list fe80::/64 dev eth0 metric 256 mtu 1500 advmss 1440 fe80::/64 dev eth1 metric 256 mtu 1500 advmss 1440 ff00::/8 dev eth0 metric 256 mtu 1500 advmss 1440 ff00::/8 dev eth1 metric 256 mtu 1500 advmss 1440 default dev eth0 proto kernel metric 256 mtu 1500 advmss 1440 default dev eth1 proto kernel metric 256 mtu 1500 advmss 1440 unreachable default dev lo proto none metric -1 error -101 [EMAIL PROTECTED]:~$ ip route get 2001:14b0:202:1::a7 2001:14b0:202:1::a7 via 2001:14b0:202:1::a7 dev eth0 src fe80::230:6eff:fe05:b968 metric 0 cache mtu 1500 advmss 1440 [EMAIL PROTECTED]:~$ so it falls back to IPv4 without any noticable delay. Try telnet mail.enyo.de 25 on master and your host for a comparison. master does suffer from a delay when the v6 address is tried, and Exim does something similar (try v6 first, then v4). -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: master mail problems -- help needed
This one time, at band camp, Florian Weimer said: * Stephen Gran: I have IPv6 support in kernel and exim, Are you sure? IPv6 socket creation failed: Address family not supported by protocol suggests something else. but no IPv6 connectivity, master has even got an IPv6 routing table and the kernel assumes it can reach IPv6 hosts with site-local addresses (fe80::/64): [EMAIL PROTECTED]:~$ ip -f inet6 route list fe80::/64 dev eth0 metric 256 mtu 1500 advmss 1440 fe80::/64 dev eth1 metric 256 mtu 1500 advmss 1440 ff00::/8 dev eth0 metric 256 mtu 1500 advmss 1440 ff00::/8 dev eth1 metric 256 mtu 1500 advmss 1440 default dev eth0 proto kernel metric 256 mtu 1500 advmss 1440 default dev eth1 proto kernel metric 256 mtu 1500 advmss 1440 unreachable default dev lo proto none metric -1 error -101 [EMAIL PROTECTED]:~$ ip route get 2001:14b0:202:1::a7 2001:14b0:202:1::a7 via 2001:14b0:202:1::a7 dev eth0 src fe80::230:6eff:fe05:b968 metric 0 cache mtu 1500 advmss 1440 [EMAIL PROTECTED]:~$ ip -f inet6 route list fe80::/64 dev eth0 metric 256 mtu 1500 advmss 1440 hoplimit 64 ff00::/8 dev eth0 metric 256 mtu 1500 advmss 1440 hoplimit 1 default dev eth0 proto kernel metric 256 mtu 1500 advmss 1440 hoplimit 64 unreachable default dev lo proto none metric -1 error -101 hoplimit 255 [EMAIL PROTECTED]:~$ ip route get 2001:14b0:202:1::a7 2001:14b0:202:1::a7 via 2001:14b0:202:1::a7 dev eth0 src fe80::20d:93ff:fe77:4a6e metric 0 cache mtu 1500 advmss 1440 hoplimit 64 so it falls back to IPv4 without any noticable delay. Try telnet mail.enyo.de 25 on master and your host for a comparison. master does suffer from a delay when the v6 address is tried, and Exim does something similar (try v6 first, then v4). [EMAIL PROTECTED]:~$ telnet mail.enyo.de 25 Trying 2001:14b0:202:1::a7... Trying 212.9.189.167... Connected to mail.enyo.de. Escape character is '^]'. 220 mail.enyo.de ESMTP [EMAIL PROTECTED]:~$ telnet mail.enyo.de 25 Trying 2001:14b0:202:1::a7... Trying 212.9.189.167... Connected to mail.enyo.de. Escape character is '^]'. 220 mail.enyo.de ESMTP No noticable time difference between the two, either. So, I don't think this is the real problem. I may be wrong, of course :) -- - | ,''`.Stephen Gran | | : :' :[EMAIL PROTECTED] | | `. `'Debian user, admin, and developer | |`- http://www.debian.org | - signature.asc Description: Digital signature
