qmail Digest 4 Jul 2000 10:00:00 -0000 Issue 1052
Topics (messages 44089 through 44153):
Re: manpages for ucspi-tcp
44089 by: Gerrit Pape
44092 by: Magnus Bodin
44103 by: Gerrit Pape
Re: ucspi-tcp man pages
44090 by: Gerrit Pape
44096 by: William E. Baxter
44104 by: Paul Farber
Re: Where is sqwebmail in courier-imap?
44091 by: Gabriel Ambuehl
Re: rblsmtp compilation error
44093 by: schinder.leprss.gsfc.nasa.gov
44098 by: Peter Green
44118 by: Todd A. Jacobs
PROBLEM WITH QMAIL-POP3D
44094 by: Giuliano Cocchi
smtpd/run
44095 by: Eddie Greer
44111 by: Eddie Greer
44112 by: Paul Jarc
qmail returns failure notices when local2remote
44097 by: Karl Voit
44135 by: Karl Voit
44149 by: wolfgang zeikat
QMAIL delivery delay problem
44099 by: Peter Mitev
Re: The most secure POP server
44100 by: Scott Gifford
44102 by: Gabriel Ambuehl
44109 by: Scott Gifford
44114 by: Joe Kelsey
44116 by: clemensF
44125 by: Scott Gifford
Re: Limit email file seize for some users
44101 by: qmail.col7.metta.lk
ucspi / rblsmtpd docs?
44105 by: Paul Farber
44106 by: Adam McKenna
44107 by: Gerrit Pape
44108 by: Paul Farber
tcpserver & alpha linux problems
44110 by: Hubbard, David
qmail-qread -- "bouncing"
44113 by: Ben Beuchler
tcprules, rcpthost, ip address problem
44115 by: Barry Dwyer
44121 by: Paul Jarc
44127 by: Christopher Tolley
44128 by: Adam McKenna
44129 by: Adam McKenna
44132 by: Barry Dwyer
44133 by: wolfgang zeikat
44134 by: Adam McKenna
44136 by: Barry Dwyer
44137 by: Barry Dwyer
44138 by: Barry Dwyer
44139 by: asantos
44146 by: ertan payci
44147 by: Giuliano Cocchi
44148 by: Adam McKenna
44152 by: Adam McKenna
FOLLOWUP: Can send, but not retrieve mail
44117 by: Lou Hevly
Not receiving from all domains - is it DNS?
44119 by: Barry Dwyer
rblsmtpd
44120 by: Paul Farber
qmail/rblsmtpd error
44122 by: Todd A. Jacobs
remote 2 local problem
44123 by: John L. Fjellstad
44124 by: John L. Fjellstad
Trashed queue
44126 by: Darren Beale
44130 by: Darren Beale
44131 by: Darren Beale
what are qmail-clean commands?
44140 by: Wayne Chu
44141 by: Ronny Haryanto
IMAP Problem
44142 by: Iman Budi Setiawan
44143 by: Kimberly Vher
Moving vpopmail users
44144 by: Charles Boening
My qmail can not receive email
44145 by: Iman Budi Setiawan
44151 by: Steffan Hoeke
qmail and dial-on-demand
44150 by: cgreen.matthaak.com
Re: limit to RCPT TO
44153 by: Claus F�rber
Administrivia:
To unsubscribe from the digest, e-mail:
[EMAIL PROTECTED]
To subscribe to the digest, e-mail:
[EMAIL PROTECTED]
To bug my human owner, e-mail:
[EMAIL PROTECTED]
To post to the list, e-mail:
[EMAIL PROTECTED]
----------------------------------------------------------------------
On Wed, Jun 28, 2000 at 11:10:59PM -0600, Vincent Danen wrote:
> Before I make some unecessary work for myself, I was wondering two
> things:
>
> Are there manpages for ucspi-tcp 0.88 somewhere? None are in the
> package. Also, is there a html2man program or something I can use to
> make this easier?
>
I did manpages from the contents of the html-pages some time ago. You find
them in: ftp://innominate.org/pub/pape/djb/ .
Gerrit.
--
[EMAIL PROTECTED]
innominate AG
networking people
fon: +49.30.308806-0 fax: -77 web: http://innominate.de pgp: /pgp/gp
On Mon, Jul 03, 2000 at 12:31:03PM +0200, Gerrit Pape wrote:
> On Wed, Jun 28, 2000 at 11:10:59PM -0600, Vincent Danen wrote:
> > Before I make some unecessary work for myself, I was wondering two
> > things:
> >
> > Are there manpages for ucspi-tcp 0.88 somewhere? None are in the
> > package. Also, is there a html2man program or something I can use to
> > make this easier?
> >
> I did manpages from the contents of the html-pages some time ago. You find
> them in: ftp://innominate.org/pub/pape/djb/ .
Did you make them manually or would you share the knowledge of
reverse-html-ify djbs mans?
/magnus
--
http://x42.com/
On Mon, Jul 03, 2000 at 01:34:01PM +0200, Magnus Bodin wrote:
> On Mon, Jul 03, 2000 at 12:31:03PM +0200, Gerrit Pape wrote:
> > On Wed, Jun 28, 2000 at 11:10:59PM -0600, Vincent Danen wrote:
> > > Before I make some unecessary work for myself, I was wondering two
> > > things:
> > >
> > > Are there manpages for ucspi-tcp 0.88 somewhere? None are in the
> > > package. Also, is there a html2man program or something I can use to
> > > make this easier?
> > >
> > I did manpages from the contents of the html-pages some time ago. You find
> > them in: ftp://innominate.org/pub/pape/djb/ .
>
> Did you make them manually or would you share the knowledge of
> reverse-html-ify djbs mans?
>
I did this manually.
Gerrit.
--
[EMAIL PROTECTED]
innominate AG
networking people
fon: +49.30.308806-0 fax: -77 web: http://innominate.de pgp: /pgp/gpa
On Thu, Jun 29, 2000 at 10:44:06AM -0600, Vincent Danen wrote:
> You can obtain the manpages for ucspi-tcp from:
>
> ftp.freezer-burn.org/pub/custom/ucspi-tcp/ucspi-tcp-0.88-man.tar.bz2
>
> These are basically taken direct from cr.yp.to/ucspi-tcp.html and
> converted into manpages.
>
Great, so work is done twice. Searching the archiv really helps. There was
an announce with Subject: man-pages daemontools-0.70 ucspi-tcp-0.88 .
Gerrit.
--
[EMAIL PROTECTED]
innominate AG
networking people
fon: +49.30.308806-0 fax: -77 web: http://innominate.de pgp: /pgp/gp
There is a mailing list for general ucspi discussion:
[EMAIL PROTECTED]
Please post there, also.
W.
On Mon, Jul 03, 2000 at 12:33:32PM +0200, Gerrit Pape wrote:
> On Thu, Jun 29, 2000 at 10:44:06AM -0600, Vincent Danen wrote:
> > You can obtain the manpages for ucspi-tcp from:
> >
> > ftp.freezer-burn.org/pub/custom/ucspi-tcp/ucspi-tcp-0.88-man.tar.bz2
> >
> > These are basically taken direct from cr.yp.to/ucspi-tcp.html and
> > converted into manpages.
> >
> Great, so work is done twice. Searching the archiv really helps. There was
> an announce with Subject: man-pages daemontools-0.70 ucspi-tcp-0.88 .
>
> Gerrit.
>
> --
> [EMAIL PROTECTED]
> innominate AG
> networking people
> fon: +49.30.308806-0 fax: -77 web: http://innominate.de pgp: /pgp/gp
ftp> open
(to) ftp.freezer-burn.org
ftp: connect: Connection refused
Not working?
Paul Farber
Farber Technology
[EMAIL PROTECTED]
Ph 570-628-5303
Fax 570-628-5545
On Mon, 3 Jul 2000, William E. Baxter wrote:
> There is a mailing list for general ucspi discussion:
>
> [EMAIL PROTECTED]
>
> Please post there, also.
>
> W.
>
> On Mon, Jul 03, 2000 at 12:33:32PM +0200, Gerrit Pape wrote:
> > On Thu, Jun 29, 2000 at 10:44:06AM -0600, Vincent Danen wrote:
> > > You can obtain the manpages for ucspi-tcp from:
> > >
> > > ftp.freezer-burn.org/pub/custom/ucspi-tcp/ucspi-tcp-0.88-man.tar.bz2
> > >
> > > These are basically taken direct from cr.yp.to/ucspi-tcp.html and
> > > converted into manpages.
> > >
> > Great, so work is done twice. Searching the archiv really helps. There was
> > an announce with Subject: man-pages daemontools-0.70 ucspi-tcp-0.88 .
> >
> > Gerrit.
> >
> > --
> > [EMAIL PROTECTED]
> > innominate AG
> > networking people
> > fon: +49.30.308806-0 fax: -77 web: http://innominate.de pgp: /pgp/gp
>
Kristina writes:
> The sqwebmail page says that courier-imap includes
> sqwebmail so there is no need to download sqwebmail
> if you have courier-imap.
> I cannot seem to find sqwebmail in my courier-imap-0.31
> installation!
> Anyone know where it could be?
Though I never worked with Courier I'm writing this with the standalone
sqwebmail which can be found at http://www.inter7.com/sqwebmail. AFAIK it
is identical to the version that ships with Courier-IMAP.
HTH
Gabriel
On Sun, Jul 02, 2000 at 09:29:57PM -0700, Todd A. Jacobs wrote:
} On Sun, 2 Jul 2000, Ben Beuchler wrote:
}
} > Do you have the linux source tree installed on your box? I'm guessing
} > not.
}
} Yes, I do: kernel-source-2.2.16-3.
Does this symbolic link exist:
linux% ls -l /usr/include/linux
lrwxrwxrwx 1 root root 26 Aug 3 1999 /usr/include/linux ->
../src/linux/include/linux
Does the file the compiler bitched about actually exist? If not, then
in spite of what rpm tells you, the kernel headers aren't installed.
}
} --
} Todd A. Jacobs
} Senior Network Consultant
}
}
--
--------
Paul J. Schinder
NASA Goddard Space Flight Center
[EMAIL PROTECTED]
also sprach nospam:
> On Sun, 2 Jul 2000, Ronny Haryanto wrote:
>
> > Installing the package kernel-headers will suffice. It's not necessary
> > to install the whole kernel source tree just to compile.
>
> I have those, too: kernel-headers-2.2.16-3
I've found that, occasionally, installing the kernel-source RPM after the
kernel-headers RPM breaks stuff. Re-install the kernel-headers RPM (rpm -Uhv
--force kernel-headers-2.2.16-3.i386.rpm) and try again.
/pg
--
Peter Green : Gospel Communications Network, SysAdmin : [EMAIL PROTECTED]
---
> I get the following error messages at bootup, could anyone tell me
> what they mean?
> fcntl_setlk() called by process 51 (lpd) with broken flock() emulation
They mean that you have not read the documentation when upgrading the
kernel.
(Seen on c.o.l.misc)
On Mon, 3 Jul 2000, Peter Green wrote:
> I've found that, occasionally, installing the kernel-source RPM after
> the kernel-headers RPM breaks stuff. Re-install the kernel-headers RPM
> (rpm -Uhv --force kernel-headers-2.2.16-3.i386.rpm) and try again.
This is pretty much what happened. Thanks. :)
--
Todd A. Jacobs
Senior Network Consultant
I have a problem with QMAIL-POP3D and any other pop3 program.
I use qmail on my server, with /$HOME/Mailbox for any user.
For a strange reason, when i try to get a message from the pop3 server, the
system does not accept my password.
Changing the password, the problem continues.
I have tried to set up /VAR/SPOOL/MAIL/$USER type with procmail, and there was
another problem.
-ERR locking file or directory.
Every time a get a message, the server does non delete the e-mail, and give me
the same error, and sometimes refuse my password too!!!!
The installation and the relay smtp was good for everyone on my net.
It's very strange!????
I tried some pop3 client and server, but the result was the same!
HELP!!
Hello all,
Just installed qmail for the first on a unix machine running Solaris 2.7. I
followed the instruction on LWQ, when I restated my computer I get the
following error:
softlimit: fatal: unable to run : file does not exist
softlimit: fatal: unable to run : file does not exist
softlimit: fatal: unable to run : file does not exist
softlimit: fatal: unable to run : file does not exist
softlimit: fatal: unable to run : file does not exist
softlimit: fatal: unable to run : file does not exist
softlimit: fatal: unable to run : file does not exist
softlimit: fatal: unable to run : file does not exist
(and it keeps going and going and going)
Here is a copy of my /var/qmail/supervise/qmail-stmpd/run file
#!/bin/sh
QMAILDUID=`/usr/xpg4/bin/id -u =qmaild`
NOFILESGID=`/usr/xpg4/bin/id -g =qmaild`
exec /usr/local/bin/softlimit -m 2000000 \
/usr/local/bin/tcpserver -v -p -x /etc/tcp.smtp.cdb \
-u $QMAILDUID -g $NOFILESGID 0 smtp /var/qmail/bin/qmail-smtpd 2>&1
Can someone please help me out.
Thanks in advance,
Eddie Greer
Network Systems Engineer
University of California San Diego
Ph: (858) 534.0526
Fax: (858) 534.7758
Pager: (619) 406.1055
[EMAIL PROTECTED] <mailto:[EMAIL PROTECTED]>
Just to let everyone know of another thing.
I looked into the log files and it reads:
@4000000395b961333720564 softlimit: fatal: unable to run
/usr/local/bin/tcpserver: files does not exist
Thanks again.
Eddie
-----Original Message-----
From: Eddie Greer [mailto:[EMAIL PROTECTED]]
Sent: Monday, July 03, 2000 8:06 AM
To: [EMAIL PROTECTED]
Subject: smtpd/run
Hello all,
Just installed qmail for the first on a unix machine running Solaris 2.7. I
followed the instruction on LWQ, when I restated my computer I get the
following error:
softlimit: fatal: unable to run : file does not exist
softlimit: fatal: unable to run : file does not exist
softlimit: fatal: unable to run : file does not exist
softlimit: fatal: unable to run : file does not exist
softlimit: fatal: unable to run : file does not exist
softlimit: fatal: unable to run : file does not exist
softlimit: fatal: unable to run : file does not exist
softlimit: fatal: unable to run : file does not exist
(and it keeps going and going and going)
Here is a copy of my /var/qmail/supervise/qmail-stmpd/run file
#!/bin/sh
QMAILDUID=`/usr/xpg4/bin/id -u =qmaild`
NOFILESGID=`/usr/xpg4/bin/id -g =qmaild`
exec /usr/local/bin/softlimit -m 2000000 \
/usr/local/bin/tcpserver -v -p -x /etc/tcp.smtp.cdb \
-u $QMAILDUID -g $NOFILESGID 0 smtp /var/qmail/bin/qmail-smtpd 2>&1
Can someone please help me out.
Thanks in advance,
Eddie Greer
Network Systems Engineer
University of California San Diego
Ph: (858) 534.0526
Fax: (858) 534.7758
Pager: (619) 406.1055
[EMAIL PROTECTED] <mailto:[EMAIL PROTECTED]>
Eddie Greer writes:
> softlimit: fatal: unable to run : file does not exist
...
> Here is a copy of my /var/qmail/supervise/qmail-stmpd/run file
>
> #!/bin/sh
> QMAILDUID=`/usr/xpg4/bin/id -u =qmaild`
> NOFILESGID=`/usr/xpg4/bin/id -g =qmaild`
Those `='s aren't suppoesd to be there, are they?
> exec /usr/local/bin/softlimit -m 2000000 \
> /usr/local/bin/tcpserver -v -p -x /etc/tcp.smtp.cdb \
> -u $QMAILDUID -g $NOFILESGID 0 smtp /var/qmail/bin/qmail-smtpd 2>&1
Make sure that there's no whitespace after the \ at the end of the
line. Or removes the backslashes and put the whole command on one
line.
paul
Hi everybody!
I've got a problem with my newly installed qmail v1.03:
local2local: everything's fine.
local2remote: error-mail is returning (see below)
In my /var/qmail/control, there is only:
me: tux.bla.bla
defaultdomain: s-link to "me"
locals: tux.bla.bla
plusdomain: empty
rcpthosts: empty
-> so, everything except tux.bla.bla should go to outside-servers as the
PIC.local2rem shows and the FAQs say.
Where do I have to search my fault?
Is it true, that I don't have to enter the mailserver of my provider
anywhere?
From: [EMAIL PROTECTED]
To: [EMAIL PROTECTED]
Subject: failure notice
Hi. This is the qmail-send program at tux.bla.bla
I'm afraid I wasn't able to deliver your message to the following
addresses.
This is a permanent error; I've given up. Sorry it didn't work out.
<[EMAIL PROTECTED]>:
Sorry, no mailbox here by that name. (#5.1.1)
--- Below this line is a copy of the message.
Return-Path: <[EMAIL PROTECTED]>
Received: (qmail 1747 invoked by uid 500); 3 Jul 2000 12:07:02 -0000
Date: Mon, 3 Jul 2000 14:07:02 +0200
From: [EMAIL PROTECTED] (Karl Voit)
To: Martin Schebesta <[EMAIL PROTECTED]>
Subject: test1
Message-ID: <[EMAIL PROTECTED]>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
X-Mailer: Mutt 1.0pre3i
--
Karl VOIT, [EMAIL PROTECTED]
Student @ University of Technology of GRAZ (Austria/Europe)
http://www.sbox.tu-graz.ac.at/home/v/vk/
OK, it seems to me that my restart of the qmail was not enough and so
after a reboot, the system delivers to remote servers.
But now, a remote mail cannot be delivered to my local server :(
I sent a mail from my gmx-account ([EMAIL PROTECTED]) to my local account
([EMAIL PROTECTED]) and this is, what I got back on my gmx-account:
So please help me!
The error-msg indicates to me that I have to enter all hosts (from where I
wish to get mails from) in my rcpthosts!?!?
Date: 4 Jul 2000 00:11:17 -0000
From: [EMAIL PROTECTED]
To: [EMAIL PROTECTED]
Subject: failure notice
Hi. This is the qmail-send program at www1.gmx.net.
I'm afraid I wasn't able to deliver your message to the following
addresses.
This is a permanent error; I've given up. Sorry it didn't work out.
<[EMAIL PROTECTED]>:
193.171.245.80 does not like recipient.
Remote host said: 553 sorry, that domain isn't in my list of allowed
rcpthosts (#5.7.1)
Giving up.
--- Below this line is a copy of the message.
Return-Path: <[EMAIL PROTECTED]>
Received: (qmail 30135 invoked by uid 0); 4 Jul 2000 00:11:16 -0000
Date: Tue, 4 Jul 2000 02:11:16 +0200 (MEST)
From: [EMAIL PROTECTED]
To: [EMAIL PROTECTED]
MIME-Version: 1.0
Subject: test: gmx 2 tux
X-Authenticated-Sender: #[EMAIL PROTECTED]
X-Authenticated-IP: [129.27.41.7]
Message-ID: <[EMAIL PROTECTED]>
X-Mailer: WWW-Mail 1.5 (Global Message Exchange)
X-Flags: 0001
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
jaja
Karl VOIT, [EMAIL PROTECTED]
Student @ University of Technology of GRAZ (Austria/Europe)
http://www.sbox.tu-graz.ac.at/home/v/vk/
in the file rcpthosts you need to list all the hosts/domains,
that you want to get mail FOR, not FROM.
that means the hosts that your qmail server is "responsible" for. so it
accepts mails from anyone for those domains and tries to deliver them
directly to the users, virtualusers or recipients listed in aliases ...
mail to hosts that are NOT listed in rcpthosts is considered "relaying"
which is only allowed for relayclients (tcp.smtp).
i administer the qmail MX for infoseek.de and webseek.de,
so our rcpthosts file contains (among others)
webseek.de
infoseek.de
mail.webseek.de
so your rcpthosts file should at least contain:
tux.dyn.priv.at
i hope this helps
(and i could explain it well enuf to make sense for you)
wolfgang
Also sprach Karl Voit <[EMAIL PROTECTED]> on 04.07.2000:
>But now, a remote mail cannot be delivered to my local server :(
>I sent a mail from my gmx-account ([EMAIL PROTECTED]) to my local account
>([EMAIL PROTECTED]) and this is, what I got back on my gmx-account:
>The error-msg indicates to me that I have to enter all hosts (from where I
>wish to get mails from) in my rcpthosts!?!?
__________________________________________________
Do You Yahoo!?
Talk to your friends online with Yahoo! Messenger.
http://im.yahoo.com
Hello,
can anybody help me with this :
I have just installed the QMAIL package (i've done this many times).
It seems to be running KO, except that when a message is delivered to
the queue - nothing happens. QMAIL waits for about 10-20-60 minutes
and then it sends the messages that are in the queue. Sometimes it
doesn't send them at all. Nothing is written in the LOG files. No
errors, no attempts, nothing at all. If I kill qmail-send and restart
it - it immediately delivers any messages in the queue, but then
again starts waiting for very long periods. I don't have proper revese
DNS running. Can anybody give me a clue ?
Gabriel Ambuehl <[EMAIL PROTECTED]> writes:
> > It works exactly the same as SSL and IMAP. You can encapsulate any
> > TCP connection in an SSL tunnel. This includes IMAP, POP3, telnet, or
> > even ssh or another SSL session, although the last two are pretty
> > pointless.
>
> May anyone explain me what sense a SSL tunnel for POP3 does have (I've
> been wondering about that for long...)?
[ ... ]
To protect the POP password.
-----ScottG.
Hello Scott,
Monday, July 03, 2000, 5:54:00 PM, you wrote:
>> May anyone explain me what sense a SSL tunnel for POP3 does have (I've
>> been wondering about that for long...)?
> [ ... ]
> To protect the POP password.
But wouldn't it be way easier to just use APOP? Or does that one have
its own security implications?
Best regards,
Gabriel
Gabriel Ambuehl <[EMAIL PROTECTED]> writes:
> Hello Scott,
>
> Monday, July 03, 2000, 5:54:00 PM, you wrote:
> >> May anyone explain me what sense a SSL tunnel for POP3 does have (I've
> >> been wondering about that for long...)?
> > [ ... ]
> > To protect the POP password.
>
> But wouldn't it be way easier to just use APOP? Or does that one have
> its own security implications?
The only particularly nasty implication of using APOP are that it
requires that the server have the password stored in plaintext. The
security aspect of that is that if somebody can steal the password
file from a system, they have direct access to all accounts, compared
to storing one-way hashes of passwords, which would make them run
crack first and they still wouldn't get well-chosen passwords. The
maintainability aspect is that standard UNIX passwords aren't stored
in plaintext, so you can't use APOP to authenticate against a standard
UNIX passwd file.
POP over SSL solves both of these, by making no changes to the POP
protocol, but just encrypting the whole session.
I haven't looked at APOP in awhile, and if what I've said is wrong,
I know that nobody on the list will hesititate to correct me. :)
-----ScottG.
Scott Gifford writes:
> Gabriel Ambuehl <[EMAIL PROTECTED]> writes:
>
> > Hello Scott,
> >
> > Monday, July 03, 2000, 5:54:00 PM, you wrote:
> > >> May anyone explain me what sense a SSL tunnel for POP3 does have (I've
> > >> been wondering about that for long...)?
> > > [ ... ]
> > > To protect the POP password.
> >
> > But wouldn't it be way easier to just use APOP? Or does that one have
> > its own security implications?
>
> The only particularly nasty implication of using APOP are that it
> requires that the server have the password stored in plaintext. The
> security aspect of that is that if somebody can steal the password
> file from a system, they have direct access to all accounts, compared
> to storing one-way hashes of passwords, which would make them run
> crack first and they still wouldn't get well-chosen passwords. The
> maintainability aspect is that standard UNIX passwords aren't stored
> in plaintext, so you can't use APOP to authenticate against a standard
> UNIX passwd file.
The APOP password only controls access to the e-mail POP account. It
DOES NOT have anything to do with a UNIX login account! In fact, if you
allow both shell and pop access, snooping the POP password gives you the
shell password, whereas you can set a single APOP password that gives
access to e-mail and has absolutely nothing to do with shell access.
Thus, in spite of (or because of) the clear-text APOP password storage
on the server, you cannot compromise anything except e-mail by
discovering the APOP password.
> POP over SSL solves both of these, by making no changes to the POP
> protocol, but just encrypting the whole session.
SSL for e-mail (especially POP) is extreme overkill, causing untold
client and server configuration difficulties for little or no effect,
seeing as SMTP is unencrypted...
/Joe
> Scott Gifford:
> The only particularly nasty implication of using APOP are that it
> requires that the server have the password stored in plaintext. The
most mail-servers that i, as a simple leafnode fetching private mail,
care for has my password(s) stored in plaintext somewhere anyway, so
that i can loose it it and have them retrieve it for me. this
"service" is offered by every mailhost, but at least nobody could
sniff it off the line, which is a little more secure than pop3's plain
ascii transmission.
> POP over SSL solves both of these, by making no changes to the POP
> protocol, but just encrypting the whole session.
i've checked around here in germany: isp's offer pop3 access plus
web access. with freenet (mobile) i just had to change my fetchmailrc
to use apop, germanynet (calisto) barked, thay would not change their
entire setup for just one customer, when i asked them for apop. i dared
to ask only because their greeting looks like an apop prompt, and it
even changes on every dialup... so much for technical competence.
clemens
"clemensF" <[EMAIL PROTECTED]> writes:
> > Scott Gifford:
[ ... ]
> > POP over SSL solves both of these, by making no changes to the POP
> > protocol, but just encrypting the whole session.
>
> i've checked around here in germany: isp's offer pop3 access plus
> web access. with freenet (mobile) i just had to change my fetchmailrc
> to use apop, germanynet (calisto) barked, thay would not change their
> entire setup for just one customer, when i asked them for apop. i dared
> to ask only because their greeting looks like an apop prompt, and it
> even changes on every dialup... so much for technical competence.
They probably don't store plaintext passwords, which would make it
impossible to support your request. Not a matter of technical
competence as much as system design.
-----ScottG.
On Sun, Jul 02, 2000 at 07:51:00AM +0200, Steffan Hoeke wrote:
> > I would like to limit some of my users to file seizes not above 1 MB
> > How do I implement that.
> man qmail-smtpd:
> databytes
> Maximum number of bytes allowed in a message, or 0
> for no limit. Default: 0. If a message exceeds this
> limit, qmail-smtpd returns a permanent error code to
> the client; in contrast, if the disk is full or
> qmail-smtpd hits a resource limit, qmail-smtpd
> returns a temporary error code.
>
> databytes counts bytes as stored on disk, not as
> transmitted through the network. It does not count
> the qmail-smtpd Received line, the qmail-queue
> Received line, or the envelope.
>
> If the environment variable DATABYTES is set, it
> overrides databytes.
What is the format of the file ?
/var/qmail/control/databytes
# ---------------
# databytes for qmail
1000
# ---------------
> AFAIK there's no easy way to implement a per-user basis.
> Or you'd have to try to experiment with setting DATABYTES in tcprules/
> tcpserver.
> databytes should be in /var/qmail/control ....
Thank you for giving the directory of the file
I do not find that in the man pages.
I suppose the best would be to implement some user disk quota
Thanks
Jacob
Hello all
Got the latest verion of ucspi (.88) that is said to incorporate the older
rblsmtpd program from djb....
Are the old rblsmtpd docs still valid??? The tcpserver man page DOES list
rblsmtpd under 'see also', but rblsmtpd is not part of ucspi.. and round
and round we go!
So.... where are the docs??? Tcpserver or rblsmtpd ????
Paul Farber
Farber Technology
[EMAIL PROTECTED]
Ph 570-628-5303
Fax 570-628-5545
On Mon, Jul 03, 2000 at 12:51:48PM -0400, Paul Farber wrote:
> Hello all
>
> Got the latest verion of ucspi (.88) that is said to incorporate the older
> rblsmtpd program from djb....
>
> Are the old rblsmtpd docs still valid??? The tcpserver man page DOES list
> rblsmtpd under 'see also', but rblsmtpd is not part of ucspi..
Um, yeah it is.
--Adam
On Mon, Jul 03, 2000 at 12:51:48PM -0400, Paul Farber wrote:
> Hello all
>
> Got the latest verion of ucspi (.88) that is said to incorporate the older
> rblsmtpd program from djb....
>
> Are the old rblsmtpd docs still valid??? The tcpserver man page DOES list
> rblsmtpd under 'see also', but rblsmtpd is not part of ucspi.. and round
> and round we go!
>
Assuming You mean the man-pages I did, sorry, I seem to forgot this one.
In fact, there are missing the man-pages for addcr, delcr, mconnect-io an
rblsmtpd. I will do them the next days.
> So.... where are the docs??? Tcpserver or rblsmtpd ????
>
http://cr.yp.to/ucspi-tcp/rblsmtpd.html .
Gerrit.
--
[EMAIL PROTECTED]
innominate AG
networking people
fon: +49.30.308806-0 fax: -77 web: http://innominate.de pgp: /pgp/gpa
I got several tarballs of ucspi doc's (.87 and .88) yet none of them had
any rblsmtpd man pages.....
anyone have a complete set?
Paul Farber
Farber Technology
[EMAIL PROTECTED]
Ph 570-628-5303
Fax 570-628-5545
On Mon, 3 Jul 2000, Adam McKenna wrote:
> On Mon, Jul 03, 2000 at 12:51:48PM -0400, Paul Farber wrote:
> > Hello all
> >
> > Got the latest verion of ucspi (.88) that is said to incorporate the older
> > rblsmtpd program from djb....
> >
> > Are the old rblsmtpd docs still valid??? The tcpserver man page DOES list
> > rblsmtpd under 'see also', but rblsmtpd is not part of ucspi..
>
> Um, yeah it is.
>
> --Adam
>
Hi all,
I just installed qmail, daemontools 0.70
and ucspi-tcp-0.88 on an alpha running
redhat v6.2. The qmail tests for local
and remote delivery from TEST.deliver work
fine, but the TEST.receive tests aren't possible
because nothing is listening on port 25. I did
some investigating and from my qmail
/var/log/qmail/smtpd/current log file, I see
an endless output of:
@400000003960c9d802f8279c /usr/local/bin/tcpserver:
error in loading shared libraries: libc.so.6.1:
failed to map segment from shared object: Cannot
allocate memory
Now I know it's not an actual memory problem
because I've got a gig of ram in the machine, so
is it an alpha related problem? I've run the same
setup steps on this box as I've done on many others
so it isn't my setup or qmail itself I don't think...
Please help. :-) I did check the archives but didn't
see anything relevant in my search for "alpha linux
tcpserver"
Thanks,
Dave
Does anyone know what specifically is meant by qmail-qread when it lists a
message as 'bouncing'? Does it mean that the actual message is a bounce
message? Or that one of the recipients bounced? Or something else
entirely?
Thanks,
Ben
--
The spectre of a polity controlled by the fads and whims of voters who
actually believe that there are significant differences between Bud Lite
and Miller Lite, and who think that professional wrestling is for real, is
naturally alarming to people who don't.
-- Neal Stephenson
Hi all,
I've got qmail running properly on a system with a DMZ-firewall setup.
All the local clients are behind the firewall, addressed as 192.168.0.n.
The firewall (a debian box) and the mail server are connected to our
ADSL router and both have class-C addresses. The clients all have hosts
files referencing the mail server.
My tcp.smtp file has proper settings to allow the local clients to work
as RELAYCLIENTS:
127.0.0.1:allow,RELAYCLIENT=""
192.168.0.:allow,RELAYCLIENT=""
:allow
(I've recompiled it just to be sure and, yes, the reference in the qmail
startup script points to the proper file '-x/etc/tcp.smtp.cdb')
If I create a rcpthosts file with just the local domain in it (that's
all I want), then every local client that tries to send mail out to the
'net gets a qmail error message saying the destination domain is not in
the list of receipt hosts (or something to that effect).
Is the problem that qmail, running on a mail server, with it's class-C
address, doesn't like the "192" block addresses in tcp.smtp? I've set up
qmail servers before as multihomed systems with a class-C card *and* and
internal one. Must I do that here?
Thanks
Barry Dwyer
Barry Dwyer writes:
> If I create a rcpthosts file with just the local domain in it (that's
> all I want), then every local client that tries to send mail out to the
> 'net gets a qmail error message saying the destination domain is not in
> the list of receipt hosts (or something to that effect).
Does rcpthosts contain `.domain.tld', or just `domain.tld'? If the
latter, it will accept messages only from that host. Use the former
to accept messages from all hosts in that domain.
paul
Make sure you've used tcprules to hash your /etc/tcp.smtp file into
/etc/tcp.smtp.cdb and then RESTART your tcpserver -x
/etc/tcp.smtp/cdb...etc. The changes to tcp.smtp.cdb won't take effect
until you restart.
-CT
----- Original Message -----
From: "Barry Dwyer" <[EMAIL PROTECTED]>
To: "QMAIL" <[EMAIL PROTECTED]>
Sent: Monday, July 03, 2000 3:10 PM
Subject: tcprules, rcpthost, ip address problem
> Hi all,
>
> I've got qmail running properly on a system with a DMZ-firewall setup.
> All the local clients are behind the firewall, addressed as 192.168.0.n.
> The firewall (a debian box) and the mail server are connected to our
> ADSL router and both have class-C addresses. The clients all have hosts
> files referencing the mail server.
>
> My tcp.smtp file has proper settings to allow the local clients to work
> as RELAYCLIENTS:
>
> 127.0.0.1:allow,RELAYCLIENT=""
> 192.168.0.:allow,RELAYCLIENT=""
> :allow
>
> (I've recompiled it just to be sure and, yes, the reference in the qmail
> startup script points to the proper file '-x/etc/tcp.smtp.cdb')
>
> If I create a rcpthosts file with just the local domain in it (that's
> all I want), then every local client that tries to send mail out to the
> 'net gets a qmail error message saying the destination domain is not in
> the list of receipt hosts (or something to that effect).
>
> Is the problem that qmail, running on a mail server, with it's class-C
> address, doesn't like the "192" block addresses in tcp.smtp? I've set up
> qmail servers before as multihomed systems with a class-C card *and* and
> internal one. Must I do that here?
>
> Thanks
> Barry Dwyer
>
On Mon, Jul 03, 2000 at 06:12:26PM -0500, Christopher Tolley wrote:
> Make sure you've used tcprules to hash your /etc/tcp.smtp file into
> /etc/tcp.smtp.cdb and then RESTART your tcpserver -x
> /etc/tcp.smtp/cdb...etc. The changes to tcp.smtp.cdb won't take effect
> until you restart.
It seems like there has been a surge in misinformation lately on this list.
The above is COMPLETELY false. You do NOT need to "restart your tcpserver"
for the changes to take effect.
--Adam
On Mon, Jul 03, 2000 at 01:10:05PM -0700, Barry Dwyer wrote:
> Hi all,
>
> I've got qmail running properly on a system with a DMZ-firewall setup.
> All the local clients are behind the firewall, addressed as 192.168.0.n.
> The firewall (a debian box) and the mail server are connected to our
> ADSL router and both have class-C addresses. The clients all have hosts
> files referencing the mail server.
>
> My tcp.smtp file has proper settings to allow the local clients to work
> as RELAYCLIENTS:
>
> 127.0.0.1:allow,RELAYCLIENT=""
> 192.168.0.:allow,RELAYCLIENT=""
> :allow
>
> (I've recompiled it just to be sure and, yes, the reference in the qmail
> startup script points to the proper file '-x/etc/tcp.smtp.cdb')
>
> If I create a rcpthosts file with just the local domain in it (that's
> all I want), then every local client that tries to send mail out to the
> 'net gets a qmail error message saying the destination domain is not in
> the list of receipt hosts (or something to that effect).
>
> Is the problem that qmail, running on a mail server, with it's class-C
> address, doesn't like the "192" block addresses in tcp.smtp? I've set up
> qmail servers before as multihomed systems with a class-C card *and* and
> internal one. Must I do that here?
No. qmail doesn't give special treatment to any IP addresses, AFAIK. Either
there is a typo in your tcp.smtp or some other problem.
--Adam
>> Either there is a typo in your tcp.smtp .
My tcp.smtp is included, in its entirety, in my original post. Can
*anyone* see any problems with it? Reproduced again:
> 127.0.0.1:allow,RELAYCLIENT=""
> 192.168.0.:allow,RELAYCLIENT=""
> :allow
>> or some other problem.
OK, great, but WHAT OTHER PROBLEM!? This is making my (thinning ) hair
go grey. I'd appreciate any suggestions as what the 'other problem'
might be.
Barry
On Mon, Jul 03, 2000 at 01:10:05PM -0700, Barry Dwyer wrote:
>
> 127.0.0.1:allow,RELAYCLIENT=""
> 192.168.0.:allow,RELAYCLIENT=""
> :allow
did you run
tcprules /etc/tcp.smtp.cdb /etc/tcp.smtp.tmp < /etc/tcp.smtp
after creating that /etc/tcp.smtp file?
--
wolfgang
__________________________________________________
Do You Yahoo!?
Talk to your friends online with Yahoo! Messenger.
http://im.yahoo.com
On Mon, Jul 03, 2000 at 04:43:52PM -0700, Barry Dwyer wrote:
> >> Either there is a typo in your tcp.smtp .
>
> My tcp.smtp is included, in its entirety, in my original post. Can
> *anyone* see any problems with it? Reproduced again:
>
> > 127.0.0.1:allow,RELAYCLIENT=""
> > 192.168.0.:allow,RELAYCLIENT=""
> > :allow
>
> >> or some other problem.
>
> OK, great, but WHAT OTHER PROBLEM!? This is making my (thinning ) hair
> go grey. I'd appreciate any suggestions as what the 'other problem'
> might be.
Is that an actual paste of your tcp.smtp or did you copy it in by hand?
--Adam
That's an actual paste of the file.
BD
Adam McKenna wrote:
> On Mon, Jul 03, 2000 at 04:43:52PM -0700, Barry Dwyer wrote:
> > >> Either there is a typo in your tcp.smtp .
> >
> > My tcp.smtp is included, in its entirety, in my original post. Can
> > *anyone* see any problems with it? Reproduced again:
> >
> > > 127.0.0.1:allow,RELAYCLIENT=""
> > > 192.168.0.:allow,RELAYCLIENT=""
> > > :allow
> >
> > >> or some other problem.
> >
> > OK, great, but WHAT OTHER PROBLEM!? This is making my (thinning ) hair
> > go grey. I'd appreciate any suggestions as what the 'other problem'
> > might be.
>
> Is that an actual paste of your tcp.smtp or did you copy it in by hand?
>
> --Adam
That's an actual paste of the file.
BD
Adam McKenna wrote:
> On Mon, Jul 03, 2000 at 04:43:52PM -0700, Barry Dwyer wrote:
> > >> Either there is a typo in your tcp.smtp .
> >
> > My tcp.smtp is included, in its entirety, in my original post. Can
> > *anyone* see any problems with it? Reproduced again:
> >
> > > 127.0.0.1:allow,RELAYCLIENT=""
> > > 192.168.0.:allow,RELAYCLIENT=""
> > > :allow
> >
> > >> or some other problem.
> >
> > OK, great, but WHAT OTHER PROBLEM!? This is making my (thinning ) hair
> > go grey. I'd appreciate any suggestions as what the 'other problem'
> > might be.
>
> Is that an actual paste of your tcp.smtp or did you copy it in by hand?
>
> --Adam
>> did you run tcprules /etc/tcp.smtp.cdb /etc/tcp.smtp.tmp <
/etc/tcp.smtp
after creating that /etc/tcp.smtp file?
Yes. A bunch of times.
Barry
It may seem a bit stupid... have you tried to put a space between the -x and
the path to the cdb file?
If so, can you please post the relevant script line ?
Armando
Hello,
Let me see if i got it right: you have users using your mailbox as
mailhost,and want
them to be able to use your mailhost as relay. Right ?
IMHO you should just delete rcpthosts and manage your relaying stuff
through
your tcp.smtp.cdb stuff. Your tcp.smtp looks correct, so give it a
trial.
Regards
Ertan
Barry Dwyer wrote:
>
> Hi all,
>
> I've got qmail running properly on a system with a DMZ-firewall setup.
> All the local clients are behind the firewall, addressed as 192.168.0.n.
> The firewall (a debian box) and the mail server are connected to our
> ADSL router and both have class-C addresses. The clients all have hosts
> files referencing the mail server.
>
> My tcp.smtp file has proper settings to allow the local clients to work
> as RELAYCLIENTS:
>
> 127.0.0.1:allow,RELAYCLIENT=""
> 192.168.0.:allow,RELAYCLIENT=""
> :allow
>
> (I've recompiled it just to be sure and, yes, the reference in the qmail
> startup script points to the proper file '-x/etc/tcp.smtp.cdb')
>
> If I create a rcpthosts file with just the local domain in it (that's
> all I want), then every local client that tries to send mail out to the
> 'net gets a qmail error message saying the destination domain is not in
> the list of receipt hosts (or something to that effect).
>
> Is the problem that qmail, running on a mail server, with it's class-C
> address, doesn't like the "192" block addresses in tcp.smtp? I've set up
> qmail servers before as multihomed systems with a class-C card *and* and
> internal one. Must I do that here?
>
> Thanks
> Barry Dwyer
Yes, deleting rcphosts the relay works correcly. But this pose the problem to
deny the relay to unwanted people.
Through the tcp.smtpd i can really manage the relay?
On Tue, 04 Jul 2000, ertan payci wrote:
> Hello,
>
> Let me see if i got it right: you have users using your mailbox as
> mailhost,and want
> them to be able to use your mailhost as relay. Right ?
> IMHO you should just delete rcpthosts and manage your relaying stuff
> through
> your tcp.smtp.cdb stuff. Your tcp.smtp looks correct, so give it a
> trial.
>
> Regards
>
> Ertan
>
> Barry Dwyer wrote:
> >
> > Hi all,
> >
> > I've got qmail running properly on a system with a DMZ-firewall setup.
> > All the local clients are behind the firewall, addressed as 192.168.0.n.
> > The firewall (a debian box) and the mail server are connected to our
> > ADSL router and both have class-C addresses. The clients all have hosts
> > files referencing the mail server.
> >
> > My tcp.smtp file has proper settings to allow the local clients to work
> > as RELAYCLIENTS:
> >
> > 127.0.0.1:allow,RELAYCLIENT=""
> > 192.168.0.:allow,RELAYCLIENT=""
> > :allow
> >
> > (I've recompiled it just to be sure and, yes, the reference in the qmail
> > startup script points to the proper file '-x/etc/tcp.smtp.cdb')
> >
> > If I create a rcpthosts file with just the local domain in it (that's
> > all I want), then every local client that tries to send mail out to the
> > 'net gets a qmail error message saying the destination domain is not in
> > the list of receipt hosts (or something to that effect).
> >
> > Is the problem that qmail, running on a mail server, with it's class-C
> > address, doesn't like the "192" block addresses in tcp.smtp? I've set up
> > qmail servers before as multihomed systems with a class-C card *and* and
> > internal one. Must I do that here?
> >
> > Thanks
> > Barry Dwyer
On Tue, Jul 04, 2000 at 09:22:24AM +0200, ertan payci wrote:
> Hello,
>
> Let me see if i got it right: you have users using your mailbox as
> mailhost,and want
> them to be able to use your mailhost as relay. Right ?
> IMHO you should just delete rcpthosts and manage your relaying stuff
> through
> your tcp.smtp.cdb stuff. Your tcp.smtp looks correct, so give it a
> trial.
What is this, disinformation day?
You should NEVER delete your rcpthosts file as this will cause qmail to
function as an OPEN RELAY, no matter what the rules say.
--Adam
On Tue, Jul 04, 2000 at 04:04:37AM -0500, Christopher Tolley wrote:
> I'm not going to argue, but I HAVE had to kill and restart tcpserver for the
> changes to take effect. If that's wrong, then I don't know how to make the
> changes take and NOT restart tcpserver...perhaps you can enlighten me a bit
> in that respect. I'm not out to perform disinformation...just speaking from
> first-hand experience
>
> BTW, I run tcpserver stand-alone, without the extra wrappers to monitor it.
> Is this the limitation or is it something else?
There is no limitation. tcpserver reads the cdb given as the argument to -x
every time a connection is made.
>From the man page:
-xrules.cdb
Follow the rules compiled into rules.cdb by
tcprules. These rules may specify setting environ�
ment variables or rejecting connections from bad
sources.
tcpserver does not read rules.cdb into memory; you
can rerun tcprules to change tcpserver's behavior
on the fly.
--Adam
[ This message is being Cc'd to [EMAIL PROTECTED] ]
Greetings (again):
I'm still having problems retrieving mail from my
/home/vpopmail/domains/ducaniveaux.com/ducaniveaux/Maildir/
mail directory.
I just checked vchkpwd:
inloc:/home/vpopmail/bin# /var/qmail/bin/qmail-popup [EMAIL PROTECTED]
vchkpw pwd
+OK <10766.962655981@[EMAIL PROTECTED]>
user ducaniveaux
+OK
pass longgens
/home/ducaniveaux
I also tried accessing the mail using a Perl script from David Cross; it fails at the
point where it checks the password:
----
print S "PASS $pass\n";
if(!&WaitForOk) {
print S "QUIT\n";&CgiError("Could not send password!<BR>Password or username may be
incorrect.")
}
----
I don't understand how, if vchkpwd is working correctly, my mail access is failing on
the password.
Any ideas or suggestions would be appreciated.
--
All the best (Ad�u-siau),
Lou Hevly
[EMAIL PROTECTED]
http://www.visca.com
Our qmail system is working fine internally and can send out to the 'net
OK. We're only receiving from certain domains, however, from others
intermittently and from some not at all. I know this is usually a DNS
issue and I've checked the MX records for our domain, 'nethan.com' and
it appears OK:
- Name=nethan.com
Type=MX, Class=1, TTL=39072 (10 Hours 51 Minutes 12 Seconds),
RDLENGTH=9
Preference=1, Mail Exchange=mail.nethan.com
Authority Records Section:
<deleted>
Additional Records Section:
- Name=mail.nethan.com
Type=A, Class=1, TTL=42982 (11 Hours 56 Minutes 22 Seconds),
RDLENGTH=4
IP Address=216.251.137.227
- Name=NS1.SOHOSKYWAY.NET
Type=A, Class=1, TTL=43200 (12 Hours), RDLENGTH=4
IP Address=209.17.143.10
- Name=NS2.SOHOSKYWAY.NET
Type=A, Class=1, TTL=43200 (12 Hours), RDLENGTH=4
IP Address=209.17.177.1
However, a reverse DNS on our mail server's IP turns up:
- Name=227.137.251.216.IN-ADDR.ARPA
Type=PTR, Class=1, TTL=43200 (12 Hours), RDLENGTH=20
PTR=137-227.ntcare.com
Would this reverse-DNS entry (apparently there for the convenience of
the ISP's reseller) be preventing some mail servers from forwarding to
ours?
Thanks,
Barry
anyway to test the rblsmtp service from ucspi .88?
by default... where do messages get logged (via syslogd?).
Paul Farber
Farber Technology
[EMAIL PROTECTED]
Ph 570-628-5303
Fax 570-628-5545
I have the following line in /etc/inetd.conf:
smtp stream tcp nowait qmaild /usr/sbin/tcpd /var/qmail/bin/tcp-env
/usr/local/bin/rblsmtpd /var/qmail/bin/qmail-smtpd
I'm getting oodles of the following errors in my logs:
Jul 3 14:12:12 cyrix inetd[810]: pid 31351: exit status 1
Jul 3 14:27:41 cyrix inetd[810]: pid 31420: exit status 1
Jul 3 14:43:22 cyrix inetd[810]: pid 31458: exit status 1
Jul 3 14:59:00 cyrix inetd[810]: pid 31481: exit status 1
Since qmail isn't restarting all the time, the problem seems to point to
rblsmtpd. I did a grep of all the source files, but only found exit(1) in
subgetopt.3, and am not sure how this applies.
Can anyone help?
--
Todd A. Jacobs
Senior Network Consultant
I have a problem with remote 2 local delivery.
When a new mail comes in, instead of processing it, it gets
stucked in the TODO directory. After a while (15+ min), it gets
processes. I can also force it to process the mail by
doing
svc -t /var/services/qmail
I'm running Linux 2.2.14. Qmail is installed in /opt/qmail.
The queue, /opt/qmail/queue, is a symlink to /var/spool/mqueue
These are my run scripts:
#### qmail rc #######
!/bin/sh
# Using splogger to send the log through syslog.
# Using qmail-local to deliver messages to ~/Mailbox by default.
exec env - PATH="/opt/qmail/bin:/usr/local/bin:$PATH" \
qmail-start ./Maildir/ multilog t n5 /var/log/qmail
#####################
#### smtpd run #####
#!/bin/bash
exec env - PATH="/usr/local/bin:/opt/qmail/bin:$PATH" \
tcpserver -v -u 101 -g 101 -x /etc/tcp.smtp.cdb 0 smtp qmail-smtpd 2>&1
####################
Anyone have an idea of what might be wrong?
--
John______________________________________________________________________
email: [EMAIL PROTECTED]
icq: thales @ 17755648
I just did some more testing. It seems that it doesn't get
processes at all automatically. Only when I do a local 2 xxx
(remote/local) delivery, does the mail in the TODO directory
get processed.
--
John______________________________________________________________________
email: [EMAIL PROTECTED]
icq: thales @ 17755648
Hi
I just totally trashed my queue when a mailing list -> disussion forum
script got totally infinite on me
a quick root>rm -Rf ./queue stopped it sending out 10MB emails to my
subscribers (sorry I panicked)
anyway, I downloaded a queue fixer
http://www.netmeridian.com/e-huss/queue-fix.tar.gz
and before I re-build it
is there anywhere that these messages could still be waiting to go out?
There is nothing in /var/qmail/queue, so i guess not, but I wanted to check
first
tia
Darren Beale
I've now re-built but there are still lots of messages in queue/remote and
queue/local
how do I delete them please?
apologies if this a RTFM, but any posts on this subject that I could find in
the archive, just say "re-build the queue"
thanks
Darren Beale
please ignore my previous post, I read a bit harder =)
I am unable to clear the queue.
The MAN page of qmail-clean simply says:
NAME
qmail-clean - clean up the queue directory
SYNOPSIS
qmail-clean
DESCRIPTION
qmail-clean reads a cleanup command from descriptor 0,
performs the cleanup, prints the results to descriptor 1,
and repeats.
SEE ALSO
qmail-send(8)
but what are these cleanup commands? where can I find them?
thanks
On 04-Jul-2000, Wayne Chu wrote:
> I am unable to clear the queue.
What do you mean by "clear"? Like flushing all the mails to go?
'killall -ALRM qmail-send' should do it. Watch the logs.
Ronny
|
Hi all,
How to set IMAP with qmail,
please ...
My POP3 is working properly ... but my IMAP
:-( ....
May be I made some mistakes when install it
with qmail ...
Thanks a lot.
~iman
|
download courier-imap more info at www.qmail.org and look for Life with Qmail
At 11:16 AM 7/4/00 +0700, Iman Budi Setiawan wrote:
> Hi all, ... my IMAP :-( .... some mistakes when install it with
>qmail ... Thanks a lot. ~iman
Apologies is this question is out of place on this list, but I'm trying to
move a working site to a new server.
Working site:
RH 6.0
vchkpw-3.4.5
Qmail 1.03
UW Imap (with Maildir patch)
New Server:
RH 6.2 (installed ok)
vpopmail 4.8a (compiled and installed ok)
Qmail 1.03 (compiled and installed ok)
Courier IMAP (compiled and installed ok)
I can get everything working just fine. It's when I try to copy my domains
directory from my current production server that all goes bonkers. Is this
possible? Any tricks?
I've tried copying all my qmail/control and qmail/user files from the
original server. I've changed the paths in the qmail/user/assign and the
vpasswd files to reflect the new installation point of vpopmail. (installed
to /home/vpopmail instead of /vpopmail). Like I say, if I create a new
domain, test.com, the then try to auth against it (telnet localhost 110), it
works like a charm. It's when I copy the users and vpasswd files from the
3.4.5 version.
Help is greatly appreciated.
Charlie
|
Hi,
Can you help me to fix my problem ...
My qmail can send to another mail, but it can not
work when other send email to my qmail. I don't know how to solve or
check this problem ...
please, tell me how to solve or how to trace it
...
Thanks.
~iman
|
On Tue, Jul 04, 2000 at 11:09:17AM +0700, Iman Budi Setiawan wrote:
> Hi,
>
> Can you help me to fix my problem ...
> My qmail can send to another mail, but it can not work when other send email to my
>qmail. I don't know how to solve or check this problem ...
> please, tell me how to solve or how to trace it ...
1) What do the logs say (tm)
2) What does qmail-showctl say (tm)
3) What is the output of ps -ax | grep qmail
4) Is qmail-smtpd running
> Thanks.
> ~iman
HTH,
Steffan
--
http://therookie.dyndns.org
I have just changed from a dial-up connection that costs me money to
dial to a dial-up connection that is free. I'm therefore changing my
(Linux Mandrake) system from dialling when manually requested to
dial-on-demand.
Up till now I have run qmail with the holdremote patch (thanks Nick!)
but now I'll be removing it.
Will an unpatched qmail bring up the connection when it has mail to
send if I have dial on demand set up right?
The other question that arises is that I'd quite like qmail *not* to
accept SMTP mail from the outside world (my ISP delivers using SMTP
but want it to continue to accept SMTP mail from other computers on my
home LAN. How can I do this?
--
Chris Green ([EMAIL PROTECTED])
Home: [EMAIL PROTECTED] Work: [EMAIL PROTECTED]
WWW: http://www.isbd.co.uk/
Rodrigo Severo <[EMAIL PROTECTED]> schrieb/wrote:
> void err_vrfy() { out("252 send some mail, i'll try my best\r\n"); }
> void err_qqt() { out("451 qqt failure (#4.3.0)\r\n"); }
> ! void err_excessrcpt() { out("666 Too many recipients specified
~~~
> (#5.5.4)\r\n"); } /* Agregado por mi para el maxrcpt */
That's a very bad idea.
Claus
--
http://www.faerber.muc.de
