On 13 Mar 1999, John Goerzen wrote: > I don't know if this is a problem with glibc2.1 or Exim -- neither of > which I have the opportunity to test (my development platform is Alpha > running sendmail). > > It is possible that your kernel version is causing trouble; being an > "unstable" and development kernel could have its risks. > > Have you tried downgrading system components one by one to make sure > that it's really an elm problem and not a glibc2.1 one? What happens > with other MTAs?
No, I haven't tried downgrading yet, though I know that the problem is not with the kernel version. I get the same problem with kernel 2.2.3. I'd also be very surprised if this were an MTA problem because pine works fine. I haven't tried downgrading glibc because that is a major task (it's a whole bunch of packages, I'm not even sure where to begin with those). So, is there anyone out there using elm with exim and glibc2.1? There's got to be at least one person! Max > Max Kamenetsky <[EMAIL PROTECTED]> writes: > > I just upgraded my potato system to the latest version of libc and exim, > > and I'm not faced with the problem of elm sending blank e-mails. If I > > send a test message or reply to someone else's e-mail, the message comes > > out blank. The mail buffer gets written to a file in /tmp just like it's > > supposed to, and I can see that it's there right before I press "s" to > > send. The strange thing is that the message is sent empty, even though > > it gets written properly to my "sent" folder. There are no error messages > > in exim's mainlog. What is even stranger is that if I send a MIME > > message, it goes through OK. Pine also works fine. So, does anyone know > > what's going on? I'd really like to get this fixed ASAP, but it seems > > that the Debian version of elm wasn't compiled with debugging support. > > > > I'm running glibc2.1 under kernel 2.1.121. > > > > Thanks, and please reply via e-mail!
