Re: sending messages by common user
QBA wrote: > > On Sat, Sep 16, 2000 at 09:09:30PM +0200, Ludvig Omholt wrote: > > > > I know this isn't the answer you requested, but I can't see why putting > > the killall -ALRM qmail-send in /etc/ppp/ip-up.local wouldn't solve your > > problems? If you are offline your messages wait in the queue and if you > > are online they get sent directly. I think it's an ideal solution, no? > > > > /Ludde > > Actually, you are right. I just forgot that qmail sends all mail at once > (sendmail that I was running before didn't do so and it was making me > sick) without any delays. But could you guide me how to change my > ip-up file so that it all works well? > Thank you in advance, > > QBA Just edit the file /etc/ppp/ip-up.local with your favorite editor (as root). If the file doesn't exist I think it should be safe to add it. This is the line I use on my home machine: # Try to deliver queued mail /usr/bin/killall -ALRM qmail-send Hope this helps. /Ludde -- _ _ _ __ __ ___ | | | | | \| \| __| Ludvig Omholt .. http://ludde.net | |_| | | D | D | _| 070-310 08 71 ... [EMAIL PROTECTED] |___|___|__/|__/|___| linux kernel 2.2.17 on an i686 +
qmail Digest 17 Sep 2000 10:00:01 -0000 Issue 1126
qmail Digest 17 Sep 2000 10:00:01 - Issue 1126 Topics (messages 48816 through 48832): Re: How can I test this? 48816 by: Ricardo Cerqueira Bounce Message Surpression 48817 by: Carl Schrader Re: Reject it during the SMTP dialogue 48818 by: Claus Färber sending messages by common user 48819 by: QBA 48820 by: Ludvig Omholt 48828 by: QBA 48832 by: Ludvig Omholt List activity 48821 by: Mike Hodson 48822 by: Eric Cox 48825 by: Ricardo Cerqueira 48826 by: Dale Miracle 48827 by: Photocon Re: problems with qmailanalog utils 48823 by: Jens Georg Re: qmail + freebsd = reboot 48824 by: Jos Backus Archive multilog logs without overlapping 48829 by: Brett Randall The local time story 48830 by: sQueaK [Announce] oMail-admin 0.95 48831 by: Olivier M. Administrivia: To unsubscribe from the digest, e-mail: [EMAIL PROTECTED] To subscribe to the digest, e-mail: [EMAIL PROTECTED] To bug my human owner, e-mail: [EMAIL PROTECTED] To post to the list, e-mail: [EMAIL PROTECTED] -- On Fri, Sep 15, 2000 at 10:54:39PM -0400, Phil Barnett wrote: > > I have been trying to get Mailman to work with qmail for a couple of > weeks now and I can't seem to make the final connection. I > researched the archives and I have dutifully read this list for over > 1000 messages. The docs on dot-qmail would probably have been enough for this :-) But that's OK. > > Mailman is able to send messages just fine. My problem is that I > can't seem to reply back to Mailman via qmail. > > qmail understands that I have created a virtual domain, because it > is only complaining that the mailbox doesn't exist. > > As far as I can tell by reading the docs, once the virtual directory is > in place, the mechanisms that qmail uses to redirect mail to other > processes are the .qmail-?? files in the virtual directory. > What to you mean by "virtual directory"? The dot-qmail files are placed in the directory owned by the user you refer to in the "virtualdomains" file, or inside the ~alias directory. Keep reading, I'll give you an example later. > I created the virtual directory (which is alongside a bunch of virtual > directories that are working just fine to deliver regular mail), put the > .qmail files there for qmail to find and redirect mail to a process. > > To the rcpthosts file, I added: > matrixlist.com > > To the virtualdomains file, I added: > matrixlist.com:matrixlist-com > OK, so here you point to a "matrixlist" user, or to a ~alias/.qmail-matrixlist-com- > But, when I send mail to those .qmail- files in the virtual directory, > like .qmail-test-request for example, I get this: > > <[EMAIL PROTECTED]>: > Sorry, no mailbox here by that name. (#5.1.1) > Now, for the examples: Assuming you keep that "virtualdomains" line, you have 2 choices: 1) Set up a bunch of ~alias/.qmail-matrixlist-com- files. In this case, [EMAIL PROTECTED] would look for a file named .qmail-matrixlist-com-test-request in ~alias. 2) Create a "matrixlist" user in the system. Inside that user's home, place the .qmail-com- files. For the previous example, it would be a file named .qmail-com-test-request in ~matrixlist. RC -- +--- | Ricardo Cerqueira | PGP Key fingerprint - B7 05 13 CE 48 0A BF 1E 87 21 83 DB 28 DE 03 42 | Novis - Engenharia ISP / Rede Técnica | Pç. Duque Saldanha, 1, 7º E / 1050-094 Lisboa / Portugal | Tel: +351 2 1010 - Fax: +351 2 1010 4459 PGP signature Hi, We recently switched to qmail after 4 years of using sendmail. With sendmail, I only received a failure notice when a piece of email was in the queue for over 5 days. Now I get a message every time someone sends a message to nonexistent mailbox, every time a bounce bounces, etc. How can I turn this off? It's annoying. TIA! J.J.Gallardo <[EMAIL PROTECTED]> schrieb/wrote: > I'm surprise today with a test that i've do it on my smtp server (qmail > 1.03): > I send an e-amil (1Mb) to an invalid user and qmail accept it a then, > send a reply to the sender (another megabyte) saying that the user is > unknown. Total = 2Mb of my lines used for no actions. > Is there a way to reject mail during the SMTP dialogue so don't accept > mail to "invalids and/or unknowns user's"? Nope. This is one of the things with qmail that bothers me too. Unfortunatly, due to qmail's modular design, implementing it would not be too easy: qmaild, as who qmail-smtpd runs, does not have access to the user database, let alone individual .qmail files. This is also one of the reasons qmail-smtpd does not support VRFY. However, it's probably possible to make a rough guess based on what's available and accessible (and thus reject a large amount of mail which has no chance of being deliverable): i
qmail and procmail
Hi! I've hade quite some success using qmail and procmail together, especially using spambouncer (http://www.spambouncer.org/), and, even more, |bouncesaying formail -D 8000 .foo.msgid.file [That's really neat...] However, my procmail logs are filled to the level of unusability with the following lines: procmail: Extraneous deliver-head flag ignored How can I make them go away (and go back to tail -f .procmail-log for biff)? -Johan -- Johan Almqvist
Re: [vmailmgr] [Announce] oMail-admin 0.95
On Sun, Sep 17, 2000 at 02:38:57AM +0200, Olivier M. wrote: > Project homepage: http://omail.omnis.ch (with old, but working live demo) Btw, just updated screenshot page, and online demo: * Demo: http://admin.omnis.ch/omail/ (test.com - test) * Screenshots: http://omail.omnis.ch/screenshots95.shtml Regards, Olivier -- _ Olivier Mueller - [EMAIL PROTECTED] - PGPkeyID: 0E84D2EA - Switzerland PGP signature
need some help...
hello my problem is: if i start pop3 with this: env - PATH="/var/qmail/bin:/usr/local/bin" tcpserver 0 pop-3 /var/qmail/bin/qmail-popup my.host.blah /var/qmail/vpopmail/bin/vchkpw /var/qmail/bin/qmail-pop3d Maildir & It starts fine, but if I logout then whoops it doesnt work anymore :P how to fix that.. and howto add alias to pop3 like this [EMAIL PROTECTED], I mean what you can ever invent @ domain.com - zrx
Re: need some help...
On Sun, Sep 17, 2000 at 05:20:50PM +0300, Simo Lakka wrote: > > hello > > my problem is: > > if i start pop3 with this: > env - PATH="/var/qmail/bin:/usr/local/bin" tcpserver 0 pop-3 > /var/qmail/bin/qmail-popup my.host.blah /var/qmail/vpopmail/bin/vchkpw > /var/qmail/bin/qmail-pop3d Maildir & > > It starts fine, but if I logout then whoops it doesnt work anymore :P > how to fix that.. try to add "nohup" before that: nohup env - PATH="/var/qmail/bin:/usr/local/bin" tcpserver 0 pop-3 /var/qmail/bin/qmail-popup my.host.blah /var/qmail/vpopmail/bin/vchkpw /var/qmail/bin/qmail-pop3d Maildir & And for aliasing: check out the .qmail-default-file in your domain directory. And read this: http://www.inter7.com/vpopmail/doc/vdelivermail.html /magnus -- http://x42.com/
Re: sending messages by common user
On Sun, Sep 17, 2000 at 11:19:26AM +0200, Ludvig Omholt wrote: > Just edit the file /etc/ppp/ip-up.local with your favorite editor (as > root). If the file doesn't exist I think it should be safe to add it. > This is the line I use on my home machine: > > # Try to deliver queued mail > /usr/bin/killall -ALRM qmail-send > > Hope this helps. > > /Ludde I added this command to my ip-up.local file but it doesn't work. Could you send me your all ip-up script, maybe I have something wrong there. Thanks for help, QBA
Trouble starting qmail on boot
Hi,
My qmail setup is based on the HOW-TO from www.flounder.net. I am using RH
6.2. When I run /etc/rc.d/init.d/svscan start Qmail starts up without any
trouble, however when I restart my server, Qmail is not being started up. I
then have to log into the server and run /etc/rc.d/init.d/svscan start.
Here is the first part of init.d/svscan:
#!/bin/sh -e
#/etc/rc.d/init.d/svscan : start or stop svcan.
case "$1" in
start)
echo -n "Starting djb services: svscan"
env - PATH="/usr/local/bin:$PATH" svscan /service &
echo $! > /var/run/svscan.pid
echo "."
;;
The perms for init.d/svscan are:
-rwxr-xr-x 1 root root 548 Sep 16 04:01 svscan
I have created symlinks in all of my /etc/rc.d/rc*.d files to init.d/svscan
the perms for those symlinks are:
lrwxrwxrwx 1 root root 16 Sep 14 08:17 K30svscan ->
../init.d/svscan
When looking at the other scripts in init.d/ I see that they all have lines
containing:
. /etc/rc.d/init.d/functions
. /etc/sysconfig/network
if [ ${NETWORKING} = "NO" ]
.
.
[ - f /usr/sbin/named ] || exit 0 ]
[ -f /etc/named.conf ] || exit 0 ]
Do I need entries like this in init.d/svscan or does something need to be in
/etc/inittab?
Any pointers to a HOW_TO or guide for using rc.d and init would be
appreciated.
Thanks
David
Re: Trouble starting qmail on boot
the K* symlinks kill the processes on shutdown, for startup you need the S* symlinks in /etc/rc.d/rc*.d, e.g. S95svscan wolfgang Also sprach Gadoury <[EMAIL PROTECTED]> on 17.09.2000: lrwxrwxrwx 1 root root 16 Sep 14 08:17 K30svscan -> ../init.d/svscan
Re: sending messages by common user
QBA wrote: > > On Sun, Sep 17, 2000 at 11:19:26AM +0200, Ludvig Omholt wrote: > > Just edit the file /etc/ppp/ip-up.local with your favorite editor (as > > root). If the file doesn't exist I think it should be safe to add it. > > This is the line I use on my home machine: > > > > # Try to deliver queued mail > > /usr/bin/killall -ALRM qmail-send > > > > Hope this helps. > > > > /Ludde > > I added this command to my ip-up.local file but it doesn't work. > Could you send me your all ip-up script, maybe I have something > wrong there. Hmmm... I don't have anything else in there... It just looks as follows. You might want to check if it is executable though. In my /etc/ppp/ip-up file which calls ip-up.local there is a check [ -x /etc/ppp/ip-up.local ] to see that the script exists and is executable before it is run. ip-up.local: ---8<--- #!/bin/bash # Try to deliver queued mail /usr/bin/killall -ALRM qmail-send ---8<--- /Ludde -- _ _ _ __ __ ___ | | | | | \| \| __| Ludvig Omholt .. http://ludde.net | |_| | | D | D | _| 070-310 08 71 ... [EMAIL PROTECTED] |___|___|__/|__/|___| linux kernel 2.2.17 on an i686 +
Re: Why Qmail could is slow?
On Fri, Sep 15, 2000 at 09:55:58PM -0400, Chris Johnson wrote: > On Fri, Sep 15, 2000 at 09:48:08PM -0700, Tim Hunter wrote: > > What do you mean by qmail-send went down? there should be a message in the > > logs as to why it "just went down" > > Actually, it's "want down." I was a bit surprised that svstat was saying this, > but I looked in the svstat source, and sure enough "want down" is in there. > Without digging too deeply into the source, I'd guess that this means that the > service is currently running, but that supervise is waiting for it to stop. Which would make perfect sense on a qmail restart. qmail needs to go down before it can go up again, and running deliveries keep it from going down. Greetz, Peter -- dataloss networks '/ignore-ance is bliss' - me
cute mail checking program
Hi ppl! I've made a super-simple super-small super-alpha_version *sh script that checks a Maildir for any new mail. If there is something there it pops up an animated gif somewhere on you screen. I have no idea if this will actually work for you, it's my first script ever. I made this because I needed it (it uses about 40k of non-shared mem) and I guess maybe someone else out there will like it. So have fun ! Peter PS I have a way-out OFF-QMAIL-TOPIC (c) question which I have to ask ;) If you feel like responding, please use mailto:[EMAIL PROTECTED] . Is there any Linux c\c++ editing program out there that resembles (or exceeds) a Borland editor/compiler (for mickeysoft) ? This would mean: F9 to compile the source ;) highlight the errors found during compile in the editor, alt-F1 to get help from C-C++ reference on the currently selected function. Many thanks, Peter postalion-0.0.1.tgz
Re: Stopping "user@virtualdomain" from receiving mail as "user@actualdomain"
> I got the virtual domain working, users in the virtual domain are able to > get mail as "user@virtualdomain". How do I stop the user from getting mail > assigned to "user@actualdomain"? $ echo @actualdomain >> /var/qmail/control/badmailfrom You cannot stop internal mails from being delivered to your actual domain. Or use a filter in your .qmail that prohibits mails not address to virtualdomain. Felix
Re: conf-spawn and FD_SET question
On Sat, Sep 16, 2000 at 11:23:59AM +0900, James T. Perry wrote: [snip] > > I got curious and was poking around with my qmail setup, > and a simple 'grep -r FD_SET' into the kernel sources gave > me (amongst many similar) a line in: > /usr/src/linux-2.2.17/include/linux/posix_types.h > which said: > #define __FD_SETSIZE 1024 > > I know that I shouldn't be screwing with kernels, but > I was just curious if this was safe/the right place to > change, or if I could change the 1024 to say 2048 (or > something appropriate?) and recompile the kernel and > also be safe to run everything. FD_SETSIZE is not a kernel variable, it's just used by the macro's for handling select() fdlists. Adding a -DFD_SETSIZE=2048 (yes, that's without the __) to the correct conf-file in the qmail source should do the trick. Ok, found it. This is what I do in my installscripts: echo Fixing $QMAIL/conf-cc... echo 'cc -O2 -DFD_SETSIZE=4096' > $QMAIL/conf-cc Greetz, Peter. -- [ircoper][EMAIL PROTECTED] - Peter van Dijk / Hardbeat [student]Undernet:#groningen/wallops | IRCnet:/#alliance [developer]_ [disbeliever - the world is backwards](__VuurWerk__(--*-
Re: conf-spawn and FD_SET question
Hi Peter, Thanks for your response. Peter van Dijk wrote: > FD_SETSIZE is not a kernel variable, it's just used by the macro's > for handling select() fdlists. Adding a -DFD_SETSIZE=2048 (yes, > that's without the __) to the correct conf-file in the qmail source > should do the trick. oops (*blush*cough*). OK :) I'm glad I didn't go diving into the kernel sources. > echo Fixing $QMAIL/conf-cc... > echo 'cc -O2 -DFD_SETSIZE=4096' > $QMAIL/conf-cc I tried this above, and "make setup" still gives me the "Oops. Your system's FD_SET() has a hidden limit of 1024 descriptors..." error message from chkspawn. I tried it also with 2048 and still the same error msg. Do you think some system environment variable is affecting this, or kernel parameters in /proc maybe? This isn't mission critical but I was just curious if I could change conf-spawn to 1000 or so for future reference (e.g. bulk-email performance tests for ball park figures -> not for abuse, I hate spammers) my setup: linux kernel 2.2.17 qmail 1.03 + localtime, DNS, big-todo, big-concurrency patches changes in qmail configuration: lspawn rspawn both set to 100 conf-spawn set to 250 ucspi-tcp-0.88 daemontools-0.70 Thanks again, jamie > [disbeliever - the world is backwards](__VuurWerk__(--*- Yes, I must agree that I have felt that way many times :) #-#-#-#-#-#-#-# -- If somebody can help create a search engine for my room, I will call them a Saint... GUI == Graphical User Interference
