|
Sender: |
|
Date: |
Tue, 16 Sep 2014 09:59:11 -0700 |
Reply-To: |
|
Message-ID: |
|
Content-Transfer-Encoding: |
7bit |
Subject: |
|
From: |
|
Content-Type: |
text/plain; charset="utf-8"; format=flowed |
In-Reply-To: |
|
MIME-Version: |
1.0 |
Comments: |
|
Hi Valdis,
Thank. I confirmed that user did receive two copies (from Exchange
log). One from cc: (internal Exchange deliver), and one from ListServ
(delivered single copy to that recipient user A).
Shinn
On 9/16/2014 8:50 AM, Valdis Kletnieks wrote:
> On Tue, 16 Sep 2014 08:35:11 -0700, Shinn Wu said:
>
>> But it was ListServ sent unique message-ID to single recipient as I saw
> Right. Listserv sends one copy.
>
>> maillog, and it only sent single copy even though sender cc: to
>> recipient (who belonged to the list).
> Right. Because it doesn't *care* what the cc: list is, and it never even
> *sees* the other copy.
>
> So you should get *two* copies in this case. One direct from sender to
> the recipient via the cc: entry, and one via listserv. Most of the time,
> the recipient's mail system will then proceed to munch whichever copy
> arrives second...
>
> ############################
>
> To unsubscribe from the LSTSRV-L list:
> write to: mailto:[log in to unmask]
> or click the following link:
> http://peach.ease.lsoft.com/scripts/wa-PEACH.exe?SUBED1=LSTSRV-L&A=1
############################
To unsubscribe from the LSTSRV-L list:
write to: mailto:[log in to unmask]
or click the following link:
http://peach.ease.lsoft.com/scripts/wa-PEACH.exe?SUBED1=LSTSRV-L&A=1
|
|
|