Re: Need help debugging send problems.

["Mark A. Flacy" <mflacy verizon net>]

On Sun, 2009-03-01 at 14:49 -0600, Mark A. Flacy wrote:
> On Sun, 2009-03-01 at 19:40 +0100, Pawel Salek wrote:
> > On 03/01/2009 07:18:32 PM, Mark A. Flacy wrote:
> > > Greetings,
> > > 
> > > My configuration to send mail via Balsa has stopped working after I
> > > upgraded to 2.3.28.  Unfortunately, the debug output that balsa  
> > > provides
> > > for message sending is not very helpful, to wit...
> > > 
> > > Send_Message: 137865176, 4,
> > > Send_Message: 137865176, 4,
> > > 
> > > I'd prefer to not have to crank up wireshark to see what's up.  Any
> > > suggestions?
> > 
> > Well, it that is all you see, we have got trouble... Are you saying you  
> > see no SMTP dialog?
> 
> That is correct.  I do not see a debug option to turn the dialog on.
> 
> > Is IMAP involved in any way?
> 
> Yes, but I can read IMAP with no issues. (And there are IMAP related
> messages in the debug output.)
> 
> >  Do you save the FCC  
> > copy of the message when sending?
> 
> Yes.
> 
> Here's a complete trace (if word wrap messes it up, I'll resend as an
> attachment)....
> 
> flacy flacy:~$ balsa -c
> ** Message: init gpgme version 1.1.6
> ** Message: protocol OpenPGP: engine /usr/bin/gpg2 (home (null), version
> 2.0.9)
> ** Message: protocol CMS: engine /usr/bin/gpgsm (home (null), version
> 2.0.9)
> ** Message: protocol (null): engine /usr/bin/gpgconf (home (null),
> version 2.0.9)
> Server loaded, host: gateway, no SSL.
> Message: 137457760, 0, POP3
> Message: 137809576, 0, Local mailbox: Inbox
> Message: 137457944, 0, Local mailbox: Outbox
> Message: 137809504, 0, Local mailbox: Sentbox
> Message: 137813224, 0, Local mailbox: Draftbox
> Message: 135931040, 1, Finished
> imap_scan_attach_mailbox: add mbox of name blocked (full path
> imap://flacy gateway/blocked)
> imap_scan_attach_mailbox: add mbox of name INBOX (full path
> imap://flacy gateway/INBOX)
> imap_scan_attach_mailbox: add mbox of name jobs (full path
> imap://flacy gateway/jobs)
> imap_scan_attach_mailbox: add mbox of name local (full path
> imap://flacy gateway/local)
> imap_scan_attach_mailbox: add mbox of name msgid_cache (full path
> imap://flacy gateway/msgid_cache)
> imap_scan_attach_mailbox: add mbox of name spam (full path
> imap://flacy gateway/spam)
> imap_scan_attach_mailbox: add mbox of name Trash (full path
> imap://flacy gateway/Trash)
> Local folder /home/flacy/mail/q
> Local folder /home/flacy/mail/draft
> Local mailbox Spam loaded as: LibBalsaMailboxMbox
> Local mailbox sent-mail loaded as: LibBalsaMailboxMbox
> Local mailbox saved-messages loaded as: LibBalsaMailboxMbox
> Send_Message: 137865176, 4, 
> Send_Message: 137865176, 4, 
> Auto-checked for new messages...
> Message: 138709744, 0, POP3
> Message: 138709384, 0, Local mailbox: Spam
> Message: 138729008, 0, Local mailbox: sent-mail
> IMAP mailbox: imap://flacy gateway/Trash
> Message: 3047187488, 0, Local mailbox: saved-messages
> Message: 3047191504, 0, IMAP mailbox: imap://flacy gateway/Trash
> IMAP mailbox: imap://flacy gateway/spam
> IMAP mailbox: imap://flacy gateway/msgid_cache
> Message: 138733248, 0, IMAP mailbox: imap://flacy gateway/spam
> Message: 138733432, 0, IMAP mailbox: imap://flacy gateway/msgid_cache
> IMAP mailbox: imap://flacy gateway/local
> Message: 138717600, 0, IMAP mailbox: imap://flacy gateway/local
> IMAP mailbox: imap://flacy gateway/jobs
> Message: 138679704, 0, IMAP mailbox: imap://flacy gateway/jobs
> IMAP mailbox: imap://flacy gateway/INBOX
> Message: 3047191504, 0, IMAP mailbox: imap://flacy gateway/INBOX
> IMAP mailbox: imap://flacy gateway/blocked
> Message: 3047191504, 0, IMAP mailbox: imap://flacy gateway/blocked
> Message: 3047191504, 0, Local mailbox: Outbox
> Message: 3047192576, 0, Local mailbox: Draftbox
> Message: 3047188568, 0, Local mailbox: Sentbox
> Message: 3047188752, 0, Local mailbox: Inbox
> Message: 3047186712, 1, Finished
> balsa_app: Finished cleaning up.

Well, I ended up running wireshark.

Traces available upon request (after a delay for editing to remove
e-mail addresses.)  Balsa had split a BDAT message across 2 packets; I
don't know if that's a problem.  I'll see what evolution does with this
message.

-- 
Mark A. Flacy <mflacy verizon net>