qmail Digest 6 Jul 2000 10:00:00 -0000 Issue 1054
Topics (messages 44191 through 44268):
Converting mbox to maildir.
44191 by: Morten Liebach
44198 by: Ronny Haryanto
Re: spam and well known smtp servers
44192 by: Cerberus - the Guardian of Hades
44205 by: Rogerio Brito
44221 by: Paul Jarc
44234 by: clemensF
44235 by: clemensF
44239 by: clemensF
44256 by: David Benfell
qmail-start
44193 by: Dennis Robertson
44222 by: Paul Jarc
Re: URGENT!!! HELP!!! HP-UX fault
44194 by: Dave Kitabjian
44195 by: Eldar Imangulov
44197 by: Dave Kitabjian
44202 by: Dave Sill
44211 by: Kvazimodo
Re: tcpserver & alpha linux problems
44196 by: Hubbard, David
Re: Error message - Again
44199 by: Dave Sill
Clearing "dead" mail from queues
44200 by: Barry Dwyer
44232 by: Dave Sill
security issue
44201 by: John Steniger
44207 by: Aaron L. Meehan
44209 by: Scott Gifford
Re: qmail and dial-on-demand
44203 by: Paul Jarc
Re: qmailq problem
44204 by: Dave Sill
44208 by: Steffan Hoeke
44212 by: Dave Sill
Re: The most secure POP server
44206 by: Scott Gifford
44257 by: clemensF
qmail on Digital UNIX 4.0D -- syslog problems
44210 by: Bj�rn Nordb�
Trying to get QMTP protocol to work....
44213 by: Igor
CNAME_lookup_failed_temporarily._(#4.4.3)
44214 by: Claudinei Luis Bianchini
44215 by: Dave Sill
44263 by: Robert Sander
Re: does qmail+ezmlm divid subscribers in "chunks" by domain?
44216 by: Magnus Bodin
Mails vanished when remote2local via fetchmail
44217 by: Karl Voit
44224 by: Karl Voit
44226 by: Dave Sill
44236 by: Karl Voit
44240 by: Charles Cazabon
Re: Bounce questions
44218 by: Dave Sill
Re: tcprules, rcpthost, ip address problem
44219 by: Tetsu Ushijima
44238 by: Barry Dwyer
Re: Masquerading while sending remote mail over ISP
44220 by: Tetsu Ushijima
44244 by: bbrade.arco.de
Changing bounce message
44223 by: Ben Beuchler
44227 by: Magnus Bodin
44229 by: Chad Day
44231 by: Ben Beuchler
44233 by: Dave Sill
Re: qmail install question
44225 by: Dave Sill
Re: QMAIL delivery delay problem
44228 by: Dave Sill
Re: Moving vpopmail users
44230 by: Dave Sill
44243 by: Charles Boening
Re: email error from outlook express
44237 by: Einar Bordewich
rejecting subscribe/unsubscribe requests
44241 by: Hand, Brian C.
44242 by: Paul Jarc
.qmail
44245 by: Eddie Greer
44266 by: Steffan Hoeke
no more splogger
44246 by: M.B.
44247 by: Adam McKenna
44248 by: Mark Mentovai
44249 by: Adam McKenna
44250 by: M.B.
44251 by: Mark Mentovai
44252 by: Mark Mentovai
44253 by: Adam McKenna
44254 by: M.B.
44255 by: Mark Mentovai
44258 by: clemensF
44259 by: Adam McKenna
44260 by: clemensF
Re: mail flood
44261 by: Eric Cox
problem with qmailadmin
44262 by: wars.telkom.net
Muchos "warning: trouble opening remote/local"...
44264 by: Hajime Lucky Okada
Large todo slows down qmail-send
44265 by: Yusuf Goolamabbas
Help plz, How to delete messages??
44267 by: david.heydari.sl.se
Re: Debian GNU/Linux (potato) Packages: var-qmail
44268 by: Gerrit Pape
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]
----------------------------------------------------------------------
Hi
I have used procmail to deliver to ~/Mail/* for a long time. There's a
lot of mail in mbox-format that I would like to convert (actually 20
mbox-files, gee!) in one go, like:
$ convert -R ~/Mail ~/Maildir
or something like that.
I couldn't find any programs/scripts for that anywherei, any ideas?
(I've looked at mbox2maildir, but as far as I could tell it didn't work
like that, but I'm not really sure).
Also; someone on this list told me that procmail can do maildirs, and
I've now upgraded to v3.15pre, but can't find any references to maildir
in the docs ($MAILDIR, yes, but not maildir-format), is it really just
to append a '/' to the folders i sort my mail into, remove locking, and
run procmail from ~/.qmail?
Thank you very much for your time.
Regards
Morten
--
Morten Liebach <[EMAIL PROTECTED]> ; http://home1.stofanet.dk/liebach
"Our scientific power has outrun our spiritual power. We have guided
missiles and misguided men (Martin Luther King, Jr.)"
On 05-Jul-2000, Morten Liebach wrote:
> lot of mail in mbox-format that I would like to convert (actually 20
> mbox-files, gee!) in one go, like:
>
> $ convert -R ~/Mail ~/Maildir
>
> or something like that.
> I couldn't find any programs/scripts for that anywherei, any ideas?
> (I've looked at mbox2maildir, but as far as I could tell it didn't work
> like that, but I'm not really sure).
for m in ~/Mail/* ~/Maildir ; do mbox2maildir $m [..whatever..] ; done
> Also; someone on this list told me that procmail can do maildirs, and
> I've now upgraded to v3.15pre, but can't find any references to maildir
> in the docs ($MAILDIR, yes, but not maildir-format), is it really just
> to append a '/' to the folders i sort my mail into, remove locking, and
> run procmail from ~/.qmail?
Yes.
Ronny
i need to unsubscribe:
[EMAIL PROTECTED]
[EMAIL PROTECTED]
[EMAIL PROTECTED]
from this list as he is no longer a user at this server. please help.
regards,
mark
On Wed, 5 Jul 2000, Erwin Hoffmann wrote:
> Hi again,
>
> At 22:37 4.7.2000 +0200, Andre Oppermann wrote:
> >Erwin Hoffmann wrote:
> >>
> >> Hi,
> >>
> >> since I'm dealing with the SPAMCONTROL patch, I would like to comment your
> >> problem:
> >>
> >> 1. You are right. Within the filtering mechanisms a logical "AND" scheme is
> >> missing. To implement this requires some attention.
> >>
> >> 2. Principally the following checks could be applied:
> >>
> >> Logic:
> >> a) The envelope's MAIL FROM: address has to be taken.
> >> b) From TCPENV the REMOTEIP has to be taken (=> real Sender IP)
> >> c) By means of a DNS A-Lookup(MAIL FROM: address) the (let's call it)
> >> pretended IP address has to be evaluated.
> >>
> >> Assumption:
> >> For legitamate E-Mails both IP addresses belong (usually) to the same IP
> >> subnet. However, one has to define a range of significant IP address bits
> >> to evaluate (common in the CIDR scheme).
> >
> >Unfortunatly this assumption is pretty much flawed. For example I have
> >two IP ranges, 195.134.128/19 and 62.48.0.0/19. Now my customers are
> >usually in the 195 range but my mail servers are in the 62 range. So
> >how do you propose to handle that?
>
> Yes, I know about that. The other attempt is to use static IP adresses as
> Markus' proposed. Both schemes could be combined. Let's assume we have an
> additional control file ./stmpallowedfrom:
>
> hotmail.com:195.111.222.200/19 (address range)
> fehcom.de:195.162.195.1,195.162.195.2 (list of static ip addresses)
>
> This would give you some possibilty without the need to really now what are
> the IP adresses of an SMTP sender. The address parsing is a little tricky.
>
>
> eh.
>
> >
> >> Result:
> >> => Comparing both IP addresses would effectively eliminate reception of
> >> E-mail thru 3rd party relays, as in your case.
> >>
> >> I think about but don't promise anything. There are other items on my
> agenda.
> >
> >--
> >Andre
> >
> +-----------------------------------------------------------------------+
> | fff hh http://www.fehcom.de Dr. Erwin Hoffmann |
> | ff hh |
> | ff eee hhhh ccc ooo mm mm mm Wiener Weg 8 |
> | fff ee ee hh hh cc oo oo mmm mm mm 50858 Koeln |
> | ff ee eee hh hh cc oo oo mm mm mm |
> | ff eee hh hh cc oo oo mm mm mm Tel 0221 484 4923 |
> | ff eeee hh hh ccc ooo mm mm mm Fax 0221 484 4924 |
> +-----------------------------------------------------------------------+
>
On Jul 04 2000, Markus Stumpf wrote:
> But this is exactly the point.
> Valid (e.g.!!!) hotmail.com eMails should come from an outgoing
> hotmail.com smtp server. If they don't they're most probably faked
> sender addresses used by spammers.
No, they should not.
For instance, all my e-mails use iname.com as the envelope and
as the From: field, but I don't send mail from them (in fact,
they are in another country); I use my ISP's relays.
The same applies to everybody that uses a forwarder address
for their e-mails and so you (and your customers) won't be
able to receive such e-mails if you block in that way.
In fact, I never use my real e-mail address because it's
constantly changing.
> There is not any switch of tcpserver that helps detect this and
> there is no rule that you can specify in a cdb file that prevents
> this spam, yet.
I guess that this is one of the harder wars against spammers,
for one can never know if the sending side is really a
legitimate user or if it is a disguised spammer.
[]s, Roger...
--
=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=
Rogerio Brito - [EMAIL PROTECTED] - http://www.ime.usp.br/~rbrito/
Nectar homepage: http://www.linux.ime.usp.br/~rbrito/nectar/
=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=
Cerberus - the Guardian of Hades writes:
> i need to unsubscribe:
>
> [EMAIL PROTECTED]
> [EMAIL PROTECTED]
> [EMAIL PROTECTED]
>
> from this list as he is no longer a user at this server. please help.
0. Arrange for mail to those addresses to be delivered somewhere where
you can get to it.
1. Send mail to [EMAIL PROTECTED],
[EMAIL PROTECTED], and
[EMAIL PROTECTED]
2. Follow the directions given in the responses. (The responses will
go to the addresses you're trying to unsubscribe, which is why you
need to redirect his mail first.)
paul
> wolfgang zeikat:
> http://spamcop.net offers handy online forms
i have used all sorts of anti-spam tricks, but presently i just look at the
headers of a spam-mail trying to spot from which domain it really originated
by scanning the recieved-lines and use "[EMAIL PROTECTED]" as well
as postmaster for chinese or mexican or whatever open relay domains without
abuse adresses. this procedure is faster then any automatix.
clemens
> Rogerio Brito:
> For instance, all my e-mails use iname.com as the envelope and
> as the From: field, but I don't send mail from them (in fact,
> they are in another country); I use my ISP's relays.
my spam peeked up when i got myself an iname.com-account. i think they
sell their email-lists to spammers. i have a friend with a hotmail-
account, and another with a yahoo-account, but nobodu with iname, and
i block them on my private system. tough if someone wants to reach me...
clemens
> Cyril Bitterich:
> But there is a good Point in you proposal. Maybe you just wanted to
> reject the mail with a notification that you do not accept this mail
> because they are not sent via Hotmail.
that's dangerous. my experience told me never to answer suspect spammers.
clemens
On Wed, Jul 05, 2000 at 09:41:50PM +0200, clemensF wrote:
>
> that's dangerous. my experience told me never to answer suspect spammers.
>
As I recall, the argument is that by responding, you confirm that the
e-mail address is valid. I can't say I've dealt with enough spam to
have relevant experience.
--
David Benfell
[EMAIL PROTECTED]
ICQ 59438240 [e-mail first for access]
---
There are no physicists in the hottest parts of hell, because the
existence of a "hottest part" implies a temperature difference, and
any marginally competent physicist would immediately use this to
run a heat engine and make some other part of hell comfortably cool.
This is obviously impossible.
-- Richard Davisson
[from fortune]
Hello List,
I am back after a disaster which caused a complete loss of all data
including backups. I am trying to reinstate my previous
mutt-qmail-fetchmail-procmail setup but unlike the first time I cannot
do an error-free install of qmail.
Firstly as user when I open a term I get the message:
env: qmail-start: Permission denied.
I have followed both LWQ and the how-to and have checked permissions
without finding what is wrong.
Secondly, when I open a term I get a number like [1] 27087 in the top
left corner, caused by the csh -cf '/var/qmail/rc &' script I added to
.bashrc as per the install notes para 14. Last time I managed to
dispense with this but I can't remember how.
Can anyone assist please? Thank you.
--
Dennis Robertson 2/2 Sylvia Street NOOSAVILLE QLD 4566
Phone: 61 7 54742343 Mob: 0419 535539
Dennis Robertson writes:
> Firstly as user when I open a term I get the message:
> env: qmail-start: Permission denied.
> I have followed both LWQ and the how-to and have checked permissions
> without finding what is wrong.
> Secondly, when I open a term I get a number like [1] 27087 in the top
> left corner, caused by the csh -cf '/var/qmail/rc &' script I added to
> .bashrc as per the install notes para 14.
These are two symptoms of the same problem. /var/qmail/rc should be
run as part of *system* startup, not user login. Normal users don't
have execute permission for qmail-start, thus your first symptom. The
second is simply what bash does when it starts a job in the
background: it prints the job number and PID. You can suppress this
by starting the job from a subshell:
$ (foo&)
But in this case, the command shouldn't be in your .bashrc at all.
paul
Would you mind also posting the contents of your file, /var/qmail/rc?
Thanks,
Dave
> -----Original Message-----
> From: Eldar Imangulov [mailto:[EMAIL PROTECTED]]
> Sent: Tuesday, July 04, 2000 2:58 PM
> To: [EMAIL PROTECTED]
> Subject: URGENT!!! HELP!!! HP-UX fault
>
>
> Hello ppl!
>
> I have
> HP-UX web1 B.11.00 U 9000/800 610339382 unlimited-user license
>
> my qmail start script runs Ok, but qmail stops. When I
> restart qmail deamon
> manualy it keeps runing.
>
> here is what I run:
> #!/sbin/sh
> #
> # /etc/rc*.d/S**qmail - Start/Stop the qmail daemon
> #
>
> PATH=/usr/bin:/bin:/var/qmail/bin:/var/qmail/conf:$PATH
>
> case $1 in
> "start")
> # csh -cf '/var/qmail/rc &' && echo -n ' qmail'
> csh -cf '/var/qmail/bin/qmail-start ./Mailbox
> splogger qmail &' &&
> echo -n ' qmail'
> sleep 10
> ;;
> "stop")
> pid=`/usr/bin/ps -e | /usr/bin/grep qmail-send |
> /usr/bin/sed -e
> 's/^ *//' -e 's/ .*//'`
> if test "$pid"
> then
> kill $pid
> fi
> ;;
> "start_msg")
> echo "Starting qmail"
> ;;
> "stop_msg")
> echo "Stopping qmail"
> ;;
> *)
> echo "usage: /sbin/init.d/qmail {start|stop}"
> ;;
> esac
>
>
> Any ideas?
>
>
> ================================
> Regards,
> Eldar Imangulov
>
>
>
here it is:
#!/sbin/sh
# Using splogger to send the log through syslog.
# Using qmail-local to deliver messages to ~/Mailbox by default.
exec env - PATH="/var/qmail/bin:$PATH" \
/var/qmail/bin/qmail-start ./Mailbox splogger qmail &
================================
Regards,
Eldar Imangulov
([EMAIL PROTECTED])
From: Dave Kitabjian <[EMAIL PROTECTED]>
To: 'Eldar Imangulov' <[EMAIL PROTECTED]>; <[EMAIL PROTECTED]>
Sent: Wednesday, July 05, 2000 4:38 PM
Subject: RE: URGENT!!! HELP!!! HP-UX fault
> Would you mind also posting the contents of your file, /var/qmail/rc?
>
> Thanks,
>
> Dave
>
> > -----Original Message-----
> > From: Eldar Imangulov [mailto:[EMAIL PROTECTED]]
> > Sent: Tuesday, July 04, 2000 2:58 PM
> > To: [EMAIL PROTECTED]
> > Subject: URGENT!!! HELP!!! HP-UX fault
> >
> >
> > Hello ppl!
> >
> > I have
> > HP-UX web1 B.11.00 U 9000/800 610339382 unlimited-user license
> >
> > my qmail start script runs Ok, but qmail stops. When I
> > restart qmail deamon
> > manualy it keeps runing.
> >
> > here is what I run:
> > #!/sbin/sh
> > #
> > # /etc/rc*.d/S**qmail - Start/Stop the qmail daemon
> > #
> >
> > PATH=/usr/bin:/bin:/var/qmail/bin:/var/qmail/conf:$PATH
> >
> > case $1 in
> > "start")
> > # csh -cf '/var/qmail/rc &' && echo -n ' qmail'
> > csh -cf '/var/qmail/bin/qmail-start ./Mailbox
> > splogger qmail &' &&
> > echo -n ' qmail'
> > sleep 10
> > ;;
> > "stop")
> > pid=`/usr/bin/ps -e | /usr/bin/grep qmail-send |
> > /usr/bin/sed -e
> > 's/^ *//' -e 's/ .*//'`
> > if test "$pid"
> > then
> > kill $pid
> > fi
> > ;;
> > "start_msg")
> > echo "Starting qmail"
> > ;;
> > "stop_msg")
> > echo "Stopping qmail"
> > ;;
> > *)
> > echo "usage: /sbin/init.d/qmail {start|stop}"
> > ;;
> > esac
> >
> >
> > Any ideas?
> >
> >
> > ================================
> > Regards,
> > Eldar Imangulov
> >
> >
> >
>
Hmm. My untrained eye isn't seeing anything offhand, but perhaps the
gurus here can comment.
You might start isolating the problem by removing the "&& echo -n '
qmail'" from your script, and running it again. Also, look in
/var/log/maillog; are there any messages being produced?
Dave
> -----Original Message-----
> From: Eldar Imangulov [mailto:[EMAIL PROTECTED]]
> Sent: Wednesday, July 05, 2000 8:40 AM
> To: Dave Kitabjian; [EMAIL PROTECTED]
> Subject: Re: URGENT!!! HELP!!! HP-UX fault
>
>
> here it is:
>
> #!/sbin/sh
>
> # Using splogger to send the log through syslog.
> # Using qmail-local to deliver messages to ~/Mailbox by default.
>
> exec env - PATH="/var/qmail/bin:$PATH" \
> /var/qmail/bin/qmail-start ./Mailbox splogger qmail &
>
>
> ================================
> Regards,
> Eldar Imangulov
> ([EMAIL PROTECTED])
>
>
>
> From: Dave Kitabjian <[EMAIL PROTECTED]>
> To: 'Eldar Imangulov' <[EMAIL PROTECTED]>; <[EMAIL PROTECTED]>
> Sent: Wednesday, July 05, 2000 4:38 PM
> Subject: RE: URGENT!!! HELP!!! HP-UX fault
>
>
> > Would you mind also posting the contents of your file,
> /var/qmail/rc?
> >
> > Thanks,
> >
> > Dave
> >
> > > -----Original Message-----
> > > From: Eldar Imangulov [mailto:[EMAIL PROTECTED]]
> > > Sent: Tuesday, July 04, 2000 2:58 PM
> > > To: [EMAIL PROTECTED]
> > > Subject: URGENT!!! HELP!!! HP-UX fault
> > >
> > >
> > > Hello ppl!
> > >
> > > I have
> > > HP-UX web1 B.11.00 U 9000/800 610339382 unlimited-user license
> > >
> > > my qmail start script runs Ok, but qmail stops. When I
> > > restart qmail deamon
> > > manualy it keeps runing.
> > >
> > > here is what I run:
> > > #!/sbin/sh
> > > #
> > > # /etc/rc*.d/S**qmail - Start/Stop the qmail daemon
> > > #
> > >
> > > PATH=/usr/bin:/bin:/var/qmail/bin:/var/qmail/conf:$PATH
> > >
> > > case $1 in
> > > "start")
> > > # csh -cf '/var/qmail/rc &' && echo -n ' qmail'
> > > csh -cf '/var/qmail/bin/qmail-start ./Mailbox
> > > splogger qmail &' &&
> > > echo -n ' qmail'
> > > sleep 10
> > > ;;
> > > "stop")
> > > pid=`/usr/bin/ps -e | /usr/bin/grep qmail-send |
> > > /usr/bin/sed -e
> > > 's/^ *//' -e 's/ .*//'`
> > > if test "$pid"
> > > then
> > > kill $pid
> > > fi
> > > ;;
> > > "start_msg")
> > > echo "Starting qmail"
> > > ;;
> > > "stop_msg")
> > > echo "Stopping qmail"
> > > ;;
> > > *)
> > > echo "usage: /sbin/init.d/qmail {start|stop}"
> > > ;;
> > > esac
> > >
> > >
> > > Any ideas?
> > >
> > >
> > > ================================
> > > Regards,
> > > Eldar Imangulov
> > >
> > >
> > >
> >
>
>
"Eldar Imangulov" <[EMAIL PROTECTED]> wrote:
>my qmail start script runs Ok, but qmail stops.
When? Shortly after rebooting?
>When I restart qmail deamon manualy it keeps runing.
Until you reboot?
If so, it sounds like you need to disassociate qmail from the
controlling tty, e.g. by "nohup"'ing it:
nohup '/var/qmail/bin/qmail-start ./Mailbox splogger qmail &' && echo -n ' qmail'
The csh should be doing that automatically, but maybe HP's csh is
different.
-Dave
> >my qmail start script runs Ok, but qmail stops.
>
> When? Shortly after rebooting?
can't see when but when after the login into the system right after the
reboot and say "ps -e | grep qmail" I see nothing.
> >When I restart qmail deamon manualy it keeps runing.
>
> Until you reboot?
Yes, untill next reboot. Until that it runs with the system.
> If so, it sounds like you need to disassociate qmail from the
> controlling tty, e.g. by "nohup"'ing it:
>
> nohup '/var/qmail/bin/qmail-start ./Mailbox splogger qmail &' &&
echo -n ' qmail'
>
> The csh should be doing that automatically, but maybe HP's csh is
> different.
>
> -Dave
looks like it work ;-)))
thanks a lot
Hey thanks a lot Wayne, that fixed my problem.
And here I was ready to blame the alpha. :-)
Dave
-----Original Message-----
From: Wayne Chan
To: Hubbard, David
Sent: 7/3/00 11:14 PM
Subject: Re: tcpserver & alpha linux problems
If you have setup your qmail according to life-with-qmail, try
increasing your softlimit to 5000000 instead of 2000000, it will help.
"Hubbard, David" wrote:
>
> 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
Roberto Samarone Ara�jo (RSA) <[EMAIL PROTECTED]> wrote:
>I don't have any alias ... If a remote host send me an email , the qmail
>doesn't put it in Maildir ... it logs the error message :
>
> delivery 38: deferral: Unable_to_chdir_to_maildir._(#4.2.1)/
Did you check ~alias/Maildir? It's not just used for aliases...
-Dave
I had to re-compile qmail. Prior to the recompile, there were 10
messages (all for local delivery) in 'todo'. After the recompile, with
qmail running properly, those 10 have moved to the queue but are not
being delivered. The log is showing the same error message for all -
"wrong owner" (or something very similar - I can't get acess to the logs
as I write this).
How do I clear the queue of these messages? I don't care if they get
deleted in the process.
Thanks,
Barry
Barry Dwyer <[EMAIL PROTECTED]> wrote:
>How do I clear the queue of these messages? I don't care if they get
>deleted in the process.
You have several choices:
1) Do nothing: they'll be purged automatically either by being
delivered or bounced.
2) Stop qmail, delete the queue files associated with the messages,
restart qmail.
3) "touch" the queue files associated with the messages a week into
the past and send qmail-send an ALRM signal. They'll bounce
immediately.
-Dave
Hello,
Running a network test against my recent qmail installation, I get reports
on the mailto programs hole, which allows users to telnet to port 25 and
issue:
MAIL FROM: root@this_host
RCPT: <any program>
This allows users to potentially execute any command with root authority.
The warning came with the caveat that this may not be an issue, as some
MTA's simply drop these messages silently.
Does anyone know how qmail handles this? Is this an issue with qmail, or is
qmail one of the exceptions?
Thanks.
Quoting John Steniger ([EMAIL PROTECTED]):
> Running a network test against my recent qmail installation, I get reports
> on the mailto programs hole, which allows users to telnet to port 25 and
> issue:
>
> MAIL FROM: root@this_host
> RCPT: <any program>
Huh. I've never heard of this exploit! Now, that doesn't mean the
exploit doesn't exist, or didn't, at some particular time, regarding
some particular MTA. I could believe sendmaul would have an exploit
like that. heh.
> This allows users to potentially execute any command with root authority.
> The warning came with the caveat that this may not be an issue, as some
> MTA's simply drop these messages silently.
It's probably assuming that since qmail didn't return an error code
that it could be vulnerable. That's not relevent with qmail since, as
you know, stock qmail will accept all messages unless some other rule
blocks you, i.e. badmailfrom.
> Does anyone know how qmail handles this? Is this an issue with qmail, or is
> qmail one of the exceptions?
qmail would not be vulnerable to any exploit like that unless you made
yourself vulnerable, and most would argue that you then not classify
it as a qmail vulnerability. Perhaps you have "| hackme" in
~alias/.qmail-hackme, so a rcpt to:<hackme> gets you in trouble. Of
course hackme will only run as user alias unless its setuid something,
so program deliveries are limited unless you or your software really
goof up.
qmail doesn't deliver to root, so nothing in ~root/.qmail can get you
clobbered, either.
good luck,
Aaron
It is not an issue. I don't remember if qmail will silently drop
these messages or return a bounce for them, but it most certainly will
not run any programs as root because of them.
----ScottG.
John Steniger <[EMAIL PROTECTED]> writes:
> Hello,
>
> Running a network test against my recent qmail installation, I get reports
> on the mailto programs hole, which allows users to telnet to port 25 and
> issue:
>
> MAIL FROM: root@this_host
> RCPT: <any program>
>
> This allows users to potentially execute any command with root authority.
> The warning came with the caveat that this may not be an issue, as some
> MTA's simply drop these messages silently.
>
> Does anyone know how qmail handles this? Is this an issue with qmail, or is
> qmail one of the exceptions?
>
> Thanks.
[EMAIL PROTECTED] writes:
> 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?
man tcprules. If you have your own block of IP addresses for your
home net, you could use somthing like:
a.b.c.:allow
:deny
Otherwise:
a0.b0.c0.d0:allow
a1.b1.c1.d1:allow
... one for each address in your network
:deny
paul
Steffan Hoeke <[EMAIL PROTECTED]> wrote:
>What *does* the last number in
>@40000000395b7d5233ba0ecc delivery 123: success: did_1+0+0/
>stand for ?
>
>The first number is a local delivery
>The second number is a remote delivery
>The third number is ...... ?
program deliveries
-Dave
On Wed, Jul 05, 2000 at 11:41:16AM -0400, Sill, Dave wrote:
> Steffan Hoeke <[EMAIL PROTECTED]> wrote:
>
> >What *does* the last number in
> >@40000000395b7d5233ba0ecc delivery 123: success: did_1+0+0/
> >stand for ?
> >
> >The first number is a local delivery
> >The second number is a remote delivery
> >The third number is ...... ?
>
> program deliveries
Could you please elaborate ?
by program do you mean a |preline e.a. in a .qmail file or something
else ?
> -Dave
TIA,
Steffan
--
http://therookie.dyndns.org
Steffan Hoeke <[EMAIL PROTECTED]> wrote:
>On Wed, Jul 05, 2000 at 11:41:16AM -0400, Sill, Dave wrote:
>> Steffan Hoeke <[EMAIL PROTECTED]> wrote:
>>
>> >What *does* the last number in
>> >@40000000395b7d5233ba0ecc delivery 123: success: did_1+0+0/
>> >stand for ?
>> >
>> >The first number is a local delivery
>> >The second number is a remote delivery
>> >The third number is ...... ?
>>
>> program deliveries
>
>Could you please elaborate ?
>by program do you mean a |preline e.a. in a .qmail file or something
>else ?
Yeah, .qmail lines starting with a "|".
Actually, the first number is *file* deliveries (mbox or maildir) and
the second number is *forward* deliveries (lines starting with "&" or
[a-zA-z0-9]), which coule be either local or remote.
-Dave
"clemensF" <[EMAIL PROTECTED]> writes:
> > Scott Gifford:
>
> > > 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.
>
> that i don't understand. i can get my password anytime from any provider,
> just askin', maybe answering "secret questions". what makes you think
> they don't store plaintext-passwords?
Just a guess; if the provider that won't provide APOP can provide
you with plaintext passwords, then I don't know what their excuse is.
:)
-----ScottG.
> Scott Gifford:
> Just a guess; if the provider that won't provide APOP can provide
> you with plaintext passwords, then I don't know what their excuse is.
well i told you mom! first they asked what apop is and when i explained
it and hinted i'd want it -- pause -- and then they said they would not change
their setup just for me! :(
clemens
Hello,
I fixed the /sbin/loader errors I mentioned before the weekend
by increasing the softlimit to 50000000, but now I have another
problem:
According to TEST.delivery qmail should syslog a line whenever
it starts. In my logs, I can't find anything, even though all
of the qmail processes seems to start nicely shortly after I
run /sbin/init.d/svscan.
The reason I ask here is that the trysyslog-program that comes
with the qmail-distribution works fine, ie. it syslogs a "foo"
line to the mail-facility.
My /etc/syslog.conf should make syslog log debug-level and above
from kern, user, mail, daemon, auth, syslog, lpr and binary, and
as far as I can tell, it works.
I would really appreciate it if anyone could help me out here.
Digital UNIX 4.0D
qmail-1.03
Native compiler
Best regards,
Bj�rn Nordb�
I've read the information in the four page printout that covers Quick
Mail Transfer Protocol (QMTP-19970201).
Qmail and Qmtp has been set up on a linux machine. I can telnet into
port 209 (no problems).
The problem is, while writing a piece of software, I cannot "QMTP" e-
mail to the linux box. I have and can very easily SMTP'd e-mail.
Does QMTP have a "verbose" setting for troubleshooting? When I send
off the requested 8 bit transmission, I do not receive any response
back. Obviously this is great for security reasons, but when
developing it has become a problem.
"Why use QMTP?" I've read how much faster it is (and agree with the
concept), and we are migrating our mail servers from an NT
environment to Linux to utilize Linux's power! ;) The back-end
program will be a windows app, and obviously the QMTP port accessible
only from our network.
I have begun to look that the qmtpd.c (source code), and find out why
it is not working.
Thank you for any help (updated documents and/or code samples).
Hi,
I had applied the patch for this and work very well with BIND.
recently, I changed to DNScache and this message came back.
where's the problem ??
--
Claudinei Luis Bianchini
[EMAIL PROTECTED]
Claudinei Luis Bianchini <[EMAIL PROTECTED]> wrote:
>I had applied the patch for this and work very well with BIND.
>recently, I changed to DNScache and this message came back.
>
>where's the problem ??
Exactly. What makes you think this message indicates a problem on your
end?
-Dave
On Wed, Jul 05, 2000 at 01:12:42PM -0400, Dave Sill wrote:
> Claudinei Luis Bianchini <[EMAIL PROTECTED]> wrote:
>
> >I had applied the patch for this and work very well with BIND.
> >recently, I changed to DNScache and this message came back.
> >
> >where's the problem ??
>
> Exactly. What makes you think this message indicates a problem on your
> end?
That exactly was my question about one week ago. How do I know where the
problem is?
Greetings
--
Robert Sander
Epigenomics AG www.epigenomics.de Kastanienallee 24
+493024345330 10435 Berlin
On Mon, Jul 03, 2000 at 09:54:25AM +0800, ??? wrote:
> for example:
> If I use ezmlm to build a mailling list.
> Which has 26 subscribers : [EMAIL PROTECTED] -- [EMAIL PROTECTED]
> All on the same host "remote.host"
>
> Then I send a message to the mailling list, does qmail+ezmlm
> 1.Send ONE message to "remote.host". And let the MTA of "remote.host"
> deliver the message to
> these 26 accounts?
> or
> 2.Send 26 message to "remote.host"?
ezmlm creates 26 different mails with different Return-path:s.
qmail delivers them one by one.
Unless you create sublists with ezmlm.
/magnus
--
http://x42.com/
On Tue, 4 Jul 2000, wolfgang zeikat wrote:
> Also sprach Karl Voit <[EMAIL PROTECTED]> on 04.07.2000:
>
> >Ow. This is getting complicated now :(
>
> No its not. its logical:
;)
I ment _my_ needs/configuration.
> [EMAIL PROTECTED] connects to your qmail via SMTP
> with a mail for [EMAIL PROTECTED]
>
> now qmail checks rcpthosts to find out if whatever.com is a host it
> accepts mail for - for delivery. if yes, it delivers them according to
> your qmail setup.
I do not know how to set up aliases. At least I get no information out of
the man-pages!
So I guessed, what I have to do:
touch ~alias/.qmail-testuser
edit ~alias/alias and added:
File : ".qmail-testuser"
&vk
I guess this would send all testuser@<accepted server from rctphosts> to
the local user vk.
btw, I also added the .qmail-default.
Now here's my problem:
When my fetchmail sends all mails from my provider-server (sbox) to my
server (tux), the mails don't come to my account. In fact, I don't know,
where they're delivered to anyway :(
Jul 5 19:03:36 tux qmail: 962816616.563087 delivery
160: success:
131.193.178.181_accepted_message./Remote_host_said:_250_ok_962816718_qp_16945/
Jul 5 19:03:36 tux qmail: 962816616.563833 status: local 0/10 remote 0/20
Jul 5 19:03:36 tux qmail: 962816616.564363 end msg 57511
... seems to be a positive entry but noone got this mail on my server tux
:(
ADDITIONAL:
starting delivery 157: msg 57507 to remote vk@localhost
tux qmail: 962816613.462226 status: local 1/10 remote 2/20
tux qmail: 962816613.560570 delivery
157: failure:
Sorry._Although_I'm_listed_as_a_best-preference_MX_or_A_for_that_host,/it_isn't_in_my_control/locals_file,_so_I_don't_treat_it_as_local._(#5.4.6)/
tux qmail: 962816613.561463 status: local 1/10 remote 1/20
tux qmail: 962816613.588289 bounce msg 57507 qp 8679
tux qmail: 962816613.589109 end msg 57507
... so all mails to vk@localhost (sent from vk@tux to vk@sbox and again to
vk@sbox) get stucked but I want it that way! ("localhost" already added to
rctphosts)
Karl VOIT, [EMAIL PROTECTED]
Student @ University of Technology of GRAZ (Austria/Europe)
http://www.sbox.tu-graz.ac.at/home/v/vk/
> Now here's my problem:
>
> When my fetchmail sends all mails from my provider-server (sbox) to my
> server (tux), the mails don't come to my account. In fact, I don't know,
> where they're delivered to anyway :(
>
> Jul 5 19:03:36 tux qmail: 962816616.563087 delivery
> 160: success:
>131.193.178.181_accepted_message./Remote_host_said:_250_ok_962816718_qp_16945/
> Jul 5 19:03:36 tux qmail: 962816616.563833 status: local 0/10 remote 0/20
> Jul 5 19:03:36 tux qmail: 962816616.564363 end msg 57511
>
> ... seems to be a positive entry but noone got this mail on my server tux
> :(
>
>
>
> ADDITIONAL:
> starting delivery 157: msg 57507 to remote vk@localhost
> tux qmail: 962816613.462226 status: local 1/10 remote 2/20
> tux qmail: 962816613.560570 delivery
> 157: failure:
>Sorry._Although_I'm_listed_as_a_best-preference_MX_or_A_for_that_host,/it_isn't_in_my_control/locals_file,_so_I_don't_treat_it_as_local._(#5.4.6)/
> tux qmail: 962816613.561463 status: local 1/10 remote 1/20
> tux qmail: 962816613.588289 bounce msg 57507 qp 8679
> tux qmail: 962816613.589109 end msg 57507
>
> ... so all mails to vk@localhost (sent from vk@tux to vk@sbox and again to
> vk@sbox) get stucked but I want it that way! ("localhost" already added to
> rctphosts)
... and ALL mails e.g. from this mailinglist aren't accepted too (because
the address of the mailinglist has no alias yet and the default doesn't
work?).
I'm getting nervous here and I'm thinking of deleting qmail again and
switching to another MTA :(
HOW can I make qmail clear, that it has to accept ALL of the incoming
mails and send ALL of them (except those which are addressed to another
local user) to the local user vk???? It seems to me that this is
impossible - at least for me as a non-guru %-}
Do I really have create an alias for _every_ address, qmail has to deliver
to local users? (I am not able to make this aliases work anyway - see
previous mail from me)
HELP!
Karl VOIT, [EMAIL PROTECTED]
Student @ University of Technology of GRAZ (Austria/Europe)
http://www.sbox.tu-graz.ac.at/home/v/vk/
Karl Voit <[EMAIL PROTECTED]> wrote:
>> When my fetchmail sends all mails from my provider-server (sbox) to my
>> server (tux), the mails don't come to my account. In fact, I don't know,
>> where they're delivered to anyway :(
That's a fetchmail issue. What's in your .fetchmailrc? Have you looked
in alias's mailbox?
>> starting delivery 157: msg 57507 to remote vk@localhost
"localhost" is remote? What's in control/locals?
>... and ALL mails e.g. from this mailinglist aren't accepted too (because
>the address of the mailinglist has no alias yet and the default doesn't
>work?).
First, qmail has to be told that localhost is local. Then you can use
~alias/.qmail-default to catch mail to all addresses that don't match
existing users or aliases.
-Dave
On Wed, 5 Jul 2000, Dave Sill wrote:
> Karl Voit <[EMAIL PROTECTED]> wrote:
>
> >> When my fetchmail sends all mails from my provider-server (sbox) to my
> >> server (tux), the mails don't come to my account. In fact, I don't know,
> >> where they're delivered to anyway :(
>
> That's a fetchmail issue. What's in your .fetchmailrc? Have you looked
> in alias's mailbox?
no, it was qmail:
> >> starting delivery 157: msg 57507 to remote vk@localhost
>
> "localhost" is remote? What's in control/locals?
oops! I forgot to add localhost to locals.
better: I suggested that localhost is covered through the entry of
tux.dyn.priv.at which is my machine here ;)
> >... and ALL mails e.g. from this mailinglist aren't accepted too (because
> >the address of the mailinglist has no alias yet and the default doesn't
> >work?).
>
> First, qmail has to be told that localhost is local. Then you can use
> ~alias/.qmail-default to catch mail to all addresses that don't match
> existing users or aliases.
THANK you VERY much!
I was stucked here and I almost began to test silly things that _might_ be
the reason ;)
Karl VOIT, [EMAIL PROTECTED]
Student @ University of Technology of GRAZ (Austria/Europe)
http://www.sbox.tu-graz.ac.at/home/v/vk/
Karl Voit <[EMAIL PROTECTED]> wrote:
>
> > Now here's my problem:
> >
> > When my fetchmail sends all mails from my provider-server (sbox) to my
> > server (tux), the mails don't come to my account. In fact, I don't know,
> > where they're delivered to anyway :(
The biggest problem here is that you're re-injecting non-local messages via
SMTP, which is fetchmail's default mode of operation.
Perhaps try using a different POP3 mail retrieval program which has fewer
bugs and doesn't cause mail loops and strange bounces -- my own "getmail",
for instance.
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.
-----------------------------------------------------------------------
"Ian Layton" <[EMAIL PROTECTED]> wrote:
>Thank you for all the comments I received about my previous question.
>
>I am now needing to make a program that will analyses bounced messages from
>Qmail and be able to distinguish between hard (permanent bounces) and soft
>(temporary) bounces. Is there any standard out there on how to recognize the
>difference. Also, I would like this program to execute upon delivery of a
>bounce message. I believe it's possible but I'm not sure how.
Russ Nelson used to have something called "bounceman" that did
that. He's no longer distributing it because ezmlm incorporates
similar (but apparently better) functionality.
-Dave
Barry Dwyer writes:
> 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
Just a speculation, but is the firewall doing NAT? Does the
mail server really see 192.168.0.n as client IP addresses?
Anyway, I'd look into the tcpserver's activity log for the
client IP addresses the mail server sees, and use tcprulescheck
to check if /etc/tcp.smtp.cdb is set up as expected.
--
Tetsu Ushijima
>> is the firewall doing NAT
That was the problem exactly. I don't know how I missed it (I'm the guy
who set up the firewall!!) but I did.
Barry
[EMAIL PROTECTED] writes:
> When sending all mail as user me for remote hosts out of ./mailppp/ by:
>
> me@bbrade:~ > maildirsmtp ./mailppp "" mail.arco.de bbrade
>
> I get following answer:
It seems to me that this has nothing to do with masquerading
issues.
What are you trying to do? If you would like outgoing mail
from your computer to be sent to ISP's SMTP server, you
should read /usr/local/doc/serialmail/TOISP and follow the
instructions.
--
Tetsu Ushijima
On 05-Jul-00 Tetsu Ushijima wrote:
> [EMAIL PROTECTED] writes:
>> When sending all mail as user me for remote hosts out of ./mailppp/
>> by:
>>
>> me@bbrade:~ > maildirsmtp ./mailppp "" mail.arco.de bbrade
>>
>> I get following answer:
>
> It seems to me that this has nothing to do with masquerading
> issues.
>
> What are you trying to do? If you would like outgoing mail
> from your computer to be sent to ISP's SMTP server, you
> should read /usr/local/doc/serialmail/TOISP and follow the
> instructions.
>
> --
> Tetsu Ushijima
>
Thanks for the tip where to find the FM, I just had to change FROM:
Header from [EMAIL PROTECTED] to [EMAIL PROTECTED] and add [EMAIL PROTECTED]
to qmail-inject for the returnpath.
Ciao
B-))ernd
----------------------------------
E-Mail: [EMAIL PROTECTED]
Date: 06-Jul-00
Time: 01:05:06
This message was sent by XFMail
----------------------------------
The Powers That Be are making noises about not liking the text of qmail's
bounce message. The whole "This is the qmail-send program at" thingy.
I don't want to mess with DJB's pristine code, so I would rather not
change it. Are there any good, concrete reasons to leave it alone? Or am
I being a wuss?
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
On Wed, Jul 05, 2000 at 01:55:44PM -0500, Ben Beuchler wrote:
> The Powers That Be are making noises about not liking the text of qmail's
> bounce message. The whole "This is the qmail-send program at" thingy.
>
> I don't want to mess with DJB's pristine code, so I would rather not
> change it. Are there any good, concrete reasons to leave it alone? Or am
> I being a wuss?
Because it's the nearest to a suggestion to a standard that is:
http://cr.yp.to/proto/qsbmf.txt
It's well defined and polite.
What part of this bounce is it that you don't like?
/magnus
--
http://x42.com/
Big wigs probably don't like the humor in qmails bounce message. It's a
shame.. I know I got a chuckle out of it the first time I read it.
Chad
-----Original Message-----
From: Magnus Bodin [mailto:[EMAIL PROTECTED]]
Sent: Wednesday, July 05, 2000 3:13 PM
To: qmail list
Subject: Re: Changing bounce message
On Wed, Jul 05, 2000 at 01:55:44PM -0500, Ben Beuchler wrote:
> The Powers That Be are making noises about not liking the text of qmail's
> bounce message. The whole "This is the qmail-send program at" thingy.
>
> I don't want to mess with DJB's pristine code, so I would rather not
> change it. Are there any good, concrete reasons to leave it alone? Or am
> I being a wuss?
Because it's the nearest to a suggestion to a standard that is:
http://cr.yp.to/proto/qsbmf.txt
It's well defined and polite.
What part of this bounce is it that you don't like?
/magnus
--
http://x42.com/
On Wed, Jul 05, 2000 at 09:12:46PM +0200, Magnus Bodin wrote:
> Because it's the nearest to a suggestion to a standard that is:
> http://cr.yp.to/proto/qsbmf.txt
>
> It's well defined and polite.
>
> What part of this bounce is it that you don't like?
I *do* like it! I don't want to change it. I'm just trying to come up
with reasonable arguments defending my position.
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
Ben Beuchler <[EMAIL PROTECTED]> wrote:
>I *do* like it! I don't want to change it. I'm just trying to come up
>with reasonable arguments defending my position.
Feel free to change it, but if you do, be careful not to break QSBMF
(qmail-send bounce message format), which bounce parsers like those in
ezmlm depend upon.
See:
ftp://koobera.math.uic.edu/www/proto/qsbmf.txt
-Dave
[EMAIL PROTECTED] wrote:
>Upon starting qmail, I get a looping error as svscan attempts to
>acquire these two directories, returning this error:
>
>supervise: fatal: unable to acquire qmail-send/supervise/lock:
>temporary failure
>supervise: fatal: unable to acuire qmail-smtpd/supervise/lock:
>temporary failure
>
>Can anyone suggest a fix? Or even a little insight into what these
>locks accomplish...
svscan runs supervise for each "service" in the directory it's
scanning. To ensure that only one supervise is supervising a service
at a time, supervise tries to acquire a lock by opening supervise/lock
exclusively.
I can think of several things that could cause this error, including,
of course, the fact that another supervise has already acquired the
lock. Another would be file/directory owner/mode/existence problems.
The general approach to fixing this problem is:
1) Stop all qmail-related processes including svscan, supervises,
anything running as a "qmail" user, qmail-send, multilogs,
etc. *Everything*.
2) Double check directory names/owners/groups/modes and the contents
of "run" scripts against LWQ. Check for extraneous ampersands (&)
at the ends of lines.
3) Restart svscan via "qmail start".
If the problem doesn't go away, repeat 1 & 2, and re-run 3 with "sh -x
/usr/local/sbin/qmail start". Cut and paste the output and post it to
the list.
-Dave
Peter Mitev <[EMAIL PROTECTED]> wrote:
>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.
See:
http://Web.InfoAve.Net/~dsill/lwq.html#trigger
-Dave
Charles Boening <[EMAIL PROTECTED]> wrote:
>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.
No kidding? Bonkers? Bummer...
Perhaps if you were more specific about how exactly it went "bonkers"
we could help.
-Dave
Apologies ... amazing what lack of sleep and frustration can do.
I figured it out though. When I installed the new server, I put vpopmail in
a different location and neglected to change the home directory in the
vpasswd file.
Thanks
Charles
-----Original Message-----
From: Dave Sill [mailto:[EMAIL PROTECTED]]
Sent: Wednesday, July 05, 2000 12:19 PM
To: [EMAIL PROTECTED]
Subject: Re: Moving vpopmail users
Charles Boening <[EMAIL PROTECTED]> wrote:
>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.
No kidding? Bonkers? Bummer...
Perhaps if you were more specific about how exactly it went "bonkers"
we could help.
-Dave
Please, do not misinform users of qmail out there. By deleting rcphosts
file, you open up qmail for third-party relaying. DON'T.
What you rater ought to do, is to control who can relay against your
SMTP-server with tools like tcpserver http://cr.yp.to/ucspi-tcp.html
package.
Keep helping newbies with their search for information, but at least be sure
what you help them with is corrcet.
BTRW: This is also good reading, Dave Sill's Life with qmail
http://web.infoave.net/~dsill/lwq.html and of course man qmail-control,
dot-qmail, etc....
regards
--
--------------------------------------------
IDG New Media Einar Bordewich
Technical Manager Phone: +47 2336 1420
E-Mail: [EMAIL PROTECTED]
--------------------------------------------
----- Original Message -----
From: "Darryl O'Keefe" <[EMAIL PROTECTED]>
To: <[EMAIL PROTECTED]>
Cc: <[EMAIL PROTECTED]>
Sent: Wednesday, July 05, 2000 8:29 PM
Subject: Re: email error from outlook express
> delete the file rcpthosts in /var/qmail/control
>
> At 11:30 PM 7/5/2000 +0530, you wrote:
> >Sir here is the message displayed by outlookexpress when sending mails
> >to outside domains:
> >
> >The message could not be sent because one of the recipients was rejected
> >by the server. The rejected e-mail address was
> >'[EMAIL PROTECTED]'. Subject 'test', Account:
> >'[EMAIL PROTECTED]', Server: 'mail.cybermaintenance.com',
> >Protocol: SMTP, Server Response: '553 sorry, that domain isn't in my
> >list of allowed rcpthosts (#5.7.1)', Port: 25, Secure(SSL):
> >No, Server Error: 553, Error Number: 0x800CCC79
>
>
>
How does one setup qmail and ezmlm to allow subscribes and unsubscribes to
be done ONLY by command line. I apologize if this is documented somewhere
but I only found out how to prevent posts to the mailing lists itself.
Brian
Hand, Brian C. writes:
> How does one setup qmail and ezmlm to allow subscribes and unsubscribes to
> be done ONLY by command line.
If you remove listdir/public, ezmlm-manage will stop responding to all
administrative requests, including -subscribe, -unsubscribe, and -get.
If you want -get to keep working, you can intercept delivery of the
subscription messages. The foo-subscribe and foo-unsubscribe
addresses are handled by the list's .qmail-default file - you can
create .qmail-[un]subscribe[-default] files to handle any messages
sent to those addresses. bouncesaying ought to be useful. If instead
you want to drop these messages silently, remember that the .qmail
files shouldn't be empty (that indicates that the system's default
delivery method should be used - ./Mailbox, or whatever), and the
first line can't be blank - `#' is the smallest no-op.
> I apologize if this is documented somewhere but I only found out how
> to prevent posts to the mailing lists itself.
Hm - how do you do that?
paul
I need a little help,
I got finally got qmail installed and everything appears to working fine.
The problem is when I telnet to localhost 25 and follow the direction from
the TEST.deliver, I connect to the port and run all the commands but the
mail does not get delivered. I took a look at the log and it states the
following:
deferral: uh-oh:_first_line_of_.qmail_file_is blank._(#4.2.1)/
I running Solaris 2.7 with deamontool, checkpassword, tcpserver and qmail
1.03.
Has anyone ever seen this before and know how to fix it. I did a search for
.qmail but did not find anything.
Also can someone tell me the proper way to add Maildir to every new user I
add.
Thanks,
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
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]>
On Wed, Jul 05, 2000 at 05:13:20PM -0700, Eddie Greer wrote:
> I need a little help,
>
> I got finally got qmail installed and everything appears to working fine.
> The problem is when I telnet to localhost 25 and follow the direction from
> the TEST.deliver, I connect to the port and run all the commands but the
> mail does not get delivered. I took a look at the log and it states the
> following:
>
> deferral: uh-oh:_first_line_of_.qmail_file_is blank._(#4.2.1)/
>
> I running Solaris 2.7 with deamontool, checkpassword, tcpserver and qmail
> 1.03.
>
> Has anyone ever seen this before and know how to fix it. I did a search for
> .qmail but did not find anything.
Have you tried looking in /var/qmail/alias/ ?
If the user you're sending to is a system user it could also have a .qmail-*
file in $HOME ....
> Also can someone tell me the proper way to add Maildir to every new user I
> add.
Change to the skeleton directory which is used as a basis for each new user
and do a maildirmake in that directory ....
> Thanks,
> Eddie Greer
HTH,
Steffan
--
http://therookie.dyndns.org
I want to move away from splogger w/o
making the full jump (yet) to supervise
and other daemontools...
here is my qmail rc file:
mail1.wlv# more /var/qmail/rc
#!/bin/sh
# Using splogger to send the log through syslog.
# Using qmail-local to deliver messages to ~/Mailbox by default.
ulimit -n 1024
exec env - PATH="/var/qmail/bin:$PATH" \
qmail-start ./Maildir/ splogger qmail
should i be able to replace splogger w/ a multilog entry? say like:
'multilog t s1000000 /var/log/qmail' instead of the splogger above?
would this then write files into /var/log/qmail?
thanks,
mike.
_____NetZero Free Internet Access and Email______
http://www.netzero.net/download/index.html
On Wed, Jul 05, 2000 at 05:27:05PM -0700, M.B. wrote:
> I want to move away from splogger w/o
> making the full jump (yet) to supervise
> and other daemontools...
>
> here is my qmail rc file:
>
> mail1.wlv# more /var/qmail/rc
> #!/bin/sh
>
> # Using splogger to send the log through syslog.
> # Using qmail-local to deliver messages to ~/Mailbox by default.
>
> ulimit -n 1024
>
> exec env - PATH="/var/qmail/bin:$PATH" \
> qmail-start ./Maildir/ splogger qmail
>
>
> should i be able to replace splogger w/ a multilog entry? say like:
> 'multilog t s1000000 /var/log/qmail' instead of the splogger above?
> would this then write files into /var/log/qmail?
I don't know about the correctness of that line, but before adding it in you
would also want to add "setuidgid qmaill" before it.
--Adam
Adam McKenna wrote:
>On Wed, Jul 05, 2000 at 05:27:05PM -0700, M.B. wrote:
>> I want to move away from splogger w/o
>> making the full jump (yet) to supervise
>> and other daemontools...
>>
>> here is my qmail rc file:
>>
>> mail1.wlv# more /var/qmail/rc
>> #!/bin/sh
>>
>> # Using splogger to send the log through syslog.
>> # Using qmail-local to deliver messages to ~/Mailbox by default.
>>
>> ulimit -n 1024
>>
>> exec env - PATH="/var/qmail/bin:$PATH" \
>> qmail-start ./Maildir/ splogger qmail
>>
>>
>> should i be able to replace splogger w/ a multilog entry? say like:
>> 'multilog t s1000000 /var/log/qmail' instead of the splogger above?
>> would this then write files into /var/log/qmail?
>
>I don't know about the correctness of that line, but before adding it in you
>would also want to add "setuidgid qmaill" before it.
Not true. qmail-start starts the logger as the log user (qmaill),
eliminating the need for setuidgid (or setuser).
To the original poster: Yes, that will work as you want it to, assuming that
you have created a /var/log/qmail directory with the appropriate permissions
(it should be owned, or at least readable, writable, and searchable, by
qmaill).
Mark
--
Do not reply directly to this e-mail address
--
Mark Mentovai
UNIX Engineer
Gillette Global Network
On Wed, Jul 05, 2000 at 08:50:52PM -0400, Mark Mentovai wrote:
> >I don't know about the correctness of that line, but before adding it in you
> >would also want to add "setuidgid qmaill" before it.
>
> Not true. qmail-start starts the logger as the log user (qmaill),
> eliminating the need for setuidgid (or setuser).
Are you sure about that? It doesn't say so in the man page.
--Adam
exec env - PATH="/var/qmail/bin:$PATH" \
qmail-start ./Maildir/ /usr/local/bin/multilog t s1000000 /var/log/qmail
qmail
unfortunately the above does no logging for me...
nor if i put some quotes in...
exec env - PATH="/var/qmail/bin:$PATH" \
qmail-start ./Maildir/ '/usr/local/bin/multilog t s1000000 /var/log/qmail'
qmail
permissions:
dev10# ls -ld /var/log/qmail
drwxr-xr-x 2 qmaill nofiles 512 Jul 5 16:40 /var/log/qmail
and sliding the setuidgid qmaill before multilog didn't do any logging
either.
:(
> To the original poster: Yes, that will work as you want it
> to, assuming that
> you have created a /var/log/qmail directory with the
> appropriate permissions
> (it should be owned, or at least readable, writable, and
> searchable, by
> qmaill).
>
_____NetZero Free Internet Access and Email______
http://www.netzero.net/download/index.html
Adam McKenna wrote:
>On Wed, Jul 05, 2000 at 08:50:52PM -0400, Mark Mentovai wrote:
>> >I don't know about the correctness of that line, but before adding it in you
>> >would also want to add "setuidgid qmaill" before it.
>>
>> Not true. qmail-start starts the logger as the log user (qmaill),
>> eliminating the need for setuidgid (or setuser).
>
>Are you sure about that? It doesn't say so in the man page.
Positive. The manpage doesn't say so explicitly (which is a surprise,
considering the nature of most of the manpages supplied with qmail), but the
source code does. Guess which wins?
(In case the answer isn't obvious, I don't run setuidgid at all to start
multilog on any of my mail servers, and multilog still runs as the qmail log
user.)
Don't confuse this with piping tcpserver's output to multilog (as in
something like qmail-smtpd), for that, you still need setuidgid.
qmail-start handles the pipes and UID/GID switching for qmail itself, when
you start redirecting from shell command lines manually, you need to be a
bit more explicit.
Mark
--
Do not reply directly to this e-mail address
--
Mark Mentovai
UNIX Engineer
Gillette Global Network
M.B. wrote:
>exec env - PATH="/var/qmail/bin:$PATH" \
>qmail-start ./Maildir/ /usr/local/bin/multilog t s1000000 /var/log/qmail
>qmail
>
>unfortunately the above does no logging for me...
Get rid of the trailing qmail. It was an argument to splogger to tell it
what program name to use.
>nor if i put some quotes in...
>
>exec env - PATH="/var/qmail/bin:$PATH" \
>qmail-start ./Maildir/ '/usr/local/bin/multilog t s1000000 /var/log/qmail'
>qmail
You don't want the quotes.
>permissions:
>
>dev10# ls -ld /var/log/qmail
>drwxr-xr-x 2 qmaill nofiles 512 Jul 5 16:40 /var/log/qmail
Permissions on /var/log? /var?
(I'm assuming / is OK.)
Mark
--
Do not reply directly to this e-mail address
--
Mark Mentovai
UNIX Engineer
Gillette Global Network
On Wed, Jul 05, 2000 at 09:39:56PM -0400, Mark Mentovai wrote:
> Adam McKenna wrote:
> >On Wed, Jul 05, 2000 at 08:50:52PM -0400, Mark Mentovai wrote:
> >> >I don't know about the correctness of that line, but before adding it in you
> >> >would also want to add "setuidgid qmaill" before it.
> >>
> >> Not true. qmail-start starts the logger as the log user (qmaill),
> >> eliminating the need for setuidgid (or setuser).
> >
> >Are you sure about that? It doesn't say so in the man page.
>
> Positive. The manpage doesn't say so explicitly (which is a surprise,
> considering the nature of most of the manpages supplied with qmail), but the
> source code does. Guess which wins?
>
> (In case the answer isn't obvious, I don't run setuidgid at all to start
> multilog on any of my mail servers, and multilog still runs as the qmail log
> user.)
No, I believe you.. I just don't remember ever hearing that before.
Well, at any rate, throwing it in there shouldn't break things.. I am pretty
sure that I had it configured that way (am using svscan now, so qmail-start
just logs to stdout.)
--Adam
> M.B. wrote:
>exec env - PATH="/var/qmail/bin:$PATH" \
> qmail-start ./Maildir/ /usr/local/bin/multilog t s1000000
> /var/log/qmail
> >qmail
> >
> >unfortunately the above does no logging for me...
>
> Get rid of the trailing qmail. It was an argument to
> splogger to tell it
> what program name to use.
Bingo. THANKS! what i now have is:
exec env - PATH="/var/qmail/bin:$PATH" \
qmail-start ./Maildir/ multilog t s5000000 /export/home/qmaillogs
(since /var's permissions didn't look inviting)
now how might i pipe this thru tai64nlocal to get some readable
(by me) time stamps in there?
mike.
____________NetZero Free Internet Access and Email_________
Download Now http://www.netzero.net/download/index.html
Request a CDROM 1-800-333-3633
___________________________________________________________
M.B. wrote:
>now how might i pipe this thru tai64nlocal to get some readable
>(by me) time stamps in there?
Yup. tai64nlocal converts what it sees on stdin and places it on stdout, so
instead of "cat /export/home/qmaillogs/current" (or similar), you can use
"tai64nlocal < /export/home/qmaillogs/current".
Mark
--
Do not reply directly to this e-mail address
--
Mark Mentovai
UNIX Engineer
Gillette Global Network
> Adam McKenna:
> > should i be able to replace splogger w/ a multilog entry? say like:
> > 'multilog t s1000000 /var/log/qmail' instead of the splogger above?
> > would this then write files into /var/log/qmail?
yes.
clemens
On Thu, Jul 06, 2000 at 07:04:51AM +0200, clemensF wrote:
> > Adam McKenna:
>
> > > should i be able to replace splogger w/ a multilog entry? say like:
> > > 'multilog t s1000000 /var/log/qmail' instead of the splogger above?
> > > would this then write files into /var/log/qmail?
>
> yes.
>
> clemens
Hi, I didn't say that.. please be more careful with your quoting.
--Adam
> M.B.:
> now how might i pipe this thru tai64nlocal to get some readable
> (by me) time stamps in there?
qmail-start ./Maildir/ multilog t s5000000 !tai64nlocal /export/home/qmaillogs
then every log that gets rotated out of business (current -> @...) will have
human readable timestamps.
clemens
Hi!
Do a web search on "tiergrubing" (Something like that anyway - the german
term for "tar pit"). I've never done it before but it involves slightly
slowing down the connection the more messages that are sent, thereby tieing
up the spammer. I think I remember reading some people talking about doing
this with qmail...
Eric
KUDLAC Tomas wrote:
>
> Hello,
>
> is there any way how to prevent mail floods with qmail? I can imagine that
> it's impossible to implement such protection that would function in all
> cases (maybe some expert system ;-)), however I need to protect our server
> against cases when somebody decides to send let's say 100000 mails to some
> internal address. Is there any way how to tell qmail to send alarm (or
> perform some action) when number of mails per time interval from one address
> (or domain) grows more than certain limit?
>
> note: I am using qmail at the gateway, it's forwarding mails between
> internet and our internal mail system.
>
> Thanx,
>
> --
> Tomas Kudlac
Dear all,
I've installed qmailadmin on OSF1 4.0F and it was successfully, but I've got
problem "Out of memory" if I try to add user virtual pop3 account via
browser. anybody know what the problem is ?
Best regards,
wars mailto:[EMAIL PROTECTED]
Hello!
Would you please give me advice for some questions?
---------------------------------------------
1. Now I'm confused with following message in the maillog.
"qmail: 962478354.405231 warning: trouble opening local/22/1105816; will try again
later"
Many massage like this are appearing in the log forever....
What is occurring and how to eliminate them?
(Mail of id "1105816" is of when testing and should have been dead......)
---------------------------------------------
2. What means (#x.x.x) number in the maillog?
I encounter it sometimes like..
"delivery 10: deferral: connected_to_aaa.bbb.ccc.ddd_but_connection_died._(#4.4.2)/"
What means "(#4.4.2)" and where can I look up them?
---------------------------------------------
3. About IDENT processing from smtp
I can see following header in a testing mail from my qmail server to
another my account.
"from host.mydoman (IDENT:[EMAIL PROTECTED] [a.b.c.d]) by host.destination
(8.9.3/8.7.1) with
SMTP id BAAxxxx for <[EMAIL PROTECTED]>; Wed, 5 Jul 2000 01:44:01 -0600"
As shown above, I allow IDENT access to the server now, but I suspect it.
because I don't see the header with IDENT in another mail not from my
server.
Essentially, qmail smtp daemon is necessary (mandatory) for IDENT connection? And if
I prohibit it,
what would happen?
Thank you in advance.
Jaime (^o^)
--
Hajime Lucky Okada
FreeBSD machine with the queue on a softupdate filesystem
Hi, I have a todo directory which has approx 200K messages in it. This
leads to congestion in qmail-send since todo processing takes up far
too much time. It's a bit too late to install the big-todo patch
(since I don't want to blow up the queue). Are there any other
techniques to help speed up qmail-send. I have temporarily shutdown
incoming mail to let the queue drain
Is there a way to put a secondary installation of qmail to help
process messages faster
Regards, Yusuf
--
Yusuf Goolamabbas
[EMAIL PROTECTED]
Hi everybody,
One of our user has tried to send more than 30000 mail (outlook autoreplay
forth and back!!) to an
external account on "SomeDomain.com" , his account is now locked out on the
remote domain,
worse is that they do'nt accept any mail from our mailserver at all and
there is more than 25000
mail left on our mail queque, how can i remove them (only for one spec.
user), there is some
important mail (from other users) among them.
best regards
/David
On Mon, Jun 26, 2000 at 11:19:37PM -0400, Russell Nelson wrote:
> Gerrit Pape writes:
> > If there is interest in having qmail in the debian-distribution, perhaps I
> > get Dan J. Bernstein's approval sometime.
>
> Produce two packages:
> qmail, which is a 100% debian-compatible binary package which puts
> files in the locations required by Debian.
> qmail-compat, which is required by qmail, and which uses symlinks
> to ensure that all files are found in the locations Dan has
> mandated.
>
> Those two packages satisfy Dan's requirements for qmail distributors,
> and satisfies Debian's requirements for locations of binaries, man
> pages, and configuration files.
>
This does my single qmail package (man pages are not linked to
/var/qmail/man). I do not see the benefit in having two packages: a user who
installs the package named 'qmail' without qmail-compat, breaking dependencies
manually, could be left in a nearly not usable qmail installation (the
debian-compatible one) without a /var/qmail tree. This may produce
confusion.
Installing the debian package 'qmail', I did, it will be fully usable for
experts, even if fastforward, dot-forward and qmail-run is not installed.
> > Getting the packages into debian is the easier part, I think, that is what
> > lintian reports as errors by now:
>
> I thought Debian was foolishly talking about removing non-free?
They did, but there is no decision yet, non-free will surely be in woody.
> about Debian compatibility. You may as well produce a 100%
> djb-compatible vanilla qmail .deb.
>
Having two qmail debs is not good. So if there is a chance to create a
djb- _and_ debian-compatible package, let's do this one. If not, I will do a
unofficial djb-compatible vanilla dot-deb.
Gerrit.
--
[EMAIL PROTECTED]
innominate AG
networking people
fon: +49.30.308806-0 fax: -77 web: http://innominate.de pgp: /pgp/gpa
