[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
[cobalt-users] Qube2 Bcc: issues.....con't.
- Subject: [cobalt-users] Qube2 Bcc: issues.....con't.
- From: "Jason Aspinall" <jaspinall@xxxxxxxxxxxxxxx>
- Date: Tue Jan 4 09:37:35 2000
Further to my Bcc: posting, laughably it would appear that my subscription
to this Cobalt list is also causing the mail to divert through to the admin
account
:|
Here's the full header:
*****HEADER START*****
Return-Path: <cobalt-users-admin@xxxxxxxxxxxxxxx>
Received: from localhost (localhost [127.0.0.1])
by mail.lion-breath.com (8.9.2/8.9.2) with ESMTP id RAA08957
for <postmaster@localhost>; Tue, 4 Jan 2000 17:18:25 GMT
Received: from pop3.mail.demon.net
by localhost with POP3 (fetchmail-4.7.4)
for postmaster@localhost (multi-drop); Tue, 04 Jan 2000 17:18:26 +0000
(GMT)
Received: from punt-2.mail.demon.net by mailstore for
jaspinall@xxxxxxxxxxxxxxx
id 947005839:20:00067:8; Tue, 04 Jan 2000 17:10:39 GMT
Received: from list.cobalt.com ([63.77.128.170]) by punt-2.mail.demon.net
id aa2000049; 4 Jan 2000 17:10 GMT
Received: from list.cobalt.com (IDENT:mail@localhost [127.0.0.1])
by list.cobalt.com (8.9.3/8.8.7) with ESMTP id JAA13618;
Tue, 4 Jan 2000 09:08:59 -0800
Received: from SSP1NO21.highway.telekom.at (EMAIL-AON.highway.telekom.at
[195.3.96.71])
by list.cobalt.com (8.9.3/8.8.7) with ESMTP id JAA13594
for <cobalt-users@xxxxxxxxxxxxxxx>; Tue, 4 Jan 2000 09:08:57 -0800
Received: from fathi (N448P023.dipool.highway.telekom.at [212.183.65.247])
by SSP1NO21.highway.telekom.at (8.9.3/8.9.3) with SMTP id SAA153932
for <cobalt-users@xxxxxxxxxxxxxxx>; Tue, 4 Jan 2000 18:08:55 +0100
Message-ID: <>
From: "Fathi Said" <fathi@xxxxxx>
To: <cobalt-users@xxxxxxxxxxxxxxx>
References: <000001bf56dd$c602d9e0$08142acb@xxxxxxxxxx>
Subject: Re: [cobalt-users] [cobalt-raq2] Brosoft SSL
Date: Tue, 4 Jan 2000 18:07:21 +0100
X-Priority: 3
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook Express 5.00.2314.1300
X-MimeOLE: Produced By Microsoft MimeOLE V5.00.2314.1300
Reply-To: cobalt-users@xxxxxxxxxxxxxxx
Sender: cobalt-users-admin@xxxxxxxxxxxxxxx
Errors-To: cobalt-users-admin@xxxxxxxxxxxxxxx
X-Mailman-Version: 1.1
Precedence: bulk
List-Id: Mailing list for users to share thoughts on Cobalt products.
<cobalt-users.list.cobalt.com>
X-BeenThere: cobalt-users@xxxxxxxxxxxxxxx
X-Fetchmail-Warning: recipient address cobalt-users@xxxxxxxxxxxxxxx didn't
match any local name
X-UIDL: f630fa5939b2934102db656be505f230
*****HEADER END*****
Two important lines taken from above are:
"Received: from punt-2.mail.demon.net by mailstore for
jaspinall@xxxxxxxxxxxxxxx"
This proves that our ISP (Demon Internet) have received a valid email
address (mine!), and;
"To: <cobalt-users@xxxxxxxxxxxxxxx>"
Clearly shows that the list server is pumping out messages that obviously
would
not comply with *any* of our users in the user database.
Therefore the Qube *cannot* be handling the Bcc: fields correctly.
The Qube2 is running the very latest firmware update with the relevant
security patches also in place.
Cobalt OS Release 4.0
Qube2-Security Release 2.1
Qube2-Security Release 2.2
Qube2-Update-OS Release 2.0
Anyone care to shed some light?
TIA
--
Jason Aspinall
Lion Laboratories Limited, Barry, UK, CF63 2BE
Tel +44(0)1446 744244 Fax +44(0)1446 720937
An almost satisfied Cobalt Qube2 Administrator http://www.cobalt.com