<<< Date Index >>>     <<< Thread Index >>>

Re: Segmentation fault from mutt-1.5.17 with SMTP



On 2008-11-12, Gary Johnson <garyjohn@xxxxxxxxxxxxxxx> wrote:
> On 2008-11-11, Brendan Cully <brendan@xxxxxxxxxx> wrote:
> 
> > If you're going to the trouble of hacking on the source anyway, I'd
> > suggest you use 1.5.18 or the latest from mercurial.
> 
> You're right--I really should have done that.
> 
> Today I downloaded, built and installed mercurial.  Then I used 
> mercurial to download the latest development sources for mutt.  Once 
> I found out that 'prepare' is that same as 'configure', the build 
> went smoothly.  Furthermore, this version does not segfault in batch 
> mode--problem solved.

It turns out that I screwed up the batch-mode test of the new mutt:  
I wasn't using the muttrc that set 'smtp_url' so mutt was using 
sendmail instead of its built-in SMTP client.  For the particular 
destination address I chose, sendmail worked fine.

When I repeated the test with 'smtp_url' set properly, mutt still 
sent the message correctly, but it also printed a lot of stuff:

   $ echo 'ya test 2' | bin/mutt -s 'one more #2' garyjohn
   Looking up mailsvr.spk.agilent.com...
   Connecting to mailsvr.spk.agilent.com...
   Sending message... 0K/0.4K (0%)
   Sending message... 0K/0.4K (0%)
   Sending message... 0K/0.4K (0%)
   Sending message... 0K/0.4K (0%)
   Sending message... 0K/0.4K (0%)
   Sending message... 0K/0.4K (0%)
   Sending message... 0K/0.4K (0%)
   Sending message... 0K/0.4K (0%)
   Sending message... 0K/0.4K (0%)
   Sending message... 0K/0.4K (0%)
   Sending message... 0K/0.4K (0%)
   Sending message... 0K/0.4K (0%)
   Sending message... 0K/0.4K (0%)
   Sending message... 0K/0.4K (0%)

Should I be concerned about those messages?  It would be nice if it 
didn't print anything unless it failed.

Regards,
Gary