Re: Bcc not working?

[Thomas Maeder <maeder+balsa glue ch>]

Am 2002.02.20 09:29 schrieb(en) Brian Stafford:
> 
> Will you *please* get the protocol trace from Balsa as previously
> instructed.  Configure balsa using "CFLAGS=-DDEBUG=1 ./configure
> ...", send the message.  balsa will print a protocol trace to
> stderr.  Post this trace to the list.

As I wrote in another message, Balsa gets totally useless when
configured and compiled like this (all IMAP folders are reported to be 
empty).

Anyway, I started this version and sent a message from it with To: and 
Bcc: both set. This is the output:

Dumping Message
Dumping a text[7] message
Locking mailbox Ausgang
Unlocking mailbox Message: balsa_sendmsg_destroy()_handler: Start.
balsa_sendmsg_destroy_handler: Freeing bsm
Message: balsa_sendmsg_destroy(): Stop.
Reading /home/maeder/mail/outbox...
Sorting mailbox...
Send_Message: 136846344, 1, Connected to MTA
S: 220 cicero.glue.ch ESMTP BusinessMail
C: EHLO madbox
S: 250-cicero.glue.ch
250-PIPELINING
250-SIZE 10240000
250-ETRN
250 8BITMIME
C: MAIL FROM:<maeder@glue.ch> SIZE=1024
S: 250 Ok
C: RCPT TO:<maeder@glue.ch>
Send_Message: 136848872, 1, From: 250 <maeder@glue.ch>
  From maeder@glue.ch: 250 Ok

S: 250 Ok
C: DATA
Send_Message: 136957056, 1, To: 250 <maeder@glue.ch>
To maeder@glue.ch: 250 Ok

S: 354 End data with <CR><LF>.<CR><LF>
H: Date: Wed, 20 Feb 2002 21:48:45 +0100
H: From: Thomas Maeder <maeder@glue.ch>
H: To: Thomas Maeder <maeder@glue.ch>
H: Subject: Test mit Bcc:
H: Message-ID: <20020220214845.A15240@madbox.hispeed.ch>
H: Mime-Version: 1.0
H: Content-Type: text/plain; format=flowed; charset=ISO-8859-1
H: Content-Transfer-Encoding: 8bit
H: X-Mailer: Balsa 1.2.4
H: Content-Length: 1
H: Lines: 1
Send_Message: 136846344, 1, Send_Message: 136848872, 1, S: 250 Ok: 
queued as B7F7F3BA5A
C: QUIT
Send_Message: 136957056, 1, 250 Ok: queued as B7F7F3BA5A

250 Ok: queued as B7F7F3BA5A

S: 221 Bye
Locking mailbox Ausgang
Unlocking mailbox LibBalsaMailbox: Closing Ausgang Refcount: 1
Locking mailbox Ausgang
Unlocking mailbox Send_Message: 136846344, 1, Disconnected
Send_Message: 136848872, 4, Writing /home/maeder/mail/outbox...
Sorting mailbox...
0 kept, 1 deleted.


[Ausgang is the German translation of outbox]


> The protocol trace you supply is not from any protocol session
> originated by balsa+libESMTP.  Balsa submits both messages in a
> single smtp session, not two sessions as your trace shows and both
> messages share the *same* message-id, not two different message ids.
> So you have gone to a lot of effort to obtain something totally
> useless.

There are two ids because I sent two messages; please read my message
again. The first part logs my sending a message with To: but no Bcc:
header. The second part logs my sending a message with both a To: and a
Bcc: header. As you correctly observed, both parts look exactly the
same (modulo message id). This is what I am writing about in this 
thread (I think).


> Despite your different conclusion, balsa *does* work correctly.
> Until you provide the protocol trace from balsa that was actually
> asked for, neither I nor anybody else on this list can or will help
> you.

Maybe it's me, but actually I'm trying to help you (assuming you're
among Balsa's developers - if this is the case: thanks!).