Re: Qmail Without Inetd
suryadi writes: > Can Qmail Works without inetd (in FreeBSD 3.5) and without others (such > as tcpserver, etc) ? CMIIW. No, qmail (spesifically qmail-smtpd) needs a 'server' (tcpserver, (x)inetd, etc) to listen to SMTP connection. Regards, Ahmad Ridha
Qmail Without Inetd
Can Qmail Works without inetd (in FreeBSD 3.5) and without others (such as tcpserver, etc) ? thx you --sur--
Re: Qmailqueue patch over current qmail 1.03
You are correct. If you don't use it then it costs you nothing. -- Paul Farber Farber Technology [EMAIL PROTECTED] Ph 570-628-5303 Fax 570-628-5545 On Tue, 14 Aug 2001, Charles Cazabon wrote: > Paul Farber <[EMAIL PROTECTED]> wrote: > > > > qmail-queue will slow down mail processing (did in my case) so if its a > > medium/high volume smtp server then you better plan for some additional > > bogomips to fire off the scanning. > > Note that the QMAILQUEUE patch alone should not increase server load by > any measurable amount; it's whatever you run using QMAILQUEUE (i.e. a > virus scanner or other mail filter) which sucks CPU cycles and memory. > > Charles >
Re: Configuring qmail to accept *all* mail
[EMAIL PROTECTED] <[EMAIL PROTECTED]> wrote: > > I have a vanilla (life with qmail-style) qmail server up and running > on an internal development x86 linux server. Since this is supposed to > be a test server for some mail applications that are being developed, > what I would like to do is to configure qmail to accept all mail it > receives for local delivery and place it in a single directory. Very simple to do. > I have already figured out that I can comment out the following two > lines in qmail-smtpd.c in order to bypass the 'rcpt to' envelope > check, so it will accept any email sent to the machine regardless of > the address: Totally unnecessary to patch qmail. From the man page for qmail-send: virtualdomains may contain wildcards: .fax:uucp-fax :alias-catchall .nowhere.mil:joe-foo-host > I also have a .qmail-default file in /var/qmail/alias, which redirects > all local mail over to /home/devmail/Maildir. Use ":alias-catchall" in virtualdomains, and create ~alias/.qmail-catchall instead of patching. > The last piece of the puzzle is to short-circuit qmail-send (I'm > guessing) so that it will hand all mail over to qmail-lspawn, and > never to qmail-rspawn. Since I'm not a programmer, I'm having > difficulty digging through qmail-send.c (over 1600 lines!) to figure > out what to comment out and/or change. Any help at all would be > greatly appreciated. With the catchall configuration above, no patching is necessary. Charles -- --- Charles Cazabon<[EMAIL PROTECTED]> GPL'ed software available at: http://www.qcc.sk.ca/~charlesc/software/ ---
Configuring qmail to accept *all* mail
Hello,
I have a vanilla (life with qmail-style) qmail server up and running on an internal
development x86 linux server. Since this is supposed to be a test server for some mail
applications that are being developed, what I would like to do is to configure qmail
to accept all mail it receives for local delivery and place it in a single directory.
I have already figured out that I can comment out the following two lines in
qmail-smtpd.c in order to bypass the 'rcpt to' envelope check, so it will accept any
email sent to the machine regardless of the address:
// else
//if (!addrallowed()) { err_nogateway(); return; }
I also have a .qmail-default file in /var/qmail/alias, which redirects all local mail
over to /home/devmail/Maildir.
The last piece of the puzzle is to short-circuit qmail-send (I'm guessing) so that it
will hand all mail over to qmail-lspawn, and never to qmail-rspawn. Since I'm not a
programmer, I'm having difficulty digging through qmail-send.c (over 1600 lines!) to
figure out what to comment out and/or change. Any help at all would be greatly
appreciated.
Thanks,
Jeremy Frank
Free, secure Web-based email, now OpenPGP compliant - www.hushmail.com
Configuring qmail to accept *all* mail
Hello,
I have a vanilla (life with qmail-style) qmail server up and running on an internal
development x86 linux server. Since this is supposed to be a test server for some mail
applications that are being developed, what I would like to do is to configure qmail
to accept all mail it receives for local delivery and place it in a single directory.
I have already figured out that I can comment out the following two lines in
qmail-smtpd.c in order to bypass the 'rcpt to' envelope check, so it will accept any
email sent to the machine regardless of the address:
// else
//if (!addrallowed()) { err_nogateway(); return; }
I also have a .qmail-default file in /var/qmail/alias, which redirects all local mail
over to /home/devmail/Maildir.
The last piece of the puzzle is to short-circuit qmail-send (I'm guessing) so that it
will hand all mail over to qmail-lspawn, and never to qmail-rspawn. Since I'm not a
programmer, I'm having difficulty digging through qmail-send.c (over 1600 lines!) to
figure out what to comment out and/or change. Any help at all would be greatly
appreciated.
Thanks,
Jeremy Frank
Free, secure Web-based email, now OpenPGP compliant - www.hushmail.com
Re: Qmailqueue patch over current qmail 1.03
Paul Farber <[EMAIL PROTECTED]> wrote: > > qmail-queue will slow down mail processing (did in my case) so if its a > medium/high volume smtp server then you better plan for some additional > bogomips to fire off the scanning. Note that the QMAILQUEUE patch alone should not increase server load by any measurable amount; it's whatever you run using QMAILQUEUE (i.e. a virus scanner or other mail filter) which sucks CPU cycles and memory. Charles -- --- Charles Cazabon<[EMAIL PROTECTED]> GPL'ed software available at: http://www.qcc.sk.ca/~charlesc/software/ ---
Re: Qmailqueue patch over current qmail 1.03
No, I did. the qmail-queue patch only mods 2 files and the config for it is also by itself. qmail-queue will slow down mail processing (did in my case) so if its a medium/high volume smtp server then you better plan for some additional bogomips to fire off the scanning. -- Paul Farber Farber Technology [EMAIL PROTECTED] Ph 570-628-5303 Fax 570-628-5545 On Tue, 14 Aug 2001, board master wrote: > Hi, > > I've already installed: > > Qmail 1.03+Vpopmail 4.10+sqwebmail+daemontools+ezmlm+autoresond+ucspi > (PHWEW!) > > and I was wondering what would happen if I patched a brand new qmail 1.03 > with the qmailqueue patch (I want to use virus scanning) and installed the > patched qmail over itself. Would I lose anything? Files, configurations, > etc? > > Thanks in advance, > Michael > > _ > Get your FREE download of MSN Explorer at http://explorer.msn.com/intl.asp > >
Re: Qmailqueue patch over current qmail 1.03
board master <[EMAIL PROTECTED]> wrote: > > I've already installed: > > Qmail 1.03+Vpopmail 4.10+sqwebmail+daemontools+ezmlm+autoresond+ucspi > (PHWEW!) > > and I was wondering what would happen if I patched a brand new qmail 1.03 > with the qmailqueue patch (I want to use virus scanning) and installed the > patched qmail over itself. You shouldn't have to use a "brand new qmail 1.03" -- none of the packages above require patching qmail, to my knowledge, so what you're running now is a pure vanilla qmail plus addons. > Would I lose anything? Files, configurations, etc? You shouldn't. Just cd to the qmail source directory where you previously compiled qmail. Then apply the QMAILQUEUE patch, and do "make setup check". Charles -- --- Charles Cazabon<[EMAIL PROTECTED]> GPL'ed software available at: http://www.qcc.sk.ca/~charlesc/software/ ---
Qmailqueue patch over current qmail 1.03
Hi, I've already installed: Qmail 1.03+Vpopmail 4.10+sqwebmail+daemontools+ezmlm+autoresond+ucspi (PHWEW!) and I was wondering what would happen if I patched a brand new qmail 1.03 with the qmailqueue patch (I want to use virus scanning) and installed the patched qmail over itself. Would I lose anything? Files, configurations, etc? Thanks in advance, Michael _ Get your FREE download of MSN Explorer at http://explorer.msn.com/intl.asp
Re: Life with qmail & smtp & daemontools
On Tue, Aug 14, 2001 at 08:01:22PM +0200, Eric Persson wrote: > [root@mailzx daemontools-0.70]# /etc/init.d/qmail start > Starting qmail > svok: fatal: unable to chdir to /service/qmail-send: file does not exist > qmail-send service not running > svok: fatal: unable to chdir to /service/qmail-smtpd: file does not > exist > qmail-smtpd service not running > > I cant find any info on what those /service/qmail-send and > /service/qmail-smtpd should be, Look a little closer at Life With qmail. It's in there, promise. GW -- Greg White
Re: Life with qmail & smtp & daemontools
At 8:01 PM +0200 8/14/01, Eric Persson wrote: >I cant find any info on what those /service/qmail-send and >/service/qmail-smtpd should be, I tried to symlink them to the files in >/var/qmail/bin that has the same names, but it seems like >/service/qmail-send and /service/qmail-smtpd should be directories. > >Can anyone point me in the right direction? Go back and re-read Life with Qmail. This is covered extensively in the section on /var/qmail/supervise/ and symlinking the subdirectories to /service/, aka "2.8.2.2. The supervise scripts". -- John Groseclose [EMAIL PROTECTED]
Life with qmail & smtp & daemontools
Hi ! I've been fiddeling around to try installing qmail on my machine but have got stuck with the smtppart. The delivering works fine, but I cant use the machine as a smtp. I read the http://lifewithqmail.org/lwq.html#install-ucspi where it says I need to install daemontools and ucspi-tcp and then create a system startupfile. I used the startupscript available at http://lifewithqmail.org/lwq.html#start-qmail but when I try to use it I get [root@mailzx daemontools-0.70]# /etc/init.d/qmail start Starting qmail svok: fatal: unable to chdir to /service/qmail-send: file does not exist qmail-send service not running svok: fatal: unable to chdir to /service/qmail-smtpd: file does not exist qmail-smtpd service not running I cant find any info on what those /service/qmail-send and /service/qmail-smtpd should be, I tried to symlink them to the files in /var/qmail/bin that has the same names, but it seems like /service/qmail-send and /service/qmail-smtpd should be directories. Can anyone point me in the right direction? Thanks in advance.. eric
Re: QMAIL-SMTPD and INETD
[EMAIL PROTECTED] <[EMAIL PROTECTED]> wrote: > > QMAIL-SMPTD doesnt work with INETD. I installed it as the INSTALL > filedasaid to, but to no avail. I rebooted the box and Qmail-SMTPD didnt > start.dadaAny help would be appreciated.dadaThis is the most current > verision and is installed into the defaultdadirectories.dadaThanks!daAndy You didn't post what you did, so nobody can help you. However, as you've noted, use of inetd/xinetd with qmail is deprecated. It's much simpler to set up with tcpserver (from ucspi-tcp). See djb's documentation on his website at cr.yp.to, or do a "Life with qmail" installation (see http://lifewithqmail.org). Charles -- --- Charles Cazabon<[EMAIL PROTECTED]> GPL'ed software available at: http://www.qcc.sk.ca/~charlesc/software/ ---
QMAIL-SMTPD and INETD
QMAIL-SMPTD doesnt work with INETD. I installed it as the INSTALL filedasaid to, but to no avail. I rebooted the box and Qmail-SMTPD didnt start.dadaAny help would be appreciated.dadaThis is the most current verision and is installed into the defaultdadirectories.dadaThanks!daAndy
RES: /var/qmail tree
Hi,
My qmail have theses permissions and work fine
-rwxr-xr-x 1 root other204 Apr 20 15:35 rc
drwxr-xr-x 2 root qmail512 May 21 11:01 users
drwxr-xr-x 2 root qmail512 May 21 11:01 boot
drwxr-xr-x 2 root qmail 1024 May 21 11:01 doc
drwxr-xr-x 10 root qmail512 May 21 11:01 man
drwxr-sr-x 2 aliasqmail512 May 21 11:01 alias
drwxr-x--- 11 qmailq qmail512 Jul 5 17:05 queue
drwxr-xr-x 2 root qmail 1024 Aug 2 11:12 bin
drwxr-xr-x 2 root qmail512 Aug 9 14:41 control
#
Agnaldo Mariano Monteiro
Engenharia de Sistemas
Fujitsu do Brasil Ltda.
Tel.: (11) 245-0964 (Direto)
[EMAIL PROTECTED]
- Mensagem original -
De: [EMAIL PROTECTED] [SMTP:[EMAIL PROTECTED]]
Enviada em: terca-feira, 14 de agosto de 2001 11:59
Para: [EMAIL PROTECTED]
Assunto:/var/qmail tree
HELLO!
I have installed qmail and have launched the 'instcheck'
program.
'instcheck' printed the following messages:
[root@timsat-srv2 qmail]# ./bin/instcheck
instcheck: warning: /var/qmail/control has wrong owner
instcheck: warning: /var/qmail/users has wrong owner
instcheck: warning: /var/qmail/bin has wrong owner
instcheck: warning: /var/qmail/boot has wrong owner
instcheck: warning: /var/qmail/doc has wrong owner
instcheck: warning: /var/qmail/man has wrong owner
instcheck: warning: /var/qmail/alias has wrong owner
On my system the owner of all these folders is 'qmaill':
[root@timsat-srv2 /tmp]# cd /var/qmail/
[root@timsat-srv2 qmail]# ll
total 15
drwxrwxrwx3 rootroot addons
drwxr-sr-x2 qmaill qmail alias <--
drwxr-xr-x2 qmaill qmail bin <--
drwxr-xr-x2 qmaill qmail boot <--
drwxr-xr-x2 qmaill qmail control <--
drwxr-xr-x2 qmaill qmail doc <--
drwxr-xr-x6 qmaill qmail man <--
drwxr-x--- 11 qmailq qmail queue
-rwxr-xr-x1 rootroot rc
-rwxr-xr-x1 rootroot rc~
-rwxr-xr-x1 rootroot rc.bak
-rwxr-xr-x1 qmaill rootrc.old
drwxr-xr-x4 qmaill root supervise
drwxr-xr-x2 qmaill qmail users <--
Could someone who have a working installed qmail server
tell me who should be the owner of these folders:
/var/qmail/control owner:
/var/qmail/usersowner:
/var/qmail/bin owner:
/var/qmail/boot owner:
/var/qmail/doc owner:
/var/qmail/man owner:
/var/qmail/aliasowner:
Thanks!
Re: /var/qmail tree
On 14 Aug 2001, at 16:59, [EMAIL PROTECTED] wrote: > HELLO! > > I have installed qmail and have launched the 'instcheck' > program. > 'instcheck' printed the following messages: > > [root@timsat-srv2 qmail]# ./bin/instcheck > > instcheck: warning: /var/qmail/control has wrong owner > instcheck: warning: /var/qmail/users has wrong owner > instcheck: warning: /var/qmail/bin has wrong owner > instcheck: warning: /var/qmail/boot has wrong owner > instcheck: warning: /var/qmail/doc has wrong owner > instcheck: warning: /var/qmail/man has wrong owner > instcheck: warning: /var/qmail/alias has wrong owner > > On my system the owner of all these folders is 'qmaill': > > [root@timsat-srv2 /tmp]# cd /var/qmail/ > [root@timsat-srv2 qmail]# ll > total 15 > drwxrwxrwx3 rootroot addons > drwxr-sr-x2 qmaill qmail alias <-- > drwxr-xr-x2 qmaill qmail bin <-- > drwxr-xr-x2 qmaill qmail boot <-- > drwxr-xr-x 2 qmaill qmail control <-- > drwxr-xr-x2 qmaill qmail doc <-- > drwxr-xr-x6 qmaill qmail man <-- > drwxr-x--- 11 qmailq qmail queue > -rwxr-xr-x1 rootroot rc > -rwxr-xr-x1 rootroot rc~ > -rwxr-xr-x1 rootroot rc.bak > -rwxr-xr-x1 qmaill rootrc.old > drwxr-xr-x4 qmaill rootsupervise > drwxr-xr-x2 qmaill qmail users <-- > > > Could someone who have a working installed qmail server > tell me who should be the owner of these folders: > [...] Here's the info from my qmail box. FYI, I didn't install qmail from scratch, it can pre-installed with my Linux Distro. (e-smith) Hope this helps. total 40 drwxr-xr-x 10 root qmail4096 Jun 23 04:48 . drwxr-xr-x 18 root root 4096 Jun 23 16:00 .. drwxr-sr-x2 aliasqmail 4096 Aug 7 14:04 alias drwxr-xr-x2 root qmail4096 Jun 23 05:39 bin drwxr-xr-x2 root qmail4096 Jun 23 04:48 boot drwxr-xr-x2 root qmail 4096 Aug 7 14:04 control drwxr-xr-x3 root qmail 4096 Jun 23 04:48 doc drwxr-xr-x 10 root qmail4096 Jun 23 04:48 man drwxr-x--- 11 qmailq qmail4096 Jun 23 04:48 queue drwxr-xr-x2 root qmail4096 Aug 7 14:04 users Cheers Dean Dean Staff Protus IP Solutions 210 - 2379 Holly Lane Ottawa, ON K1V 7P2 Canada 613-733- ex 546 Fax 613-248-4553 e-mail: [EMAIL PROTECTED] Web: http://www.protus.com
Announce: QSP - Qmail Spamkiller Project
Hello ,
Spamkiller engine for QMAIL with SHA authentication and more
I would like to announce my QSP - a new approach in blocking SPAM with
SHA authentication, special support for mailinglists, individual
templates and so on Its
a very modular system comes with rich API to make your own extensions.
I wrote this modules and libraries for python because I am really angry against spam
and its
time to stop this with some intelligent and new ways and without the
usage of online-blacklists and so on.
Detailed project informations: www.x-itec.de/QSP
Source and Download available at the beginning of 09/2001
Tested with more than 90.000 mails at the moment.
Status: Development, SHA authentication is complete, working on the
next module for mailinglists.
If you want to read more about this interesting project, see my
project page. If you want to test it just for fun, send me a mail *ggg
to [EMAIL PROTECTED] - if the system is enabled, you will get an
authorization request. Otherwise there is a bug again -((
The project is free for download in 09/2001 and comes with source and
documentation. Pyhton required.
--
Boris Köster [MCSE, CNA]
void SurfTo ( "http://www.x-itec.de "){ thanks(0);exit(0); }
Maintainer of the FreeBSD IPSEC-MiniHowTo
Mantainer of QSP - QMail Spamkiller Project
Re: /var/qmail tree
I have root as owner... On Tue, 14 Aug 2001 [EMAIL PROTECTED] wrote: > HELLO! > > I have installed qmail and have launched the 'instcheck' > program. > 'instcheck' printed the following messages: > > [root@timsat-srv2 qmail]# ./bin/instcheck > > instcheck: warning: /var/qmail/control has wrong owner > instcheck: warning: /var/qmail/users has wrong owner > instcheck: warning: /var/qmail/bin has wrong owner > instcheck: warning: /var/qmail/boot has wrong owner > instcheck: warning: /var/qmail/doc has wrong owner > instcheck: warning: /var/qmail/man has wrong owner > instcheck: warning: /var/qmail/alias has wrong owner > > On my system the owner of all these folders is 'qmaill': > > [root@timsat-srv2 /tmp]# cd /var/qmail/ > [root@timsat-srv2 qmail]# ll > total 15 > drwxrwxrwx3 rootroot addons > drwxr-sr-x2 qmaill qmail alias <-- > drwxr-xr-x2 qmaill qmail bin <-- > drwxr-xr-x2 qmaill qmail boot <-- > drwxr-xr-x 2 qmaill qmail control <-- > drwxr-xr-x2 qmaill qmail doc <-- > drwxr-xr-x6 qmaill qmail man <-- > drwxr-x--- 11 qmailq qmail queue > -rwxr-xr-x1 rootroot rc > -rwxr-xr-x1 rootroot rc~ > -rwxr-xr-x1 rootroot rc.bak > -rwxr-xr-x1 qmaill rootrc.old > drwxr-xr-x4 qmaill rootsupervise > drwxr-xr-x2 qmaill qmail users <-- > > > Could someone who have a working installed qmail server > tell me who should be the owner of these folders: > /var/qmail/control owner: > /var/qmail/usersowner: > /var/qmail/bin owner: > /var/qmail/boot owner: > /var/qmail/doc owner: > /var/qmail/man owner: > /var/qmail/aliasowner: > > Thanks! >
/var/qmail tree
HELLO!
I have installed qmail and have launched the 'instcheck'
program.
'instcheck' printed the following messages:
[root@timsat-srv2 qmail]# ./bin/instcheck
instcheck: warning: /var/qmail/control has wrong owner
instcheck: warning: /var/qmail/users has wrong owner
instcheck: warning: /var/qmail/bin has wrong owner
instcheck: warning: /var/qmail/boot has wrong owner
instcheck: warning: /var/qmail/doc has wrong owner
instcheck: warning: /var/qmail/man has wrong owner
instcheck: warning: /var/qmail/alias has wrong owner
On my system the owner of all these folders is 'qmaill':
[root@timsat-srv2 /tmp]# cd /var/qmail/
[root@timsat-srv2 qmail]# ll
total 15
drwxrwxrwx3 rootroot addons
drwxr-sr-x2 qmaill qmail alias <--
drwxr-xr-x2 qmaill qmail bin <--
drwxr-xr-x2 qmaill qmail boot <--
drwxr-xr-x2 qmaill qmail control <--
drwxr-xr-x2 qmaill qmail doc <--
drwxr-xr-x6 qmaill qmail man <--
drwxr-x--- 11 qmailq qmail queue
-rwxr-xr-x1 rootroot rc
-rwxr-xr-x1 rootroot rc~
-rwxr-xr-x1 rootroot rc.bak
-rwxr-xr-x1 qmaill rootrc.old
drwxr-xr-x4 qmaill root supervise
drwxr-xr-x2 qmaill qmail users <--
Could someone who have a working installed qmail server
tell me who should be the owner of these folders:
/var/qmail/control owner:
/var/qmail/usersowner:
/var/qmail/bin owner:
/var/qmail/boot owner:
/var/qmail/doc owner:
/var/qmail/man owner:
/var/qmail/aliasowner:
Thanks!
Re: script filter before qmail-local .. solved
Ok, just in case anybody else will fight with it too, I found this: seekablepipe http://www.skarnet.org/software/qmail-local-mda/ -- jozef :-)
Re: qmail + Courrier-IMAP vs just Courrier-IMAP server (newbie)
-BEGIN PGP SIGNED MESSAGE- Hello Jean-Christian, Tuesday, August 14, 2001, 5:13:34 AM, you wrote: > My original plan was to install qmail - VMailMgr - Courrier-IMAP. > But after a little reading I find out that Courrier-IMAP has it own > email server implementation. So it seems that qmail is not needed? > Am I right? If so what are the advantages/disadvantages to either > using qmail with the Courrier-IMAP engine or just using Courrier as > the mail and IMAP server? AFAIK, Mr. Sam doesn't consider courier-mta as being production quality and I know of nobody that actually uses it. But if you want to use qmail and courier-imap in a virtual domain environment, I suggest you take a look at http://inter7.com/vpopmail as courier-imap got direct integration of vpopmail. Best regards, Gabriel -BEGIN PGP SIGNATURE- Version: PGP 6.5i iQEVAwUBO3kHDMZa2WpymlDxAQHuYQf9F3NM69LzTG9hNimFk2B72FaTf047jzVy PH+C7+MuGvU+2CnI9jiavsIm9w6ChC+Eeq0VNps4UvYIwU1PJ09yP16Dtjh7xzXH c/EIHEAmGMV3+g40JkXGQdOIwSIfj2lg2HFCtEM4g2nuVL5tUiJuPXBPajEtfXYs rloUUurepslsIUyKhoIBmmpx28FNOtRhKnnF/pW8yI7pESdHwumi3gxZ5Hflk8oT NDrmDvsShrMC5Kvg8b/hdw6vktAlqdnor/vjoFtHx2EkESVRLPoQI6mjKv3VtmMK IJk/QwqbgVphrMGSb2At4i9L0QE7N5PWCjwlRYqHXu7AL1KsOrOozA== =TnrE -END PGP SIGNATURE-
Re: Security Check generated by AXENT Netrecom 3.0 points security flaw in qmail-smtpd
-BEGIN PGP SIGNED MESSAGE- Hello Agnaldo, Tuesday, August 14, 2001, 1:59:47 PM, you wrote: > Questions: Anybody know anything about this? Where can I get > additional information about this? This Results checks is True or > false? Someone should PLEASE correct me if I'm wrong but my experience with Nessus checking our qmail servers has been pretty similar because qmail won't complain about broken To headers but simply ignore them so there isn't anything that this exploit could do to your server. Best regards, Gabriel -BEGIN PGP SIGNATURE- Version: PGP 6.5i iQEVAwUBO3kGaMZa2WpymlDxAQH2mAf6A0Ad2fsvVOlmDqu4USAclToe9Yk94Ifh baCKpu0T2WMdIWiTslpOupMh4fNLbwTBYSqtyd7c7b48CLOuh6UUR1vDcfQS0tqN bWeS11IfZeqNldmIaFd6dJdwbMU9ZAGfZPx5bNyb9SyhDPGi9OY4MTH65j9M24kw 6+gZqpLK8TQ743kl6et+f7ddKRY0SrmMwE35zLzc3RaKJ10grIH0iPedaK1wWIQz dUuZbbPL2bDERezWbSIK/XFixAL0TUlow29EOrOfFziicnj4Dh+VGHrPRr8WDpG+ sLuZvTdkpuL/WGKSEFGEHGcjAbFNsFZUZoGzuwxQAi66abuLWaaoig== =soou -END PGP SIGNATURE-
Re: Security Check generated by AXENT Netrecom 3.0 points security flaw in qmail-smtpd
On Tue, Aug 14, 2001 at 08:59:47AM -0300, Agnaldo M. Monteiro wrote: > SMTP allows remote command execution via recipient filter. As you didn't show us the SMTP transaction we can only guess what's meaned. My guess is for RCPT TO: "|/path/to/anything" or something likely. This is no risk in qmail. A false positive once more. -- * Henning Brauer, [EMAIL PROTECTED], http://www.bsws.de * * Roedingsmarkt 14, 20459 Hamburg, Germany * Unix is very simple, but it takes a genius to understand the simplicity. (Dennis Ritchie)
Security Check generated by AXENT Netrecom 3.0 points security flaw in qmail-smtpd
Hi all, I have qmail 1.03, with tcpserver, vpopmail and qmailscanner and when I test my network for vulnerabilities using AXENT Netrecom 3.0 the following security results is displayed about my qmail server host: SMTP allows remote command execution via recipient filter. Risk: 86 Description: Attackers can execute arbitrary shell commands by addressing e-mail to a filter. Note: If your SMTP software does not support filters, this is not a vulnerability. if you are not sure if your SMTP software supports filters, contact your vendor. This vulnerability aplies primarily to UNIX systems. Solution: Upgrade or replace your SMTP server, or verify that it does not support filter. Questions: Anybody know anything about this? Where can I get additional information about this? This Results checks is True or false? (Sorry by my poor english) Best regards, Agnaldo Mariano Monteiro
Re: Unsubscribe from qmail mailing lists
Hi!, I had subscribed to receive qmail mailing lists messages by sending an empty message to [EMAIL PROTECTED] from my subscribed address i.e [EMAIL PROTECTED], now i want to unsubscribe from it as i have subscribed with my other address. I tried sending an empty message from the same address to [EMAIL PROTECTED], but it gave me an error message which is as below,can you help me with this it is urgent. Thanks & Regards Franco.F Hi! This is the ezmlm program. I'm managing the [EMAIL PROTECTED] mailing list. Acknowledgment: The address [EMAIL PROTECTED] is not on this mailing list. See http://pobox.com/~djb/qmail.html for more information about qmail. Please read http://pobox.com/~djb/qmail/faq.html before sending your question to the qmail mailing list. --- Here are the ezmlm command addresses. I can handle administrative requests automatically. Just send an empty note to any of these addresses: <[EMAIL PROTECTED]>: Receive future messages sent to the mailing list. <[EMAIL PROTECTED]>: Stop receiving messages. <[EMAIL PROTECTED]>: Retrieve a copy of message 12345 from the archive. DO NOT SEND ADMINISTRATIVE REQUESTS TO THE MAILING LIST! If you do, I won't see them, and subscribers will yell at you. To specify [EMAIL PROTECTED] as your subscription address, send mail to <[EMAIL PROTECTED]>. I'll send a confirmation message to that address; when you receive that message, simply reply to it to complete your subscription. --- Below this line is a copy of the request I received. Return-Path: <[EMAIL PROTECTED]> Received: (qmail 17465 invoked from network); 7 Aug 2001 11:00:43 - Received: from unknown (HELO support-34) (203.197.56.227) by muncher.math.uic.edu with SMTP; 7 Aug 2001 11:00:43 - Received: from 192.68.1.200 by support-34 ([192.68.1.34] running VPOP3) with ESMTP for <[EMAIL PROTECTED] >; Tue, 7 Aug 2001 16:25:07 +0530 To: [EMAIL PROTECTED] X-Mailer: Lotus Notes Release 5.0.4 June 8, 2000 Message-ID: From: "FRANCO FERNANDES" <[EMAIL PROTECTED]> Date: Tue, 7 Aug 2001 15:35:03 +0530
Re: qmail + Courrier-IMAP vs just Courrier-IMAP server (newbie)
#include On Tue, Aug 14 2001, Jean-Christian Imbeault <[EMAIL PROTECTED]> wrote: > My original plan was to install qmail - VMailMgr - Courrier-IMAP. But after > a little reading I find out that Courrier-IMAP has it own email server > implementation. So it seems that qmail is not needed? Yeah, it seams so. > Am I right? If so what are the advantages/disadvantages to either using > qmail with the Courrier-IMAP engine or just using Courrier as the mail and > IMAP server? No, you're wrong. There're some nifty features like userauth and tlsauth in courier, but just look into the source code. I don't say that's a mess but there're some design flaws in that what are missing from qmail. ---jul
Re: How to Unsubscribe from qmail mailing lists
Hi!, I had subscribed to receive qmail mailing lists messages by sending an empty message to [EMAIL PROTECTED] from my subscribed address i.e [EMAIL PROTECTED], now i want to unsubscribe from it as i have subscribed with my other address. I tried sending an empty message from the same address to [EMAIL PROTECTED], but it gave me an error message which is as below,can you help me with this it is urgent. Thanks & Regards Franco.F Hi! This is the ezmlm program. I'm managing the [EMAIL PROTECTED] mailing list. Acknowledgment: The address [EMAIL PROTECTED] is not on this mailing list. See http://pobox.com/~djb/qmail.html for more information about qmail. Please read http://pobox.com/~djb/qmail/faq.html before sending your question to the qmail mailing list. --- Here are the ezmlm command addresses. I can handle administrative requests automatically. Just send an empty note to any of these addresses: <[EMAIL PROTECTED]>: Receive future messages sent to the mailing list. <[EMAIL PROTECTED]>: Stop receiving messages. <[EMAIL PROTECTED]>: Retrieve a copy of message 12345 from the archive. DO NOT SEND ADMINISTRATIVE REQUESTS TO THE MAILING LIST! If you do, I won't see them, and subscribers will yell at you. To specify [EMAIL PROTECTED] as your subscription address, send mail to <[EMAIL PROTECTED]>. I'll send a confirmation message to that address; when you receive that message, simply reply to it to complete your subscription. --- Below this line is a copy of the request I received. Return-Path: <[EMAIL PROTECTED]> Received: (qmail 17465 invoked from network); 7 Aug 2001 11:00:43 - Received: from unknown (HELO support-34) (203.197.56.227) by muncher.math.uic.edu with SMTP; 7 Aug 2001 11:00:43 - Received: from 192.68.1.200 by support-34 ([192.68.1.34] running VPOP3) with ESMTP for <[EMAIL PROTECTED] >; Tue, 7 Aug 2001 16:25:07 +0530 To: [EMAIL PROTECTED] X-Mailer: Lotus Notes Release 5.0.4 June 8, 2000 Message-ID: From: "FRANCO FERNANDES" <[EMAIL PROTECTED]> Date: Tue, 7 Aug 2001 15:35:03 +0530
qmail + Courrier-IMAP vs just Courrier-IMAP server (newbie)
My original plan was to install qmail - VMailMgr - Courrier-IMAP. But after a little reading I find out that Courrier-IMAP has it own email server implementation. So it seems that qmail is not needed? Am I right? If so what are the advantages/disadvantages to either using qmail with the Courrier-IMAP engine or just using Courrier as the mail and IMAP server? Thanks! Jc _ Get your FREE download of MSN Explorer at http://explorer.msn.com/intl.asp
Re: Qmail-Scanner
On 14 Aug 2001 02:47:18 +0200, Craig Spiers <[EMAIL PROTECTED]> wrote: > is there any way to make qmail-scanner leave an email it has been scanned > allready? You do not want to do this, because between two runs of the qmail-scanner is one .qmail file, where it is very simple to add a virus... Greetings -- Robert Sander Computer Scientist Epigenomics AG Bioinformatics R&Dwww.epigenomics.com Kastanienallee 24 +493024345330 10435 Berlin
Qmail-Scanner
Hi All, Im using qmail-scanner etc.. I have one problem however, im using fastforward to do aliasing, and qmail- scanner scan's and print's headers on the email's twice .. is there any way to make qmail-scanner leave an email it has been scanned allready? Regards, Craig
Re: why does Hotmail put Qmail emails to "Junk Mail"?
> > Return-Path : <[EMAIL PROTECTED]> > > From : [EMAIL PROTECTED] >This _may_ be the reason. That was it! It was the headers. They need to have an X-Sender, X-Mailer, RFC 822 formatted date, and Return-Path, or Hotmail puts it in the Junk Mail folder automatically. Thanks Henning & everyone who helped.
Re: why does Hotmail put Qmail emails to "Junk Mail"?
On Mon, Aug 13, 2001 at 02:20:54PM -0700, CD Baby wrote: > Return-Path : <[EMAIL PROTECTED]> > From : [EMAIL PROTECTED] This _may_ be the reason. I'm not sure, though. Try using qmail-inject's -f options to set the envelope sender. -- * Henning Brauer, [EMAIL PROTECTED], http://www.bsws.de * * Roedingsmarkt 14, 20459 Hamburg, Germany * Unix is very simple, but it takes a genius to understand the simplicity. (Dennis Ritchie)
Re: why does Hotmail put Qmail emails to "Junk Mail"?
Sorry - I forwarded one I sent to my Hushmail account, because Hotmail doesn't let you see the full and complete headers. So - YES - email sent to my hotmail account had the exact address in the "To:" header. It wasn't CC:'d or anything - it was a unique email sent. So . . . maybe Hotmail is doing some kinda reverse lookup? (though my Qmail-SMTP box has its own reversed domain & IP... fully legit.) I thought maybe it was something else in the headers - because when I use that Qmail SMTP server with Eudora things go through fine. Again - I'll put the headers below if anyone might have any insight? > Does anyone know why Hotmail would put any of my Qmail-sent emails into the > "Junk Mail" folder automatically? > > How do they determine what's junk mail? Or - rather - how do I prove to > them this is not junk mail? To my knowledge, their only criteria is whether the recipient address appears in the To: or cc: headers. If it doesn't (mailing list mail, bcc'd mail), it's junk mail. > To : [EMAIL PROTECTED] > From : [EMAIL PROTECTED] The hotmail address doesn't appear in the To: header -- ergo, it's junk mail. Here are my Qmail headers (when sent to hushmail - which can show you full headers.) --- Return-Path : <[EMAIL PROTECTED]> X-Sieve : cmu-sieve 2.0 Return-Path : <[EMAIL PROTECTED]> Received : from smtp1.hushmail.com (smtp1.hushmail.com [64.40.111.31]) by imap1.hushmail.com (Postfix) with ESMTP id 2BB615F02C7 for <[EMAIL PROTECTED]>; Mon, 13 Aug 2001 11:27:41 -0700 (PDT) Received : from mail.hitmedia.com (unknown [65.169.21.164]) by smtp1.hushmail.com (Postfix) with SMTP id 8D9881378B for <[EMAIL PROTECTED]>; Mon, 13 Aug 2001 11:24:36 -0700 (PDT) Received : (qmail 17552 invoked from network); 13 Aug 2001 18:25:50 - Received : from unknown (HELO qmail.hitmedia.com) (65.169.21.163) by 65.169.21.164 with SMTP; 13 Aug 2001 18:25:50 - To : [EMAIL PROTECTED] From : [EMAIL PROTECTED] Subject : Testing this little mail to [EMAIL PROTECTED] Message-Id : <[EMAIL PROTECTED]> Date : Mon, 13 Aug 2001 11:24:36 -0700 (PDT) [EMAIL PROTECTED] - Hey - how are you? Just testing this thing.
Re: Qmail deferred messages..
Leonardo <[EMAIL PROTECTED]> wrote: > > I need to change the time of deferred messages in qmail. My server is = > very busy and I need retry to send every 15 minutes the messages. > How and where I can change in the source code to make this? Don't. qmail doesn't try "every 10 minutes" or "every five minutes". It retries with a quadratic backoff algorithm, less frequently as the message ages. What problem are you trying to solve? Perhaps your hardware is under-spec'ed for the amount of mail you're trying to handle. Charles -- --- Charles Cazabon<[EMAIL PROTECTED]> GPL'ed software available at: http://www.qcc.sk.ca/~charlesc/software/ ---
Qmail deferred messages..
Hello Guys, I need to change the time of deferred messages in qmail. My server is = very busy and I need retry to send every 15 minutes the messages. How and where I can change in the source code to make this? Thankz a lot.
Re: Qmail, tcpserver, environment variables, and qmail-smtpd
Bill Arlofski <[EMAIL PROTECTED]> wrote: > > I am trying to understand the purpose of being able to set environment > variables like $TCPREMOTEHOST with tcpserver for incoming connections > (ie: using the -h option or -p 'paranoid' option to perform reverse DNS > lookups) and set or unset the $TCPREMOTEHOST variable based on DNS > information. when qmail-smtpd does not seem to care, or make any use of it. > > Is a shell script to be called in place of qmail-smtpd to check > environment variables, then pass control back onto qmail-smtpd? Yes. Write a small wrapper that checks either for the presence of the appropriate environment variable, or checks that the given variable is non-empty, and either execs the rest of its commandline (if the variable meets your criteria) or exits otherwise. Then insert this wrapper in the tcpserver commandline before qmail-smtpd. Charles -- --- Charles Cazabon<[EMAIL PROTECTED]> GPL'ed software available at: http://www.qcc.sk.ca/~charlesc/software/ ---
Re: Hot to add POP3 users to qmail? (newbie)
yes, you for sure are right this questions are answered in a FAQ or lWQ i guess ;) qmail serves all unix users on your local system as .. umm local users even :) They have to have a home dir and a Maildir (depending on your setup using LWQ) as regular unix have, thats how it works. But, not just for the comfort, i recommend you using vpopmail (www.inter7.com/vpopmail), because it supports so called virtual domains. And also the "main" domain can be a virtual. Whats the most advantage part of it, also on small systems? IMHO its because, regular users do have its own UID and GID (user id group id), virtual users (using vpopmail) only takes one UID/GID to manage them all. Another advantage, there are good tools to administer them all with your webbrowser. Just have a try at www.inter7.com/qmailadim. YOu can add/del/ set their passwords etc etc.. hth Anton Pirnat Jean-Christian Imbeault wrote: > > I've gone throuhg lwq and have just finished installing qmail-pop3d and > checkpassword for qmail. They seem to be working. > > However lwq is a little short on how to actually add POP3 user accounts. Can > anyone point me to some documentation on how to add POP3 users? (If this is > a FAQ or in lwq sorry for asking but I did look and couldn't find it). > > Also there aren't any local users, so I don't want to do anything like > setting up a seperate $HOME/username directory for every user ... if > avoidable. > > Thanks! > > Jc > > _ > Get your FREE download of MSN Explorer at http://explorer.msn.com/intl.asp
Re: Hot to add POP3 users to qmail? (newbie)
On Mon, Aug 13, 2001 at 10:24:36AM +, Jean-Christian Imbeault wrote: > However lwq is a little short on how to actually add POP3 user accounts. Can > anyone point me to some documentation on how to add POP3 users? (If this is > a FAQ or in lwq sorry for asking but I did look and couldn't find it). man passwd ( if you are using linux ) the standard checkpasswd does only support standard *nix users, which are located in the /etc/passwd file. If you want to use virtual users, you have to use another solution. > Also there aren't any local users, so I don't want to do anything like > setting up a seperate $HOME/username directory for every user ... if > avoidable. yes, this is avoidable, you have to use something like vmailmgr. google.com is your friend -- Lukas Beeler<[EMAIL PROTECTED]> GPG Fingerprint: 8030 1C2F 66C5 9D80 AA31 6604 7D4D 0A67 68D8 B67E
Hot to add POP3 users to qmail? (newbie)
I've gone throuhg lwq and have just finished installing qmail-pop3d and checkpassword for qmail. They seem to be working. However lwq is a little short on how to actually add POP3 user accounts. Can anyone point me to some documentation on how to add POP3 users? (If this is a FAQ or in lwq sorry for asking but I did look and couldn't find it). Also there aren't any local users, so I don't want to do anything like setting up a seperate $HOME/username directory for every user ... if avoidable. Thanks! Jc _ Get your FREE download of MSN Explorer at http://explorer.msn.com/intl.asp
qmail Digest 13 Aug 2001 10:00:00 -0000 Issue 1455
qmail Digest 13 Aug 2001 10:00:00 - Issue 1455
Topics (messages 67735 through 67761):
Re: qmail-lspawn patch for hosting multiple local domains
67735 by: Andre Oppermann
67738 by: Henning Brauer
Re: Perl and Qmail
67736 by: Henning Brauer
Re: pop3d question
67737 by: Henning Brauer
qmail & anti-virii
67739 by: Averroes
67742 by: Eduardo Augusto Alvarenga
67743 by: Noel Mistula
67744 by: Bill Arlofski
rblsmtpd and 'tagging' emails
67740 by: Qmail
67741 by: Henning Brauer
Qmail, tcpserver, environment variables, and qmail-smtpd
67745 by: Bill Arlofski
temporary qmail-inject error
67746 by: KY Lui
67760 by: Ross Cooney
qmail-pop3d
67747 by: qmail
67748 by: Greg White
local-local delivery error (newbie)
67749 by: Jean-Christian Imbeault
67752 by: Johan Almqvist
67756 by: Jean-Christian Imbeault
67759 by: Johan Almqvist
qmail, avoid spam mail
67750 by: KY Lui
67751 by: Brett Randall
Cannot find host with name... error
67753 by: Sito Garcia
67755 by: meling
67761 by: Sito Garcia
checkpassword and IMAP
67754 by: meling
overwrite locals
67757 by: Peter Marenbach
Question about Process Usage and running problems (newbie)
67758 by: Dave Lewis
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]
--
MarkD wrote:
>
> On Sat, Aug 11, 2001 at 11:41:52AM +0200, Andre Oppermann allegedly wrote:
> > MarkD wrote:
> > >
> > > > argument, the name of the local user to verify. This patch makes
> > > > qmail-lspawn call qmail-getpw with two arguments; the name and the domain
> > > > of the local user to verify. This, together with a modified qmail-getpw,
> > > > will enable qmail to differentiate between the local domains that the
> > > > server is hosting.
> > >
> > > I have never checked, but I wonder whether the qmail-ldap guys have
> > > had to do the same thing?
> >
> > No, we did not have to. We're simply ignoring locals and virtualdomains
> > alltogether for the ldap lookup. We simply take the whole address and
> > do the lookup. An entry in either locals or virtualdomains is still
> > neccessary because of the check for a valid domain. Unless you run it
> > in mixed mode (ldap and normal) it doesn't matter whether you put the
> > domain into locals or virtualdomains.
>
> Oh. So LDAP lookups are run out of a .qmail-default or similar? FWIW,
> the original motive for the patch was to authentication using LDAP but
> we wanted to avoid the double queue insertion of a .qmail-default as
> it was a high-volume site. By writing an LDAP aware qmail-getpw and
> apply the patch we achieved that.
No, qmail-ldap is not doing .qmail-default. Instead it sort of replaces
the users file. The ldap lookup code is integrated into qmail(-spawn)
itself. Also checkpassword is adjusted for this. It can either interpret
the password field itself or do a connect to the ldap server with the
specified user name and password. Then the ldap server is checking the
password.
> Of course that was prior to the existence of either qmail-ldap or
> maildrop which presumably could be combined to achieve almost the same
> results - assuming single-uid delivery is acceptable.
You can specify the UID/GID for every user in the ldap object.
--
Andre
On Fri, Aug 10, 2001 at 08:26:43PM +, MarkD wrote:
> > argument, the name of the local user to verify. This patch makes
> > qmail-lspawn call qmail-getpw with two arguments; the name and the domain
> > of the local user to verify. This, together with a modified qmail-getpw,
> > will enable qmail to differentiate between the local domains that the
> > server is hosting.
>
> I have never checked, but I wonder whether the qmail-ldap guys have
> had to do the same thing?
No. You need to forget aboy some qmail stuff when using qmail-ldap. We just
have user accounts and assigned mail addresses. VEry straightforward. A
simple (simplyfied) user entry looks like
dn: cn=brahe, ou=intern, dc=bsws, dc=de
cn: brahe
userPassword: {crypt}censored
uid: brahe
mail: [EMAIL PROTECTED]
mailAlternateAddress: [EMAIL PROTECTED]
mailAlternateAddress: [EMAIL PROTECTED]
and so on.
Basically, in qmail-lspawn a search using the filter
(|(mail=address)(mailalternateaddress=address))
is done, where address is the full rcpt address.
For auth'ing the uid and userPassword a
Re: temporary qmail-inject error
On Mon, Aug 13, 2001 at 11:28:10AM +0800, KY Lui wrote: > hello > > i found "temporary qmail-inject error" in qmail log file > what's the meaning? > It means that you have messed with the qmail-queue or qmail-inject files. Please post more information, versions of software, output of log files, and start up scripts. _ Ross Cooney Virus Scanner: http://www.antivirus.ie/index.mv?free_scan=1 Perl Tutorial: http://www.cyber-sentry.com/perl/tut.mv?art=1
Re: qmail, avoid spam mail
>>>>> On Mon, 13 Aug 2001 14:28:53 +0800, KY Lui <[EMAIL PROTECTED]> said: > Hello recently, i found that someone using my qmail server to send > mail. how can i avoid this? 1. Include logs in your mail 2. Tell us how they used your qmail server to send mail 3. Reinstall using www.lifewithqmail.org -- Programming today is a race between software engineers striving to build bigger and better idiot-proof programs, and the Universe trying to produce bigger and better idiots. So far, the Universe is winning.
qmail, avoid spam mail
Title: qmail, avoid spam mail Hello recently, i found that someone using my qmail server to send mail. how can i avoid this? thanks regards KY
Re: qmail-pop3d
On Mon, Aug 13, 2001 at 11:42:25AM -0400, qmail wrote: > After I test the qmail-smtpd and qmail-send is ok,it seems to me ok. > I try to install qmail-pop3d and start this service. > I add the run script in /var/qmail/supervise/qmail-pop3d > I use the method to test the checkpasswd program, the response is ok. > #!/bin/sh > exec /usr/local/bin/softlimit -m 200 /usr/local/bin/tcpserver -v -R > -H -l 0 0 110 /var/qmail/bin/qmail-popup sbs01.helka.com.hk > /bin/checkpassword /var/qmail/bin/qmail-pop3d Maildir 2>&1 > > but I find a process: > root 8461 0.0 0.0 00 ?Z11:17 0:00 > [supervise > is it ok? > I can't check the pop3 with email client. > > anything that I should install after enable qmail-pop3d? I have two questions for you: 1. What is the output of 'svstat /service/*' ? 2. Is it just linewrap issues, or is 'run' really multilined without escape characters like that? -- Greg White
qmail-pop3d
After I test the qmail-smtpd and qmail-send is ok,it seems to me ok. I try to install qmail-pop3d and start this service. I add the run script in /var/qmail/supervise/qmail-pop3d I use the method to test the checkpasswd program, the response is ok. #!/bin/sh exec /usr/local/bin/softlimit -m 200 /usr/local/bin/tcpserver -v -R -H -l 0 0 110 /var/qmail/bin/qmail-popup sbs01.helka.com.hk /bin/checkpassword /var/qmail/bin/qmail-pop3d Maildir 2>&1 but I find a process: root 8461 0.0 0.0 00 ?Z11:17 0:00 [supervise
temporary qmail-inject error
Title: temporary qmail-inject error hello i found "temporary qmail-inject error" in qmail log file what's the meaning? thanks regards KY
Qmail, tcpserver, environment variables, and qmail-smtpd
Quick question regarding tcpserver, environment variables, and qmail-smtpd. I'd like to be able to stop inbound smtp connections for systems that don't have at least a DNS A record. I mean, c'mon... If you are running a mail server, it should have a valid DNS entry, no? Anyway, here is where tcpserver comes in, or so I thought. I figure I can use the default -h option (or -p 'parinoid') to set the $TCPREMOTEHOST variable for inbound servers with valid DNS entries, and have inbound connections stopped or allowed based on that, right? Wrong. (or so far it appears to be wrong) I am trying to understand the purpose of being able to set environment variables like $TCPREMOTEHOST with tcpserver for incoming connections (ie: using the -h option or -p 'paranoid' option to perform reverse DNS lookups) and set or unset the $TCPREMOTEHOST variable based on DNS information. when qmail-smtpd does not seem to care, or make any use of it. Is a shell script to be called in place of qmail-smtpd to check environment variables, then pass control back onto qmail-smtpd? Any comments, or pointers would be appreciated, even if you are just going to tell me I am being too paranoid.:) Bill Arlofski Unix Systems Administrator The Hotchkiss School [EMAIL PROTECTED]
Re: qmail & anti-virii
I am working through a few last minor issues, but Kaspersky Antivirus for Linux servers has a nice qmail integration piece. http://www.kaspersky.com (You'll want at least the August 1st 3.5 build 136 version - mime problems with earlier versions) Basically, you start the antivirus daemon, rename the original qmail-queue file, drop Kaspersky's qmail-queue in it's place. qmail-smtpd passes inbound mail to the Kaspersky qmail-queue which performs the scan via the running daemon process, then passes off virus-free email to the original qmail-queue program. Logging is to syslog, or a file, or both. You have options of emailing the offending users that they have sent infected email (most of these I am finding are getting bounced for all the obvious reasons). You can also send an administrative mail to your network admins to keep you up to date on incoming (or outgoing) email virus activity. I am pretty happy with it. I'd be glad to comment more, show configs, or help in any way.. I just don't want to clog up the list on my first day here. Averroes wrote: >Hi There, > >I am new in qmail and want to migrate qmail with security purposes >but I want to know how to deal with virus, worms, etc. > >It is possible to configure qmail with some tools >which check the contents of mail, attached docs, etc. > >All my server are Linux powered and all clients are Win2k. >This is why of my mail. > >Docs, Tutorials, etc. will be helpful. > >In advance Thanks! > >#-- ># Averroes A. Aysha http://www.keyserver.net/en/ ># Think Linux, Think Slackware! ># Network Security Auditor (NSA) ># [EMAIL PROTECTED] ># Fingerprint = 73B7 2559 2968 5094 3B95 5C70 4E85 5F94 6068 1DD8 >#-- > > >
Re: qmail & anti-virii
You can also try this script; http://www.ornl.gov/its/archives/mailing-lists/qmail/2001/03/msg01041.html don't forget to use the -i flag on all grep commands so that you won't miss the upper case characters. cheers Eduardo Augusto Alvarenga wrote: > > Averroes <[EMAIL PROTECTED]> wrote: > > > I am new in qmail and want to migrate qmail with security purposes > > but I want to know how to deal with virus, worms, etc. > > It is possible to configure qmail with some tools > > which check the contents of mail, attached docs, etc. > > All my server are Linux powered and all clients are Win2k. > > This is why of my mail. > > I encourage you to take a look at the AMaViS project at > http://www.amavis.org. Totally qmail compatible. > > Best Regards, > > -=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=- > Eduardo Augusto Alvarenga - Analista de Suporte - #179653 > Blumenau - Santa Catarina. Tel. (47) 9102-3303 >http://www.netron.com.br/~eduardo > -=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=- -- Noel G. Mistula Network & Systems Administrator Meriton Apartments Pty Ltd
Re: qmail & anti-virii
Averroes <[EMAIL PROTECTED]> wrote: > I am new in qmail and want to migrate qmail with security purposes > but I want to know how to deal with virus, worms, etc. > It is possible to configure qmail with some tools > which check the contents of mail, attached docs, etc. > All my server are Linux powered and all clients are Win2k. > This is why of my mail. I encourage you to take a look at the AMaViS project at http://www.amavis.org. Totally qmail compatible. Best Regards, -=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=- Eduardo Augusto Alvarenga - Analista de Suporte - #179653 Blumenau - Santa Catarina. Tel. (47) 9102-3303 http://www.netron.com.br/~eduardo -=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-
qmail & anti-virii
Hi There, I am new in qmail and want to migrate qmail with security purposes but I want to know how to deal with virus, worms, etc. It is possible to configure qmail with some tools which check the contents of mail, attached docs, etc. All my server are Linux powered and all clients are Win2k. This is why of my mail. Docs, Tutorials, etc. will be helpful. In advance Thanks! #-- # Averroes A. Ayshahttp://www.keyserver.net/en/ # Think Linux, Think Slackware! # Network Security Auditor (NSA) # [EMAIL PROTECTED] # Fingerprint = 73B7 2559 2968 5094 3B95 5C70 4E85 5F94 6068 1DD8 #--
Re: qmail-lspawn patch for hosting multiple local domains
On Fri, Aug 10, 2001 at 08:26:43PM +, MarkD wrote:
> > argument, the name of the local user to verify. This patch makes
> > qmail-lspawn call qmail-getpw with two arguments; the name and the domain
> > of the local user to verify. This, together with a modified qmail-getpw,
> > will enable qmail to differentiate between the local domains that the
> > server is hosting.
>
> I have never checked, but I wonder whether the qmail-ldap guys have
> had to do the same thing?
No. You need to forget aboy some qmail stuff when using qmail-ldap. We just
have user accounts and assigned mail addresses. VEry straightforward. A
simple (simplyfied) user entry looks like
dn: cn=brahe, ou=intern, dc=bsws, dc=de
cn: brahe
userPassword: {crypt}censored
uid: brahe
mail: [EMAIL PROTECTED]
mailAlternateAddress: [EMAIL PROTECTED]
mailAlternateAddress: [EMAIL PROTECTED]
and so on.
Basically, in qmail-lspawn a search using the filter
(|(mail=address)(mailalternateaddress=address))
is done, where address is the full rcpt address.
For auth'ing the uid and userPassword attributes count. There is no need in
qmail-ldap to distinguisch between local part and domain part in an address,
and there is no relation between email addresses and uids except that they
belong to an user account.
--
* Henning Brauer, [EMAIL PROTECTED], http://www.bsws.de *
* Roedingsmarkt 14, 20459 Hamburg, Germany *
Unix is very simple, but it takes a genius to understand the simplicity.
(Dennis Ritchie)
Re: Perl and Qmail
On Fri, Aug 10, 2001 at 08:44:56AM -0700, Greg White wrote: > I'm not aware of any _reason_ you'd want to recieve mail in a Perl > program -- that's what your MTA is there for. Ever thought about Mailrobots? I've written tons of them - how do you think all the domains get registered? -- * Henning Brauer, [EMAIL PROTECTED], http://www.bsws.de * * Roedingsmarkt 14, 20459 Hamburg, Germany * Unix is very simple, but it takes a genius to understand the simplicity. (Dennis Ritchie)
Re: Perl and Qmail
On Fri, Aug 10, 2001 at 03:10:29PM +, eric wrote: > > > > - Original Message - > > [snip] > > > > > I'm not aware of any _reason_ you'd want to recieve mail in a Perl > > program -- that's what your MTA is there for. > > > > Using perl to create your own MUA, using perl to create an > autoresponder, blah, blah, blah..., using perl to grab the stuff > from your inbox and then process it. > Possibly my misunderstanding of what the OP meant by 'recieve' -- all that stuff happens at the filesystem level or MDA level, not at the level of receipt, at least to my mind. (I had visions of him trying to get a daemon to listen on 25 and accept connections. :) ) -- Greg White
Re: Perl and Qmail
- Original Message - [snip] > > I'm not aware of any _reason_ you'd want to recieve mail in a Perl > program -- that's what your MTA is there for. > Using perl to create your own MUA, using perl to create an autoresponder, blah, blah, blah..., using perl to grab the stuff from your inbox and then process it. Eric Calvert
Re: Perl and Qmail
On Fri, Aug 10, 2001 at 01:45:35PM -, Frederik Van Herterijck wrote: > I'm having some problems sending e-mail from within a perl program > using qmail. > > Can someone tell me how I can easily send and receive mails in perl > using qmail. I'm trying and trying but nothing works. > Qmail works perfectly. This isn't really a qmail question. Reply-to set appropriately. Perl has nearly any way you can imagine to send mail. 1. Net::SMTP -- this is the one I prefer 2. using a pipe to qmail-inject (mentioned elsewhere in this thread) 3. using a pipe to the sendmail wrapper are the best three, in order, IMHO. I'm not aware of any _reason_ you'd want to recieve mail in a Perl program -- that's what your MTA is there for. -- Greg White
Re: Perl and Qmail
Hi Frederik, > I'm having some problems sending e-mail from within a perl program > using qmail. try opening a 'pipe' to qmail-inject and send your mail in -- open(INJECTPIPE, "| qmail-inject"); print all you info to the pipe Bcc: Cc: From: Reply-To: Subject: and the other stuff required after that, the text of the mail example: print INJECTPIPE "Subject: " . . "\n"; then close(INJECTPIPE); -- works like a charm and is very fast :-) that's for sending, receiving could be done by processing $HOME/Maildir/new/* or doing the SMTP-handling yourself, which I would try to avoid (qmail is better than you doing this :-) hope this helps, Chris
Perl and Qmail
I'm having some problems sending e-mail from within a perl program using qmail. Can someone tell me how I can easily send and receive mails in perl using qmail. I'm trying and trying but nothing works. Qmail works perfectly. It should be nice to have some perl-code which does this. Thankx Frederik
qmail exit codes..?
Hey folks. So, more questions. Always, eh. I've got a script that uses the qmail-queue patch that scans and logs/drops/saves/rejects mail based on content.. What I'm wondering is if there is a way I can change the "message" that is sent when various exit codes are recieved? For example, if I exit(31) I get: (reason: 554 mail server permanently rejected message (#5.3.0) If I exit anything else between 11 and 40 except 11 and 31, I get: (reason: 554 qq permanent problem (#5.3.0) man qmail-queue pretty much mentions this as well. Also, looking at qmail.c I see the full list of what does what. (its right at the bottom, easy to find.) Now, I could obviously twist on this to get it to produce a desired message...(even I with my nonexistant programming skills could probably handle it...it doesnt look like it would take much more then a line or so..) BUT, I'd rather not add more patches then I have to, so I fall on the accumulated wisdom here. Is there a way, short of a code patch, that I can change the "message" that is sent back when a certian exit code is returned? I'm not seeing anything in the scattered docs... I know that bouncesaying pretty much does this...but I dont think it would be good to use bouncesaying in the between-smtpd and -queue stages...would it? I'm finding no reference to how it pulls this off in the docs, and the code..well...its the sort that makese no sense to me. :) I googled on this for a bit and came up with nada...but I dont claim to be very good at searches...ah well. Any suggestions or pointers? thanksdavid -- David Raistrick (deep in the south georgia woods) [EMAIL PROTECTED]
Re: Removing Headers with qmail
On Thu, Aug 09, 2001 at 11:47:44PM +0800, Paul Tan wrote: > I am looking for a solution to remove most of the headers in a message, so > that the recepient cannot see any info of my internal network. If you're using tcpserver (and if you're not, you should be), see: http://marc.theaimsgroup.com/?l=qmail&m=98678523400345&w=2 for a painless solution to your problem. Chris PGP signature
Re: qmail-queue question
Edward McLain <[EMAIL PROTECTED]> wrote: > > Ok.. so qmail-remote crashed.. but why? Who knows? Did you kill it? > It had also been running for over 3 hours? So? Long messages to a slow host can do this. > Well to test it out I did the following: [...] You didn't use proper SMTP syntax, which qmail-remote would have. Who says you connected to the same machine as qmail-remote did? "mx09.mindspring.com" could be a cluster of machines sitting behind a load balancer. > mail from: [EMAIL PROTECTED] > rcpt to: [EMAIL PROTECTED] This isn't proper SMTP. > Any ideas? Just one: stop worrying until you have evidence of an actual problem. Everything you've described so far can be completely normal behaviour. Charles -- --- Charles Cazabon<[EMAIL PROTECTED]> GPL'ed software available at: http://www.qcc.sk.ca/~charlesc/software/ ---
Re: qmail-queue question
> Ok.. so as someone pointed out I have to now search by the deliver > number.. So I ran: > > [root@mail send]# grep "delivery 366" * | /usr/local/bin/tai64nlocal > 2001-08-09 13:41:28.533103500.s:@40003b72c36a2839ff1c starting > delivery 366: msg 112603 to remote [EMAIL PROTECTED] > [root@mail send]# > > Ok.. so the last attempt started at 1:41PM.. > So what happened to the one before it? > > [root@mail send]# grep "delivery 26:" * | /usr/local/bin/tai64nlocal > 2001-08-09 10:17:31.319774500.s:@40003b72a32e0b08b30c starting > delivery 26: msg 112603 to remote [EMAIL PROTECTED] > 2001-08-09 13:41:28.533103500.s:@40003b72c33a3620be2c delivery 26: > deferral: qmail-remote_crashed./ > [root@mail send]# > > Ok.. so qmail-remote crashed.. but why? Unless something very unusual is happening to your system, I'd say that someone or something killed it. An unpatched qmail-remote has no record of crashing in the last, oh, 3 years of people using it. > It had also been running for over 3 hours? That's not necessarily a problem. Mail is allowed to get stuck. Is any mail getting thru to these sites or are they all failing? > Well to test it out I did the following: > > [root@mail qmail]# telnet mx09.mindspring.com 25 > Trying 207.69.200.36... > Connected to mx09.mindspring.com. > Escape character is '^]'. > 220 pickering.mail.mindspring.net EL_3_4_0 /EL_3_4_0 ESMTP Earthlink > Mail Service Thu, 9 Aug 2001 16:20:40 -0400 (EDT) > helo mail.highspd.net > 250 pickering.mail.mindspring.net Hello mail.highspd.net > [208.62.90.230], please to meet you > mail from: [EMAIL PROTECTED] > 250 [EMAIL PROTECTED] Sender ok > rcpt to: [EMAIL PROTECTED] > 250 <[EMAIL PROTECTED]>... Recipient ok > data > 354 Enter mail, end with "." on a line by itself > this is a test. > please disregard > . > 250 tn5s62.1dc.37kbi14 Message accepted for delivery > quit > 221 pickering.mail.mindspring.net closing connection > Connection closed by foreign host. > > Ok.. so I can send mail directly just fine.. So what in the heck is > going on here? This is what is puzzling me the most..? Hard to say. It could be that the contents of the mail are a problem for mindspring, are they large? Do they have binary data? It could be that qmail-remote is connecting to an MX that's particularly slow or dead. It could be that you have an smtproutes entry for that domain that points incorrectly. > BTW.. this was happening with "stock" qmail also before I patched it > with the qmail-queue patch for qmailscanner. If you are saying you are sure that qmail-remote was crashing with a stock qmail install, then I'd be highly suspicious of a library/compiler/OS problem. I know that might sound like a cop-out, but a crashing qmail-remote is virtually unheard of. It's also possible that there is some sort of system resource that is becoming unavailable causing the kernel to kill the qmail-remote. Does this happen to all qmail-remotes or only those sending to mindspring? Does it happen to all qmail-remotes or only those that run for a long time? If you can reliably determine which ones are going to crash in advance of them crashing, then do a system call trace on one of them to see why it's dying. Show us the trace. Regards.
RE: qmail-queue question
Ok.. after searching through the logs for a bit, I have discovered the following about some of the messages getting stuck in the queue.. This is the method I used to do this test, if it's wrong tell me, but this is what I did. First off I ran: [root@mail qmail]# ps ax | grep qmail-remote | wc -l 35 Not a problem. So now I run: [root@mail qmail]# ps ax | grep qmail-remote 1822 ?S 0:00 qmail-remote mindspring.com [EMAIL PROTECTED] [EMAIL PROTECTED] 1826 ?S 0:00 qmail-remote mindspring.com [EMAIL PROTECTED][EMAIL PROTECTED] 1827 ?S 0:00 qmail-remote mindspring.com [EMAIL PROTECTED][EMAIL PROTECTED] 1833 ?S 0:00 qmail-remote mindspring.com [EMAIL PROTECTED] [EMAIL PROTECTED] 1834 ?S 0:00 qmail-remote mindspring.com [EMAIL PROTECTED] [EMAIL PROTECTED] 1836 ?S 0:00 qmail-remote mindspring.com [EMAIL PROTECTED] [EMAIL PROTECTED] 1838 ?S 0:00 qmail-remote mindspring.com [EMAIL PROTECTED][EMAIL PROTECTED] 1839 ?S 0:00 qmail-remote msn.com [EMAIL PROTECTED] [EMAIL PROTECTED] 1841 ?S 0:00 qmail-remote msn.com [EMAIL PROTECTED] 1842 ?S 0:00 qmail-remote mindspring.com mcculley@in- prepaid.com [EMAIL PROTECTED] 1843 ?S 0:00 qmail-remote mindspring.com [EMAIL PROTECTED][EMAIL PROTECTED] 1844 ?S 0:00 qmail-remote mindspring.com [EMAIL PROTECTED] [EMAIL PROTECTED] 1846 ?S 0:00 qmail-remote mindspring.com [EMAIL PROTECTED][EMAIL PROTECTED] 1847 ?S 0:00 qmail-remote mindspring.com [EMAIL PROTECTED] [EMAIL PROTECTED] 1848 ?S 0:00 qmail-remote microsoft.com [EMAIL PROTECTED] 1850 ?S 0:00 qmail-remote mindspring.com [EMAIL PROTECTED][EMAIL PROTECTED] 1851 ?S 0:00 qmail-remote mindspring.com [EMAIL PROTECTED] 1852 ?S 0:00 qmail-remote mindspring.com [EMAIL PROTECTED][EMAIL PROTECTED] 1854 ?S 0:00 qmail-remote mindspring.com [EMAIL PROTECTED][EMAIL PROTECTED] 1855 ?S 0:00 qmail-remote msn.com [EMAIL PROTECTED] [EMAIL PROTECTED] 1856 ?S 0:00 qmail-remote mindspring.com [EMAIL PROTECTED][EMAIL PROTECTED] 1858 ?S 0:00 qmail-remote mindspring.com [EMAIL PROTECTED][EMAIL PROTECTED] 1859 ?S 0:00 qmail-remote mindspring.com mcculley@in- prepaid.com [EMAIL PROTECTED] 1860 ?S 0:00 qmail-remote mindspring.com [EMAIL PROTECTED][EMAIL PROTECTED] 1861 ?S 0:00 qmail-remote mindspring.com [EMAIL PROTECTED] [EMAIL PROTECTED] 1862 ?S 0:00 qmail-remote mindspring.com [EMAIL PROTECTED] [EMAIL PROTECTED] 1863 ?S 0:00 qmail-remote mindspring.com [EMAIL PROTECTED] [EMAIL PROTECTED] 1864 ?S 0:00 qmail-remote mindspring.com [EMAIL PROTECTED][EMAIL PROTECTED] 1865 ?S 0:00 qmail-remote mindspring.com [EMAIL PROTECTED] 1866 ?S 0:00 qmail-remote mindspring.com [EMAIL PROTECTED] [EMAIL PROTECTED] 1868 ?S 0:00 qmail-remote mindspring.com [EMAIL PROTECTED][EMAIL PROTECTED] 1869 ?S 0:00 qmail-remote mindspring.com [EMAIL PROTECTED][EMAIL PROTECTED] 1870 ?S 0:00 qmail-remote mindspring.com [EMAIL PROTECTED] [EMAIL PROTECTED] 1871 ?S 0:00 qmail-remote mindspring.com [EMAIL PROTECTED] [EMAIL PROTECTED] 1872 ?S 0:00 qmail-remote mindspring.com [EMAIL PROTECTED] [EMAIL PROTECTED] [root@mail qmail]# Nothing to weird here except all of the connections to mindspring.com. So I go and do a mailq and look up the message id numbers. Then I go do: [root@mail send]# grep 112603 * | /usr/local/bin/tai64nlocal 2001-08-08 17:42:58.097835500.s:@40003b71ba7b2578952c starting delivery38: msg 112603 to remote [EMAIL PROTECTED] 2001-08-08 20:42:43.879282500.s:@40003b71d96719f67df4 starting delivery44: msg 112603 to remote [EMAIL PROTECTED] 2001-08-08 20:42:43.879282500.s:@40003b71dec231dccf04 starting delivery129: msg 112603 to remote [EMAIL PROTECTED] 2001-08-09 10:17:31.319774500.s:@40003b72a32e0b08b30c starting delivery26: msg 112603 to remote [EMAIL PROTECTED] 2001-08-09 13:41:28.533103500.s:@40003b72c36a2839ff1c starting delivery366: msg 112603 to remote [EMAIL PROTECTED] [root@mail send]# Ok.. so as someone pointed out I have to now search by the deliver number.. So I ran: [root@mail send]# grep "delivery 366" * | /usr/local/bin/tai64nlocal 2001-08-09 13:41:28.533103500.s:@40003b72c36a2839ff1c starting delivery366: msg 112603 to remote [EMAIL PROTECTED] [root@mail send]# Ok.. so the last attempt started at 1:41PM.. So what happened to the one before it? [root@mail send]# grep "delivery 26:" * | /usr/local/bin/tai64nlocal 2001-08-09 10:17:31.319774500.s:@40003b72a32e0b08b30c starting delivery26: msg 112603 to remote [EMAIL PR
Re: qmail-queue question
Edward McLain <[EMAIL PROTECTED]> wrote: > > Not to start anything else, but is there any better way to stop qmail > when using tcp-daemonts than svc -d /service/qmail-send ? No -- that is the proper way to stop qmail with daemontools. > This doesn't seem to always work [...] Nope -- it always works. If not, you didn't install daemontools and your /service directories properly. Charles -- --- Charles Cazabon<[EMAIL PROTECTED]> GPL'ed software available at: http://www.qcc.sk.ca/~charlesc/software/ ---
Re: qmail-queue question
On Thu, Aug 09, 2001 at 12:39:28PM -0500, Edward McLain allegedly wrote: > > > -Original Message- > From: MarkD [mailto:[EMAIL PROTECTED]] > Sent: Thursday, August 09, 2001 12:23 PM > To: [EMAIL PROTECTED] > Subject: Re: qmail-queue question > > >> 3. When the queue shows the message arriving on 30 Jul 2001 15:08:23 > I > >> tend to think that it actually arrive at 3:08 on Jul 30 of 2001, that > is > >> unless qmail is doing something funking with date and time stamps. ;) > > >But you didn't show the log entry that corresponds to this message. As > >a consultant with 8 years experience you have probably deduced that > >*all* messages inserted into the queue create a "new msg" log > >entry. Where is it? > > There was no "new msg" log entry. Best I can tell the logs only go back > maybe 3 or 4 days and the messages originated 9 days ago.. Thus the > problem. It probably would have been helpful if you'd told us about this at the start. It seemed like you were trying to suggest that the log entry never existed. I guess that's a lesson for next time. > I took Richard's advice and added the socket keep-alive patch and that > actually seems to have fixed the problem. The old messages seemed to > have mysteriously disappeared after replacing the qmail-remote exec. Mysteriously? Since we've stressed the importance of looking at logs for answers, I'm sure you've checked the logs to solve the "mystery". What did they say? I'm sure if you bother, you'll see that it's not a "mystery" at all. Unless of course you kill -9 qmail-send, but no one or no docs have ever told you to do this, right? In any event, as I said in the the last post; queuelifetime applies *after* the last delivery attempt has exited. It's almost certainly the case that you killed qmail-remote (or it exited of its own accord) at which point qmail-send would notice that queuelifetime is exceeded and bounce the mail. The logs show this stuff by the way. > Not to start anything else, but is there any better way to stop qmail > when using tcp-daemonts than svc -d /service/qmail-send ? > > This doesn't seem to always work and I can't ever seem to get all the It always works. But qmail-send won't exit until all current deliveries have exited - in fact it logs an entry each time an outstanding delivery completes. Did you see different when you checked the logs? If so, show us. Edward, for someone with 8 years experience, you should rejoice that so many of your mysteries and misunderstandings can be solved by examining and understanding the logs. If the log messages are a mystery to you, there are plenty of archived posts explaining the messages. Regards.
Re: done qmail installation but can't telnet to port 25
On Thu, Aug 09, 2001 at 12:31:34PM +, Jean-Christian Imbeault wrote: > I've done the lwq installation. As a test I have tried to telnet from my > mail server to itself on port 25 to see if qmail is listening. But I get a > "connection refused" message. > > I've enable telnet in inetd.conf and my /etc/tcp.smtp file looks like this: Wy do you want people to connect to port 23 of your machine? You don't need a telnet server to use a telnet client... Are you running qmail-smtpd? _How_ are you running qmail-smtpd? Via inetd or via tcpserver? -- Brian 'you Bastard' Reichert<[EMAIL PROTECTED]> 37 Crystal Ave. #303Daytime number: (603) 434-6842 Derry NH 03038-1713 USA Intel architecture: the left-hand path
RE: qmail-queue question
-Original Message- From: MarkD [mailto:[EMAIL PROTECTED]] Sent: Thursday, August 09, 2001 12:23 PM To: [EMAIL PROTECTED] Subject: Re: qmail-queue question >> 3. When the queue shows the message arriving on 30 Jul 2001 15:08:23 I >> tend to think that it actually arrive at 3:08 on Jul 30 of 2001, that is >> unless qmail is doing something funking with date and time stamps. ;) >But you didn't show the log entry that corresponds to this message. As >a consultant with 8 years experience you have probably deduced that >*all* messages inserted into the queue create a "new msg" log >entry. Where is it? There was no "new msg" log entry. Best I can tell the logs only go back maybe 3 or 4 days and the messages originated 9 days ago.. Thus the problem. >> 5. To get the logs I went to /var/log/qmail/send and did a grep on the >> message id number like so: >> grep 112535 * >> If you know something I don't know, then please tell me, but as far as I >How long does the system keep the logs for? Has it been rolled off by, >eg, newsyslog? >> Any real help on this issue would be appreciated from anyone. >We want all the log entries associated with the message. If your log >system has rolled them off, then stop the log rolling so you can >retain all the information. Then pick an example that shows us the >full life-cycle of the message and how it exceeds queuelifetime after >the last delivery attempt. >It may simply be that the delivery program is not exiting. It's only >at the point that qmail-send looks at queuelifetime. >Regards. I took Richard's advice and added the socket keep-alive patch and that actually seems to have fixed the problem. The old messages seemed to have mysteriously disappeared after replacing the qmail-remote exec. Not to start anything else, but is there any better way to stop qmail when using tcp-daemonts than svc -d /service/qmail-send ? This doesn't seem to always work and I can't ever seem to get all the daemons to stop loading and running without editing /etc/inittab and commenting out the line that runs the svcscanboot and doing a kill -HUP 1. Then I have to do a kill or killall on all the qmail daemons to actually shut it down. Later, ed
Re: qmail-queue question
> 3. When the queue shows the message arriving on 30 Jul 2001 15:08:23 I > tend to think that it actually arrive at 3:08 on Jul 30 of 2001, that is > unless qmail is doing something funking with date and time stamps. ;) But you didn't show the log entry that corresponds to this message. As a consultant with 8 years experience you have probably deduced that *all* messages inserted into the queue create a "new msg" log entry. Where is it? > 5. To get the logs I went to /var/log/qmail/send and did a grep on the > message id number like so: > grep 112535 * > If you know something I don't know, then please tell me, but as far as I How long does the system keep the logs for? Has it been rolled off by, eg, newsyslog? > Any real help on this issue would be appreciated from anyone. We want all the log entries associated with the message. If your log system has rolled them off, then stop the log rolling so you can retain all the information. Then pick an example that shows us the full life-cycle of the message and how it exceeds queuelifetime after the last delivery attempt. It may simply be that the delivery program is not exiting. It's only at the point that qmail-send looks at queuelifetime. Regards.
Re: qmail-queue question
Edward McLain <[EMAIL PROTECTED]> wrote: > OK... Let me explain this a little bit better and maybe clear some > things up. Okay. > 2. The only patch on this system is the qmailqueue-patch for the > qmailscanner. This can cause qmail-queue to not be run, but not qmail-remote to crash. > 5. To get the logs I went to /var/log/qmail/send and did a grep on the > message id number like so: > grep 112535 * > If you know something I don't know, then please tell me, but as far as I > know, that scans all the files for that number and outputs the line, but > then again, what do I know. That doesn't give all the information about that message; in particular, delivery status lines don't contain the message number, only the delivery number, which you get from the "starting delivery" lines. > 6. You really could try to be just a little bit less of an ass to > everyone that may seem new and actually *TRY* to help them, What do you think I'm doing? You're wasting everyone's time by posting incomplete reports -- I'm trying to help you post better reports, so we can _help_ you. You want better service than that? Call Russ Nelson -- he'll come to your house and hold your hand, given sufficient incentive. For free, it doesn't get any better than this. Charles -- --- Charles Cazabon<[EMAIL PROTECTED]> GPL'ed software available at: http://www.qcc.sk.ca/~charlesc/software/ ---
Re: qmail on AFS
-BEGIN PGP SIGNED MESSAGE- > Andrea mentioned that AFS is very similar to CODA, and the CODA > solution is > to use rename() as I was planning on doing. Peter had cautioned > that rename > will overwrite existing files whereas hard links will not lose > any existing > files. Archived discussion threads indicate that renaming is still > relatively safe because the email file name is composed of the > current date/time, PID and host name and it is unlikely that the > PID would recycle within 1 second. I think rename() is safe. Even link() is of course better, the event that two nodes of the cluster are writing a mail with same data,pid,hostname (???) is obviously very very rare (impossible?). > The extended explanation of the problem is that AFS implements > its own ACL, > so that even the Unix root user may have no access to a users ~home > directory; the holds true also that a user who has managed to log > in to the > Linux/Unix box may have no access to his own ~home directory. Like Coda. > Access to AFS > files are granted by tokens issued by the AFS/Kerberos > authentication server. Like Coda, but Coda doesn't use kerberos. > So during mail delivery, qmail-lspawn will setuid to become the > email receipient, except that in most cases, this user will not > have a valid > token. I don't know well AFS, but with Coda / Vpopmail is trivial. It's sufficient to get a token for vpopmail and root users. When qmail starts, it launch 2 scripts to get root and vpopmail tokens. Then, crontab perform authentication for root / vpopmail every 4 hours (security reasons, tokens are valid for much longer). I really didn't need to patch qmail-local. > In conjunction with all of the above, I will need a cron job to > periodically > refresh qmaill's AFS/Kerberos token so that qmaill will always > have a valid > token in order to make use of the ACL privileges that have been > given to qmaill. > Yep. But I don't see the needs for patching qmail-local.c (except for rename()). - --- Cordiali saluti / Best regards Andrea Cerrito ^^ Net.Admin @ Centro MultiMediale di Terni S.p.A. P.zzale Bosco 3A 05100 Terni IT Tel. +39 0744 5441330 Fax. +39 0744 5441372 -BEGIN PGP SIGNATURE- Version: PGPfreeware 6.5.3 for non-commercial use <http://www.pgp.com> iQEVAwUBO3K16vo9HK4+yTI3AQF0IQgAmgnnlQABR9szQN2KQHrxOLaSo92xxs8u 4vIkfmYT7eZrEIlYoRBazBa+8TfDyUqORNxatydzIBqiHBQcEf7AxBT8BhegNu9n QN8UNhCOEJNRHf/DvluInZm2I6+MRxity2o6psKfkWliFFaP6Lu6G8bw41J0qKul sVUkm5XtBzC5cfkiDzqAHmr+J8yv5CJiOAYuOueQ+yY2KJd0qlvMEmewBYr0rDsK kCuGEqrcxc0khtu8Wt1mdqHGhLN2yoMafhw2CUCggxiqrB5xLuoydNdAM/i/YuA1 76REBt/7LckUAH2Lb0Ej8TD0UC5w1G7MoQ1m1QEwY3ONfgdAsZ/L/Q== =wble -END PGP SIGNATURE-
RE: qmail-queue question
OK... Let me explain this a little bit better and maybe clear some things up. 1. I've been using unix for about 8 years now and when someone says to restart a service or proggy after changing a config file, by god that service or proggy gets restarted, even if it takes a kill -9 or killall -9 to do it. 2. The only patch on this system is the qmailqueue-patch for the qmailscanner. 3. When the queue shows the message arriving on 30 Jul 2001 15:08:23 I tend to think that it actually arrive at 3:08 on Jul 30 of 2001, that is unless qmail is doing something funking with date and time stamps. ;) 4. I am a freaking consultant and I wouldn't bother this mailing list unless it was something worthwhile. But when all the instructions fail, and searching through code, and rewriting part of qmail-remote output actual logging, this is generally the place to turn to. 5. To get the logs I went to /var/log/qmail/send and did a grep on the message id number like so: grep 112535 * If you know something I don't know, then please tell me, but as far as I know, that scans all the files for that number and outputs the line, but then again, what do I know. 6. You really could try to be just a little bit less of an ass to everyone that may seem new and actually *TRY* to help them, that is what mailing list are for aren't they. Arrogance is nice and all, but what good does it do you an empty room when everyone has left you. Any real help on this issue would be appreciated from anyone. Later, Ed McLain -Original Message- From: Charles Cazabon [mailto:[EMAIL PROTECTED]] Sent: Thursday, August 09, 2001 9:58 AM To: [EMAIL PROTECTED] Subject: Re: qmail-queue question Edward McLain <[EMAIL PROTECTED]> wrote: [...] > But I have messages that are getting stuck in the queue sometimes for > more than 3 weeks. I have /var/qmail/control/queuelifetime set to > 345600 (4 days). Anyone have any idea why this is happening? You broke something. You didn't restart qmail after changing queuelifetime, or you've got buggy patches applied, or you're incorrect about how long these messages have been in the queue, or something else -- stock qmail simply will not do this. > Q. What do the logs say about the messages? > A. @40003b71c07c05d4d9ec.s:@40003b71ba7b07110754 starting > delivery 5: msg 112535 to remote emailTrimmed > That is all I can find in the qmail-send logs about it Nope, there's lots more in your logs about that -- like the "new msg" line, and the delivery result line, and various other things. Either post all the relevant lines from your log, or put the whole log somewhere on the net for an interested party to look at, or hire a qmail consultant. Charles -- --- Charles Cazabon<[EMAIL PROTECTED]> GPL'ed software available at: http://www.qcc.sk.ca/~charlesc/software/ ---
Re: Re: Can I use qmail for this purpose? (newbie)
"Jean-Christian Imbeault" <[EMAIL PROTECTED]> wrote: >[Mike Hodson <[EMAIL PROTECTED]> wrote] > >>Another great resource is 'Life With Qmail' at www.lifewithqmail.org. > >Got that already. But as I found out it's Linux-centric. I'll be installing >on OpenBSD and worse for me is that I don't know OpenBSD well at all. "Life with qmail" is *NOT* Linux-centric. I've used it myself to install qmail under OpenBSD, Solaris, IRIX, and Tru64-UNIX. I know others who've used it under FreeBSD and NetBSD. Yes, it's Linux-compatible. It would be stupid to produce documentation for any Unix software these days that isn't. As evidence of LWQ's non-Linux-centricity, I include these quotes: FreeBSD: includes GCC by default Then, using your favorite editor, remove all of the file except the lines you want. For example, here's what IDS would look like for FreeBSD after editing: On BSD systems (no /etc/inittab), put the following in /etc/rc.local and reboot the system: Note: Under Solaris, the normal id program won't work right in this script. Instead of id, use /usr/xpg4/bin/id, e.g.: -Dave
Re: Removing Headers with qmail
Paul Tan <[EMAIL PROTECTED]> wrote: > > I am looking for a solution to remove most of the headers in a > message, so that the recepient cannot see any info of my internal > network. Why? Your internal network is firewalled off, right? Futzing with headers is, in general, a very bad idea. What problem are you trying to solve? Perhaps there's a better way to do it. Charles -- --- Charles Cazabon<[EMAIL PROTECTED]> GPL'ed software available at: http://www.qcc.sk.ca/~charlesc/software/ ---
RE: qmail-queue question
Edward, I've had problems with qmail-remote hanging - it had nothing to do with the queue lifetime, but with some code in qmail-remote failing, possibly due to an O/S bug. A fix which works for me is to enable socket keep-alives. This will kill the socket if it has died after about 2-3 hours. I've put a patch on the web at http://www.duff.org/qmail/ Richard -Original Message- From: Edward McLain [mailto:[EMAIL PROTECTED]] On a side note, is there any reason that qmail-remote should start up and then just sit there connected to a remote host for like 6 or 7 hours trying to send one email? I get this all the freaking time and I'm just wandering what exactly the freaking thing is doing? (although this problem only really seems to occur with mindspring.com, yet if I telnet to port 25 of mindsprings mail server and send the same message through telnet to the same user, from the same user as the one qmail's trying to send it works just fine and I don't get any errors or return codes.)
Removing Headers with qmail
Hi guys, I am looking for a solution to remove most of the headers in a message, so that the recepient cannot see any info of my internal network. Looking thru the archives of this mailing list, I can see that most ppl would recommend using the qmail-queue patch + qmail-qfilter or qmail-masq to do the job. After Removing headers it should look something like this: - Return-Path: <[EMAIL PROTECTED]> Received: from sophia.pacific.net.sg ([203.120.90.146]) by pob5.pacific.net.sg (Post.Office MTA v3.5.3 release 223 ID# 0-53829L2S100V35) with ESMTP id sg for <[EMAIL PROTECTED]>; Wed, 8 Aug 2001 23:45:23 +0800 Received: from muncher.math.uic.edu (muncher.math.uic.edu [131.193.178.181]) by sophia.pacific.net.sg with SMTP id f78FjLE09845 for <[EMAIL PROTECTED]>; Wed, 8 Aug 2001 23:45:21 +0800 (SGT) Received: ( Information Filtered ) Mailing-List: contact [EMAIL PROTECTED]; run by ezmlm Precedence: bulk Delivered-To: mailing list [EMAIL PROTECTED] Date: Wed, 8 Aug 2001 09:41:33 -0600 From: John Doe<[EMAIL PROTECTED]> To: [EMAIL PROTECTED] Subject: Re: Whats up * My questions are: 1) Is there any other way to do the job, maybe even a different MTA ( Sorry, i know this is a qmail list but i'll go for what does the job best ) 2) If I am already using qmail-scanner, with the qmail-queue environment set, how do i call qmail-qfilter? Thks in advance, Paul Tan
Re: qmail-remote crashed ...
On Thu, Aug 09, 2001 at 04:59:08PM +0200, Martin Hasenbein wrote: > Hi, > > what could be the reason for such an error message???: > > 2001-08-09 16:55:10.524490500 new msg 365071 > 2001-08-09 16:55:10.525218500 info msg 365071: bytes 234 from <> qp 2344 uid 8001 > 2001-08-09 16:55:10.612899500 starting delivery 7: msg 365071 to remote >[EMAIL PROTECTED] > 2001-08-09 16:55:10.613655500 status: local 0/100 remote 1/100 > 2001-08-09 16:55:10.618145500 delivery 7: deferral: qmail-remote_crashed./ > 2001-08-09 16:55:10.618697500 status: local 0/100 remote 0/100 > > > I've patched qmail with a few patches, to have SMTP_AUTH, QMTP, Spamcontrol ... > and it compiled without any problems. I have this qmail running on another > server without any problems but on my server qmail-remote crashes. Why? > Local mail delivery works on both servers. Remote delivery works only > on the other server, but not on mine :-( What patches have you installed? To try to debug the setup type: ll | mail [EMAIL PROTECTED] and post your output. This will tell you if your qmail-queue is broken Ross > > Thanks! > > /martin > > > --- > > >Martin Hasenbein Phone (Fax): (+49) 89 1216376-1 (3) > \|/ Weiglstr.9 mailto:[EMAIL PROTECTED] > @ @ D-80636 München http://martin.hasenbein.com > -oOO-(_)-OOo > > On the 8th day, god created Unix ;-) -- _ Ross Cooney Virus Scanner: http://www.antivirus.ie/index.mv?free_scan=1 Perl Tutorial: http://www.cyber-sentry.com/perl/tut.mv?art=1
Re: qmail-remote crashed ...
Martin Hasenbein <[EMAIL PROTECTED]> wrote: > > what could be the reason for such an error message???: [...] > 2001-08-09 16:55:10.618145500 delivery 7: deferral: qmail-remote_crashed./ [...] > I've patched qmail with a few patches, [...] There's your answer -- your patches are buggy. Remove the patches and recompile a stock qmail. Charles -- --- Charles Cazabon<[EMAIL PROTECTED]> GPL'ed software available at: http://www.qcc.sk.ca/~charlesc/software/ ---
Re: Flame Bait: Using Qmail as a front-line mail server
Steve writes: > 1. Is it possible to list the Qmail server as the primary MX record and > still forward the mail to its final destination? All my research > says no, but I need to be certain. Use smtproutes. It essentially functions as an MX record with priority -1 (in other words, a stronger priority than any possible MX record). The other way you could do it is with split DNS. djbdns (http://www.djbdns.org) makes split DNS trivially easy. -- -russ nelson <[EMAIL PROTECTED]> http://russnelson.com Crynwr sells support for free software | PGPok | 521 Pleasant Valley Rd. | +1 315 268 1925 voice | All extremists should Potsdam, NY 13676-3213 | +1 315 268 9201 FAX | be shot.
qmail-remote crashed ...
Hi, what could be the reason for such an error message???: 2001-08-09 16:55:10.524490500 new msg 365071 2001-08-09 16:55:10.525218500 info msg 365071: bytes 234 from <> qp 2344 uid 8001 2001-08-09 16:55:10.612899500 starting delivery 7: msg 365071 to remote [EMAIL PROTECTED] 2001-08-09 16:55:10.613655500 status: local 0/100 remote 1/100 2001-08-09 16:55:10.618145500 delivery 7: deferral: qmail-remote_crashed./ 2001-08-09 16:55:10.618697500 status: local 0/100 remote 0/100 I've patched qmail with a few patches, to have SMTP_AUTH, QMTP, Spamcontrol ... and it compiled without any problems. I have this qmail running on another server without any problems but on my server qmail-remote crashes. Why? Local mail delivery works on both servers. Remote delivery works only on the other server, but not on mine :-( Thanks! /martin --- Martin Hasenbein Phone (Fax): (+49) 89 1216376-1 (3) \|/ Weiglstr.9mailto:[EMAIL PROTECTED] @ @ D-80636 München http://martin.hasenbein.com -oOO-(_)-OOo On the 8th day, god created Unix ;-)
Re: qmail-queue question
Edward McLain <[EMAIL PROTECTED]> wrote: [...] > But I have messages that are getting stuck in the queue sometimes for > more than 3 weeks. I have /var/qmail/control/queuelifetime set to > 345600 (4 days). Anyone have any idea why this is happening? You broke something. You didn't restart qmail after changing queuelifetime, or you've got buggy patches applied, or you're incorrect about how long these messages have been in the queue, or something else -- stock qmail simply will not do this. > Q. What do the logs say about the messages? > A. @40003b71c07c05d4d9ec.s:@40003b71ba7b07110754 starting > delivery 5: msg 112535 to remote emailTrimmed > That is all I can find in the qmail-send logs about it Nope, there's lots more in your logs about that -- like the "new msg" line, and the delivery result line, and various other things. Either post all the relevant lines from your log, or put the whole log somewhere on the net for an interested party to look at, or hire a qmail consultant. Charles -- --- Charles Cazabon<[EMAIL PROTECTED]> GPL'ed software available at: http://www.qcc.sk.ca/~charlesc/software/ ---
Re: done qmail installation but can't telnet to port 25
Jean-Christian Imbeault <[EMAIL PROTECTED]> wrote: > I've done the lwq installation. As a test I have tried to telnet from my > mail server to itself on port 25 to see if qmail is listening. But I get a > "connection refused" message. [...] > I think qmail is running a ps -ax gives: > > 11988 ?? S 0:00.05 svscan /service > 2591 ?? S 0:00.22 readproctitle service errors: ...\nenv: > qmail-start: > 31908 ?? S 0:01.44 supervise qmail-smtpd > 10717 ?? S 0:01.45 supervise qmail-send > 32271 ?? I 0:00.01 supervise log > 20618 ?? I 0:00.01 supervise log > 6245 ?? S 0:00.10 /usr/local/bin/multilog t /var/log/qmail/stmpd > 16675 ?? I 0:00.01 /usr/local/bin/multilog t /var/log/qmail Your installation has at least two problems, just from the above output, and possibly many more. Try again, following "Life with qmail" to the letter instead of however you did it this time. Charles -- --- Charles Cazabon<[EMAIL PROTECTED]> GPL'ed software available at: http://www.qcc.sk.ca/~charlesc/software/ ---
Re: qmail on AFS
Got a solution for this; thanks for all your help. The problem was qmail was unable to deliver mail if the Maildir is stored on AFS. Andrea mentioned that AFS is very similar to CODA, and the CODA solution is to use rename() as I was planning on doing. Peter had cautioned that rename will overwrite existing files whereas hard links will not lose any existing files. Archived discussion threads indicate that renaming is still relatively safe because the email file name is composed of the current date/time, PID and host name and it is unlikely that the PID would recycle within 1 second. The extended explanation of the problem is that AFS implements its own ACL, so that even the Unix root user may have no access to a users ~home directory; the holds true also that a user who has managed to log in to the Linux/Unix box may have no access to his own ~home directory. Access to AFS files are granted by tokens issued by the AFS/Kerberos authentication server. So during mail delivery, qmail-lspawn will setuid to become the email receipient, except that in most cases, this user will not have a valid token. So before we can even come to the problem of link() versus rename(), qmail is stymied by a lack to access to the Maildir. My solution of choice is to make qmail-local.c setuid to a mail delivery user (I picked qmaill) and make the qmail-local binary be setuid and owned by qmaill. The Maildir/tmp directory will grant allow lookup, insert, and delete privileges to qmaill, and Maildir/new will grant lookup, and insert to qmaill. The lack of a delete privilege on Maildir/new means that if a rename() is going to overwrite an existing file, AFS fails this operation because it implies a delete of the existing file, which privilege has not been granted to qmaill. (This scenario was tested by me by making qmail-local.c always generate the same email file name; on the first delivery it succeeds; on subsequent deliveries qmail defers the delivery as long as a file of the same name exists in Maildir/new.) In conjunction with all of the above, I will need a cron job to periodically refresh qmaill's AFS/Kerberos token so that qmaill will always have a valid token in order to make use of the ACL privileges that have been given to qmaill. The unified diff of my patch to qmail-local.c appears below for whatever you want to do with it. -- ...Ru (a low-cost superhero) On, on! Blue skies. Think snow. 1740484I 123 998300172 076662 82968/A17215 045124P E286/184435 975-203608 11859 DS1160 --- qmail-local.c.orig Wed Aug 8 14:34:18 2001 +++ qmail-local.c Thu Aug 9 01:05:42 2001 @@ -1,5 +1,6 @@ #include #include +#include #include "readwrite.h" #include "sig.h" #include "env.h" @@ -44,6 +45,77 @@ int flagdoit; int flag99; +/* Wed Aug 8 16:02:32 2001, Rudy Zung on vice1.bluezulu.com + * The AFS patch short form: + * 1) Incorporate the AFS patch into qmail-local.c + * 2) Compile per INSTALL + * 3) Issue: chmod u+s /var/bin/qmail/qmail-local + * 4) Issue: chown qmaill /var/bin/qmail/qmail-local + * 5) Issue: fs setacl ~home qmaill l + * 6) Issue: fs setacl ~home/Maildir/tmp qmaill lidk + * 7) Issue: fs setacl ~/home/Maildir/new qmaill lik + * IMPORTANT: ~home/Maildir/new MUST NEVER HAVE d privilege for qmaill, + * system:authuser, or system:anyuser. The qmail-local process must + * not have the ability to delete files. + * 8) Create qmaill as an AFS user; use the AFS kas and pts utilities. + * Make sure that the AFS UID for qmaill matches the /etc/passwd UID + * for qmaill + * 9) su to qmaill and run the AFS utility klog. + * (Consider cron job to refresh this token prior to its expiration) + * 10) Follow INSTALL for starting up qmail processes. + * The commands needed for the fs setacl can be embedded into the + * AFS uss template file for subsequent users who will be created via the + * uss utility. + * + * Long form: The AFS patch is designed to solve a couple of problems where + * the Maildir is in AFS space: AFS does not support hard links thus + * instead of the normal qmail operation of using link(2) to move an email + * message from Maildir/tmp to Maildir/new, we have to use rename(2). Under + * AFS, a processes Unix UID has no bearing on file access on AFS volumes. + * Access to AFS space is managed via AFS/Kerberos tokens, which are valid + * for a limited lifetime usually of less than 24 hours. An AFS/Kerberos + * token is granted by a separate authentication to the authentication + * server, and may not necessarily be integrated with the Unix login(1) + * command. Thus it is a very posssible scenario that a user may have his + * home directory in AFS, and has managed to log in to the Unix box, but + * have no access to his ~home directory because he hasn't requested + * a AFS/Kerberos token. In the normal case, qmail-lspawn will setuid to + * the email receipient which usually will have full access to ~home
Re: done qmail installation but can't telnet to port 25
>>>>> On Thu, 09 Aug 2001 13:10:34 +, "Jean-Christian Imbeault" ><[EMAIL PROTECTED]> said: >> case, tail -f /var/log/qmail/smtpd/current and start qmail. > @40003b728c052b1e1bdc tcpserver: fatal: no IP address for O Ah, then this is a configuration error. Please put the contents of /service/qmail-smtpd/run in a post. -- "Win95 not found, [P]arty, [C]elebrate, [D]rink ?"
Re: done qmail installation but can't telnet to port 25
On Thu, Aug 09, 2001 at 01:10:34PM +, Jean-Christian Imbeault wrote:
> >case, tail -f /var/log/qmail/smtpd/current and start qmail.
>
> @40003b728c052b1e1bdc tcpserver: fatal: no IP address for O
You got an O ('oh') that should be a 0 ('zero').
Unless your hostname is O ('oh') in which case it's just a resolving
problem :)
Greetz, Peter
--
Against Free Sex! http://www.dataloss.nl/Megahard_en.html
Re: done qmail installation but can't telnet to port 25
On Thu, Aug 09, 2001 at 01:10:34PM +, Jean-Christian Imbeault wrote: > >case, tail -f /var/log/qmail/smtpd/current and start qmail. > > @40003b728c052b1e1bdc tcpserver: fatal: no IP address for O Fix your run file: you've got the letter O in there where you should have the number 0. > I'm thinking that the reason qmail is unahppy is that my machine is not on > the Internet yet. So the name the machine has will not resolve properly. That has nothing to do with it. Just change the O to 0 and you should be in business. Chris
Re: Flame Bait: Using Qmail as a front-line mail server
enough anti Microsoft shit and lets get on with life. Ross [moved to mutt from Outlook for this listperfer Outlook] On Thu, Aug 09, 2001 at 09:17:24AM +0100, Adam Nealis wrote: > --- Sean Chittenden <[EMAIL PROTECTED]> wrote: > > * Exchange box is firewalled and boarded up and placed behind wallboard > Except you can't do that with an NT box because > you'll need access to reboot it every so many days > and you can't do that remotely out of the box ;). > > > Do You Yahoo!? > Get your free @yahoo.co.uk address at http://mail.yahoo.co.uk > or your free @yahoo.ie address at http://mail.yahoo.ie
Re: done qmail installation but can't telnet to port 25
> I've done the lwq installation. As a test I have tried to telnet from > my > mail server to itself on port 25 to see if qmail is listening. But I > get a > "connection refused" message. Too vague...you typed what exactly ? Hopefully :- telnet localhost 25 or telnet 127.0.0.1 25 > I've enable telnet in inetd.conf and my /etc/tcp.smtp file looks like > this: > > 127.:allow,RELAYCLIENT="" > 10.:allow,RELAYCLIENT="" AND... You`ve put it in /etc/tcp.smtp BUT have you built the cdb yet ? ie. qmailctl cdb OR, in case that doesn`t work tcprules /etc/tcp.smtp.cdb /etc/tcp.smtp.tmp < /etc/tcp.smtp > I think qmail is running a ps -ax gives: > > 11988 ?? S 0:00.05 svscan /service > 2591 ?? S 0:00.22 readproctitle service errors: ...\nenv: > qmail-start: > 31908 ?? S 0:01.44 supervise qmail-smtpd > 10717 ?? S 0:01.45 supervise qmail-send > 32271 ?? I 0:00.01 supervise log > 20618 ?? I 0:00.01 supervise log > 6245 ?? S 0:00.10 /usr/local/bin/multilog t /var/log/qmail/stmpd > 16675 ?? I 0:00.01 /usr/local/bin/multilog t /var/log/qmail > You need to do :- ps waux | grep qmail to show ALL the qmail processes. ...later...Martin
Re: done qmail installation but can't telnet to port 25
>case, tail -f /var/log/qmail/smtpd/current and start qmail. @40003b728c052b1e1bdc tcpserver: fatal: no IP address for O >I can tell you now that, from >your ps output, qmail is not running. If it was, there would be a >tcpserver running as well, listening to port 25 and spawning >qmail-smtpd when you telnet there... Sorry, cut that out of the output. There is a tcpserver running. I'm thinking that the reason qmail is unahppy is that my machine is not on the Internet yet. So the name the machine has will not resolve properly. Though I was hoping I could test the machine without putting out on the Big Bad Internet. Jc _ Get your FREE download of MSN Explorer at http://explorer.msn.com/intl.asp
Re: done qmail installation but can't telnet to port 25
>>>>> On Thu, 09 Aug 2001 12:31:34 +, "Jean-Christian Imbeault" ><[EMAIL PROTECTED]> said: > I've done the lwq installation. As a test I have tried to telnet > from my mail server to itself on port 25 to see if qmail is > listening. But I get a "connection refused" message. It would appear as if you have followed Life With Qmail. Good. In this case, tail -f /var/log/qmail/smtpd/current and start qmail. See if any errors come up, and paste them here. I can tell you now that, from your ps output, qmail is not running. If it was, there would be a tcpserver running as well, listening to port 25 and spawning qmail-smtpd when you telnet there... -- Press any key to continue or any other key to quit...
done qmail installation but can't telnet to port 25
I've done the lwq installation. As a test I have tried to telnet from my mail server to itself on port 25 to see if qmail is listening. But I get a "connection refused" message. I've enable telnet in inetd.conf and my /etc/tcp.smtp file looks like this: 127.:allow,RELAYCLIENT="" 10.:allow,RELAYCLIENT="" I think qmail is running a ps -ax gives: 11988 ?? S 0:00.05 svscan /service 2591 ?? S 0:00.22 readproctitle service errors: ...\nenv: qmail-start: 31908 ?? S 0:01.44 supervise qmail-smtpd 10717 ?? S 0:01.45 supervise qmail-send 32271 ?? I 0:00.01 supervise log 20618 ?? I 0:00.01 supervise log 6245 ?? S 0:00.10 /usr/local/bin/multilog t /var/log/qmail/stmpd 16675 ?? I 0:00.01 /usr/local/bin/multilog t /var/log/qmail Where else should I look for installation errors? I have a feeling "readproctitle services errors" in the ps output is not a good thing. Jc PS right ow my machine has a 10. address. I am testing the installation before putting on the Internet. _ Get your FREE download of MSN Explorer at http://explorer.msn.com/intl.asp
Re: Flame Bait: Using Qmail as a front-line mail server
--- Sean Chittenden <[EMAIL PROTECTED]> wrote: > * Exchange box is firewalled and boarded up and placed behind wallboard Except you can't do that with an NT box because you'll need access to reboot it every so many days and you can't do that remotely out of the box ;). Do You Yahoo!? Get your free @yahoo.co.uk address at http://mail.yahoo.co.uk or your free @yahoo.ie address at http://mail.yahoo.ie
qmail-queue question
I’ve got a slight problem here and hoping that someone can help solve this. Due to a high volume of stupid users and mailing list addicts on our network (a small isp) we tend to get a lot of bounced messages, or messages to address that don’t exist or what have you. The problem here is that they start to fill the queue up pretty fast. Now this isn’t that big of a problem anymore since I raised our connection limit way the hell up there. But I have messages that are getting stuck in the queue sometimes for more than 3 weeks. I have /var/qmail/control/queuelifetime set to 345600 (4 days). Anyone have any idea why this is happening? Just to answer all the simple questions: Q. Is the file readable by qmail? A. -rw-r--r-- 1 root qmail 7 Jul 20 18:06 queuelifetime Q. What do the logs say about the messages? A. @40003b71c07c05d4d9ec.s:@40003b71ba7b07110754 starting delivery 5: msg 112535 to remote emailTrimmed That is all I can find in the qmail-send logs about it Q. Is it bouncing? A. Output from mailq | grep 112535 : 31 Jul 2001 01:01:12 GMT #112535 15511 <emailAddressTrimmed > On a side note, is there any reason that qmail-remote should start up and then just sit there connected to a remote host for like 6 or 7 hours trying to send one email? I get this all the freaking time and I’m just wandering what exactly the freaking thing is doing? (although this problem only really seems to occur with mindspring.com, yet if I telnet to port 25 of mindsprings mail server and send the same message through telnet to the same user, from the same user as the one qmail’s trying to send it works just fine and I don’t get any errors or return codes.) Any thoughts would be appreciated. Later, Ed McLain High Speed Solutions
Re: Flame Bait: Using Qmail as a front-line mail server
> > 1. Is it possible to list the Qmail server as the primary MX record and > > > > still forward the mail to its final destination? All my research says > > no, > > but I need to be certain. > > Yes, use smtproutes. See the manual page for qmail-remote. Or create a ton of forwarding rules (.qmail for starters). qmail works as a great buffer between the internet and an Exchange server. * [EMAIL PROTECTED] -> qmail box * qmail box looks up .qmail file for user * qmail forwards to [EMAIL PROTECTED] * corp.example.com is exchange and accepts mail for the user from corp.example.com * Exchange routes all outgoing mail to the qmail box as [EMAIL PROTECTED] * Exchange box is firewalled and boarded up and placed behind wallboard -sc -- Sean Chittenden PGP signature
Re: Is there a better way to log qmail smtp & pop3
On Wed, Aug 08, 2001 at 09:01:33PM +0200, Jörgen Persson wrote:
>
> The archives will tell you more about pop3d than the tcpserver log. The
> following article[1], by Bernstein himself, might interest you.
>
> Jörgen
> [1]http://www.ornl.gov/its/archives/mailing-lists/qmail/1998/08/msg00896.html
I took me some time to do that easily with multilog and I did not find a
hint in the archive, this pop3/run script works for me
#!/bin/sh
exec /usr/local/bin/softlimit -m 400 \
/usr/local/bin/tcpserver -v -R -H -l 0 0 110 /var/qmail/bin/qmail-popup \
`cat /var/qmail/control/me` /bin/checkpassword sh -c '
echo "$TCPREMOTEIP" "$USER" >&7
exec /var/qmail/bin/qmail-pop3d Maildir' \
2>&1 7>&1
Gerrit.
--
[EMAIL PROTECTED]
innominate AG
tel: +49.30.308806-0 fax: -77 http://www.innominate.com
Re: Flame Bait: Using Qmail as a front-line mail server
On Mon, Aug 06, 2001 at 09:00:46PM -0400, Steve wrote: > 1. Is it possible to list the Qmail server as the primary MX record and > > still forward the mail to its final destination? All my research says > no, > but I need to be certain. Yes, use smtproutes. See the manual page for qmail-remote.
Re: Fix for qmail-remote process hanging on Linux (and possibly o ther s)
On Tue, Aug 07, 2001 at 12:04:50PM +1200, Jason Haar wrote: > We have exactly the same issue here. Exchange goes down. Mail backs up on > Qmail servers. Exchange comes back up. USERS ARE TOLD ITS WORKING AGAIN. > Users then wonder why it takes up to 2 hours for queued mail to get to them. > USERS COMPLAIN THAT SOMETHING IS WRONG. qmail will wait up to two hours to deliver a message only if the message has been sitting in its queue for 11 hours, see <http://web.infoave.net/~dsill/lwq.html#retry-schedule>. Perhaps you should fix Exchange so it doesn't go down for 11 hours at a time.
Re: Is there a better way to log qmail smtp & pop3
On Mon, Aug 06, 2001 at 11:31:29PM +, board master wrote: Please don't use HTML formatted mail The archives will tell you more about pop3d than the tcpserver log. The following article[1], by Bernstein himself, might interest you. Jörgen [1] <http://www.ornl.gov/its/archives/mailing-lists/qmail/1998/08/msg008 96.html>
Vpopmail + qmail + mysql, 1 last problem
Here is my situation. Almost everything is working. I've set up qmail and vpopmail using mysql. I can log a user into a virtual domain through mailtoweb and read any emails that I may have. I can send emails to my virtual domain users from any other account(hotmail for example), but when I try to send mail from my virtual domain user to any other account from webtomail I get a message saying that the message could not be sent. I've had similar results from outlook. Any ideas? Thanks, Cameron. _ Get your FREE download of MSN Explorer at http://explorer.msn.com/intl.asp
Where to store extended envelope info in /var/qmail/queue ?
Vanilla qmail 1.03 stores the envelope sender address (preceded by an F and
followed by a NUL) in a file in the directory /var/qmail/info/.
RFC 1869 ("SMTP Service Extensions") allows one to pass additional information
on the MAIL command line after the FROM: . Some of this information
should in principle be passed on to qmail-local and/or qmail-remote for
correct processing.
(One example is BODY=8BITMIME. Regardless of how one thinks qmail-remote
should behave when relaying to a server that doesn't advertise 8BITMIME
--- I don't wish to revive *that* discussion --- it may be nice to pass
on the 8BITMIME flag to those servers that do claim to support it --- but
only if it was set on the inbound message; qmail-remote shouldn't try to
compute it from the message content.)
In the INTERNALS file, DJB wrote inter alia:
Currently info/457 serves two purposes: first, it records the envelope
sender; second, its modification time is used to decide when a message
has been in the queue too long. In the future info/457 may store more
information. Any non-backwards-compatible changes will be identified by
version numbers.
I think I may have a need to store more information. I would like to do so
in a manner that won't clash with future official qmail releases.
Would it be OK to store the information after the F...\0 envelope
sender, as a (possibly empty) list of P...\0 parameters?
Or am I better off creating a separate file xinfo/457 ?
Sergio Gelato
