Re: Bcc not working?

[Thomas Maeder <maeder+balsa glue ch>]

Am 2002.02.18 13:50 schrieb(en) Brian Stafford:
> 
> Balsa DOES work correctly, i.e. two messages - one with, one without 
> the Bcc header correctly submitted to the SMTP server.

I come to a different conclusion.

This is the transcript of my sending two messages. The first one only 
has a To:, the second also a Bcc: (to a different address)

<- 220 cicero.glue.ch ESMTP BusinessMail\r\n
-> EHLO madbox\r\n
<- 250-cicero.glue.ch\r\n
250-PIPELINING\r\n
250-SIZE 10240000\r\n
250-ETRN\r\n
250 8BITMIME\r\n
-> MAIL FROM:<maeder@glue.ch> SIZE=1024\r\n
<- 250 Ok\r\n
-> RCPT TO:<maeder@glue.ch>\r\n
<- 250 Ok\r\n
-> DATA\r\n
<- 354 End data with <CR><LF>.<CR><LF>\r\n
-> Date: Mon, 18 Feb 2002 19:38:51 +0100\r\n
From: Thomas Maeder <maeder@glue.ch>\r\n
To: Thomas Maeder <maeder@glue.ch>\r\n
Subject: Test 1\r\n
Message-ID: <20020218193851.Y2353@madbox.hispeed.ch>\r\n
Mime-Version: 1.0\r\n
Content-Type: text/plain; format=flowed; charset=ISO-8859-1\r\n
Content-Transfer-Encoding: 8bit\r\n
X-Mailer: Balsa 1.2.4\r\n
Content-Length: 7\r\n
Lines: 1\r\n
\r\n
Test 1\r\n
.\r\n
<- 250 Ok: queued as ED7713BA48\r\n
-> QUIT\r\n
<- 221 Bye\r\n
->

<- 220 cicero.glue.ch ESMTP BusinessMail\r\n
-> EHLO madbox\r\n
<- 250-cicero.glue.ch\r\n
250-PIPELINING\r\n
250-SIZE 10240000\r\n
250-ETRN\r\n
250 8BITMIME\r\n
-> MAIL FROM:<maeder@glue.ch> SIZE=1024\r\n
<- 250 Ok\r\n
-> RCPT TO:<maeder@glue.ch>\r\n
<- 250 Ok\r\n
-> DATA\r\n
<- 354 End data with <CR><LF>.<CR><LF>\r\n
-> Date: Mon, 18 Feb 2002 19:40:16 +0100\r\n
From: Thomas Maeder <maeder@glue.ch>\r\n
To: Thomas Maeder <maeder@glue.ch>\r\n
Subject: Test with Bcc\r\n
Message-ID: <20020218194016.A2353@madbox.hispeed.ch>\r\n
Mime-Version: 1.0\r\n
Content-Type: text/plain; format=flowed; charset=ISO-8859-1\r\n
Content-Transfer-Encoding: 8bit\r\n
X-Mailer: Balsa 1.2.4\r\n
Content-Length: 14\r\n
Lines: 1\r\n
\r\n
Test with Bcc\r\n
.\r\n
<- 250 Ok: queued as 4C4CB3BA48\r\n
-> QUIT\r\n
<- 221 Bye\r\n
->

The transcript was produced by the following simple sniffer script (I 
modified the transcript slightly for better readability):

#! /bin/sh

# restart under -*- Tcl -*- shell \
     exec tclsh $0 "$*"


proc connection {name host port} {
     global peer remoteHost remotePort
     puts connection:$name
     set peer($name) [socket $remoteHost $remotePort]
     fconfigure $name -buffering none -translation binary -blocking 0
     fconfigure $peer($name) -buffering none -translation binary 
-blocking 0
     set peer($peer($name)) $name
     fileevent $name readable [list readable $name]
     fileevent $peer($name) readable [list readable $peer($name)]
}

proc readable {name} {
     global peer smtplog
     puts "readable $name"
     if {[eof $name]} {
         puts "$name eof"
         close $name
         close $peer($name)
         unset peer($peer($name))
         unset peer($name)
     } else {
         set input [read $name]
         puts -nonewline $peer($name) $input
         regsub -all \r $input \\r input
         regsub -all \n $input \\n\n input
         puts -nonewline $smtplog $name:$input
     }
}

proc bgerror {msg} {
     global errorInfo
     puts stderr bgerror:$errorInfo
}


set argv [lindex $argv 0]
set argc [llength $argv]

if {$argc<3} {
     puts "Usage: sniffer.tcl <localport> <remotehost> <remoteport>"
} else {
     set localPort [lindex $argv 0]
     set remoteHost [lindex $argv 1]
     set remotePort [lindex $argv 2]

     set smtplog [open /tmp/smtp.log w]
     fconfigure $smtplog -buffering none

     socket -server connection $localPort

     set x 1
     vwait x
}

Connection requests and eofs are written to stdout, the transfered data 
to
/tmp/smtp.log