qmail Digest 9 Jun 2000 10:00:01 -0000 Issue 1027
Topics (messages 42877 through 42935):
Forwarding catchall acount to multiple Maildirs?
42877 by: Snowcrash
42878 by: jmroth.iip.lu
42889 by: Ken Jones
Re: www.ezmlm.org
42879 by: Peter Green
42881 by: Magnus Bodin
42882 by: Peter Green
42883 by: Magnus Bodin
Re: qmailanalog and multilog
42880 by: Kevin Bucknum
Blocking of Mail Domain for a specific users
42884 by: ruchandra.hss.hns.com
42885 by: OK 2 NET - Andr� Paulsberg
42895 by: Adam McKenna
42923 by: OK 2 NET - Andr� Paulsberg
42926 by: Petr Novotny
42929 by: ruchandra.hss.hns.com
42934 by: OK 2 NET - Andr� Paulsberg
ezmlm.org
42886 by: Ken Jones
42887 by: Peter Green
42890 by: Magnus Bodin
Qmail Virtual Users
42888 by: John Golovich
convert mbox -> maildirs
42891 by: Enrique Vadillo
42892 by: clemensF
42893 by: Alex Rubenstein
42894 by: Yiorgos Adamopoulos
Security warning: using linuxconf(RedHat 6.2) and permissions of /usr/sbin/sendmail
42896 by: Peter Bieringer
42898 by: VANTASSLE, GEORDON M. (AIT)
42900 by: Jim Simmons
42909 by: Christian Wiese
42912 by: Bruce Guenter
mail forwarding: alias
42897 by: Zhiliang Hu
42899 by: Chris Johnson
42901 by: Zhiliang Hu
42904 by: Chris Johnson
42906 by: Zhiliang Hu
42908 by: Chris Johnson
42910 by: Zhiliang Hu
42911 by: Charles Cazabon
42918 by: clemensF
ezmlm-sub question?
42902 by: cdowns
42903 by: Steffan Hoeke
frequent double deliveries
42905 by: Nathan Clegg
Re: qmail+mrtg+multilog mods
42907 by: Mark E. Drummond
the point with the dot in dot-qmail
42913 by: Jens Georg
42914 by: Mikko H�nninen
group mailboxes don't seem to work after I installed ezmlm
42915 by: Martin Searancke
DNS subdomain question
42916 by: Susan Short
42930 by: Robert Varga
Re: Does someone knows what is this about?
42917 by: Peter van Dijk
LAST command not working. Any workarounds?
42919 by: Ben Beuchler
courier-imap: make check errors
42920 by: Kristina
HELP PLEASE
42921 by: Sinisa Malesevic
syslog issue:(
42922 by: Brendan Laws
few simple questions abt qmail
42924 by: Stefan Beke
42928 by: Petr Novotny
42931 by: Stefan Beke
Re: syslog issue:( pop3d
42925 by: Neal Pollack
Re: tcpserver: unable to bind
42927 by: Luca Zancan
qmail inquiry
42932 by: Verna Vergara
42933 by: Eric Cox
characteristic of my server
42935 by: Julien Marguet
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]
----------------------------------------------------------------------
|
I currently have a catchall
account set up and it succesfully delivers to one user. However I would
like to have the mail delived to multiple people. I'm not quite sure how
to do this. My current .qmail-default is:
| /home/vpopmail/bin/vdelivermail ''
/home/vpopmail/domains/foo.com/user
Thanks in advance,
Daniel Daley
|
Try:
| /home/vpopmail/bin/vdelivermail '' /home/vpopmail/domains/foo.com/user
& [EMAIL PROTECTED]
& [EMAIL PROTECTED]
etc.
Regards!
--jmr
Snowcrash writes:
>
> I currently have a catchall account set up and it succesfully delivers to one
>user. However I would like to have the mail delived to multiple people. I'm not
>quite sure how to do this. My current .qmail-default is:
>
> | /home/vpopmail/bin/vdelivermail '' /home/vpopmail/domains/foo.com/user
>
> Thanks in advance,
> Daniel Daley
> [EMAIL PROTECTED]
----
J.M. Roth
> Snowcrash wrote:
>
>
> I currently have a catchall account set up and it succesfully
> delivers to one user. However I would like to have the mail delived
> to multiple people. I'm not quite sure how to do this. My current
> .qmail-default is:
>
> | /home/vpopmail/bin/vdelivermail ''
> /home/vpopmail/domains/foo.com/user
>
> Thanks in advance,
> Daniel Daley
> [EMAIL PROTECTED]
the vdelivermail program only accepts one account for the "catchall"
"catchall" being a horrible phrase meaning:
All those emails which neither match a .qmail-user file nor are
in the vpopmail user authentication system for this domain.
Adding lines after the vdelivermail line will not have your intended
effect. The lines after will receive all email that does not match
a .qmail-user file (standard .qmail-default processing), including
email for vpopmail pop accounts. This is not a "catchall" behavior.
What you could do is put an email address at the end of vdelivermail.
Say.. [EMAIL PROTECTED] Then create a .qmail-catchall file with the list
of Maildirs you want the catchall email to go to. This will cause
a re-injection of the "catch all'd" email into the queue. But will
do what you want.
For example:
cat .qmail-default
| /home/vpopmail/bin/vdelivermail '' [EMAIL PROTECTED]
cat .qmail-catchall
./user1/Maildir/
./user2/Maildir/
Ken Jones
also sprach mwangu:
> All,
>
> Does anyone know what has happened to www.ezmlm.org
It appears to be on hold by Network Solutions, awaiting payment. :(
/pg
--
Peter Green : Gospel Communications Network, SysAdmin : [EMAIL PROTECTED]
---
Go not unto the Usenet for advice, for you will be told both yea and nay (and
quite a few things that just have nothing at all to do with the question).
(Seen in a .sig somewhere.)
On Thu, Jun 08, 2000 at 08:04:04AM -0400, Peter Green wrote:
> also sprach mwangu:
> > All,
> >
> > Does anyone know what has happened to www.ezmlm.org
>
> It appears to be on hold by Network Solutions, awaiting payment. :(
Sure? Not anymore at least.
https://payments.networksolutions.com/cgi-bin/payment-decision.pl?EntityType=domain&EntityName=ezmlm.org
/magnus
--
http://x42.com
also sprach magnus:
> On Thu, Jun 08, 2000 at 08:04:04AM -0400, Peter Green wrote:
> > also sprach mwangu:
> > > All,
> > >
> > > Does anyone know what has happened to www.ezmlm.org
> >
> > It appears to be on hold by Network Solutions, awaiting payment. :(
>
> Sure? Not anymore at least.
fwhois "dump ezmlm.org"@whois.networksolutions.com shows that it still is:
[...]
(29) parentdom: HOLD-PAY|
[...]
But I wouldn't be surprised if NetSlow's records were outta whack. :/
/pg
--
Peter Green : Gospel Communications Network, SysAdmin : [EMAIL PROTECTED]
---
What say? Is UNIX dead _again_? I thought the blockheads at _PC Week_
and so on didn't have that story scheduled for regurgitation until
_next_ month. Oh, I forgot: Not There v.4.0 is out. That explains it.
(Rick Moen <[EMAIL PROTECTED]> in comp.os.linux.misc)
On Thu, Jun 08, 2000 at 08:35:16AM -0400, Peter Green wrote:
> also sprach magnus:
> > On Thu, Jun 08, 2000 at 08:04:04AM -0400, Peter Green wrote:
> > > also sprach mwangu:
> > > > All,
> > > >
> > > > Does anyone know what has happened to www.ezmlm.org
> > >
> > > It appears to be on hold by Network Solutions, awaiting payment. :(
> >
> > Sure? Not anymore at least.
>
> fwhois "dump ezmlm.org"@whois.networksolutions.com shows that it still is:
>
> [...]
> (29) parentdom: HOLD-PAY|
> [...]
You're probably right.
RIVERTOWN.NET is on hold as well.
I guess it's Fred B Ringels business.
/magnus
Not using the patches from www.qmail.org, but this works for me
Script to convert to a format qmailanalog likes
#!/usr/bin/perl
while (<>) {
if (my($s,$t,$rest)=/^\@.(\w{15})(\w{8})(.*)/) {
$s = hex($s);
$t = hex($t); $t =~ s/500$//;
$_ = "$s.$t$rest\n";
}
} continue {
print;
}
exit 0;
Script to process the logs and mail to me
#!/bin/sh
PATH=/usr/local/qmailanalog/bin:/var/qmail/bin:/bin:/usr/bin
QMAILLOG="/tmp/q.$$"
QMAILTMP="/tmp/r.$$"
umask 077
cat /var/log/qmail/@* > $QMAILTMP
cat /var/log/qmail/current >> $QMAILTMP
cat $QMAILTMP | tai64n2time | matchup > $QMAILLOG 5>/dev/null
DATE=`date +'%a %d %b'`
(echo "To: [EMAIL PROTECTED]"
echo "From: [EMAIL PROTECTED]"
echo "Subject: Qmail daily report $DATE"
echo ""
zoverall < $QMAILLOG) | qmail-inject
rm -f $QMAILLOG
rm -f $QMAILTMP
-----Original Message-----
From: kbo [mailto:kbo]On Behalf Of Ken Jones
Sent: Wednesday, June 07, 2000 3:29 PM
To: [EMAIL PROTECTED]
Subject: qmailanalog and multilog
Does anyone have a patch to qmailanalog to read
the new multilog time format?
Ken Jones
inter7
I want to block incoming of mails from few domains for few users (POP and
SMTP both) only.
If i put these domain in the badmailfrom file it blocks for all the users.
kindly suggest how it can be done for individuall users.
> I want to block incoming of mails from few domains for few users (POP and SMTP both)
>only.
>
> If i put these domain in the badmailfrom file it blocks for all the users.
>
> kindly suggest how it can be done for individuall users.
You'll need to make a short script,
and add it into these users .qmail file.
You CAN write the commands directly into this file,
but then it will look a bit messy if it's long/many entries.
| if [ "$SENDER" = "[EMAIL PROTECTED]" ]; then exit 99 ;fi
| if [ "$SENDER" = "[EMAIL PROTECTED]" ]; then exit 99 ;fi
./Maildir/.
You'll need to "cut" the $SENDER varibale to get only the domain,
I don't have the perfect way but this one works for SENDERS with only one "@"
(most of them only have one, but you can't trust that!!! )
| DOMAIN=`echo $SENDER | cut -f2 -d\@` ; if [ "$DOMAIN" = "bad.com" ]; then exit 99 ;
|fi
Regards Andr� Paulsberg
On Thu, Jun 08, 2000 at 03:20:25PM +0200, OK 2 NET - Andr� Paulsberg wrote:
> > I want to block incoming of mails from few domains for few users (POP and SMTP
>both) only.
> >
> > If i put these domain in the badmailfrom file it blocks for all the users.
> >
> > kindly suggest how it can be done for individuall users.
>
> You'll need to make a short script,
> and add it into these users .qmail file.
> You CAN write the commands directly into this file,
> but then it will look a bit messy if it's long/many entries.
Ok, I suppose that's one way of doing it.
The other, easier way is to just put the email addresses in badmailfrom.
I.e. instead of putting domain.com in badmailfrom, put [EMAIL PROTECTED]
--Adam
>>> I want to block incoming of mails from few domains for few users (POP and SMTP
>both) only.
>>>
>>> If i put these domain in the badmailfrom file it blocks for all the users.
>
> The other, easier way is to just put the email addresses in badmailfrom.
>
> I.e. instead of putting domain.com in badmailfrom, put [EMAIL PROTECTED]
I belive that is just what i could NOT do, since only some users
should be stopped from getting mail from these domains / users.
Regards Andr� Paulsberg
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
On 9 Jun 00, at 8:40, OK 2 NET - André Paulsberg wrote:
> I belive that is just what i could NOT do, since only some users
> should be stopped from getting mail from these domains / users.
Yeah, that's how I read the original question, too.
Let me add a few generic comments:
There are three places where you can stop the mail: The first one
is inside qmail-smtpd (it refuses to accept the mail altogether), the
second one is in qmail-queue or its wrapper (after seeing the whole
e-mail, your qmail replies with 5xx (permanent error) code), the
third one is in user's .qmail (qmail accepts the mail, and then
generates a bounce and sends it back).
You can see how the bandwidth demands grow with each model
(with #1, you don't get to see a piece of the message; with #2, you
accept it; with #3, you accept it and send it back).
You may want to stop mail from certain users to certain users for
bandwidth reasons - then #1 is probably your option. Or you may
want to protect your users from seeing what they don't want to (but
you don't need to care about bandwidth).
If you want to block uncoditionally from certain people, #1 (or #2)
are just fine; however, if you want to block according to the whole
pair "sender-receiver", you are in trouble; such a database of all
disallowed "sender-receiver" pair will be too large for any practical
purposes, and would be painful to maintain. (You'd also have to
patch qmail-smtpd, but that part is minor.)
Therefore it seems that your option is to filter the mail in user's
.qmail file. (It generally requires that the user volunteers - unless on
your setup, the user can't control his .qmail files.) The overall idea
is to put
|bouncesaying "I don't want to talk to you" [ -r .badsenders] &&
grep --line-regexp --quiet --ignore-case "$SENDER" .badsenders
(that all one one line) before the normal delivery instruction, ie.
./Maildir/
(The file ~/.badsenders contains addresses of refused senders, one
per line.)
(You may also do a similar line for ~/.badsenderdomains.)
(You may also want to test that the ~/.bad* are owned by the
addressee of the mail and are not group- or world-writable - and
temporarily defer mail otherwise.)
Hope this makes sense.
-----BEGIN PGP SIGNATURE-----
Version: PGP 6.0.2 -- QDPGP 2.60
Comment: http://community.wow.net/grt/qdpgp.html
iQA/AwUBOUCH9FMwP8g7qbw/EQI7QQCgyQFuL3YHUDe5mi5gWmVJ6IhsX2YAnirV
W1+P9Gwp+NSyQ2QxEcU7hLGb
=KxqM
-----END PGP SIGNATURE-----
Dear Andru,
Thanks for the info, i checked it for the POP users it is working
fine.
I want to know how it can be done for SMTP users. Kindly suggest.
cordially
Ruchir Chandra
"OK 2 NET - Andr? Paulsberg" <[EMAIL PROTECTED]> on 08/06/2000 06:50:25 PM
To: ruchandra
cc: [EMAIL PROTECTED]
Subject: Re: Blocking of Mail Domain for a specific users
> I want to block incoming of mails from few domains for few users (POP and
SMTP both) only.
>
> If i put these domain in the badmailfrom file it blocks for all the
users.
>
> kindly suggest how it can be done for individuall users.
You'll need to make a short script,
and add it into these users .qmail file.
You CAN write the commands directly into this file,
but then it will look a bit messy if it's long/many entries.
| if [ "$SENDER" = "[EMAIL PROTECTED]" ]; then exit 99 ;fi
| if [ "$SENDER" = "[EMAIL PROTECTED]" ]; then exit 99 ;fi
./Maildir/.
You'll need to "cut" the $SENDER varibale to get only the domain,
I don't have the perfect way but this one works for SENDERS with only one
"@"
(most of them only have one, but you can't trust that!!! )
| DOMAIN=`echo $SENDER | cut -f2 -d\@` ; if [ "$DOMAIN" = "bad.com" ]; then
exit 99 ; fi
Regards Andr? Paulsberg
> Thanks for the info, i checked it for the POP users it is working fine.
>
> I want to know how it can be done for SMTP users. Kindly suggest.
Could you please explain how you identify the users,
is it only done by their address or is it done by IP.
The only method I can think of @ the top of my head is to set
control/virtualdomains & control/rcpthosts
so that the domains you want to block goes to a certain user.
This user could have the same type of script in it's .qmail,
also using the $DEFAULT variable to filter out the unwanted.
All messages that isn't blocket will be stored in this users maildir/box,
and must be resent unless you can do this directly from the script.
Because this method catches mail going to the domains you
are looking to block, you cannot resend them to the same mailserver.
It is very important that you test the script carefully,
to avoid looping or losing E-Mail to these domains.
#stops everyone from sending to [EMAIL PROTECTED]
|if [ "$DEFAULT" = "badguy" ]; then exit 99 ;fi
#stops [EMAIL PROTECTED] from sending to *@domain.com
|if [ "$SENDER" = "[EMAIL PROTECTED]" ]; then exit 99 ;fi
#stops [EMAIL PROTECTED] from sending to [EMAIL PROTECTED]
|if [ "$SENDER" = "[EMAIL PROTECTED]" ]; then if [ "$DEFAULT" = "badguy" ]; then
|exit 99 ;fi ;fi
#delivers the mail temporarly, remember to resend them.
./Maildir/
It's also important to note that any user allowed to send trough your mailserver,
can forge his address bypassing all $SENDER checks and get to his destination.
Regards Andr� Paulsberg
Does anyone know what happened to the ezmlm.org site?
Ken Jones
inter7
also sprach kbo:
>
> Does anyone know what happened to the ezmlm.org site?
ezmlm.org appears to be on hold by NetSol, waiting for payment. Fred Ringel
dropped off the face of the earth some time ago. Fred L. is probably
horribly busy with umpteen things.
Just a little state of disarray... :)
/pg
--
Peter Green : Gospel Communications Network, SysAdmin : [EMAIL PROTECTED]
---
I hope to get Perl 5 out this summer, for certain values of summer.
-- <[EMAIL PROTECTED]>
On Thu, Jun 08, 2000 at 09:41:40AM -0400, Peter Green wrote:
> also sprach kbo:
> >
> > Does anyone know what happened to the ezmlm.org site?
>
> ezmlm.org appears to be on hold by NetSol, waiting for payment. Fred Ringel
> dropped off the face of the earth some time ago. Fred L. is probably
> horribly busy with umpteen things.
>
> Just a little state of disarray... :)
Fred L paid it yesterday.
Mirror here for now: http://ezmlm.x42.com/
/magnus
--
"Security is not about addons. It is about trusting the base of the system,
all the way down to 8 line functions in libc or the kernel."
-- Theo de Raadt
Looking through the life with qmail document it appears that migrating a
sendmail virtusetable over to qmail would be very difficult. If I am
reading it correctly it appears that it uses the format of:
[EMAIL PROTECTED]:prepend
Is there any way to have qmail read the virtualuser table as
[EMAIL PROTECTED]:[EMAIL PROTECTED]
so that a seperate alias didnt need to be created and it could forward the
email to the correct location.
I'm switching more than 15.000 users to Qmail using maildirs,
i'd like to know what is the best tool i can use in order to
convert /var/mail/user mboxes into ~user/Maildir format and to
convert ~user/Mail/folder into ~user/Maildir/.folder format too.
thanks!
Enrique-
> Enrique Vadillo:
> I'm switching more than 15.000 users to Qmail using maildirs,
> i'd like to know what is the best tool i can use in order to
> convert /var/mail/user mboxes into ~user/Maildir format and to
> convert ~user/Mail/folder into ~user/Maildir/.folder format too.
formail from the procmail suite.
clemens
I am no Perl wizard, but this works:
lithium:~$ more /usr/local/bin/convertbox
#!/usr/bin/perl
# usage: convertbox [mbox] [dir for maildir to placed]
#
# ie: convertbox /usr/mail/blah/mbox /var/qmail/mailhome/user/Maildir
require 'stat.pl';
($mbox, $maildir) = @ARGV;
chdir($maildir) || die("fatal: unable to chdir to $maildir.\n");
-d "tmp" || mkdir("tmp",0700) || die("fatal: unable to make tmp/ subdir\n");
-d "new" || mkdir("new",0700) || die("fatal: unable to make new/ subdir\n");
-d "cur" || mkdir("cur",0700) || die("fatal: unable to make cur/ subdir\n");
open(BOX, "<$mbox") || die ("fatal: unable to open $mbox");
while(<BOX>)
{
if (/^From /)
{
$fn = sprintf("new/%d.$$.mbox", $i);
open(MDIR, ">$maildir/$fn") || die("fatal: unable to create new
message");;
chown ($uid,$gid,$fn);
$i++;
};
s/^>From /From /;
print MDIR || die("fatal: unable to write to new message");
};
close(SPOOL);
close(BOX);
You'll need to do some chownage..
On Thu, 8 Jun 2000, Enrique Vadillo wrote:
> I'm switching more than 15.000 users to Qmail using maildirs,
> i'd like to know what is the best tool i can use in order to
> convert /var/mail/user mboxes into ~user/Maildir format and to
> convert ~user/Mail/folder into ~user/Maildir/.folder format too.
>
> thanks!
>
> Enrique-
>
Isn't Russell Nelson's convert-and-create script doing this?
>From the Qmail web page:
Russell Nelson's convert-and-create script will create Maildirs for all
users who receive mail and will convert their /var/spool/mail mbox-format
mailboxes into messages in a Maildir.
Hi,
some days ago another guy mentioned that he has detected wrong permissions
on his RedHat system using
qmail at the wrapper "/usr/sbin/sendmail".
I have reproduced this on 2 systems:
Scenario:
RedHat 6.2 (including linuxconf 1.17r2)
sendmail-RPM deinstall
qmail-SRPM build and install
After original Qmail installation:
/usr/sbin/sendmail 0755 root:qmail
After adding a user with "linuxconf":
/usr/sbin/sendmail 6755 root:root (suid,sgid!)
That's really not Qmails intention that the wrapper runs now with suid root...
So ***everyone using Qmail (or postfix also) on RedHat systems should do
following check***:
1) Test if sendmail-RPM is really not installed:
[root@mail /root]# rpm -qi sendmail
package sendmail is not installed
2) check permissions of wrapper binary "/usr/sbin/sendmail"
[root@mail /root]# ls -al /usr/sbin/sendmail
BAD: -rwsr-sr-x 1 root root 9748 Apr 27 20:13
/usr/sbin/sendmail
GOOD: -rwxr-xr-x 1 root mail 9748 Apr 27 20:13
/usr/sbin/sendmail
3) Re-secure, if BAD:
[root@mail /root]# chown root:mail /usr/sbin/sendmail
4) Turnarounds to prevent re-insecuring:
* do not use "linuxconf" anymore for adding users until RedHat has released
a new version which do no longer reset the owner/group/permissions of
"/usr/sbin/sendmail" (if it's not from the sendmail-RPM)
* setup a cron script with does 3) as often as possible (i.e. all hours or
shorter)
Peter
Three things:
First, linuxconf is NOT owned by RedHat. Therefore, it's not RedHat's
problem. (You might want to convey your concerns to the linuxconf
maintainers)
Second, this is a GREAT example of why one might not want to trust someone
else's RPM packages.
Third, if installing qmail via LWQ, your /usr/sbin/sendmail might very well
be symlinked to /var/qmail/bin/sendmail
(I did it that way)
Regards,
Geordon
(who has finally gone back to Slackware from RedHat)
-----Original Message-----
From: Peter Bieringer [mailto:[EMAIL PROTECTED]]
Sent: Thursday, June 08, 2000 12:17 PM
To: [EMAIL PROTECTED]
Subject: Security warning: using linuxconf(RedHat 6.2) and permissions
of /usr/sbin/sendmail
Importance: High
Hi,
some days ago another guy mentioned that he has detected wrong permissions
on his RedHat system using
qmail at the wrapper "/usr/sbin/sendmail".
I have reproduced this on 2 systems:
Scenario:
RedHat 6.2 (including linuxconf 1.17r2)
sendmail-RPM deinstall
qmail-SRPM build and install
After original Qmail installation:
/usr/sbin/sendmail 0755 root:qmail
After adding a user with "linuxconf":
/usr/sbin/sendmail 6755 root:root (suid,sgid!)
That's really not Qmails intention that the wrapper runs now with suid
root...
So ***everyone using Qmail (or postfix also) on RedHat systems should do
following check***:
1) Test if sendmail-RPM is really not installed:
[root@mail /root]# rpm -qi sendmail
package sendmail is not installed
2) check permissions of wrapper binary "/usr/sbin/sendmail"
[root@mail /root]# ls -al /usr/sbin/sendmail
BAD: -rwsr-sr-x 1 root root 9748 Apr 27 20:13
/usr/sbin/sendmail
GOOD: -rwxr-xr-x 1 root mail 9748 Apr 27 20:13
/usr/sbin/sendmail
3) Re-secure, if BAD:
[root@mail /root]# chown root:mail /usr/sbin/sendmail
4) Turnarounds to prevent re-insecuring:
* do not use "linuxconf" anymore for adding users until RedHat has released
a new version which do no longer reset the owner/group/permissions of
"/usr/sbin/sendmail" (if it's not from the sendmail-RPM)
* setup a cron script with does 3) as often as possible (i.e. all hours or
shorter)
Peter
It isn't the rpm's fault, it is actually linuxconf. Even if you did a
by-the-book (i.e. following Dan's instructions to the letter) qmail install,
linuxconf will follow the /usr/sbin/sendmail link and change the permissions
on /var/qmail/bin/sendmail for you. It does this even if you don't have the
sendmail rpm installed.
To stop it from making this change, I believe you can edit
/usr/lib/linuxconf/redhat/perm and remove the /usr/sbin/sendmail line.
Jim
On Thu, Jun 08, 2000 at 01:22:26PM -0400, VANTASSLE, GEORDON M. (AIT) wrote:
> Three things:
>
> First, linuxconf is NOT owned by RedHat. Therefore, it's not RedHat's
> problem. (You might want to convey your concerns to the linuxconf
> maintainers)
>
> Second, this is a GREAT example of why one might not want to trust someone
> else's RPM packages.
>
> Third, if installing qmail via LWQ, your /usr/sbin/sendmail might very well
> be symlinked to /var/qmail/bin/sendmail
>
> (I did it that way)
>
> Regards,
> Geordon
> (who has finally gone back to Slackware from RedHat)
>
Hi,
I think it's also possible to disable the sendmail module in linuxconf.
regards
christian
On Thu, Jun 08, 2000 at 01:42:32PM -0400, Jim Simmons wrote:
> It isn't the rpm's fault, it is actually linuxconf. Even if you did a
> by-the-book (i.e. following Dan's instructions to the letter) qmail install,
> linuxconf will follow the /usr/sbin/sendmail link and change the permissions
> on /var/qmail/bin/sendmail for you. It does this even if you don't have the
> sendmail rpm installed.
>
> To stop it from making this change, I believe you can edit
> /usr/lib/linuxconf/redhat/perm and remove the /usr/sbin/sendmail line.
In fact, here's what /usr/lib/linuxconf/redhat/perm/mail should read:
/usr/sbin/sendmail root qmail f 755
/etc/mail root root d 755
--
Bruce Guenter <[EMAIL PROTECTED]> http://em.ca/~bruceg/
PGP signature
I have following mail forwarding set up in /var/qmail/alias/:
(1) postmaster -> mail
listmaster -> mail -> admin1, admin2, ...
list-admin -> mail
(2) webmaster -> web
www-admin -> web -> admin1, admin2, ...
www -> web
All the forwarding indicated by "->" is made in /var/qmail/alias/
(individual .qmail-*** files of course); "mail" and "web" are
two regular user accounts, were setup almost identically.
Now the problem is, while mails through "mail" could be distributed
to "admin1, admin2, ...", mails through "web" were all deposited
into its incoming mail box, as if "web -> admin1, admin2,..." alias
didn't exist.
I have checked/compared everything I could think of without getting
a clue what is happening. Could you give some suggestions?
Zhiliang
On Thu, Jun 08, 2000 at 12:20:49PM -0500, Zhiliang Hu wrote:
> I have following mail forwarding set up in /var/qmail/alias/:
>
> (1) postmaster -> mail
> listmaster -> mail -> admin1, admin2, ...
> list-admin -> mail
>
> (2) webmaster -> web
> www-admin -> web -> admin1, admin2, ...
> www -> web
>
> All the forwarding indicated by "->" is made in /var/qmail/alias/
> (individual .qmail-*** files of course); "mail" and "web" are
> two regular user accounts, were setup almost identically.
>
> Now the problem is, while mails through "mail" could be distributed
> to "admin1, admin2, ...", mails through "web" were all deposited
> into its incoming mail box, as if "web -> admin1, admin2,..." alias
> didn't exist.
Could you just post the actual contents of the various .qmail-* files? I, for
one, don't know what " www-admin -> web -> admin1, admin2, ..." means.
Chris
Ok, here they are:
File Content
---------------------------------- -------
/var/qmail/alias/.qmail-postmaster mail
/var/qmail/alias/.qmail-listmaster mail
/var/qmail/alias/.qmail-list-admin mail
/var/qmail/alias/.qmail-webmaster web
/var/qmail/alias/.qmail-www-admin web
/var/qmail/alias/.qmail-www web
/var/qmail/alias/.qmail-mail user1
/var/qmail/alias/.qmail-web user1
---------------------------------- -------
> Date: Thu, 8 Jun 2000 13:31:30 -0400
> From: Chris Johnson <[EMAIL PROTECTED]>
> To: Zhiliang Hu <[EMAIL PROTECTED]>
> Cc: [EMAIL PROTECTED]
> Subject: Re: mail forwarding: alias
>
> On Thu, Jun 08, 2000 at 12:20:49PM -0500, Zhiliang Hu wrote:
> > I have following mail forwarding set up in /var/qmail/alias/:
> >
> > (1) postmaster -> mail
> > listmaster -> mail -> admin1, admin2, ...
> > list-admin -> mail
> >
> > (2) webmaster -> web
> > www-admin -> web -> admin1, admin2, ...
> > www -> web
> >
> > All the forwarding indicated by "->" is made in /var/qmail/alias/
> > (individual .qmail-*** files of course); "mail" and "web" are
> > two regular user accounts, were setup almost identically.
> >
> > Now the problem is, while mails through "mail" could be distributed
> > to "admin1, admin2, ...", mails through "web" were all deposited
> > into its incoming mail box, as if "web -> admin1, admin2,..." alias
> > didn't exist.
>
> Could you just post the actual contents of the various .qmail-* files? I, for
> one, don't know what " www-admin -> web -> admin1, admin2, ..." means.
>
> Chris
>
On Thu, Jun 08, 2000 at 01:29:53PM -0500, Zhiliang Hu wrote:
>
> Ok, here they are:
> File Content
> ---------------------------------- -------
> /var/qmail/alias/.qmail-postmaster mail
> /var/qmail/alias/.qmail-listmaster mail
> /var/qmail/alias/.qmail-list-admin mail
> /var/qmail/alias/.qmail-webmaster web
> /var/qmail/alias/.qmail-www-admin web
> /var/qmail/alias/.qmail-www web
>
> /var/qmail/alias/.qmail-mail user1
> /var/qmail/alias/.qmail-web user1
> ---------------------------------- -------
You said that "mail" and "web" are regular user accounts. If that's the case,
then ~alias/.qmail-mail and ~alias/.qmail-web will never be consulted.
Chris
> > Date: Thu, 8 Jun 2000 13:31:30 -0400
> > From: Chris Johnson <[EMAIL PROTECTED]>
> > To: Zhiliang Hu <[EMAIL PROTECTED]>
> > Cc: [EMAIL PROTECTED]
> > Subject: Re: mail forwarding: alias
> >
> > On Thu, Jun 08, 2000 at 12:20:49PM -0500, Zhiliang Hu wrote:
> > > I have following mail forwarding set up in /var/qmail/alias/:
> > >
> > > (1) postmaster -> mail
> > > listmaster -> mail -> admin1, admin2, ...
> > > list-admin -> mail
> > >
> > > (2) webmaster -> web
> > > www-admin -> web -> admin1, admin2, ...
> > > www -> web
> > >
> > > All the forwarding indicated by "->" is made in /var/qmail/alias/
> > > (individual .qmail-*** files of course); "mail" and "web" are
> > > two regular user accounts, were setup almost identically.
> > >
> > > Now the problem is, while mails through "mail" could be distributed
> > > to "admin1, admin2, ...", mails through "web" were all deposited
> > > into its incoming mail box, as if "web -> admin1, admin2,..." alias
> > > didn't exist.
> >
> > Could you just post the actual contents of the various .qmail-* files? I, for
> > one, don't know what " www-admin -> web -> admin1, admin2, ..." means.
> >
> > Chris
> You said that "mail" and "web" are regular user accounts. If that's the case,
> then ~alias/.qmail-mail and ~alias/.qmail-web will never be consulted.
You mean in qmail the user account precedes system alias?
(in sendmail it is opposite).
But why one alias, ~alias/.qmail-mail, works fine? That was where
I got confused and started to ask ... ;-)
For your further information, none of the two accounts were setup
for mails. i.e. no ~/.qmail whatsoever, no ~/Mail, no ~/Mailbox ..)
Zhiliang
On Thu, Jun 08, 2000 at 03:18:32PM -0500, Zhiliang Hu wrote:
>
> > You said that "mail" and "web" are regular user accounts. If that's the case,
> > then ~alias/.qmail-mail and ~alias/.qmail-web will never be consulted.
>
> You mean in qmail the user account precedes system alias?
> (in sendmail it is opposite).
Yep. See /var/qmail/doc/PIC.local2alias. alias will get control of mail only if
a user account doesn't exist.
> But why one alias, ~alias/.qmail-mail, works fine? That was where
> I got confused and started to ask ... ;-)
I don't know, and couldn't tell you without looking at your whole setup. But if
there's an account called "mail" and there's nothing in users/assign that says
otherwise, ~alias/.qmail-mail won't do anything. If it works in your case, then
something isn't exactly as you described.
Chris
Thank Chris!
There is one more instance: system alias for root works, ignoring
the account ~root ... is there an exception?
Zhiliang
> > You mean in qmail the user account precedes system alias?
> > (in sendmail it is opposite).
>
> Yep. See /var/qmail/doc/PIC.local2alias. alias will get control of mail only if
> a user account doesn't exist.
Chris Johnson <[EMAIL PROTECTED]> wrote:
>Yep. See /var/qmail/doc/PIC.local2alias. alias will get control of mail only
>if a user account doesn't exist.
>> But why one alias, ~alias/.qmail-mail, works fine? That was where I got
>> confused and started to ask ... ;-)
> I don't know, and couldn't tell you without looking at your whole setup. But
> if there's an account called "mail" and there's nothing in users/assign that
> says otherwise, ~alias/.qmail-mail won't do anything. If it works in your
> case, then something isn't exactly as you described.
I could be wrong, but it might be because something about those "regular
accounts" is funny, and qmail doesn't consider it a valid account. The
rules qmail-getpw uses are (from the manpage):
qmail-getpw considers an account in /etc/passwd to be a user if (1) the
account has a nonzero uid, (2) the account's home directory exists (and is
visible to qmail- getpw), and (3) the account owns its home directory.
qmail-getpw ignores account names containing uppercase letters
So if "mail" or "web" has a non-existent home directory, or one they don't
own, the ~alias/.qmail- files might work for those accounts.
Charles
--
----------------------------------------------------------------------- Charles
Cazabon <[EMAIL PROTECTED]> GPL'ed software
available at: http://www.qcc.sk.ca/~charlesc/software/ Any opinions expressed
are just that -- my opinions.
-----------------------------------------------------------------------
> Charles Cazabon:
> >> But why one alias, ~alias/.qmail-mail, works fine? That was where I got
> >> confused and started to ask ... ;-)
>
> > I don't know, and couldn't tell you without looking at your whole setup. But
excusee moi, je suis hercule poirot! je pens que les accounts `mail' et
`user1' sont identical, et `user1' est =root=! oui!
c'est le seulement way les deuz could work!
hercule `clemens' poirot
i am trying to add a bulk list to my server and using this script i get
the runtime error: ( ezmlm-sub: fatal: dir and dot must start with slash
), does anyone know what this means? my script is below. thanks
christopher m downs
#!/bin/sh
## this is to use ezmlm-sub function
## to add a list of e-mail users to
## a particular list.
# <----------------------------------
## example :ListLoc=/var/qmail/alias/lists/listname
$ListLoc=/var/qmail/alias/lists/test6
InputFile=list.txt
##
# <----------------------------------
## pull names from list using @
for name in $(cat $InputFile)
do
echo "Subscribing $name to $ListLoc"
## there is a comment here so i know the execution is out of play.
#ezmlm-sub $listLoc $name
done
## <---------------------------------
# End of File
On Thu, Jun 08, 2000 at 03:19:48PM -0400, cdowns wrote:
> i am trying to add a bulk list to my server and using this script i get
> the runtime error: ( ezmlm-sub: fatal: dir and dot must start with slash
> ), does anyone know what this means? my script is below. thanks
>
> christopher m downs
>
>
> #!/bin/sh
> ## this is to use ezmlm-sub function
> ## to add a list of e-mail users to
> ## a particular list.
> # <----------------------------------
> ## example :ListLoc=/var/qmail/alias/lists/listname
> $ListLoc=/var/qmail/alias/lists/test6
Remove the $ from $ListLoc
The $ is used to reference variables not to define them ...
> InputFile=list.txt
> ##
> # <----------------------------------
> ## pull names from list using @
> for name in $(cat $InputFile)
> do
> echo "Subscribing $name to $ListLoc"
> ## there is a comment here so i know the execution is out of play.
> #ezmlm-sub $listLoc $name
$listLoc is not defined, it's $ListLoc
Variable names are case sensitive ...
> done
> ## <---------------------------------
> # End of File
>
--
http://therookie.dyndns.org
Yesterday the message "warning: trouble marking local/xx/xxxxxx;
message will be delivered twice!" appeared in my log over 1000 times!
This was followed by over 1000 "unable to unlink local/xx/xxxxxx" and
135,000 "trouble opening local/xx/xxxxxx" messages!
This is a daily occurrence for which I cannot determine the cause.
It appears that qmail is marking and unlinking these files and
doesn't know it. The partition is only at 40% use, so disk space
shouldn't be an issue, and the messages do appear to be getting to
their destinations (sometimes more than once), but qmail is trying to
hold on to them. We get about 100,000 emails a day, so it looks like
this problem is showing up about 1% of the time.
Shutting down qmail, queue-fix'ing or manually deleting incomplete
messages, and starting up again remains quiet only for a few minutes
before the cycle kicks in again.
>From this end it looks like a bug in qmail...please tell me there's
something I can fix locally. Thanks.
Oh yeah...running on a Sun E250 Solaris 2.7, 2 CPUs, 1 gig of RAM.
----------------------------------
Nathan Clegg
[EMAIL PROTECTED]
Hi all. A while back I mentioned modifying the qmailmrtg stuff to work
with multilog formatted files and some of you have asked me about them.
They are almost complete .. the mods seem pretty easy really, though I
am not much of a programmer. I think I have it working. The queue script
did not require any changing of course ... and the concurrency script
was easy to fix up. Just a change in the regexp that matches log files.
I am having some trouble with the message bandwidth script though ... it
seems to work when I run it by hand but not when run from cron.
Long story short I am almost done. Just so damn busy, the summer being
our big projects & upgrades time. I will attempt to just provides diffs,
but I have never made a diff before so I guess I have some man pages to
read. If anyone wants to give me a crash course in making diffs I'd
appreciate it. Crash courses are all I have time for these days ...
--
Mark Drummond|ICQ#19153754|mailto:[EMAIL PROTECTED]
UNIX System Administrator|Royal Military College of Canada
The Kingston Linux Users Group|http://signals.rmc.ca/klug/
Saving the World ... One CPU at a Time
Please excuse me if I am terse. I answer dozens of emails every day.
hi,
i would like to forward incoming emails for an special user of a virtual
domain to an external email-address. my emailformat is always i.e.
[EMAIL PROTECTED], which nearly all of my customers want to have.
all emails to vdomain.com are delivered to a local user "vdomain" and
fetched via pop3 by user "vdomain". there is an empty .qmail-default in
/home/vdomain/.
now, if i touch a new .qmail file like i.e. /home/vdomain/.qmail-bob.miller
with i.e. &[EMAIL PROTECTED] inside, mails for [EMAIL PROTECTED] are
still delivered to "vdomain". altering .qmail-bob.miller to .qmail-bob_miller
forwards correctly, but this doesn't fit to my emailformat using a "."
instead of "_". qmail seems not to like a second "." in any dot-qmail files.
is there no way to get forwarding working with the "." ?
--
jens
-----------------------------------------------------------------------------
department computer science, university of dortmund
linux ... life's too short for reboots!
Jens Georg <[EMAIL PROTECTED]> wrote on Fri, 09 Jun 2000:
> is there no way to get forwarding working with the "." ?
Yes, there is a way. Use : instead of the . in the dot-qmail file.
eg. .qmail-bob:miller for an address of "bob.miller".
Regards,
Mikko
--
// Mikko H�nninen, aka. Wizzu // [EMAIL PROTECTED] // http://www.iki.fi/wiz/
// The Corrs list maintainer // net.freak // DALnet IRC operator /
// Interests: roleplaying, Linux, the Net, fantasy & scifi, the Corrs /
The Monkeys are listening.
I just installed the latest ezemlm on my system and have just discovered a
serious problem with a group mailbox.
I have a domain ace.org.nz where all email is put into one mailbox. (I have
normal users as well) This was working well. The domain is setup in the
virtualhosts file and points a mailbox called ace (ie. ace.org.nz:ace)
Yesterday I installed ezmlm on the system and I just received a call saying
that no email is getting through to ace.org.nz. The message I receive is
saying that there is some problem with the subject line, but it doesn't
matter what the subject is I still get the following syslog entries...
Jun 9 11:50:29 holly qmail: [ID 748625 mail.info] 960508229.521238 starting
delivery 13556: msg 842662 to local [EMAIL PROTECTED]
Jun 9 11:50:29 holly qmail: [ID 748625 mail.info] 960508229.521773 status:
local 1/10 remote 0/20
Jun 9 11:50:29 holly qmail: [ID 748625 mail.info] 960508229.585153 delivery
13556: deferral: qmail-inject:_subject:hello:_not_found/
I have no idea where to start looking for this.
background.
I have just installed this box with the latest version of qmail. I use to
run a sgi with the same configuration (group mailbox for ace.org.nz and
ezmlm list server). I have just got this new box up and running about 2
weeks ago to replace the old and setup ezmlm yesterday. The new box is
Solaris 8.
Thanks
Martin
Martin Searancke
CommSoft Group Ltd.
Level 8, CommSoft House
90 Symonds St
Auckland, New Zealand
[EMAIL PROTECTED]
+64 21 778592
*What* you know is not as important as
*who* you know. But what you know about
who you know is where the REAL money is.
(Jonathan D. Colan)
I am wondering if this is a DNS issue, a gauntlet firewall issue, or why
this isn't working.
I have 2 sites in different locations. One has DNS domain: ecorp.com the
other has DNS domain dev.ecorp.com.
Mail works fine to ecorp.com but when trying to deliver to dev.ecorp.com
mail gets rejected by mail.ecorp.com saying that dev.ecorp.com is not in its
rcpthosts. dev.ecorp.com is in the rcpthosts on mail.dev.ecorp.com not
mail.ecorp.com
If I run nslookup
>set type=MX
>ecorp.com
Server: ns2.pnap.net
Address: 206.253.194.97
ecorp.com preference = 10, mail exchanger = mail.ecorp.com
>dev.ecorp.com
Server: ns2.pnap.net
Address: 206.253.194.97
dev.ecorp.com preference = 10, mail exchanger = mail.dev.ecorp.com
Shouldn't DNS deliver this to mail.dev.ecorp.com rather than mail.ecorp.com?
The only other thing I can think is that either I don't understand DNS MX
records for subdomains or the gauntlet firewall that receives this message
first is forwarding it to the other side.
What do you think?
Susan Short
________________________________________________________________________
Get Your Private, Free E-mail from MSN Hotmail at http://www.hotmail.com
Or perhaps your mailserver forwards it automatically to the other site.
Look at your mailserver logs whether the mail was or was not at
mail.dev.ecorp.com
If it was there, then look at the locals/virtualdomains and smtproutes
files on mail.dev.ecorp.com. If they are incorrect (correct is if
locals/virtualdomains contains dev.ecorp.com, and smtproutes does not
contain it). If neither of them contains it, and smtproutes contains a
default entry pointing to mail.ecorp.com, then you know why it turns up
on mail.ecorp.com.
If the previous is not the case, then you probably have a transparent
proxy working somewhere (eg. in the fw)
Regards,
Robert Varga
On Thu, 8 Jun 2000, Susan Short wrote:
> I am wondering if this is a DNS issue, a gauntlet firewall issue, or why
> this isn't working.
>
> I have 2 sites in different locations. One has DNS domain: ecorp.com the
> other has DNS domain dev.ecorp.com.
>
> Mail works fine to ecorp.com but when trying to deliver to dev.ecorp.com
> mail gets rejected by mail.ecorp.com saying that dev.ecorp.com is not in its
> rcpthosts. dev.ecorp.com is in the rcpthosts on mail.dev.ecorp.com not
> mail.ecorp.com
>
> If I run nslookup
> >set type=MX
> >ecorp.com
> Server: ns2.pnap.net
> Address: 206.253.194.97
>
> ecorp.com preference = 10, mail exchanger = mail.ecorp.com
> >dev.ecorp.com
> Server: ns2.pnap.net
> Address: 206.253.194.97
>
> dev.ecorp.com preference = 10, mail exchanger = mail.dev.ecorp.com
>
> Shouldn't DNS deliver this to mail.dev.ecorp.com rather than mail.ecorp.com?
>
> The only other thing I can think is that either I don't understand DNS MX
> records for subdomains or the gauntlet firewall that receives this message
> first is forwarding it to the other side.
>
> What do you think?
>
> Susan Short
> ________________________________________________________________________
> Get Your Private, Free E-mail from MSN Hotmail at http://www.hotmail.com
>
>
On Wed, Jun 07, 2000 at 08:47:46AM -0400, Russell Nelson wrote:
> Peter van Dijk writes:
> > ORBS does not list a machine until it has received a relayed test
> > message.
>
> Then why does Alan suggest that qmail is an open relay by default
> simply because its smtp server accepts more mail than it will deliver?
He is talking about qmail being an open relay when there is no rcpthost
file.
> Why would he care?
This is not the standard 'it accepts so it must be an open relay!' problem.
Greetz, Peter.
--
[EMAIL PROTECTED] - Peter van Dijk [student:developer:madly in love]
As I'm sure you are all aware, qmail's implementation of the LAST command
seems to endlessly confuse several MUAs, especially if they choose to
leave their mail on the server.
Is there any way around this? Any patches?
I know 'LAST' has been deprecated, but we're getting a lot of flack from
our customers that try to use some odd POP clients, like the Yahoo! web
pop client.
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
When I run make check for courier-imap on Solaris7 sparc using gcc-2.95.
I get the following output. Make check doesn't finish: it just
hangs with the last two lines "broken pipe". However, if
I go ahead and install it anyway, courier-imap appears to work fine.
Are the following errors something
to worry about?
Any help would be great,
Kristina
-------------------------------------------------
****************************
* Sanity check in progress *
****************************
INFO: LOGIN, user=user, ip=[127.0.0.1]
INFO: LOGOUT, user=user, ip=[127.0.0.1]
INFO: LOGIN, user=user, ip=[127.0.0.1]
INFO: LOGOUT, user=user, ip=[127.0.0.1]
make[1]: *** [check] Error 1
make[1]: Leaving directory `/usr/local/SRC/IMAP/courier-imap-0.31/imap'
make: *** [check-recursive] Error 1
ldaptest% INFO: LOGIN, user=user, ip=[127.0.0.1]
INFO: LOGOUT, user=user, ip=[127.0.0.1]
Broken Pipe
INFO: LOGIN, user=user, ip=[127.0.0.1]
INFO: LOGOUT, user=user, ip=[127.0.0.1]
Broken Pipe
Broken Pipe
INFO: LOGIN, user=user, ip=[127.0.0.1]
INFO: LOGOUT, user=user, ip=[127.0.0.1]
Broken Pipe
Broken Pipe
INFO: LOGIN, user=user, ip=[127.0.0.1]
INFO: LOGOUT, user=user, ip=[127.0.0.1]
Broken Pipe
Broken Pipe
INFO: LOGIN, user=user, ip=[127.0.0.1]
INFO: LOGOUT, user=user, ip=[127.0.0.1]
Broken Pipe
Broken Pipe
----------------------------------------------
I use qmail with serialmail and fetchmail. I conect
to my ISP with dial up.
All messages for out are stored in
"/var/qmail/alias/pppdir/" and that is OK.
All mesages witch I receive (with
fetchmail) are in "/var/qmail/qlias/pppdir/" too.
And that is problem. Why
this mesages not in maildir of my users??? How
qmail can dislocate this
messages in maildir of my users????
I use vpopmail.
Sinisa Malesevic [EMAIL PROTECTED]
|
HI there,
I was wondering if anyone can help me with this problem, I am
running redhat version 6.1 and I cannot get POP3 connections logging in my
syslog to /var/log/mail
smtp syslog works fine but POP is cause me trouble and I can not see
any referance to POP/syslog in the FAQ's or anything else on the qmail
site...
below is a copy of my start up script to start qmail-pop3d using
Maildir
Any help would be much welcomed:)
#!/bin/sh
#
# Start POP3D
#
tcpserver 0 110 /var/qmail/bin/qmail-popup daemon.supression.net \
/bin/checkpassword /var/qmail/bin/qmail-pop3d Maildir 2>&1 |
/var/qmail/bin/splogger pop3d 3 &
cheers
brendan
#!/bin/sh
#
# Start POP2D
#
tcpserver 0 110 /var/qmail/bin/qmail-popup daemon.supression.net \
/bin/checkpassword /var/qmail/bin/qmail-pop3d Maildir 2>&1 |
/var/qmail/bin/splogger pop3d 3 &
winmail.dat
1. i could't find out, how to get pop3d work with shadow passwords, so i'm
using qpopper [and therefore i have to switch to mailbox format]
So - is it possible to use pop3d with shadow passw?
2. Next annoying problem. My Qmail is up and running. I'm using it with
serialmail. ppp0 connection gets into serious trouble after exactly 20 min.
Everything freezes and in 1 or 2 min i'm disconnected. This never happens BQ
( before Qmail, 2 weeks ago ;-)), so I suppose, it have something to do with
it.
Any idea, how to solve this, how to locate source of trouble? Is it Qmail,
serialmail?
Am I overlooking something?
Thanks
---------------
ico66
---------------
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
On 9 Jun 00, at 8:36, Stefan Beke wrote:
> 1. i could't find out, how to get pop3d work with shadow passwords, so
> i'm using qpopper [and therefore i have to switch to mailbox format]
> So - is it possible to use pop3d with shadow passw?
Yeah; get a patch on www.qmail.org for /bin/checkpassword. (If
your system is PAMified, get a patch for PAMified checkpassword;
I'm using it this way.)
> 2. Next annoying problem. My Qmail is up and running. I'm using it
> with serialmail. ppp0 connection gets into serious trouble after
> exactly 20 min. Everything freezes and in 1 or 2 min i'm disconnected.
> This never happens BQ ( before Qmail, 2 weeks ago ;-)), so I suppose,
> it have something to do with it. Any idea, how to solve this, how to
> locate source of trouble? Is it Qmail, serialmail? Am I overlooking
> something?
The information you provide is insufficient. What does "get into
serious trouble" mean? What do the logs say? What do the
diagnostic tools say?
I'd be really surprised if it's qmail or serialmail - except, of course,
that they trigger a bug in your setup.
-----BEGIN PGP SIGNATURE-----
Version: PGP 6.0.2 -- QDPGP 2.60
Comment: http://community.wow.net/grt/qdpgp.html
iQA/AwUBOUCItVMwP8g7qbw/EQIzKwCg1kLiKzb0LB3uUlNCvSink8bCkQYAoOZ6
CtyCKQsx9XuyXkwS6B1JQwE2
=pUYO
-----END PGP SIGNATURE-----
--
Petr Novotny, ANTEK CS
[EMAIL PROTECTED]
http://www.antek.cz
PGP key ID: 0x3BA9BC3F
-- Don't you know there ain't no devil there's just God when he's drunk.
[Tom Waits]
1. i could't find out, how to get pop3d work with shadow passwords, so i'm
using qpopper [and therefore i have to switch to mailbox format]
So - is it possible to use pop3d with shadow passw?
2. Next annoying problem. My Qmail is up and running. I'm using it with
serialmail. ppp0 connection gets into serious trouble after exactly 20 min.
Everything freezes and in 1 or 2 min i'm disconnected. This never happens BQ
( before Qmail, 2 weeks ago ;-)), so I suppose, it have something to do with
it.
Any idea, how to solve this, how to locate source of trouble? Is it Qmail,
serialmail?
Am I overlooking something?
Thanks
---------------
ico66
---------------
On Fri, Jun 09, 2000 at 04:15:40PM +1000, Brendan Laws wrote:
> HI there,
>
> I was wondering if anyone can help me with this problem, I am
> running redhat version 6.1 and I cannot get POP3 connections logging in my
> syslog to /var/log/mail
>
> smtp syslog works fine but POP is cause me trouble and I can not see
> any referance to POP/syslog in the FAQ's or anything else on the qmail
> site...
>
> below is a copy of my start up script to start qmail-pop3d using
> Maildir
>
> Any help would be much welcomed:)
>
> #!/bin/sh
> #
> # Start POP3D
> #
> tcpserver 0 110 /var/qmail/bin/qmail-popup daemon.supression.net \
> /bin/checkpassword /var/qmail/bin/qmail-pop3d Maildir 2>&1 |
> /var/qmail/bin/splogger pop3d 3 &
I assume you had a line continuation character "\" after the "2>&1 |"
above? Also, why do you have a "3" all by itself at the end, before
the "&" character? There are also some missing options to tcpserver.
Here is my working /etc/rc.d startup script fragment for this, if
you wish to compare. Hope it helps some.
case "$1" in
start)
echo -n "Starting qmail pop server"
/usr/local/bin/tcpserver -v -R 0 pop3 /var/qmail/bin/qmail-popup \
moon.demibit.com \
/bin/checkpassword /var/qmail/bin/qmail-pop3d Maildir 2>&1 | \
/var/qmail/bin/splogger pop3d &
Sincerely,
Neal
>
> cheers
>
> brendan
>
>
>
>
>
>
>
>
>
>
>
>
>
>
> #!/bin/sh
> #
> # Start POP2D
> #
> tcpserver 0 110 /var/qmail/bin/qmail-popup daemon.supression.net \
> /bin/checkpassword /var/qmail/bin/qmail-pop3d Maildir 2>&1 |
> /var/qmail/bin/splogger pop3d 3 &
Thank you, Clemence, for your support,
but I'm not automatically starting qmail... and no qmail process is visible
with "ps -ef" before I start qmail with "/etc/rc.d/svscan start"...
I've followed the instructions in "Qmail 2 HOW-TO" and "A life with Qmail",
downloaded from www.qmail.org.
In any case I will re-check my configuration.
Thank you again,
luca
clemensF wrote:
> > Luca Zancan:
>
> > What should I verify???
>
> you have set up qmail somehow, so there is a line w.r.t. qmail in your
> start up files. you must have started two server processes, usually due to
> a commandline ending in '&' where it shouldn't.
>
> clemens
--
__________________________________________________
Luca Zancan
Logica S.r.l.
e-mail [EMAIL PROTECTED]
URL http://www.logicaonline.com
__________________________________________________
hi
how can set up a quota to all my users mailbox? please help
Verna Vergara wrote:
>
> hi
>
> how can set up a quota to all my users mailbox? please help
Seems to me you can just use the normal unix per-user quota
mechanism. qmail-local runs _as_ the user to which it's
delivering.
Eric
Hi,
Where can I found advice on what characteristic my
mail-sever should have, to be reliable.It must manage about
500 mailboxes.
What about the mail-server characteristic should have, if
i use httpd (Apache) on it ?
_______________________________________________________
Vendez tout... aux ench�res - http://www.caraplazza.com
