Your message dated Wed, 16 Apr 2008 17:40:43 -0400
with message-id <[EMAIL PROTECTED]>
and subject line exim has been removed from Debian, closing #99504
has caused the Debian Bug report #99504,
regarding Segfault in exim
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact [EMAIL PROTECTED]
immediately.)
--
99504: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=99504
Debian Bug Tracking System
Contact [EMAIL PROTECTED] with problems
--- Begin Message ---
Package: exim
Version: 3.22-4
Architecture: powerpc
Kernel: Linux 2.4.5-pre1
libc6: 2.2.3-5
Exim running as user mail (or root) doesn't accept SMTP mail
from stdin. It finishes with segfault. So it cannot be
started from inetd. May be architecture specific (endianess)
error. Running as ordinary user works fine. Previous woody
version worked fine.
kybl:~# /usr/sbin/exim -bs -d 9
Exim version 3.22 debug level 9 uid=0 gid=0
Berkeley DB: Sleepycat Software: Berkeley DB 2.7.7:
(08/20/99)
kybl in local_domains? yes (matched kybl)
Unable to create IPv6 socket to find interface addresses:
error 97 Address family not supported by protocol
Trying for an IPv4 socket
Actual local interface address is 127.0.0.1 (lo)
Actual local interface address is 128.226.121.51 (eth0)
Caller is an admin user
Caller is a trusted user
user name "root" extracted from gecos field "root"
originator: uid=0 gid=0 login=root name=root
sender address = NULL
SMTP>> 220 kybl ESMTP Exim 3.22 #1 Fri, 01 Jun 2001 12:33:55
-0400
Segmentation fault
kybl:~#
--- End Message ---
--- Begin Message ---
Version: 3.36-18.2+rm
The exim package has been removed from Debian testing, unstable and
experimental, so I am now closing the bugs that were still opened
against it.
For more information about this package's removal, read
http://bugs.debian.org/420191 . That bug might give the reasons why
this package was removed, and suggestions of possible replacements.
Don't hesitate to reply to this mail if you have any question.
Thank you for your contribution to Debian.
Barry deFreese
--- End Message ---
