Re: Possible to drop instead of bounce (globally)?
one method would be to use .qmail-default files that contain nothing but a comment line. -tcl. On Tue, 7 Aug 2001, eric wrote: > > I am wondering if it is possible to drop SOME of the normal bounce > messages. What I would like to do is send bounce messages for all normal > bounce situations EXCEPT for unknown user. If the user does not exist on > the system, I'd like to just silently discard the message. > > Is this possible? > > Eric Calvert > Caveland Connection >
Re: Distinct user@domain routing
http://cr.yp.to/qmail/faq/incominghost.html#multi-virtual and the rest of http://cr.yp.to/qmail/faq/incominghost.html -tcl. On Mon, 9 Jul 2001, Kevin DeGraaf wrote: > I run a qmail server that handles mail for 8 domains, all of which are in > my "rcpthosts" and "locals" files. It works fine, but I'd like to have a > bit more control over specific user@domain combinations. > > Currently, sending mail to "kevin" at any of the 8 domains works fine, and > the mail is delivered to /var/spool/mail/kevin. > > I'd like to set up some aliases that behave differently depending on the > domain. I'd like to be able to specify, for example, that > "[EMAIL PROTECTED]" gets sent to one user, but "[EMAIL PROTECTED]" is sent to > another user. > > If I make an ~alias/.qmail-foo file, then anything sent to "foo", at any > of our domains, goes to foo's mailbox. I've been RTFMing all morning. > Ideas? > > - > Kevin DeGraaf > > > > >
Re: [Q] qmail with lwq
it looks like you have svscan running on / and /service instead of just /service. check your /etc/inittab and other init scripts and such and make sure that only 1 svscan is running and only on /service. there are also 2 supervise processes running on qmail-smtpd for some reason. it could be related to the above. since 2 of those are running, 1 of them is actually running it (bound on port 25/tcp), and the other one keeps trying to start it but fails because it can't bind to that port since the first one already has it... somewhere to start, at least. -tcl. On Sat, 16 Jun 2001, YOON, Joo-Yung wrote: > I installed qmail in accordance with lwq (dated 13 June 2001). > I am gone to chapter 2 Installation, and did not go to chapter 3 > Configuratin yet. > > Tried to stop qmail, but it does not stop by saying > qmail-send: no file > qmail-smtp: no file > > But I have them in /service linked to /var/qmail/supervise. > > So I restarted the linux box. > Then I could stop and start the qmail system. > > But the log in /var/log/qmail/smtpd/current says > @40003b2b26d422cdd01c tcpserver: fatal: unable to bind: address already used > @40003b2b26d53b4973bc tcpserver: fatal: unable to bind: address already used > @40003b2b26d70196845c tcpserver: fatal: unable to bind: address already used > @40003b2b26d80352e22c tcpserver: fatal: unable to bind: address already used > @40003b2b26d90504dfbc tcpserver: fatal: unable to bind: address already used > > and the terminal of the booting still produces junk fatal error messages that > I can not read because they scroll up too fast. > > The environment of my system is > linux-2.2.18 > debian-2.2 (potato) > qmail-1.03 > ucspi-tcp-0.88 > daemontools-0.70 > > Now the qmail is running, and I attach the ps output for your information. > > Could you please help me? > I will highly appreciate it. > > Warm regards, > -- > YOON, Joo-Yung / ArBaGo Int'l > KOREA 420-111 BooChun WonMi-1-Dong 1-28 (GunYong Bldg. 302) > Mobile +82.19.350.1369 Fax +82.32.655.855.9 Email [EMAIL PROTECTED] >
Re: sending mail using qmail-inject
you might just need to throw an extra echo in between the subject and grep so there's a blank line between the header and body... -tcl. On Thu, 24 May 2001, Qmail wrote: > Is it possible to script qmail-inject to send a full bodied message from the > command line? > > I'm trying something like this: > > ( echo to: alerts@XYZnet ; echo from: [EMAIL PROTECTED] ; echo subject: logs ; > grep '@customer.com' /var/log/qmail/* ) | /var/qmail/bin/qmail-inject > > I get the header, ok, but no body? > > Regards, > > Lance > >
Re: tcpserver blues
tcpserver runs in the foreground. that line:
tcpserver: status: 0/40
is its [logging] output. when it accepts a new connection, it will output
more.
just run it in the background.
maybe pipe stdout and stderr to a file for logging.
or be elegant and use supervise and svscan (see daemontools
documentation on cr.yp.to).
-tcl.
On Thu, 10 May 2001, Chris Ochap wrote:
> can anyone help me figure out why qmail-smtpd will not start. i have been
> following multiple peices of literature to complete the install...although
> they all differ slightly...i have had no trouble with any stage of the
> install except getting qmail to start listening for remote deliveries.
> whenever i enter the tcpserver command to start qmail-smtpd whether it be in
> a startup script or command line...i get
>
> tcpserver: status: 0/40
>
> and the prompt just sits there like it is waiting for me to enter another
> parameter. i am fairly confident that the command line options are all
> correct:
> tcpserver executable and switches -v = verbose -p = accept comm w/o remote
> host dns lookup -x = use rules database
> location of rules database with a very simple set of rules
> user and group ids for qmail users...define whether tcpserver is on
> localhost...use smtp...ok sorry im going over what most of you probably know
> already. does anyone have any suggestions or need more info? here is a
> copy of my little script...i am running rh 7.1. thanx all.
>
>
> ---
> # Source function library.
> . /etc/rc.d/init.d/functions
>
> # Source networking configuration.
> . /etc/sysconfig/network
>
> # Check that qmail is loaded
> [ -f /var/qmail/bin/qmail-start ] || exit 0
>
> RETVAL=0
> prog="qmail"
>
> start() {
> # Start daemons.
> echo -n $"Starting $prog: "
> daemon /var/qmail/rc
> /usr/local/bin/tcpserver -v -p -x /etc/tcprules/tcp.smtp.cdb -u
> 51 -g 50 0 smtp /var/qmail/bin/qmail-smtpd
> RETVAL=$?
> [ $RETVAL -eq 0 ] && touch /var/lock/subsys/qmail
> echo
> return $RETVAL
> }
> stop() {
> # Stop daemons.
> echo -n $"Stopping $prog: "
> killproc qmail-send
> RETVAL=$?
> [ $RETVAL -eq 0 ] && rm -f /var/lock/subsys/qmail
> echo
> return $RETVAL
> }
>
> restart() {
> stop
> start
> }
>
> # See how we were called.
> case "$1" in
> start)
> start
> ;;
> stop)
> stop
> ;;
> restart)
> restart
> ;;
> *)
> echo $"Usage: $0 {start|stop|restart}"
> exit 1
> esac
>
> exit $?
>
>
Re: How to increase the qmail "concurrency"?
On Fri, 4 May 2001 [EMAIL PROTECTED] wrote: > > my qmail-mrtg show that the qmail concurrency value 20 is not enough. anyone > can tell me how to increase it. > http://cr.yp.to/qmail/faq/efficiency.html#concurrency -tcl.
Re: Pine for Maildir
On Sat, 14 Apr 2001, Nick (Keith) Fish wrote: > Stefan Laudat wrote: > > there are patches for pine Maildir access, please rtfm at www.qmail.org > > I've tested that and worked a couple of months ago. > > I am working on this issue right now. What it's boiled down to has > been my installing the courier-imap package with the intent of having > Pine access that. I've patched pine's source code with Mattias > Larsson's pine-maildir-4.33 patch; but couldn't figure out how to > configure Pine to access the Maildirs (namely due to lack of > documentation on Larsson's patch, and his site seems to be down as > well). I would be interested to hear of the patch you used and the > configuration adjustments you made to Pine. > By the way, I must say that I do not care for mutt. The interface is > rather dirty (I don't mean its aesthetics) and the configuration rather > cryptic. Maybe I just didn't devote enough time to it? Anyways, it's > not a viable option. i use that same patch for pine 4.33. it appears to work much better than whatever i was using before. something with pine 4.10 i think. in pine's config i simply set inbox-path to the string: $MAIL /etc/profile.d/qmail.sh exists to set $MAIL (and $MAILDROP) properly. that profile file came with Bruce Guenter's qmail rpms (http://em.ca/~bruceg/qmail+patches/). typically $MAIL would look like: /home/user/Maildir/ (with the trailing slash). i've never used pine with imap, so i'm not sure how that works. i never cared for mutt either, although i never spent a huge amount of time trying to figure it out. my main issue with it is that i could never get it to sort my inbox properly (just normal sorting - by arrival time - how the files in the maildir are already sorted). it could be due to me having tried old version of mutt. -tcl.
Re: how can i run qmail on a port that is not 25 under tcpserver?
On Mon, 26 Mar 2001, Linux!audimed wrote: > how can i run qmail on a port that is not 25 (non standart port Ex:300) > under tcpserver? > THX. you probably mean qmail-smtpd. same way you'd do it with port 25 -- just use a different number. http://cr.yp.to/ucspi-tcp/tcpserver.html -tcl.
stralloc?
has any thought been put into releasing the stralloc library/interface by itself? qmail's stralloc files appear a bit different than djbdns', and i'm unsure about the ones in other packages, but stralloc could be rather useful for developers of other projects. sorry that this is to the qmail list. none of the cr.yp.to lists were very relevant. -tcl.
Re: Load Balancing with qmail
On Wed, 14 Feb 2001, Andrew Wafula wrote: > > Is there any way one can do load balancing with qmail, i.e I have two > machines both with qmail set up and running. Is there a way that I can have > them both serving as smtp servers without the clients knowing which machine > is sending the ail for them? > you can use dns mx preferences for smtp. you can use dns round-robin a records. you can use a load balancer like http://www.linuxvirtualserver.org/, or an f5 bigip, or alteon's, or cisco's, etc etc. -tcl.
Re: Unable_to_open_./Maildir:_is_a_directory ERROR?
> Default delivery target contains: ./Maildir you want this to be "./Maildir/", not "./Maildir", assuming you actually want to deliver to a maildir-style layout. check how you're starting qmail and make sure that / is on the end of the "Maildir" string. -tcl. On Sun, 28 Jan 2001, Sean Coyle wrote: > Hello again there guys, > > I have one final question before my qmail installation becomes truly > "installed". I am getting this error below from 'qmail-send'. > > @40003a74201f3a196f9c starting delivery 96: msg 299022 to local > [EMAIL PROTECTED] > @40003a74201f3a1a7d24 status: local 1/10 remote 0/20 > @40003a74202003bb391c delivery 96: deferral: > Unable_to_open_./Maildir:_is_a_directory._(#4.2.1)/ > @40003a74202003bc65e4 status: local 0/10 remote 0/20 > > I have installed (and it is working mind you) vmailmgr, omail, > qmail+patches, and relay-ctrl-2.5. > > Virtual users are working 100% correctly using vmailmgr. What I seem to > be having a problem with is mail delivery with local users. > > Domain = g0thic.com (is local & localhost) > > Qmail-lint output gives off no errors > > > Qmail-showctl output below: > > [root@www qmail]# qmail-showctl > qmail home directory: /var/qmail. > user-ext delimiter: -. > paternalism (in decimal): 2. > silent concurrency limit: 509. > subdirectory split: 23. > user ids: 890, 891, 892, 0, 893, 894, 895, 896. > group ids: 890, 891. > aliasempty: > Default delivery target contains: ./Maildir > badmailfrom: (Default.) Any MAIL FROM is allowed. > bindroutes: (Default.) No binding routes. > bouncefrom: (Default.) Bounce user name is MAILER-DAEMON. > bouncehost: (Default.) Bounce host name is g0thic.com. > checkpassword: Password checking program is checkvpw > /usr/sbin/relay-ctrl-allow. > concurrencylocal: (Default.) Local concurrency is 10. > concurrencypop3d: (Default.) POP-3 daemon concurrency is 20. > concurrencyqmqpd: (Default.) QMQP daemon concurrency is 20. > concurrencyqmtpd: (Default.) QMTP daemon concurrency is 20. > concurrencyremote: (Default.) Remote concurrency is 20. > concurrencysmtpd: (Default.) SMTP daemon concurrency is 20. > concurrencyspop3d: (Default.) SSL POP-3 daemon concurrency is 20. > databytes: (Default.) SMTP DATA limit is 0 bytes. > defaultdomain: Default domain name is g0thic.com. > defaulthost: Default host name is g0thic.com. > doublebouncehost: (Default.) 2B recipient host: g0thic.com. > doublebounceto: (Default.) 2B recipient user: postmaster. > envnoathost: (Default.) Presumed domain name is g0thic.com. > helohost: (Default.) SMTP client HELO host name is g0thic.com. > idhost: (Default.) Message-ID host name is g0thic.com. > localiphost: (Default.) Local IP address becomes g0thic.com. > locals: > Messages for localhost are delivered locally. > Messages for g0thic.com are delivered locally. > Messages for mail.g0thic.com are delivered locally. > logger: (Default.) Logging is done via: splogger. > me: My name is g0thic.com. > percenthack: (Default.) The percent hack is not allowed. > plusdomain: (Default.) Plus domain name is g0thic.com. > qmqpservers: (Default.) No QMQP servers. > queuelifetime: (Default.) Message lifetime in the queue is 604800 seconds. > rcpthosts: > SMTP clients may send messages to recipients at localhost. > SMTP clients may send messages to recipients at g0thic.com. > SMTP clients may send messages to recipients at mail.g0thic.com. > SMTP clients may send messages to recipients at worldvibe.org. > SMTP clients may send messages to recipients at mail.worldvibe.org. > SMTP clients may send messages to recipients at .worldvibe.org. > SMTP clients may send messages to recipients at planet-sun.com. > SMTP clients may send messages to recipients at mail.planet-sun.com. > SMTP clients may send messages to recipients at optikalcomputing.com. > SMTP clients may send messages to recipients at mail.optikalcomputing.com. > morercpthosts: (Default.) No effect. > morercpthosts.cdb: (Default.) No effect. > smtpgreeting: (Default.) SMTP greeting: 220 g0thic.com. > smtproutes: (Default.) No artificial SMTP routes. > timeoutconnect: (Default.) SMTP client connection timeout is 60 seconds. > timeoutremote: (Default.) SMTP client data timeout is 1200 seconds. > timeoutsmtpd: (Default.) SMTP server data timeout is 1200 seconds. > ulimitcpu: (Default.) Maximum amount of CPU time in seconds is unlimited. > ulimitdata: (Default.) Maximum process data size in kbytes is unlimited. > virtualdomains: > Virtual domain: worldvibe.org:worldvibe > Virtual domain: .worldvibe.org:worldvibe > Virtual domain: planet-sun.com:planet_mail > Virtual domain: .planet-sun.com:planet_mail > Virtual domain: optikalcomputing.com:optikalmail > Virtual domain: .optikalcomputing.com:optikalmail > defaultdelivery: I have no idea what this file does. > concurrencyincoming: I have no idea what this file does. > >
Re: [OT] pine and Maildir (was: Maildir versus malibox)
On Sun, 21 Jan 2001, Alex Pennace wrote: > On Sat, Jan 20, 2001 at 08:02:51PM -0500, tc lewis wrote: > > i've had lots of problems with mutt concerned its sorting. i've > > consistently seen mutt think messages from november 28th interpreted as > > being from january 4th, 2002, as an example. weird things like that. > > that's simply unacceptable to me. > > When sorting by date mutt only barfs when the date header is messed > up. Are you sure the date headers in those messages are standards > compliant? i would much rather simply sort by the mailbox. which i've tried. and it still gets messed up. why on earth do muas think they're smarter than mtas? whatever. but i was using an old version of mutt so who knows? > > plus the whole idiotic self-quoting thing on the top of mutt's web page, > > and some other stuff on the web pages, just makes me think that the author > > is an idiot. but that's certainly not very objective reasoning. > > This is coming from someone who doesn't know what capitalization > is. But you can't please them all, right? this is the absolute worst argument i've ever heard in my entire life. don't ever email me again. > > for now i'm still using an old pine with the maildir patch, as that mutt > > date interpretation thing simply makes it impossible for me to use. > > Like I said I've had no problems in this area except when the message > itself was flawed. Are you sure you are using Mutt properly? no, i'm not sure. i've been talking about this in private messages with someone else. i'm not sure that my use of mutt is perfect, altho i have no idea what i could possibly be messing up. nevertheless, if i have to mess around with it that much for it to be coherent for me to use, it's not the proper tool for me. to each his own. -tcl.
Re: [OT] pine and Maildir (was: Maildir versus malibox)
i've had lots of problems with mutt concerned its sorting. i've consistently seen mutt think messages from november 28th interpreted as being from january 4th, 2002, as an example. weird things like that. that's simply unacceptable to me. plus the whole idiotic self-quoting thing on the top of mutt's web page, and some other stuff on the web pages, just makes me think that the author is an idiot. but that's certainly not very objective reasoning. old redhat releases of pine included a patch for maildir support. however, pine is _extremely_ inefficient when it comes to large mailboxes (maildirs, i should say). get a few thousand messages in one, and pine will annoy you something awful. it seems to try to rebuild the message list in a box from scratch repeatedly every time certain operations are performed, or a timeout is met. very, very frustrating. for now i'm still using an old pine with the maildir patch, as that mutt date interpretation thing simply makes it impossible for me to use. i started writing my own mua that will probably be very, very minimal in features, just so i can avoid these stupid yet horrendous problems. i haven't done much with it recently, however, so who knows when it will be usable. pine's license is also kind of...not cool. but then again, people using qmail probably aren't very license-religious. chuckle. so shrug, lose-lose situation. -tcl.
Re: Svscan
looks like you didn't give svscan an argument to your service directory. check to see what the svscan line is like. should be invoked like svscan /service, not just svscan or svcan /. -tcl. On Fri, 19 Jan 2001, Gavin McCord wrote: > > I'm getting error msgs to the console (a small > selection): > > supervise: fatal: unable to start lib/run: file does not exist > supervise: fatal: unable to start tmp/run: file does not exist > supervise: fatal: unable to start cdrom/run: file does not exist > supervise: fatal: unable to start bin/run: file does not exist > supervise: fatal: unable to start usr/run: file does not exist > supervise: fatal: unable to start var/run: access denied > ad infinitum > > This from the entry in inittab. > > -- > I'm Keyser Soze...No, I'm Keyser Soze. I'm Keyser Soze and so's my wife! > (Monty Python play The Usual Suspects.) >
Re: who rotates the logs?
not much reason to use multilog if you're not going to use its rotation features, unless you're using other features it possesses, like pattern matching or something. i can't think of what self-rotation would be wiser than multilog, however. anyway, check out: http://cr.yp.to/daemontools/multilog.html for a man page substitution of sorts. -tcl. On Thu, 18 Jan 2001, Clemens Hermann wrote: > Hi, > > who rotates the logs when using multilog? I did not find a manpage for > multilog. I want to avoid the automatic rotation and rotate the logs my > own. qmail is installed as described in LWQ. > > thanks > > /ch >
Re: Multilog
check out tai64nlocal. it comes with daemontools. http://cr.yp.to/daemontools/tai64nlocal.html might help. -tcl. On Mon, 15 Jan 2001, Alex Kramarov wrote: > Hi. I have been happily running qmail now for some time, till now, > then I have decided to try qmailmrtg > (i also happily run mrtg for some time, to monitor my router). > > As I see, qmailmrtg requires that qmail logging will be done with multilog, (till >now I use syslog, although it's supposed to be slow which is not my primary concern). > I successfully ran multilog, but now I have a problem with it's timestamps - its >some TAI format which is pretty hard to decipher when you want to fond a log of what >happened say half an hour ago. > is there an easy way to display multilog log with "normal" (syslog-like) timestamps >(display-not write it in this format, because qmailmrtg need it in TAI).. > > Thanks.
