Your message dated Mon, 16 Jan 2006 17:26:01 -0700
with message-id <[EMAIL PROTECTED]>
and subject line Read Carefully.
has caused the attached Bug report to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what I am
talking about this indicates a serious mail system misconfiguration
somewhere.  Please contact me immediately.)

Debian bug tracking system administrator
(administrator, Debian Bugs database)

--------------------------------------
Received: (at submit) by bugs.debian.org; 22 Jan 1999 03:59:50 +0000
Received: (qmail 11060 invoked from network); 22 Jan 1999 03:59:50 -0000
Received: from cpu1612.adsl.bellglobal.com (HELO gatekeeper.bcwhite.ml.org) 
([EMAIL PROTECTED])
  by master.debian.org with SMTP; 22 Jan 1999 03:59:50 -0000
Received: from dragon.bcwhite.ml.org (pobox.com) [192.168.1.10] (bcwhite)
        by gatekeeper.bcwhite.ml.org with esmtp (Exim 2.05 #1 (Debian))
        id 103XlM-0007Bl-00; Thu, 21 Jan 1999 23:00:04 -0500
Sender: bcwhite
Message-ID: <[EMAIL PROTECTED]>
Date: Thu, 21 Jan 1999 23:00:33 -0500
From: Brian White <[EMAIL PROTECTED]>
X-Mailer: Mozilla 4.5 [en] (X11; U; Linux 2.0.36 i686)
X-Accept-Language: en
MIME-Version: 1.0
To: Debian Bugs <[EMAIL PROTECTED]>
Subject: Unexpected use of /cgi-bin/
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit

Package: apache
Version: 1.3.3-4

As there were really no objections to the personal mail I sent about this,
I'm filing it as a bug...

Most people setting up a web site expect /cgi-bin/ to be available for
scripts on their site.  Unfortunately, Debian uses this for those scripts
packages that get installed.  These two need to be independant.

As such, Debian's system needs to be altered a bit.  I recommend using
instead the name "/cgi-lib/" for scripts under /usr/lib/cgi-bin/.  This
will keep both features independant and not affect the general use of
the system.

                                          Brian
                                  ( [EMAIL PROTECTED] )

-------------------------------------------------------------------------------
      You can never be too good looking or too well equipped.  -- Dilbert
---------------------------------------
Received: (at 32263-done) by bugs.debian.org; 17 Jan 2006 01:26:03 +0000
>From [EMAIL PROTECTED] Mon Jan 16 17:26:03 2006
Return-path: <[EMAIL PROTECTED]>
Received: from tomts52.bellnexxia.net ([209.226.175.177] 
helo=tomts52-srv.bellnexxia.net)
        by spohr.debian.org with esmtp (Exim 4.50)
        id 1Eyfbn-0004Xw-4S
        for [EMAIL PROTECTED]; Mon, 16 Jan 2006 17:26:03 -0800
Received: from [70.51.178.165] by tomts52-srv.bellnexxia.net
          (InterMail vM.5.01.06.13 201-253-122-130-113-20050324) with SMTP
          id <[EMAIL PROTECTED]>;
          Mon, 16 Jan 2006 20:25:59 -0500
Message-ID: <[EMAIL PROTECTED]>
From: BarClays Bank <[EMAIL PROTECTED]>
To: client <[EMAIL PROTECTED]>
Subject: Read Carefully.
Date: Mon, 16 Jan 2006 17:26:01 -0700
MIME-Version: 1.0
Content-Type: text/plain;
        charset="us-ascii"
X-Priority: 3
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook Express 6.00.2800.1106
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1106
X-Spam-Checker-Version: SpamAssassin 2.60-bugs.debian.org_2005_01_02 
        (1.212-2003-09-23-exp) on spohr.debian.org
X-Spam-Level: **
X-Spam-Status: No, hits=2.1 required=4.0 tests=RAZOR2_CF_RANGE_51_100,
        RAZOR2_CHECK autolearn=no version=2.60-bugs.debian.org_2005_01_02

Dear Customer,
We are happy to announce that our software programming has been 
updated. Our new software programming with advanced online access and 
improved security allows you performing faster and better online 
activity. Due to the complexity of the following process, some 
technical errors we made and some of the personal data were lost. At 
the moment we are unable to restore all of the information, therefore 
some of the accounts that have been enrolled for online access can 
experience faulty errors.
A new data base for personal data filling has been activated to 
prevent customers from possible online-banking activity delays. We 
update our data base with customers' account information to allow our 
specialists restoring all of the data lost within a 3-day period and 
to avoid future data loss. Otherwise the process can take up to 
several weeks. Until then your online access can be disabled and 
experience faulty errors during the online-banking activity.
Your personal data can still be available, but we can't guarantee 
that. If you do wish to participate in the data base update and to 
have your online-banking access enabled within a 3-day period, please 
complete the personal data recovery process and fill out all the 
required info on this page. You will get a notice within a 3-day 
period if we will experience faulty errors with your online-account. 
If no errors occur, the bank does not send out a notice. After the 
data recovery process is complete via our new site, personal data 
update and verification process will be completed. To complete the 
personal data recovery process, please follow the link below or just 
paste it in your Internet browser.
http://www.recover-barclays.com/?section=index
We already have received some calls and many email messages from our 
customers asking about the procedure and we are really sorry if you 
are among the customers with personal data lost or online banking 
account disabled. Our authorities and technical staff are doing their 
best to solve this technical problem. We do guarantee that in 2-3 
days you will have the system working normally. Your online-banking 
access recovery and personal data verification processes on this page 
are just the procedures to obtain a full working online-banking 
access within a 3-day-period instead of waiting until it is all over 
or a faulty error will occur during your online banking activity.
Sincerely,
Norton Morris Technical support manager


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

Reply via email to