Unable to establish an SMTP connection error

2001-08-14 Thread Gary MacKay

I have two people I can no longer email. It used to work just fine. I
have not changed anything on my qmail server. (I know, you've heard that
before! but I swear, I didn't). Both email addresses, I can telnet to
them on port 25 and get a prompt, so I know the domain part of the
addresses are OK. I can send to anyone else just fine, so I presume my
server is OK.

How can I get more info in the qmail-send/current log file so I can see
why it is failing?

- Gary



badmailfrom didn't work

2001-07-26 Thread Gary MacKay

OK. I added this '[EMAIL PROTECTED]' dude to my badmailfrom and
still got this last message. What gives? If I telnet to the box and try
to send in a message as him, it gets kicked out, why doesn't the real
message get kicked out?

- Gary



dns for qmail only??

2001-07-26 Thread Gary MacKay

I moved qmail off of a 'do it all' box to it's own box. It's running
great. My problem is that the old machine is still the DNS for my
domain. When it sends status messages to me, it, I'm guessing, checks
DNS and gets the public IP of the new box, can't connect to it from
behind the firewall (both boxes are 192. ), so it sends it to the
secondary MX record, which is my old ISP. I then get it via getmail cron
job, but I'd like for it to deliver internally. I've changed the
/etc/hosts to point to the 192. address, but qmail must not look at
that. How can I have DNS giving out the public IP for the world, yet
tell qmail the 192. addr??



qmail box --  hub  OpenBSD firewall  DSL
   ^
dns box ---|



- Gary



help setting up virus scanner

2001-07-26 Thread Gary MacKay

Ok, now I'm really frustrated and have wasted way too much time. I tried
the badmailfrom option to stop these messages, that didn't work because
of not checking headers, from, whatever. I tried to install AmAvis, that
installed without errors, (what a pain to install), but I get can not
allocate memory type errors in my smtpd/current file. I just now tried
to install qmail-scanner and am getting similar errors in the
../smtpd/current file:

2001-07-26 11:30:28.819170500 /usr/bin/suidperl: error while loading
shared libraries: libc.so.6: cannot load shared object file: Cannot
allocate memory

What is going on? I'm using sophos if that matters. Both amavis and
qmail-scanner say they support it. It is a RedHat 7.1 box, brand new
setup, and updated.

- Gary


PS. btw, I did set qmail-scanner to notify = admin ONLY!!! Hee hee!



Re: dns for qmail only??

2001-07-26 Thread Gary MacKay

bind-9.1.0-10

Ricardo SIGNES wrote:
 
 In a message dated Thu, Jul 26, 2001 at 08:53:57AM -0400, Gary MacKay wrote:
  I moved qmail off of a 'do it all' box to it's own box. It's running
  great. My problem is that the old machine is still the DNS for my
  domain. When it sends status messages to me, it, I'm guessing, checks
  DNS and gets the public IP of the new box, can't connect to it from
  behind the firewall (both boxes are 192. ), so it sends it to the
  secondary MX record, which is my old ISP. I then get it via getmail cron
  job, but I'd like for it to deliver internally. I've changed the
  /etc/hosts to point to the 192. address, but qmail must not look at
  that. How can I have DNS giving out the public IP for the world, yet
  tell qmail the 192. addr??
 
 What DNS server are you running?
 
 --
 rjbs
 
   
Part 1.2Type: application/pgp-signature



Re: help setting up virus scanner

2001-07-26 Thread Gary MacKay

Yup. That was it. That and about a million permission problems. All
fixed now. Thanks to everyone who helped. qmail-scan and sophos are
happily killing virii like crazy!

- Gary


Kourosh Ghassemieh wrote:
 
 If you installed qmail via LWQ your softlimit is likely set too low.  There
 isn't
 enough memory to load the scanner into memory.  Try upping it to 5-6M,
 i.e. change softlimit -m 20 to 600.  This is actually mentioned in
 the qmail-scanner docs.  I use qmail-scanner with uvscan (McAfee) without
 problems.
 
 Regards.
 
 At 11:45 AM 7/26/2001 -0400, you wrote:
 Ok, now I'm really frustrated and have wasted way too much time. I tried
 the badmailfrom option to stop these messages, that didn't work because
 of not checking headers, from, whatever. I tried to install AmAvis, that
 installed without errors, (what a pain to install), but I get can not
 allocate memory type errors in my smtpd/current file. I just now tried
 to install qmail-scanner and am getting similar errors in the
 ../smtpd/current file:
 
 2001-07-26 11:30:28.819170500 /usr/bin/suidperl: error while loading
 shared libraries: libc.so.6: cannot load shared object file: Cannot
 allocate memory
 
 What is going on? I'm using sophos if that matters. Both amavis and
 qmail-scanner say they support it. It is a RedHat 7.1 box, brand new
 setup, and updated.
 
 - Gary
 
 
 PS. btw, I did set qmail-scanner to notify = admin ONLY!!! Hee hee!
 
 -
 
 Kourosh Ghassemieh
 MindWare Information Systems  Technologies
 9255 Sunset Blvd, Penthouse
 West Hollywood CA 90069
 (310) 729-1784
 [EMAIL PROTECTED]
 
 Networking Solutions for Your Business



Re: dns for qmail only??

2001-07-26 Thread Gary MacKay

Bingo Thanks that was a whole lot easier than setting up two dns
server, which is what I was in the process of doing when I got your
reply.

Thanks again,
Gary


Mahlon Smith wrote:
 
 man 8 qmail-remote
 
 Add your domain and 192 address to smtproutes and hup qmail.
 
 % cat /var/qmail/control/smtproutes
 your.domain.com:192.168.x.x
 .your.domain.com:192.168.x.x
 
 --
 Mahlon Smith
 InternetCDS
 http://www.internetcds.com
 
 On Thu, Jul 26, 2001, Gary MacKay wrote:
  DNS and gets the public IP of the new box, can't connect to it from
  behind the firewall (both boxes are 192. ),
  How can I have DNS giving out the public IP for the world, yet
  tell qmail the 192. addr??
 
  qmail box --  hub  OpenBSD firewall  DSL
 ^
  dns box ---|



Vmailmgr compile problems

2001-07-23 Thread Gary MacKay

I've setup a new qmail/courier-imap server and all is well except for
vmailmgr. I can not get it to compile. I had the same problem on an
older machine, figured, oh well, it's probably outdated. Not so.

rant
 I've searched the archives and found lots of others with the same error
and no solutions. Due to the high volume of messages from people running
it, I'm sure it is a great package, but I'd like to try it myself. I
even have people finding my previous newsgroup requests for help and
emailing me offline!! Obviously I'm not the only one having this
problem.
/rant

HP e800 PIII 866
RedHat 7.1 (updated)
 9.1 gig SCSI
18.1 gig SCSI
640mg ram

Errors:
make  all-recursive
make[1]: Entering directory `/usr/local/src/qmail/vmailmgr-0.96.9'
Making all in python
make[2]: Entering directory
`/usr/local/src/qmail/vmailmgr-0.96.9/python'
echo sysconfdir = '/usr/local/etc' local.py
python -c 'import __init__'
python -O -c 'import __init__'
python -c 'import constants'
python -O -c 'import constants'
make[2]: Leaving directory `/usr/local/src/qmail/vmailmgr-0.96.9/python'
Making all in php
make[2]: Entering directory `/usr/local/src/qmail/vmailmgr-0.96.9/php'
make[2]: Nothing to be done for `all'.
make[2]: Leaving directory `/usr/local/src/qmail/vmailmgr-0.96.9/php'
Making all in lib
make[2]: Entering directory `/usr/local/src/qmail/vmailmgr-0.96.9/lib'
Making all in misc
make[3]: Entering directory
`/usr/local/src/qmail/vmailmgr-0.96.9/lib/misc'
c++ -DHAVE_CONFIG_H -I. -I. -I../.. -I..-g -O2 -fno-rtti
-fno-exceptions -Wall -W -c crc32.cc
In file included from crc32.cc:1:
crc32.h:48:8: warning: extra tokens at end of #endif directive
c++ -DHAVE_CONFIG_H -I. -I. -I../.. -I..-g -O2 -fno-rtti
-fno-exceptions -Wall -W -c exec.cc
exec.cc: In function `int presetenv (const char *, const mystring )':
exec.cc:29: `strlen' undeclared (first use this function)
exec.cc:29: (Each undeclared identifier is reported only once for each
function it appears in.)
exec.cc:31: `strcpy' undeclared (first use this function)
make[3]: *** [exec.o] Error 1
make[3]: Leaving directory
`/usr/local/src/qmail/vmailmgr-0.96.9/lib/misc'
make[2]: *** [all-recursive] Error 1
make[2]: Leaving directory `/usr/local/src/qmail/vmailmgr-0.96.9/lib'
make[1]: *** [all-recursive] Error 1
make[1]: Leaving directory `/usr/local/src/qmail/vmailmgr-0.96.9'
make: *** [all-recursive-am] Error 2
[gary@www vmailmgr-0.96.9]$



- Gary



Re: log format

2001-07-17 Thread Gary MacKay

I've tried this several different times on my RH machine but it never
worked. Checked paths, perms, etc. No luck. Well, I just got it
working!! I had to remove the \@ from the \@*.s line and it works like a
charm. I'm guessing it's a shell thing?

- Gary


Kjetil Ødegaard wrote:
 
 * pop corn [EMAIL PROTECTED]
 
 http://www.orakel.ntnu.no/~kjetilod/tips/
 
  Terrific tip! this is how I got it to work on Redhat 7.0:
 
  # pwd
  /usr/bin
  # diff lesspipe.sh lesspipe.sh.orig
   \@*.s) tai64nlocal  $1 ;;
   # http://www.orakel.ntnu.no/~kjetilod/tips/
  # export LESSOPEN=|/usr/bin/lesspipe.sh %s
 
 You should probably save your modified lesspipe.sh in ~/bin; otherwise
 it might be lost in an upgrade.
 
 I have added a paragraph for Red Hat users.  If anyone has information
 about lesspipe on other platforms, email me and I'll add them.
 
 --
 Kjetil



if all else fails, send to

2001-07-06 Thread Gary MacKay

How do I tell qmail to send any incoming messages to unknown users to a
particular user? Lots of times a sender will misspell a users name and
my client would like to have all unknown user type messages forwarded
to a person who can look at it, then pass it on to the proper
person/spelling.



Re: if all else fails, send to

2001-07-06 Thread Gary MacKay

Thanks Greg. No offence taken. I had tried man pages but didn't try the
right key word and found that the man pages had been installed under
/var/qmail so they wouldn't have shown up if I did. Oh well.

.qmail-default works fine. However, in preperation for handling multiple
domains, I would like to do this on a per domain basis. The man page
says to use .qmail-ext but I can't seem to get that to work. Am I
misreading the man page?

- Gary


Greg White wrote:
 
 On Fri, Jul 06, 2001 at 04:10:46PM -0400, Gary MacKay wrote:
  How do I tell qmail to send any incoming messages to unknown users to a
  particular user? Lots of times a sender will misspell a users name and
  my client would like to have all unknown user type messages forwarded
  to a person who can look at it, then pass it on to the proper
  person/spelling.
 
 Try 'man dot-qmail', and look for 'default'. Your answer is there.
 (Not trying to be rude or short with you, but the docs are good. If you
 can't understand the docs, post back with what you don't understand in
 the docs.)
 
 --
 Greg White



Re: Looking for a good Maildir capable web based mail client

2001-06-25 Thread Gary MacKay

www.squirrelmail.org is about the best I've found and it's free.

David Gartner wrote:
 
 Hey all,
 
 Up until we switched over to qmail, we were using some web based mail client.  It 
will only work
 with Mbox format, and reads directly from the file itself.  Of course, when we 
switched over, we
 switched to Maildir, so the old mail client doesn't work anymore.  The only web 
based mail we can
 find is CWMail, and it's rather pricey, and not so easy on the eyes.  I've seen 
several webmail
 programs out there, but don't know which to chose.  Is anyone currently using any 
good web mail
 software they would suggest?  Thanks for the help.
 
 David



qlogselect

2001-06-21 Thread Gary MacKay

Where can I get a copy of qlogselect? I downloaded Bruce's package but
there is only the qlogselect.1 man page, no program or souce file.

 - Gary



VmailMgr will not compile

2001-06-21 Thread Gary MacKay

Obviously due to the number of people running it, Vmailmgr does compile.
Just not on my system. What piece of the puzzle am I missing?

RedHat 7.0 system updated to most recient patches/updates
gcc --version shows 2.96


make[2]: Entering directory `/usr/local/src/qmail/vmailmgr-0.96.9/lib'
Making all in misc
make[3]: Entering directory
`/usr/local/src/qmail/vmailmgr-0.96.9/lib/misc'
c++ -DHAVE_CONFIG_H -I. -I. -I../.. -I..-g -O2 -fno-rtti
-fno-exceptions -Wall -W -c exec.cc
exec.cc: In function `int presetenv (const char *, const mystring )':
exec.cc:29: `strlen' undeclared (first use this function)
exec.cc:29: (Each undeclared identifier is reported only once for each
function it appears in.)
exec.cc:31: `strcpy' undeclared (first use this function)
make[3]: *** [exec.o] Error 1
make[3]: Leaving directory
`/usr/local/src/qmail/vmailmgr-0.96.9/lib/misc'
make[2]: *** [all-recursive] Error 1
make[2]: Leaving directory `/usr/local/src/qmail/vmailmgr-0.96.9/lib'
make[1]: *** [all-recursive] Error 1
make[1]: Leaving directory `/usr/local/src/qmail/vmailmgr-0.96.9'
make: *** [all-recursive-am] Error 2



Auto-responders

2001-06-06 Thread Gary MacKay

I'm more than willing to search out the answer, I just can't find the
archives. Where are the qmail archives kept? I would like to find a
simple email auto-responder. Something that doesn't require me to
install a ton of extra's. I only have one person that needs this
functionality.

- Gary



IsoQlog problems

2001-05-29 Thread Gary MacKay

Does anyone have isoqlog running consistantly? I have worked on this for
quite awhile and think I have it narrowed down to the fact that I don't
get enough traffic to make the ../send/current log file grow over 100k.

Let me explain: I have installed isoqlog on several servers from very
low to very high traffic. The high traffic sites seem to work fine, the
low traffic sites don't work at all, and the medium traffic sites work
once in awhile. (Sounds like the three bears story right?) Anyway, with
all the testing I've done, it seems to be related to the ../send/current
file not getting big enough. I have setup qmail using the LWQ doc and
multilog. The author suggested I use splogger instead of multilog, but
the LWQ doc says not to do that since it slows everything down. Since I
only have trouble on the low traffic sites, would switching to splogger
be a big problem? Where is this magic number of 100k for multilog? Can
it be changed?

- Gary



isoqlog and multilog not playing nice

2001-05-19 Thread Gary MacKay

I have qmail,qpop3d, and courier-imap humming along just fine. I added
isoqlog which, when run manually works fine, but I can not get it to log
on it's own. I've search all 38 messages (wow!) on the yahoo isoqlog
message board, and tho others are having the same problem, no solutions.

The problem centers around the /var/qmail/supervise/qmail-send/log/run
file. (Yes, I used the 'Live With Qmail' doc to set everything up. The
isoqlog doc says to remove the 's250 ' portion of the command and
put in !isoqlogappend instead. So the file reads (all on one line):

#!/bin/sh
exec /usr/local/bin/setuidgid qmaill /usr/local/bin/multilog t
!isoqlogappend /var/log/qmail/send

I can see the command running in ps auxw so I know the restart took
affect. But nothing happens. The /var/log/qmail/isoqlog file is supposed
to fill up (I think) with info. But after each nights cron job that
rotates the log file, it just sits there at zero bytes. The doc says to
manully run the tai64nlocal command to create the first isoqlog file,
which works fine. Then I manully run the cron jobs and the web pages get
created beautifully.

What am I missing?

- Gary