Mailing List Archive

[Bug 384] 0x000b: terminated by signal 11
http://www.exim.org/bugzilla/show_bug.cgi?id=384


info@shadowfox.biz changed:

What |Removed |Added
----------------------------------------------------------------------------
Priority|medium |critical
Version|4.62 |4.63






------- You are receiving this mail because: -------
You are the QA contact for the bug, or are watching the QA contact.

--
## List details at http://www.exim.org/mailman/listinfo/exim-dev Exim details at http://www.exim.org/ ##
[Bug 384] 0x000b: terminated by signal 11 [ In reply to ]
http://www.exim.org/bugzilla/show_bug.cgi?id=384





------- Additional Comments From blists@nobaloney.net 2006-10-30 22:58 -------
(In reply to comment #1)
> (In reply to comment #0)
> > I'm a Directadmin user on FreeBSD 6.1.
>
> I don't even know what Directadmin is; whether it is relevant is therefore
unknown.
Dr. Hazel (and others),

DirectAdmin is a hosting control panel. DirectAdmin doesn't care which version
of exim is being used; the individual with the problem will have to say which
version.

The default exim.conf file may be found here:

http://files.directadmin.com/services/exim.conf

But users may change it; the individual with the problem will have to say
whether or not s/he has.

I wrote most of the current exim.conf file (above) and I'm the first to say it's
not perfect. I'm working on another now.

I'm a member of the exim-users list, we can carry on a discussion there.

Jeff Lasman


>
> > R=lookuphost T=remote_smtp defer (-1): smtp transport process returned
non-zero s
> > tatus 0x000b: terminated by signal 11
> > Frozen
>
> If you unfreeze the message, does it then get delivered normally?
>
> > Many Directadmin users seem to have the same problem going after the
> > directadmin forum.
>
> So it may be related ... which means you or some other Directadmin user will
> have to do the debugging. What would be ideal, of course, would be to run Exim
> with debugging turned on, but how to do this in your environment I don't know.

(In reply to comment #1)
> (In reply to comment #0)
> > I'm a Directadmin user on FreeBSD 6.1.
>
> I don't even know what Directadmin is; whether it is relevant is therefore
unknown.
>
> > R=lookuphost T=remote_smtp defer (-1): smtp transport process returned
non-zero s
> > tatus 0x000b: terminated by signal 11
> > Frozen
>
> If you unfreeze the message, does it then get delivered normally?
>
> > Many Directadmin users seem to have the same problem going after the
> > directadmin forum.
>
> So it may be related ... which means you or some other Directadmin user will
> have to do the debugging. What would be ideal, of course, would be to run Exim
> with debugging turned on, but how to do this in your environment I don't know.



------- You are receiving this mail because: -------
You are the QA contact for the bug, or are watching the QA contact.

--
## List details at http://www.exim.org/mailman/listinfo/exim-dev Exim details at http://www.exim.org/ ##