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
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]
* 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=
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
>>>
* 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 M
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 hav
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
>
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).
--
,''`.
: :' :
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 r
* 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 ne
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
* 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
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
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
>
* 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
* 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/e
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 proble
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
>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 ac
19 matches
Mail list logo
