Hello,
Did you recieve my email from last week? I'm happy to tell you
that you are approved for a home loan with a 2.78% rate.
Your tracking number is # Q9 729 636
You must visit the link below in 24 hrs to confirm your details.
http://bsch.easy-lender.com/a1/jj.php?v2l=49
Best Regards,
ScanMail for Microsoft Exchange took action on the message. The message
details were:
Sender = [EMAIL PROTECTED]
Recipient(s) = [EMAIL PROTECTED];
Subject = Re: Your letter
Scanning time = 07/07/2004 08:19:23
Engine/Pattern = 7.000-1004/929
Action taken on message:
The attachment
Your message dated Wed, 07 Jul 2004 05:41:39 -0400
with message-id [EMAIL PROTECTED]
and subject line Bug#248038: fixed in apache2 2.0.50-1
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 message dated Wed, 07 Jul 2004 05:41:39 -0400
with message-id [EMAIL PROTECTED]
and subject line Bug#242169: fixed in apache2 2.0.50-1
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 message dated Wed, 07 Jul 2004 05:41:39 -0400
with message-id [EMAIL PROTECTED]
and subject line Bug#234955: fixed in apache2 2.0.50-1
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 message dated Wed, 07 Jul 2004 05:41:39 -0400
with message-id [EMAIL PROTECTED]
and subject line Bug#234489: fixed in apache2 2.0.50-1
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 message dated Wed, 07 Jul 2004 05:41:39 -0400
with message-id [EMAIL PROTECTED]
and subject line Bug#234591: fixed in apache2 2.0.50-1
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 message dated Wed, 07 Jul 2004 05:41:39 -0400
with message-id [EMAIL PROTECTED]
and subject line Bug#231665: fixed in apache2 2.0.50-1
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 message dated Wed, 07 Jul 2004 05:41:39 -0400
with message-id [EMAIL PROTECTED]
and subject line Bug#208569: fixed in apache2 2.0.50-1
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 message dated Wed, 07 Jul 2004 05:41:39 -0400
with message-id [EMAIL PROTECTED]
and subject line Bug#231147: fixed in apache2 2.0.50-1
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 message dated Wed, 07 Jul 2004 05:41:39 -0400
with message-id [EMAIL PROTECTED]
and subject line Bug#242351: fixed in apache2 2.0.50-1
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 message dated Wed, 07 Jul 2004 05:41:39 -0400
with message-id [EMAIL PROTECTED]
and subject line Bug#246139: fixed in apache2 2.0.50-1
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 message dated Wed, 07 Jul 2004 05:41:39 -0400
with message-id [EMAIL PROTECTED]
and subject line Bug#245488: fixed in apache2 2.0.50-1
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 message dated Wed, 07 Jul 2004 05:41:39 -0400
with message-id [EMAIL PROTECTED]
and subject line Bug#246134: fixed in apache2 2.0.50-1
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 message dated Wed, 07 Jul 2004 05:41:39 -0400
with message-id [EMAIL PROTECTED]
and subject line Bug#251102: fixed in apache2 2.0.50-1
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
Accepted:
apache2-common_2.0.50-1_sparc.deb
to pool/main/a/apache2/apache2-common_2.0.50-1_sparc.deb
apache2-doc_2.0.50-1_all.deb
to pool/main/a/apache2/apache2-doc_2.0.50-1_all.deb
apache2-mpm-perchild_2.0.50-1_sparc.deb
to pool/main/a/apache2/apache2-mpm-perchild_2.0.50-1_sparc.deb
Final Notice!We have tried
to contact you 2 times, with no success. Your lo
an has been appr\oved at 3.o %, but we need more
information from you. This will only take a
second, then a
representative will contact you.
secure
link for AppID 54006
Thanks
Jay Dill
sltbwrme juhlrihx vfhlv vgjyex
Your message dated Wed, 7 Jul 2004 16:03:17 +0200 (CEST)
with message-id [EMAIL PROTECTED]
and subject line Bug#258071: debian-policy: request for virtual package 'apache'
has caused the attached Bug report to be marked as done.
This means that you claim that the problem has been dealt with.
If
Your message dated Wed, 7 Jul 2004 15:38:46 +0100
with message-id [EMAIL PROTECTED]
and subject line see 258068
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
On Wed, Jul 07, 2004 at 09:00:52AM -0500, John Goerzen wrote:
On Wed, Jul 07, 2004 at 09:43:52AM -0400, Brian Minton wrote:
Aren't apache-ssl and apache-perl obsolete by now? That is, someone
could:
apt-get install apache libapache-mod-perl libapache-mod-ssl
and get the same functionality?
Package: apache
Version: 1.3.31-2
While upgrading:
Setting up apache (1.3.31-2) ...
Starting web server: apache failed
invoke-rc.d: initscript apache, action start failed.
dpkg: error processing apache (--configure):
I needed to stop apache before update to make it install.
On Wed, 7 Jul 2004, Rafi Rubin wrote:
Package: apache
Version: 1.3.31-2
While upgrading:
Setting up apache (1.3.31-2) ...
Starting web server: apache failed
invoke-rc.d: initscript apache, action start failed.
dpkg: error processing apache (--configure):
I needed to stop apache before
Yes it is set to start on boot. Unfortunately I don't know what version
had been running.
Rafi
On Wed, 7 Jul 2004, Fabio Massimo Di Nitto wrote:
On Wed, 7 Jul 2004, Rafi Rubin wrote:
Package: apache
Version: 1.3.31-2
While upgrading:
Setting up apache (1.3.31-2) ...
Starting web
Package: apache2-common
Version: 2.0.50-1
Severity: important
apache2-common.postinst contains an unconditional call to
a2enmod userdir
, which is prone to failure for various reasons. The main problem is
that it is not idempotent, as a2enmod exits with status 1 if the
module is already
Package: apache2-common
Version: 2.0.50-1
Severity: normal
Installing new version of config file /etc/init.d/apache2 ...
ln: `/etc/apache2/mods-enabled/userdir.conf': File exists
dpkg: error processing apache2-common (--configure):
I think you just need '2/dev/null || true'.
-- System
Processing commands for [EMAIL PROTECTED]:
reassign 258071 apache
Bug#258071: debian-policy: request for virtual package 'apache'
Bug reassigned from package `debian-policy' to `apache'.
thanks
Stopping processing here.
Please contact me if you need assistance.
Debian bug tracking system
26 matches
Mail list logo
