i think there is no necessary to go to a lawer!
- Original Message -
From: Uwe Ohse <[EMAIL PROTECTED]>
To: dick <[EMAIL PROTECTED]>
Cc: <[EMAIL PROTECTED]>
Sent: Thursday, February 08, 2001 12:22 AM
Subject: Re: thanks for you answer my question!but it is none used.
> On
]
Subject: Re: problem qmail
On Thu, Jul 20, 2000 at 08:53:35AM +1000, Noel Mistula wrote:
> Someone is sending a KAK worm on this list.
> There are only two possibilities why this happens.
> 1. Intentional to ruin this list.
> 2. The sender is a stupid idiot.
>
> Please filter
What?? a lose the ability to replicate worms??? hahahahahaha
You could turn off scripting for your mail client. or crank up the
security settings.
Paul Farber
Farber Technology
[EMAIL PROTECTED]
Ph 570-628-5303
Fax 570-628-5545
On Wed, 19 Jul 2000, Ben Beuchler wrote:
> On Thu, Jul 20,
On Thu, Jul 20, 2000 at 08:53:35AM +1000, Noel Mistula wrote:
> Someone is sending a KAK worm on this list.
> There are only two possibilities why this happens.
> 1. Intentional to ruin this list.
> 2. The sender is a stupid idiot.
>
> Please filter out those postings that uses HTML formatin
Noel Mistula
-Original Message-
From: Agus Hariadi <[EMAIL PROTECTED]>
To: [EMAIL PROTECTED] <[EMAIL PROTECTED]>
Date: Thursday, 20 July 2000 5:25
Subject: problem qmail
Hi,
I was found error when start qmail the message is
Jul 19 18:43:27 freebsd qmail: 964032207.134614 a
Hi,
I was found error when start qmail the message
is
Jul 19 18:43:27 freebsd qmail: 964032207.134614
alert: cannot start: hath the daemon spawn no fire?
what going on ?
help me
Petr Novotny wrote:
>
>
> On 21 Dec 99, at 20:27, Michael Neubert wrote:
> > pop3 stream tcp nowait root /var/qmail/bin/qmail-popup qmail-popup
> > michael.neubert.de /bin/checkpassword /var/qmail/bin/qmail-pop3d
> > /home/$USER/.mailspool/
>
> Will not work. At the moment inetd is reading the
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 21 Dec 99, at 20:36, bert hubert wrote:
> You probably have shadow passwords. These cannot be read by any user but
> root. This means that checkpassword needs to be 'set user id root', suid
> root for short. Try this:
>
> chown root:root /bin/chec
On Tue, Dec 21, 1999 at 08:40:06PM +0100, bert hubert wrote:
> On Tue, Dec 21, 1999 at 08:36:07PM +0100, bert hubert wrote:
>
> > You probably have shadow passwords. These cannot be read by any user but
> > root. This means that checkpassword needs to be 'set user id root', suid
> > root for shor
On Tue, Dec 21, 1999 at 08:36:07PM +0100, bert hubert wrote:
> You probably have shadow passwords. These cannot be read by any user but
> root. This means that checkpassword needs to be 'set user id root', suid
> root for short. Try this:
>
> chown root:root /bin/checkpassword
> chmod +s /bin/ch
On Tue, Dec 21, 1999 at 08:27:05PM +0100, Michael Neubert wrote:
> I'm an newbie to qmail (and also linux) and hope to find help.
You've come to the right place.
> michael:~ # /var/qmail/bin/qmail-popup host /bin/checkpassword pwd
> +OK <548.945710015@host>
> user linux
> +OK
> pass 12345
> /ho
I'm an newbie to qmail (and also linux) and hope to find help.
After setting up qmail on SuSE-Linux 6.1 I found a problem with my
pop3-server.
When contacting the pop3-server the messages "authorization failed"
appears. I start the pop3-server in /etc/inetd.conf with this line:
pop3 stream tcp
"Warren 'Llama' Ernst" <[EMAIL PROTECTED]> wrote:
>So I'm installing qmail on my RedHat 6 distrubution a la the "Life with
>qmail" document, and its going great (I've been doing a little each day all
>week) until section 2.8.2 when I am suppposed to type "/usr/local/sbin/qmail
>cdb"
>
>Well, I do
Warren 'Llama' Ernst wrote:
> All,
>
> So I'm installing qmail on my RedHat 6 distrubution a la the "Life with
> qmail" document, and its going great (I've been doing a little each day all
> week) until section 2.8.2 when I am suppposed to type "/usr/local/sbin/qmail
> cdb"
>
> Well, I do this, a
"Bryan J. Ischo" wrote:
> Warr,
>
> Check the top line of the qmail file. It will name a program to be run
> to process the qmail script. Check to make sure that this program
> exists on your
> system and is runnable.
>
> For example, if the program is named as:
>
> #!/bin/sh
>
> Make sure t
Warren 'Llama' Ernst wrote:
>
> All,
>
> So I'm installing qmail on my RedHat 6 distrubution a la the "Life with
> qmail" document, and its going great (I've been doing a little each day all
> week) until section 2.8.2 when I am suppposed to type "/usr/local/sbin/qmail
> cdb"
>
> Well, I do thi
All,
So I'm installing qmail on my RedHat 6 distrubution a la the "Life with
qmail" document, and its going great (I've been doing a little each day all
week) until section 2.8.2 when I am suppposed to type "/usr/local/sbin/qmail
cdb"
Well, I do this, and I get "bash: /usr/local/sbin/qmail: No s
On Mon, 15 Feb 1999, Dileep Agrawal wrote:
>
> SMTP server said:
>
> 451 put, E=\r\n at the end of Mether, Mtcp, or Msmtp in sendmail.cf if you
> are using Solaris 2.5 (fixed in 2.5). I cannot accept messages with stray
> newlines
The mention of sendmail.cf might be a hint that the problem
Dileep Agrawal writes:
> It does not happen with Eudora 3.0. Does Eudora put in stray newlines? Is
Yes. Eudora 4.0 is broken.
> there a fix?
Ask Qualcomm. There's a patch on www.qmail.org that makes Qmail equally
broken as Eudora, thus letting it tolerate most of Eudora's nonsense.
--
Sa
Some of my customers using Eudora 4.0 are having problems using qmail for
relaying (SMTP server). They get this error message:
SMTP server said:
451 put, E=\r\n at the end of Mether, Mtcp, or Msmtp in sendmail.cf if you
are using Solaris 2.5 (fixed in 2.5). I cannot accept messages with stray
20 matches
Mail list logo
