Eric Sorenson writes:
>
>Note that lmtpd won't send a response back if the mail looks like it
>came from a bounce/root/daemon address, or if the From matches any
>of the To :addresses
I asked somebody else to send mail to my test account today, and
they didn't get a response. This was just in case it only failed
when I sent the message. I still suspect that lmtpd is just deciding
that no vacation response is needed.
>Do you have a corefile in the deliverdb directory? Run 'gdb -c' over
>it and if so and paste the results of a 'bt' backtrace. I'm betting
>it's either the In-Reply-To header or the EX_USAGE error from sendmail
>due to the commandline being wrong.
There is a core from lmtpd that was created from the `deliver -l'
test. I can't use gdb but adb says this about it:
# adb /usr/local/cyrus/bin/lmtpd /var/core/core.lmtpd.9900
core file = /var/core/core.lmtpd.9900 -- program ``lmtpd'' on platform
SUNW,SPARCstation-20
SIGSEGV: Segmentation Fault
$c
strlen() + 80
data address not found
$?
Not many clues in the registers except this one:
o7 0xef4c12b8 _doprnt+0x1a74 i7 0xef4c2d60 fprintf+0xe8
Looks like an fprintf of a null string. I found these strings together
in the dump:
X-Sieve: cmu-sieve 2.0
From: <[EMAIL PROTECTED]>
To: <[EMAIL PROTECTED]>
Subject: Re: Seeing if this will work
In-Reply-To:
That looks like this piece of code in lmtpd.c:
fprintf(sm, "Subject: %s\r\n", src->subj);
fprintf(sm, "In-Reply-To: %s\r\n", m->id);
fprintf(sm, "Auto-Submitted: auto-replied (vacation)\r\n");
I'd say that for some reason the message-id was NULL, and I suspect
that this is a known bug. In any case, it never happens when
sendmail is feeding lmtpd, only when deliver is doing it.
>Here's a good way to debug all things lmtp-related:
Thanks. I have more debugging to do.
--
-Gary Mills- -Unix Support- -U of M Academic Computing and Networking-
