Re: [vchkpw] Re: qmail+vpopmail on redhat 7.3 server gets very busy

2005-11-08 Thread Sam

I changed root /var/spool/cron/
to
/home/vpopmail/bin/clearopensmtp 21 /dev/null


Do you still get the error message? If you are still getting the same
error message, maybe you need to restart the cron service for the
changes to be effective.


No more error messages.
Thank you All,
Sam


Re: [vchkpw] Re: qmail+vpopmail on redhat 7.3 server gets very busy

2005-11-07 Thread Sam

Cron [EMAIL PROTECTED] /home/vpopmail/bin/clearopensmtp 2$1  /dev/null



Body: /bin/sh: $1: ambiguous redirect



How can I fix this error in redirect?



change the 2$1 to 21, as it should be.


How do you edit clearopensmtp to change the 2$1 to 21 ?


man sh will explain this in more detail.


man sh is not working.  How to tell  the man command where to look to 


find man pages fro sh?

Thanks a lot,

Sam







Re: [vchkpw] Re: qmail+vpopmail on redhat 7.3 server gets very busy

2005-11-07 Thread Alberto Brealey Guzmán
Sam wrote:
 Cron [EMAIL PROTECTED] /home/vpopmail/bin/clearopensmtp 2$1  /dev/null
 Body: /bin/sh: $1: ambiguous redirect
 How can I fix this error in redirect?
 change the 2$1 to 21, as it should be.
 How do you edit clearopensmtp to change the 2$1 to 21 ?

probably by running 'crontab -e' as root: the redirect is not in the
clearopensmtp command, but in the command that the cronjob is running.
Actually, replace the command run by cron with:

/home/vpopmail/bin/clearopensmtp 21 /dev/null

since the one that is running in your server is missing the redirect
from STDOUT to /dev/null.

 man sh will explain this in more detail.
 man sh is not working.  How to tell  the man command where to look to 
 find man pages fro sh?

with the MANPATH env variable, but the 'sh' manpage should be there..
what OS are you running? What error do you get when you run 'man sh'?

hope this helps,

-- 
Alberto Brealey Guzmán
[EMAIL PROTECTED]


Re: [vchkpw] Re: qmail+vpopmail on redhat 7.3 server gets very busy

2005-11-07 Thread Sam

I changed root /var/spool/cron/
to
/home/vpopmail/bin/clearopensmtp 21 /dev/null

I am using redhat 7.3 and I get:
No manual entry for sh
When I run the command:
man sh

Thanks,
Sam

- Original Message - 
From: Alberto Brealey Guzmán [EMAIL PROTECTED]

To: vchkpw@inter7.com
Sent: Monday, November 07, 2005 11:18 AM
Subject: Re: [vchkpw] Re: qmail+vpopmail on redhat 7.3 server gets very busy



Sam wrote:

Cron [EMAIL PROTECTED] /home/vpopmail/bin/clearopensmtp 2$1  /dev/null
Body: /bin/sh: $1: ambiguous redirect
How can I fix this error in redirect?
change the 2$1 to 21, as it should be.
How do you edit clearopensmtp to change the 2$1 to 21 ?


probably by running 'crontab -e' as root: the redirect is not in the
clearopensmtp command, but in the command that the cronjob is running.
Actually, replace the command run by cron with:

   /home/vpopmail/bin/clearopensmtp 21 /dev/null

since the one that is running in your server is missing the redirect
from STDOUT to /dev/null.


man sh will explain this in more detail.
man sh is not working.  How to tell  the man command where to look to
find man pages fro sh?


with the MANPATH env variable, but the 'sh' manpage should be there..
what OS are you running? What error do you get when you run 'man sh'?

hope this helps,

--
Alberto Brealey Guzmán
[EMAIL PROTECTED] 




Re: [vchkpw] Re: qmail+vpopmail on redhat 7.3 server gets very busy

2005-11-07 Thread Alberto Brealey Guzmán
Sam wrote:
 I changed root /var/spool/cron/
 to
 /home/vpopmail/bin/clearopensmtp 21 /dev/null

Do you still get the error message? If you are still getting the same
error message, maybe you need to restart the cron service for the
changes to be effective.

 I am using redhat 7.3 and I get:
 No manual entry for sh
 When I run the command:
 man sh

perhaps you need to install a -doc package... I haven't used Red Hat in
a long long time :) Or, if you are using bash, then do a 'man bash'
instead, or 'man csh' if that's the shell you are using for root.


-- 
Alberto Brealey Guzmán
[EMAIL PROTECTED]


Re: [vchkpw] Re: qmail+vpopmail on redhat 7.3 server gets very busy

2005-11-06 Thread Shane Chrisp
On Sat, 2005-11-05 at 19:04 -0500, Sam wrote:
 Adrew,
 
 This is what I typed:
 echo # /var/qmail/alias/.qmail-doublebounce
 Just curious to know why it didn't create the .qmail-doublebounce file with 
 # in the file.

Because you should have typed

echo # /var/qmail/alias/.qmail-doublebounce

Everything after the # would have been eval'd as a comment.

Shane



Re: [vchkpw] Re: qmail+vpopmail on redhat 7.3 server gets very busy

2005-11-06 Thread Bob Hutchinson
On Sunday 06 Nov 2005 00:04, Sam wrote:
 Adrew,

 This is what I typed:
 echo # /var/qmail/alias/.qmail-doublebounce
 Just curious to know why it didn't create the .qmail-doublebounce file with
 # in the file.

echo # /var/qmail/alias/.qmail-doublebounce
works

echo # /var/qmail/alias/.qmail-doublebounce
does not


 Sam

 - Original Message -
 From: Andrew Hodgson [EMAIL PROTECTED]
 To: vchkpw@inter7.com
 Sent: Saturday, November 05, 2005 6:43 AM
 Subject: [vchkpw] Re: qmail+vpopmail on redhat 7.3 server gets very busy

  On Fri, 4 Nov 2005 22:30:03 -0500, in gmane.mail.vpopmail you wrote:
 Hi,
 
 The command
 #Echo doublebounce /var/qmail/control/doublebounceto
 worked.
 As for the second command
 #echo # /var/qmail/alias/.qmail-doublebounce
 Nothing happened. I do not know why, but I installed it
 using
 #touch .qmail-doublebounce
 then I put# and saved.
 
  I did wonder whether that command would work - it didn't seem right
  when I wrote it.  I may have had to escape the # character or
  something.  I take it you didn't copy the # character at the beginning
  - if you left this in it would have made a comment and would not be
  processed.
 
  Andrew.

-- 
-
Bob Hutchinson
Midwales dot com
-


Re: [vchkpw] Re: qmail+vpopmail on redhat 7.3 server gets very busy

2005-11-06 Thread Sam

Thank you All for your help.

Now that my server is up and running,
two last questions:

1- I know that a bad address causes the email to bounce, but what is a
doublebounce exactly?

2- Every hour I get a message:
   from:   Cron Daemon
  To:   root
   Subject: Cron [EMAIL PROTECTED] /home/vpopmail/bin/clearopensmtp 2$1  
/dev/null


   Body: /bin/sh: $1: ambiguous redirect

  How can I fix this error in redirect?
Thanks again,

Sam 



Re: [vchkpw] Re: qmail+vpopmail on redhat 7.3 server gets very busy

2005-11-06 Thread John Simpson

On 2005-11-06, at 1933, Sam wrote:


Now that my server is up and running,
two last questions:

1- I know that a bad address causes the email to bounce, but what is a
doublebounce exactly?


let's say a message arrives, addressed to a userid on your system  
which doesn't exist. that message will bounce, because the recipient  
mailbox doesn't exist.


now let's say that message was spam, and the Return-Path header in  
the message contained a forged address, and when qmail tries to  
deliver the bounce message, it is unable to do so. this is a  
doublebounce.


an interesting case is if the doublebounce message cannot be  
delivered, because your /var/qmail/control/doublebounceto or /var/ 
qmail/control/doublebouncehost files are wrong (or they don't exist,  
and your postmaster alias isn't working.) this is known as a  
triplebounce. qmail handles triplebounces by dropping the message  
from the queue entirely.


the man page for qmail-send explains the doublebounceto and  
doublebouncehost control files. if man qmail-send doesn't work on  
your system, add the line MANPATH /var/qmail/man to your /etc/ 
man.config file so that the man command will know to look there to  
find man pages.



2- Every hour I get a message:
   from:   Cron Daemon
  To:   root
   Subject: Cron [EMAIL PROTECTED] /home/vpopmail/bin/clearopensmtp 2$1  
 /dev/null


   Body: /bin/sh: $1: ambiguous redirect

  How can I fix this error in redirect?


change the 2$1 to 21, as it should be.

you will see the construct 21 in a lot of shell scripts- it means  
that whatever command is running with that modifier, the standard  
error channel (i.e. 2) is added in with the standard out channel  
(i.e. 1). in scripts run from cron, this prevents you from receiving  
an extra email with the error output.


man sh will explain this in more detail.

--
| John M. Simpson - KG4ZOW - Programmer At Large |
| http://www.jms1.net/   [EMAIL PROTECTED] |
--
| Mac OS X proves that it's easier to make UNIX  |
| pretty than it is to make Windows secure.  |
--




PGP.sig
Description: This is a digitally signed message part


[vchkpw] Re: qmail+vpopmail on redhat 7.3 server gets very busy

2005-11-05 Thread Andrew Hodgson
On Fri, 4 Nov 2005 22:30:03 -0500, in gmane.mail.vpopmail you wrote:

Hi,

The command
#Echo doublebounce /var/qmail/control/doublebounceto
worked.
As for the second command
#echo # /var/qmail/alias/.qmail-doublebounce
Nothing happened. I do not know why, but I installed it
using
#touch .qmail-doublebounce
then I put# and saved.

I did wonder whether that command would work - it didn't seem right
when I wrote it.  I may have had to escape the # character or
something.  I take it you didn't copy the # character at the beginning
- if you left this in it would have made a comment and would not be
processed.

Andrew.


Re: [vchkpw] Re: qmail+vpopmail on redhat 7.3 server gets very busy

2005-11-05 Thread Sam

Adrew,

This is what I typed:
echo # /var/qmail/alias/.qmail-doublebounce
Just curious to know why it didn't create the .qmail-doublebounce file with 
# in the file.


Sam

- Original Message - 
From: Andrew Hodgson [EMAIL PROTECTED]

To: vchkpw@inter7.com
Sent: Saturday, November 05, 2005 6:43 AM
Subject: [vchkpw] Re: qmail+vpopmail on redhat 7.3 server gets very busy



On Fri, 4 Nov 2005 22:30:03 -0500, in gmane.mail.vpopmail you wrote:


Hi,

The command
#Echo doublebounce /var/qmail/control/doublebounceto
worked.
As for the second command
#echo # /var/qmail/alias/.qmail-doublebounce
Nothing happened. I do not know why, but I installed it
using
#touch .qmail-doublebounce
then I put# and saved.


I did wonder whether that command would work - it didn't seem right
when I wrote it.  I may have had to escape the # character or
something.  I take it you didn't copy the # character at the beginning
- if you left this in it would have made a comment and would not be
processed.

Andrew.