On Fri, 20 Oct 2000 08:55:58 +1100, "Stephen Monty"
<stephe...@nospam.esc.ipex.com.au> wrote:
>Exchange 5.5 SP2
>
>I have a strange problem... When clients send messages externally with
>recipients only in the Bcc field (both the To and Cc fields are blank), some
>of those Bcc recipients appear in the To field when the message is received.
>But some of them are always visable - ie, it never works as it should. This
>happens on all receiving systems including Exchange. The only Technet
>articles I could find referred to specific systems such as PROFS.
>
>The odd thing is, is that different recipients see different names in the To
>field for the same message and not all the Bcc recipients appear - It
>appears to be random.
>
>Any idea's - The only thing I can think of doing is applying SP3 to the
>server running the IMS - However we are waiting for a replacement disk for
>that server as the mirror broke. I didn't really want to play around with
>the server until the HDD has been installed.
>
>Any suggestions would be greatly appreciated.
>
>Regards,
>
>Stephen.
>
--
Chris Scharff, MVP-Exchange
Senior Systems Consultant
Simpler-Webb, Inc.
Exchange FAQ: http://www.swinc.com/resource/exch_faq.htm
E-Mail Resource Guide: http://www.mail-resources.com/resources/search.cgi
Chris Scharff wrote in message
<3puuuss48on5d06kb...@4ax.com>...
>I think one of the early versions of Exchange 4.0 or perhaps it was
>Outlook 97 unpatched had a problem with Bcc recipients.. but Exchange
>in and of itself shouldn't.
>
>On Fri, 20 Oct 2000 08:55:58 +1100, "Stephen Monty"
><stephe...@nospam.esc.ipex.com.au> wrote:
>
>Yeah - It's odd... It happens with both Exchange Clients and Outlook 98.
>It really seems to be a problem with the Exchange Server, but it is version
>5.5 with SP2 ??? I'm stumped.
Do you have a firewall or other mail relay server in place?
--
Chris Scharff
Simpler-Webb, Inc.
Austin, TX
Exchange FAQ: http://www.swinc.com/resource/exch_faq.htm
Tools & Utilities: http://www.mail-resources.com/resources/search.cgi
Stephen Monty wrote:
--
If you feel that anything in my post needs correction - feel free to do so.
And please, keep all discussions in NG, so that everybody can participate.
Kirill
>Yep, all messages are forward to a UNIX box running Sendmail. However, I
>setup an account and used that server as my Outgoing mail server and sent a
>message using the BCC field and it worked - well, sort of...it didn't leave
>the 'To...' field blank. But it only put the receivers name in the 'to...'
>field - all the other names were still hidden. I'm assuming this is just
>how Sendmail handles it. In any case it still appears to be the Exchange
>server causing the problem?
Well, an Exchange server will leave the To: header blank, it doesn't
rewrite the RFC822 header at all. So Id' suspect it's either the
client or the Unix box.
>Yep, all messages are forward to a UNIX box running Sendmail. However, I
setup an account and used that server as my Outgoing mail server and sent a
message using the BCC field and it worked - well, sort of...it didn't leave
the 'To...' field blank.
*** this bit ------ But it only put the SENDERS name in the 'to...' field -
all the other names were still hidden ****. I'm assuming this is just how
The only way to know for sure I guess would be to turn up protocol
logging on the Exchange server.
On Tue, 24 Oct 2000 08:49:32 +1100, strategically shaved monkeys
watched in awe as "Stephen Monty"
<stephe...@nospam.esc.ipex.com.au> wrote:
>OK - I created a text file with Bcc recipients to put in the IMC Pickup
>directory. I am admin for a few agencies so I put this text file into two
>agencies Pickup directories. Here are the headers from both messages;
>
>From the Agency that works (5.5 SP3)
>
>Message-Id: <2000102306...@conargo.dpie.gov.au>
>Received: from PickupDirectory by MyServer with SMTP (Microsoft Exchange
>Internet Mail Service Version 5.5.2650.21)
> id 4Z8LP9M1; Mon, 23 Oct 2000 17:10:08 +1100
>Subject: Sent via IMCGATE
>To: undisclosed-recipients: ;
>
>
>And this from the one that is having the problem (5.5 SP2)
>
>Received: from PickupDirectory by MyServer with SMTP (Microsoft Exchange
>Internet Mail Service Version 5.5.2448.0)
> id VF97W0JA; Mon, 23 Oct 2000 17:15:09 +1100
>To: <step...@yahoo.com>
>To: <mont...@hotmail.com>
>To: <stephe...@affa.gov.au>
>To: <john.d...@esc.ipex.com.au>
>To: <stephe...@esc.ipex.com.au>
>Subject: Sent via MLCEX1
>Message-Id: <00Oct23.1650...@fwsge.atsic.sge.gov.au>
>Date: Mon, 23 Oct 2000 16:50:42 +1000
>
>I have tested this at another agency running SP2 and it works fine too -
>Just this one agency having the problem. To me these headers says that the
>Exchange server is doing it. Is that what you would get from this too????
>If you need the full headers unedited let me know. The only thing I changed
>above was the server name to "MyServer".
\
Thanks for your comments.
Step.
Chris Scharff [MVP] wrote in message ...
>
>Er.. well, Exchange would never put the undisclosed recipients thing
>in a message and I'm not sure about messages in a pickup directory
>from Exchange. If you can crank up the logging on the IMS and actually
>look at the data being transmitted by the Exchange server... that's
>the only way I can suggest determining what's actually doing it. And..
>if it's Exchange, I think a call to PSS would be required since I've
>never seen that behavior from Exchange before. Sorry.
>
>On Tue, 24 Oct 2000 08:49:32 +1100, strategically shaved monkeys
>watched in awe as "Stephen Monty"
><stephe...@nospam.esc.ipex.com.au> wrote:
>
>\
----------------------------------------------------------------------------
-------------------------
10/24/00 1:59:10 PM : <<< 250-8BITMIME
250-EXPN
250 HELP
10/24/00 1:59:10 PM : >>> MAIL FROM:<IPEX...@atsic.gov.au>
10/24/00 1:59:10 PM : <<< IO: |250 Ok
|
10/24/00 1:59:10 PM : <<< 250 Ok
10/24/00 1:59:10 PM : >>> RCPT TO:<stephe...@esc.ipex.com.au>
10/24/00 1:59:10 PM : <<< IO: |250 Ok
|
10/24/00 1:59:10 PM : <<< 250 Ok
10/24/00 1:59:10 PM : >>> RCPT TO:<stephe...@affa.gov.au>
10/24/00 1:59:10 PM : <<< IO: |250 Ok
|
10/24/00 1:59:10 PM : <<< 250 Ok
10/24/00 1:59:10 PM : >>> RCPT TO:<step...@yahoo.com>
10/24/00 1:59:10 PM : <<< IO: |250 Ok
|
10/24/00 1:59:10 PM : <<< 250 Ok
10/24/00 1:59:10 PM : >>> DATA
10/24/00 1:59:10 PM : <<< IO: |354 Start mail input; end with <CRLF>.<CRLF>
|
10/24/00 1:59:10 PM : <<< 354 Start mail input; end with <CRLF>.<CRLF>
10/24/00 1:59:10 PM : <<< IO: |250 Roger
|
10/24/00 1:59:10 PM : <<< 250 Roger
10/24/00 1:59:10 PM : >>> QUIT
10/24/00 1:59:10 PM : <<< IO: |221 atsic.sge.gov.au Out
|
10/24/00 1:59:10 PM : <<< 221 atsic.sge.gov.au Out
10/24/00 1:59:12 PM : A connection was accepted from 156.16.1.1.
10/24/00 1:59:12 PM : <<< IO: |EHLO atsic1.atsic.gov.au
|
10/24/00 1:59:12 PM : <<< EHLO atsic1.atsic.gov.au
10/24/00 1:59:12 PM : >>> 250-mlcex1.atsic.gov.au Hello [156.16.1.1]
250-XEXCH50
250-HELP
250-ETRN
250-DSN
250-SIZE 2048000
250-AUTH LOGIN
250-AUTH=LOGIN
250-STARTTLS
250 TLS
----------------------------------------------------------------------------
--------------
>OK, I'm not too good at interpretting these logs. I turned the protocol log
>on and this is what I find? How should it look for Bcc recipients?
Well, to begin, they'd be on the _inbound_ connections. Each thread
has its own log file (that's why there're more than one in the
directory).
In your log (edited to reduce unnecessary clutter), they'd appear as
below:
[ snip ]
>10/24/00 1:59:10 PM : >>> MAIL FROM:<IPEX...@atsic.gov.au>
>10/24/00 1:59:10 PM : <<< 250 Ok
>10/24/00 1:59:10 PM : >>> RCPT TO:<stephe...@esc.ipex.com.au>
>10/24/00 1:59:10 PM : <<< 250 Ok
>10/24/00 1:59:10 PM : >>> RCPT TO:<stephe...@affa.gov.au>
>10/24/00 1:59:10 PM : <<< 250 Ok
>10/24/00 1:59:10 PM : >>> RCPT TO:<step...@yahoo.com>
>10/24/00 1:59:10 PM : <<< 250 Ok
>10/24/00 1:59:10 PM : >>> DATA
>10/24/00 1:59:10 PM : <<< 354 Start mail input; end with <CRLF>.<CRLF>
From: <me>
To: <Santa Claus>
Subject: Ho-Ho-Ho!
Didja notice there ISN'T a "Bcc:" header?
.
>10/24/00 1:59:10 PM : <<< 250 Roger
>10/24/00 1:59:10 PM : >>> QUIT
IOW, either <stephe...@esc.ipex.com.au>,
<stephe...@affa.gov.au>, or <step...@yahoo.com> could be in the
"Bcc:" header of the message when it got to the transmitting SMTP
server. But it'll never be sent.
------------------
Rich Matheisen
MCSE+I, Exchange MVP
MS Exchange FAQ at http://www.swinc.com/resource/exch_faq.htm
>Thanks Rich, but how can I tell which server is at fault? Is it the
>Exchange server sending it wrong. When I looked at logs on a server that
>sends correctly, it actually appeared to break the message up into 3
>separate messages, whereas with this one, it had all addresses in the same
>message?
Either way will work. If all three recipients are in the same domain
then sending three "RCPT TO" command and one copy of the message is
the "approved" way. If the recipients are in separate domains then a
copy must be sent to each.
>I'm guessing that when the two servers establish a connection they
>work out how they can send information to each other.
SMTP isn't that smart.
>So how can I tell
>which one is moving the Bcc recipients into the 'To...' field of the
>message?
It isn't Exchange. Exchange does nothing with the message body (which
is where those "To:" headers are located.
Rich Matheisen [MVP] wrote in message ...
>"Stephen Monty" <stephe...@nospam.esc.ipex.com.au> wrote:
>
>>OK, I'm not too good at interpretting these logs. I turned the protocol
log
>>on and this is what I find? How should it look for Bcc recipients?
>
>Well, to begin, they'd be on the _inbound_ connections. Each thread
>has its own log file (that's why there're more than one in the
>directory).
>
>In your log (edited to reduce unnecessary clutter), they'd appear as
>below:
>
> [ snip ]
>
>>10/24/00 1:59:10 PM : >>> MAIL FROM:<IPEX...@atsic.gov.au>
>>10/24/00 1:59:10 PM : <<< 250 Ok
>>10/24/00 1:59:10 PM : >>> RCPT TO:<stephe...@esc.ipex.com.au>
>>10/24/00 1:59:10 PM : <<< 250 Ok
>>10/24/00 1:59:10 PM : >>> RCPT TO:<stephe...@affa.gov.au>
>>10/24/00 1:59:10 PM : <<< 250 Ok
>>10/24/00 1:59:10 PM : >>> RCPT TO:<step...@yahoo.com>
>>10/24/00 1:59:10 PM : <<< 250 Ok
>>10/24/00 1:59:10 PM : >>> DATA
>>10/24/00 1:59:10 PM : <<< 354 Start mail input; end with <CRLF>.<CRLF>
>From: <me>
>To: <Santa Claus>
>Subject: Ho-Ho-Ho!
>
>Didja notice there ISN'T a "Bcc:" header?
>.
>>10/24/00 1:59:10 PM : <<< 250 Roger
>>10/24/00 1:59:10 PM : >>> QUIT
>
>
>IOW, either <stephe...@esc.ipex.com.au>,
><stephe...@affa.gov.au>, or <step...@yahoo.com> could be in the
>"Bcc:" header of the message when it got to the transmitting SMTP
>server. But it'll never be sent.
>