RE: SMTP doesn't respond
Mark Douglas <[EMAIL PROTECTED]> wrote: >QMAILDUID=`/usr/xpg4/bin/id -u qmaild` >NOFILESGID=`/usr/xpg4/bin/id -g qmaild` You're using Solaris? -Dave
unsubscribing (Was: QMQP - mini qmail)
Lukasz Gogolewski <[EMAIL PROTECTED]> wrote: >How do i get off this list? Sigh. This has become such a FAQ that I'm reposting the detailed instructions: First, ask your Internet Provider to mail you an Unsubscribing Kit. Then follow these directions. The kit will most likely be the standard no-fault type. Depending on requirements, System A and/or System B can be used. When operating System A, depress lever and a plastic dalkron unsubscriber will be dispensed through the slot immediately underneath. When you have fastened the adhesive lip, attach connection marked by the large "X" outlet hose. Twist the silver- coloured ring one inch below the connection point until you feel it lock. The kit is now ready for use. The Cin-Eliminator is activated by the small switch on the lip. When securing, twist the ring back to its initial condition, so that the two orange lines meet. Disconnect. Place the dalkron unsubscriber in the vacuum receptacle to the rear. Activate by pressing the blue button. The controls for System B are located on the opposite side. The red release switch places the Cin-Eliminator into position; it can be adjusted manually up or down by pressing the blue manual release button. The opening is self- adjusting. To secure after use, press the green button, which simultaneously activates the evaporator and returns the Cin-Eliminator to its storage position. You may log off if the green exit light is on over the evaporator . If the red light is illuminated, one of the Cin-Eliminator requirements has not been properly implemented. Press the "List Guy" call button on the right of the evaporator . He will secure all facilities from his control panel. To use the Auto-Unsub, first undress and place all your clothes in the clothes rack. Put on the velcro slippers located in the cabinet immediately below. Enter the shower, taking the entire kit with you. On the control panel to your upper right upon entering you will see a "Shower seal" button. Press to activate. A green light will then be illuminated immediately below. On the intensity knob, select the desired setting. Now depress the Auto-Unsub activation lever. Bathe normally. The Auto-Unsub will automatically go off after three minutes unless you activate the "Manual off" override switch by flipping it up. When you are ready to leave, press the blue "Shower seal" release button. The door will open and you may leave. Please remove the velcro slippers and place them in their container. If you prefer the ultrasonic log-off mode, press the indicated blue button. When the twin panels open, pull forward by rings A & B. The knob to the left, just below the blue light, has three settings, low, medium or high. For normal use, the medium setting is suggested. After these settings have been made, you can activate the device by switching to the "ON" position the clearly marked red switch. If during the unsubscribing operation, you wish to change the settings, place the "manual off" override switch in the "OFF" position. You may now make the change and repeat the cycle. When the green exit light goes on, you may log off and have lunch. Please close the door behind you. -Dave
Re: smtpd times out
kamesh jayachandran <[EMAIL PROTECTED]> wrote: >Everything was working fine before applying qmail-ldap-1.03-20010501.patch >to qmail-1.03 and building.Now after applying the patch,rebuilding,stopping >qmail and restarting,the telnetting to port 25 timesout immedeately. Times out immediately? That's a neat trick. Sure it's not being refused? How is qmail-smtpd being started? >me: My name is kameshj Should be fully-qualified. >ldapserver: (Default.) My LDAP Server is undefined! Uh-oh. Hmm. Maybe that should be set. -Dave
Re: Advanced masquerading
Marek Szuba <[EMAIL PROTECTED]> wrote: >The thing is: there is a host called stargate.net.local doing IP >masquerading for a LAN, which is known to the outside world as >zone13.outside.net. I'd like to set up qmail on this host in such a way >that: > - all the mail sent from stargate to any other machine on the LAN will have >all the sender's data similar to: Joe Blow <[EMAIL PROTECTED]> > - all the mail sent from stargate to the Internet will have all that data >similar to: Joe Blow <[EMAIL PROTECTED]> > - all the main sent from the LAN to the Internet (and relayed by >stargate, of course) will have it like: Joe Blow ><[EMAIL PROTECTED]>, What about mail from within the LAN address to recipients both local and outside the LAN? E.g., From: Joe Blow <[EMAIL PROTECTED]> To: John Doe <[EMAIL PROTECTED]>, Jane Roe <[EMAIL PROTECTED]> Would John receive a message from [EMAIL PROTECTED] while Jane receives one from [EMAIL PROTECTED]? Why not just masquerade everything with the external domain? >Can anyone help me with that? I've been trying to solve that myself, and >failed - qmail lacks good documentation I'm afraid. I disagree. I'm not just tooting my own horn (Life with qmail), but the man pages, FAQ's, www.qmail.org, and various user contributed docs are generally quite good. >I've also asked in numerous places places and noone was able to help >me. I've started wondering if qmail is capable of handling such >complicated transpations at all, and whether I shouldn't restart >using sendmail after all... I'd like to hear more about how sendmail handles such configurations. -Dave
Re: QMQP - mini qmail
[EMAIL PROTECTED] wrote: >1. tcpserver -x /etc/qmqp.cdb -u 7770 -g 2108 0 628 qmail-qmqpd & > >I need to add this to the boot script. First I'm kinda confused. Now >I have /var/qmail/supervise/qmail-smtpd/run file for smtp server, can >I run this and qmqp server at the same time so I would have another >file at /var/qmail/supervise/qmail-qmqpd/run Yes. This would be on the QMQP server. >2. Is mini-qmail a different program from qmail, No, "mini-qmail" is a name DJB coined for qmail installations in which qmail-queue is replaced by a symbolic link to qmail-qmqpc. > can they both exist. Yes, you have multiple qmail installations on a single system, one or more of which are "mini". > I want to use the mini-qmail to run huge mailing list since it > sends 1000 mails in 10 seconds. All QMQP does is queue mail remotely. It doesn't deliver 1000 messages in 10 seconds to mailboxes, it just hands them off to a QMQP server which still has to deliver them the old-fashioned way: SMTP. >3. How do I create a symbolic links to /var/qmail/bin/sendmail from > /usr/sbin/sendmail and /usr/lib/sendmail. rm /usr/sbin/sendmail /usr/lib/sendmail ln -s /var/qmail/bin/sendmail /usr/sbin /usr/lib But this is UNIX 101 stuff... >And why do I need to do this?? Because "sendmail" is a de facto API used for injecting messages. If you don't replace it with a link to the qmail "sendmail", you'll be delivering messages using sendmail. >The way I see it, the only files that are missing is >/var/qmail/control/qmqpservers - is this ip address of my server >/var/qmail/control/idhost It's a list of the IP address(es) of one or more *remote* QMQP servers. >I'm still confused. Is setting up mini-qmail like setting it up in >different machine that doesn't have qmail installed or can I set up >qmail and mini-qmail in the same machine. Mini-qmail is typically used on small end-user workstations that don't want to maintain a queue and run the long-lived qmail daemons. >by me setting up qmqp server do I need to deactivate smtp server. No. -Dave
Re: badmailfrom file and subdomains
audit <[EMAIL PROTECTED]> wrote: >I've been working on getting my badmailfrom file setup and would like to >block a entire domain from connecting. badmailfrom won't block anyone from *connecting*. >I've tried the following >@*.domain.net Nope. badmailfrom doesn't support domain wildcards. >I would also like to add the entire RBL lists but can't seem to find a >file where I can download it. Is this possible without messing the my DNS >records? Try installing rblsmtpd from ucspi-tcp. -Dave
Re: 40 simultaneous qmail-smtpd
[EMAIL PROTECTED] wrote:
>I am trying to create a server to do just mailing. I installed the
>qmail and right now I'm trying to optimize it so it can handle huge
>amount of mailing which will be handle by ezmlm.
>
>My first question is about qmail-smtpd and qmail-qmtpd
>
>1. what's the difference and which do you perfer.
They're two different protocols used for accepting incoming
mail. Neither will improve outgoing performance at all.
>second question?
>2. the faq states it like this
>tcpserver -u 7770 -g 2108 0 smtp /var/qmail/bin/qmail-smtpd &
>and to raise the limit to 400 use
>tcpserver -c 400
>
>so will the final line be
>
>tcpserver -u 7770 -g 2108 -c 400 0 smtp /var/qmail/bin/qmail-smtpd &
Yes, but, again, a list server doesn't generally deal with lots of
simultaneous incoming connections. You should be looking at maximizing
concurrencyremote.
>"Answer: Install daemontools
>(http://pobox.com/~djb/daemontools.html). Make a /var/log/qmail
>directory, owned by qmaill, mode 2700("What does this mean??(mode
>2700).
See "man chmod".
>Do
>
> qmail-start ./Mailbox /usr/local/bin/accustamp \
> | setuser qmaill /usr/local/bin/cyclog /var/log/qmail &
>
>in /var/qmail/rc.
This is outdated information. Cyclog was the predecessor of multilog.
>I already have tcpserver running but don't get this cyclog stuff.
>I have /var/log/qmail/qmail-smtpd directory already.
You're probably using multilog.
>I have pIII 600mhz, 128mb ram, 9G scsi server under linux 7.0 would
>really like this server to handle 10 million emails per day(little
>exaggeration). Is this possible. I'm also using djbdns and using
>local cache. and want to implement cdb database somehow.
Do you have high-speed network connectivity? And waht do you want to
put in a cdb?
-Dave
Re: smtp times out
kamesh jayachandran <[EMAIL PROTECTED]> wrote: >@40003b140df82d486e1c /var/qmail/bin/qmail-smtpd: error in >loading shared libraries: libc.so.6: failed to map segment from >shared object: Cannot allocate memory If you run qmail-smtpd under softlimit or some other memory limiting mechanism, the limit might be too low. E.g., if you have /var/qmail/supervise/qmail-smtpd/run and it contains: exec /usr/local/bin/softlimit -m 200 \ You might try raising that 200 to 40 or 800 and restart tcpserver, e.g. by "qmail-restart" or "svc -t /var/qmail/supervise/qmail-smtpd". -Dave
Re: limiting databytes per user
Charles Cazabon <[EMAIL PROTECTED]> wrote: >If you want to change DATABYTES on a per-user basis using tcpserver's tcprules >files, you're going to have to be able to map user IDs to IP addresses. >There's no way around that. tcprules supports matching hostnames as well as IP addresses. -Dave
Re: TCPSERVER status 256
"Nathaniel L. Keeling III" <[EMAIL PROTECTED]> wrote: >How can I verify if this is a bare line problem or not? Use recordio to record the complete SMTP dialogue. See the faq. >My rc file contains 'qmail-start '|dot-forward .forward ./Maildir/' >and nothing is showing up in the qmail-send log file. That's not nothing to do with your SMTP problems. If you're not running qmail using svscan, a la "Life with qmail", you probably should "splogger qmail" to the end of your qmail-start command. -Dave
Re: problem with local mailboxes
Kelly Shutt <[EMAIL PROTECTED]> wrote: >for those of you that were asking, i'm running slackware 7.1 and i've >installed qmail according to the life with qmail document... minus >the init.d config files, I don't use init.d, I just added >/usr/local/sbin/qmail start" to my rc.local file. I used the IDS >file to add users and such, OK so far... >and for my rc file I used the included file "binm1," I think this may >be where my problem is, Yep. >I'm not sure which rc file applies to my machine, since i'm not sure >what the default mail delivery is for sendmail in slack, but with >this one qmail appears to be functioning properly except for not >finding the mailboxes. You could look at the sendmail.cf that comes with Slackware to see what local delivery agent it's using. Or you could just use procmail (/var/qmail/boot/proc). >As I have said, qmail was configured exactly like the life with qmail >document. I don't think "exactly" means what you think it means. -Dave
Re: Domain aliases
Ahmad Ridha <[EMAIL PROTECTED]> wrote: >Petter Sundl=F6f writes: > >> So, mailing to [EMAIL PROTECTED] should be the same as >> [EMAIL PROTECTED] The same goes for petter.sundlof -- an alias on >> findus.dhs.org; [EMAIL PROTECTED] should be the same as= >> [EMAIL PROTECTED] >> I want it to be global, that it apply for all users.=20 > >Just put useless.dhs.org and findus.dhs.org in /var/qmail/control/loca= ls.=20 And rcpthosts. -Dave
Re: list got quite
Bruno Wolff III <[EMAIL PROTECTED]> wrote: >If you get the messages of changes to the crypto web site, you get to >see an update when DJB adds the event description to his web page. >You won't get this until his machine is back up, but in this case I >knew not to expect any list messages for about a day. To join that list, send a message to [EMAIL PROTECTED] -Dave
RE: postfix/qmail best for message tracking through system
"Mark Gebhardt" <[EMAIL PROTECTED]> wrote: >Do you know if there's any way I can extend the VERP thing so that I can >insert a unique message-ID into the return address or similar? qmail-inject supports two kinds of VERP: per-recipient and per-message. Per-recipient VERP's encode the recipient's address and per-message VERP's encode the date and PID. The combination of timestamp and PID is essentially a message ID. -Dave
Re: SV: relay problem
P=E5l Fr. Johansen <[EMAIL PROTECTED]> wrote: >SoHOW THE F.. DO I UNSUBSCRIBE, from this...amazing mail-list =3F > >PLEASE SOMEONE HELP ! Every message sent to the list contains the field: Mailing-List: contact [EMAIL PROTECTED]; run by ezmlm -Dave
Re: setting a custom environment var
Mark Jeftovic <[EMAIL PROTECTED]> wrote: >On Fri, 25 May 2001, Dave Sill wrote: >> >> You can parse that from the Received fields. > >That's my plan of last resort. I didn't want to do this unless I really >had to because of the different formats the Received headers can have, >and that there can be any number of them. It's not that bad because they're in reverse cronological order, and the one you want to look at is always in qmail-smtpd's format, and it's the second Received field. >My life would be made a lot easier if I had ready access to the >hostname/IP that is giving me the email without doing the guesswork >(which is what parsing the Received headers will amount to in the end) No, Received fields aren't randon junk. You can trust the ones added by qmail. >So I guess there is no readily available way to do this? Nothing easier that parsing the Received fields. E.g., it took me about a minute to come up with: 822field received P.S. I take it you are using tmda for your reply-to? I stumbled on this >in the course of researching and it looks like just what the doctor >ordered for my purposes. It's great. I've received almost no spam since implementing it. The only spam that's gotten through has gone through our "helpful" relay which "fixes" unqualified addresses by tacking on "ornl.gov", which is on my whitelist, of course. -Dave
Re: relay problem
Radoslaw Tomczyszyn <[EMAIL PROTECTED]> wrote: >I'm using qmail with tcpserver and have some problems with relay. >I set all needed sets of relay in tcp.smtp and qmtp.tcp >With masquerade ips it works fine - no problem but i want to relay other >class of ip 195.205.148. I wrote to files (tcp.smtp and so on) and >tcpserver is accepting connections and meesages but qmail doesn't send >them to the world. All those messages stay in mess folder. >What's wrong ? You've misconfigured something. If my response is unhelpful, it's because you've supplied insufficient information. Show us the contents of your config files and relevant log entries, at a minimum. -Dave
Re: postfix/qmail best for message tracking through system
"Mark Gebhardt" <[EMAIL PROTECTED]> wrote: >A central requirement of the mailing engine is that it can be used to >track the delivery status of messages through the system (i.e. if I send >message A and then message B to [EMAIL PROTECTED] and message A bounces, >whilst message B is received, I need to know this via logs/API whatever). > >It seems that qmail and Postfix are by far the best performing MTAs for >Linux, so the differentiating factor for us will be which can provide our >required functionality with the minimum of modification. Both qmail and Postfix log complete delivery information including all sucessful and failed delivery attempts. Depending upon your application, you might be able to take advantage of qmail's variable envelope return path (VERP) mechanism, which allows reliable bounce processing by encoding the bouncing address in the return address. -Dave
Re: Forward a message to me and another account
[EMAIL PROTECTED] wrote: >I want that all the mail directed to [EMAIL PROTECTED] is forwarded to >[EMAIL PROTECTED] and [EMAIL PROTECTED] >Someone is my real user on the server with qmail, someone1 is my backup user. > >How i can do this redirection? In ~someone/.qmail: ./Maildir/ &[EMAIL PROTECTED] I.e., deliver it locally and forward a copy to someone1. -Dave
Re: preventing local delivery
David Young <[EMAIL PROTECTED]> wrote: >What is the proper way to configure qmail so it does not attempt local >delivery, even when a specific host is given in the email address? Leave control/locals empty. >For example, if mail is sent to [EMAIL PROTECTED], I want it to >actually be delivered to [EMAIL PROTECTED] (or >[EMAIL PROTECTED]). You have two choices: (a) create an MX record for www.nettonettech.com pointing to nettonettech.com or mail.nettonettech.com, or (2) add a control/smtproutes entry like: www.nettonettech.com:nettonettech.com >I thought the proper way to do this would be to >put nothing in control/locals, however this results in the error message >"Although I'm listed as a best-preference MX or A for that host,/it isn't in >my control/locals file, so I don't treat it as local. (#5.4.6)/". Right, you told it not to deliver it locally, but you didn't tell it where to deliver it remotely. -Dave
Re: setting a custom environment var
Mark Jeftovic <[EMAIL PROTECTED]> wrote: >I'm playing with a privacy gateway for whois records. To make a long >story short I want to be able act based on which remote mail server >is sending me the message. > >Looking at the environment when I pipe to a perl script I see nifty >settings such as DTLINE, RECIPIENT, LOCAL and HOST. > >What I also need is something like REMOTE_SMTP, which would contain >the hostname or IP of the mail hub giving us the email. You can parse that from the Received fields. >Not much of a source hacker I did go into received.c and tried adding Stop right there. Do NOT hack qmail's source unless you *really* know what you're doing. -Dave
Re: Virtualdomains setup?
Joan Picanyol i Puig <[EMAIL PROTECTED]> wrote: >I'm trying to set up a virtualdomain > >user joan should get all mail for cancortina.com, so I set up: > >joan:/home/joan # cat /var/qmail/control/rcpthosts >localhost >grummit.earth >213.97.212.86 >tuixent21.com >cancortina.com > >joan:/home/joan # cat /var/qmail/control/virtualdomains >tuixent21.com:joan-tuixent21 >cancortina.com:joan-cancortina > >joan:/home/joan # cat .qmail-cancortina-default >./Maildir/ > >joan:/home/joan # cat .qmail-cancortina-info >./Maildir/ > > >This is the qmail log: > >@40003b0d9d3c0f7b8a04 starting delivery 22: msg 40966 to local >[EMAIL PROTECTED] >@40003b0d9d3c10018ab4 delivery >22: failure: Sorry,_no_mailbox_here_by_that_name._(#5.1.1)/ > >I must be missing something, why doesn't a mailbox exist for >[EMAIL PROTECTED]? Is concortina.com in control/locals? -Dave
Re: doublebounceto ignored??
David Boone <[EMAIL PROTECTED]> wrote: >Trying to get rid of annoying doublebounceto emails I get as a=20 >result of spam, I did an echo "doublebounce" >=20 >/var/qmail/control/doublebounceto and an echo '#' >=20 >~alias/.qmail-doublebounce in an effort to stop them from being=20 >delivered to postmaster. a showctl indicates that doublebounceto is=20= >being recognized. Correction: showctl indicates that the doublebounceto control file is set. "man qmail-control" says: control defaultused by doublebounceto postmaster qmail-send "man qmail-send" says: WARNING: qmail-send reads its control files only when it starts. If you change the control files, you must stop and restart qmail-send. Exception: If qmail-send receives a HUP signal, it will reread locals and virtualdo=AD mains. So you need to restart qmail-send. -Dave
Re: Another question
"Kennie J. Cruz-Gutierrez" <[EMAIL PROTECTED]> wrote: >The user exists and it's a valid shell account, but gives this error: > > <[EMAIL PROTECTED]>: > Sorry, no mailbox here by that name. (#5.1.1) From "man qmail-getpw": qmail-getpw considers an account in /etc/passwd to be a user if (1) the account has a nonzero uid, (2) the account's home directory exists (and is visible to qmail- getpw), and (3) the account owns its home directory. qmail-getpw ignores account names containing uppercase letters. qmail-getpw also assumes that all account names are shorter than 32 characters. -Dave
Re: qmail ignores my sorry ass...
Charles Cazabon <[EMAIL PROTECTED]> wrote: >Run your injection job again with a load that will cause it to fail, but >strace/truss it this time. Capture the output of that to a logfile. Post the >logfile to the list. Better yet, post a URL to the logfile since it'll probably be huge. -Dave
Re: Problems using qmail
"Alle"<[EMAIL PROTECTED]> wrote: >hi, I'm alessandro from Italy Welcome. I'm Dave from Tennessee, USA. >I'm using Qmail with XINETD, and it *works* Are you sure? :-) >When I send a mail to someone, qmail appends >a "" to the end of the TO field, so if the the recipients' email >is <[EMAIL PROTECTED]>, qmail try to connect to <[EMAIL PROTECTED]""> >and fails.. Right away I'm thinking "RELAYCLIENT"... >This problem doesn't exist if i send a mail trough qmail-inject.. And this nearly clinches it. I suspect you're using xinetd to set RELAYCLIENT to enable selective relaying. What you want is for RELAYCLIENT to be set to the null string for hosts allowed to relay. You're probably saying something like: RELAYCLIENT="" But apparently xinetd is not setting RELAYCLIENT to the null string, it's setting it to, literally, "". And according to the qmail-smtpd man page: Exception: If the environment variable RELAYCLIENT is set, qmail-smtpd will ignore rcpthosts, and will append the value of RELAYCLIENT to each incoming recipient address. So, perhaps setting RELAYCLIENT like: RELAYCLIENT= in your xinetd config will do the trick. >The curious thing is that if I put in the FROM field an external >address, qmail is able to send-out >the error message whitout any problem!!! Not sure what's going on there, though. -Dave
Re: how to test for a qmail virtualdomain?
"Jason R. Mastaler" <[EMAIL PROTECTED]> wrote: >Does anyone know of a reliable way to programatically test whether an >incoming message is part of a qmail "virtualdomain" or not? I think you'll have to parse control/virtualdomains. >I've been looking at qmail-send's environment variables under >both a regular setup and a virtualdomain, and can't find a surefire >way to differentiate the two cases. With a virtualdomains entry like: virtual.domain:de5-virtual A message sent to [EMAIL PROTECTED] is very similar to a message sent to de5-foo@localhost. Diff'ing the qmail-command environments, I get: < HOST2=sws5.ctd.ornl < HOST3=sws5.ctd < DTLINE=Delivered-To: [EMAIL PROTECTED] < HOST4=sws5 < HOST=sws5.ctd.ornl.gov < [EMAIL PROTECTED] --- > HOST2=virtual > HOST3=virtual > DTLINE=Delivered-To: [EMAIL PROTECTED] > HOST4=virtual > HOST=virtual.domain > [EMAIL PROTECTED] -Dave
Re: Can't stop open relay
"John Kuhn" <[EMAIL PROTECTED]> wrote: >Can you people please stop sending me "you didn't read the docs" email.. I >DID.. if I didn't I probably would have never got qmail up and running in >the first place.. Then either you didn't read the right docs or you didn't understand them. >I'm am whole heartly sorry for being confused about >something and asking for a little help.. There's no need to apologize for being confused. Just take a couple deep breaths, calm down, and study: http://www.lifewithqmail.org/lwq.html#relaying If it doesn't make sense, ask some specific questions about the bits you don't get. -Dave
Re: Using vchkpw (vpopmail) with qmail-pop3d?
"Steven Katz" <[EMAIL PROTECTED]> wrote: >I'm trying to get the smtp after pop authentication part of vpopmail >to work. I followed the LWQ instructions to install qmail and I'm >using qmail-pop3d. Where should the below startup line for vchkpw be >placed? In qmail-pop3d/run. See: http://www.faqts.com/knowledge_base/view.phtml/aid/8225/fid/223 -Dave
Re: problem
"colette tostivint" <[EMAIL PROTECTED]> wrote: >qmail runs without problems and i give a new route and new interface it >doesn't run >Why? What do you mean by "doesn't run"? Network reconfiguration won't stop qmail processes from running. -Dave
Re: Handling high volume lists
Andy Bradford <[EMAIL PROTECTED]> wrote: >It wouldn't be hard to configure your Gnus to add the >mail-followup-to header for this list. Better yet, create a file containing a list of mailing lists, e.g.: [EMAIL PROTECTED] [EMAIL PROTECTED] ... And set the QMAILMFTFILE environment variable to the name of that file. -Dave
Re: SMTP_AUTH
<[EMAIL PROTECTED]> wrote: >I had some instructions on how to test the server with the AUTH cmd through >checkpasswd ( I only tested plain at the time) which I can no longer find - >it work as outlines and put me in my home dir. Since I have upgraded I need >to retest the server. Right now under AUTH plain it gives me out of memory - >I don't know that I'm still testing this procedure right. I would like to >test LOGIN but don't know how or what to return when it returns it's string. > >qmail_smtp_auth 0.30 >cmd5checkpd 0.22 or checkpasswd >qmail 1.03 > >tcpserver smtp startup >#!/bin/sh >QMAILDUID=`/usr/xpg4/bin/id -u qmaild` >NOFILESGID=`/usr/xpg4/bin/id -g qmaild` >MAXSMTPD=`cat /var/qmail/control/concurrencyincoming` >exec /usr/local/bin/softlimit -m 200 \ >/usr/local/bin/tcpserver -v -p -x /etc/tcp.smtp.cdb -c "$MAXSMTPD" \ >-u "$QMAILDUID" -g "$NOFILESGID" 0 smtp /var/qmail/bin/qmail-smtpd >me.me.com \ >/bin/cmd5checkpw /bin/true smtpd 3 2>&1 > >I have followed the outgoing instruction for Outlook for the client but it >won't let me auth. Try raising the memory limit (the 200) to 400, 800 until the "out of memory" error goes away. >question - what should be in inet.conf if I'm using tcpserver? Nothing related to the services handled by tcpserver. -Dave
Re: newbie question with concurrency remote
"Michael Geier" <[EMAIL PROTECTED]> wrote: >I am running qmail on: > RedHat 6.2 > 256 Mb Ram > >I set concurrency remote = 150... > >however, most of the time, it seems like only a handful of remote processes >are running, even though the queue backs up (right now, over 14000 msgs in >queue and only 20 remote processes running)... Are you sure concurrencyremote is set to 150? You restarted qmail-send after changing it? The logs reflect the 150 setting? >Anybody have an idea about how to force it to run faster Faster disk More memory Faster network Replace syslog with multilog Install djbdns, run dnscache Kill non-qmail processes Faster CPU >or at least not kill off my qmail-remote processes? What makes you think qmail-remote processes are being killed off? -Dave
RE: QMail autostart problem
"Neil Whittington" <[EMAIL PROTECTED]> wrote: >The default run level is 3. > >The links created are: > ln -s ../init.d/svscan S89svscan >in rc3.d and rc5.d > > ln -s ../init.d/svscan K12svscan >in rc0.d rc1.d rc2.d and rc6.d So you're starting svscan at runlevel 3. Is it running after the system boots? What links did you create for qmail? -Dave
Re: qmail retry
Jamyn <[EMAIL PROTECTED]> wrote: >$qmail_home/control/concurrencyremote > The number you insert into this file determines how > many remote sockets/connections at a time your mail > server will open. Yes. >$qmail_home/control/concurrencylocal > The number you insert into this file determines how > many local/incoming mail connections you want Qmail > to allow at a time. No. It's the maximum number of simultaneous local deliveries. The limit on incoming SMTP sessions is determined by tcpserver, if you use it. The default is 20. "Life with qmail" adds a pseudo-control file called concurrencyincoming that is passed to tcpserver. -Dave
Re: pop3 connection reset after exactly 1 minute
"Jens Hassler" <[EMAIL PROTECTED]> wrote: >Same problem. After exactly 1 minute the connection resets. Try strace'ing the qmail-pop3d process. >I didn't recompile QMail though, just copied the binaries. Maybe there's a >problem with one of my compiled files? What files are involved in a POP3 >session? qmail-pop3d and qmail-send? qmail-pop3d, tcpserver (or inetd/xinetd), qmail-popup, and checkpasswd, at least. Not qmail-send. >So, because there is a completely different hardware with a very up-to-date >Linux and other network cards / drivers, there must be a problem with one of >my QMail files...? Or your configuration. >This thing is ... Frustrating? Exasperating? -Dave
Re: remote smtp problem
[EMAIL PROTECTED] wrote: >When ever a remote client tries to send mail thru my qmail box, qmail >appends a question mark to the end of the domain i.e >Sorry, I couldn't find any host named rbi.co.uk?. (#5.1.2) Clients injecting messages via SMTP? Using selective relaying? I'd guess that "RELAYCLIENT" is being set to " " instead of "" in the access file (perhaps /etc/tcp.smtp). -Dave
Re: QMail autostart problem
"Neil Whittington" <[EMAIL PROTECTED]> wrote: >I have created my svscan and qmail startup scripts (see below) in the = init.d >directory and set their permissions. > >In the rcX.d directories, I have set up the link to svscan (eg ln =96= s >../init.d/svscan K12svscan ) Which links did you create=3F What is your default runlevel=3F >Now, when I reboot, qmail doesn't start. If I go into the /etc/rc.d/in= it.d >directory and type > >./qmail start >./svscan start > >it all runs perfectly. What am I doing wrong=3F Well, that shouldn't work. The "qmail start" will only work if svscan (and supervise) is already running. Perhaps you're not starting svscan first. -Dave
Newbies vs. arrogant experts (was: Newbie with tcpserver)
[Barry, the "Re[2]" syntax your mailer uses is non-RFC-compliant.] Barry Hill <[EMAIL PROTECTED]> wrote: >First of all: This is the most arrogant list I have come across. All >the other lists that I'm on help out beginners with a short answer (we >were all beginners once ... ), but here the beginner is either told to >RTFM or told to pay for support. First of all, don't judge the entire list based the actions of a small nonrepresentative sample. Second, the offer of commercial support made to Pablo was sent privately, not to list. Pablo's reposting it publicly is at least as rude as trolling the list for clients. >If the beginner can't find the >relevant section in the FAQ then answers have to be teased out of the >list, which generates more traffic than one short and helpful mail >(this thread is a good example of this). There are at least four schools : 1) Flame newbies posting FAQ's. 2) Answer newbies posting FAQ's. 3) Point newbies to the answers to their FAQ's. 4) Ignore newbies posting FAQ's. I've listed them from least effective to most effective, IMO. Flaming is supposed to be a deterrent--and it might be--but it's just plain rude. Answering FAQ's is "nice", but it's tiresome and contributes to lowering the signal/noise ratio on the list and it encourages other newbies to ask their FAQ's. Pointing newbies *politely* to the docs answering their question is OK--it at least helps teach them to help themselves--but it's tedious work and it also encourages other newbies to ask FAQ's. Telling a newbie to RTFM is a flame. Telling a newbie which M to F'ing R is not. Ignoring FAQ's is the easiest and safest approach. It encourages the newbie to search the web, list archives, etc. and doesn't reward newbies by answering their question. It keeps the signal/noise ratio high, and it keeps the civility and morale high. >AFAIK (and I'm no expert), TCPSEVER is configured in the command line, >and uses /etc/tcp.* files for security & access settings. The manual >files are installes with the software and can be read with "man >tcpserver". Else they're in the source directory. The documentation is on the web. No man pages are included with ucspi-tcp. -Dave
Re: Daemontools & Supervise
Pablo Buenaventura <[EMAIL PROTECTED]> wrote: >For which way could I know if daemontools is installed >already? If you've got /usr/local/bin/supervise, you've probably got daemontools. On Red Hat, you could check for an RPM: rpm -qa | grep daemontools >What supervise qmail-send, supervise qmail-smtpd and >supervise qmail-pop3d are used for? supervise starts, monitors, and controls services. The qmail-send service consists of qmail-send, of course, and the other long-running qmail daemons started by qmail-start: qmail-clean, qmail-lspawn, and qmail-rspawn. -Dave
Re: linebreak handling / qmail-inject
"Sascha Dahl" <[EMAIL PROTECTED]> wrote:
>I considered that qmail seems to make a difference between DOS and UNIX
>style linebreaks ("\r\n" AND "\n") when sending mails from localhost.
qmail runs on UNIX systems, and UNIX systems use newlines, not CR-LF.
>Is this the usual behaviour of qmail?
Yes.
>That would mean, that it is not 100% sendmail compatible...
Correct. qmail is not bug-compatible with Sendmail.
>or did I misconfigure something?
No.
>If there is a solution for handling DOS style linebreaks with qmail I
>would appreciate any hints.
Why not just store files with the line breaks appropriate for the OS
they're stored on?
-Dave
Re: SMTP AUTH and TLS
Joshu=E9 Mart=EDn <[EMAIL PROTECTED]> wrote: > But when I tried to apply the two patches to Qmail sources (f= irst=20 >the TLS patch and then the AUTH), the second patch rejects parts of th= e >AUTH patch. I tried to apply manually the parts of the patch that >were rejected, but the resultant qmail-smtp didn't allow authenticate >nor encript. I've merged these two patches, but I've just got diffs for the two files the conflicted: qmail-remote.c and qmail-smtpd.c. Available upon request. -Dave
Re: Can MX record be CNAME?
"q question" <[EMAIL PROTECTED]> wrote: >END OF DISCUSSION Sorry, q, but I'm not ready to end the discussion, despite your declaration. >Dave Sill wrote: >> >>"q question" <[EMAIL PROTECTED]> wrote: >> >> >I was appalled when [Charles] said "please don't post BIND zonefiles >> >to Dan's lists". That is a blanket directive that is not necessarily >> >shared by everyone on this list, certainly not me. >> >>directive <> request You ignored this comment, which is, I think, critical. Charles said "please don't post...". Charles did not say "never post...". The former is a request. The latter is a directive. If Charles had given a directive, your reaction *might* have been justified. >BINDthinkers cannot just jump blindly into djbdnsthink. There are going to >be a few posts now and again where someone is going to show a few zone >records to clarify their point while they transition into qmail/djbdns/etc. Such zone file excerpts should be prefaced with an apology. If no apology is included, offenders should not be surprised if people point out their faux pas. >Noone should say: "please don't post BIND zonefiles to Dan's lists". Who is Noone, and why should he repeat Charles' request? -Dave
Re: Can MX record be CNAME?
"q question" <[EMAIL PROTECTED]> wrote: >I was appalled when [Charles] said "please don't post BIND zonefiles >to Dan's lists". That is a blanket directive that is not necessarily >shared by everyone on this list, certainly not me. directive <> request >A few lines of zone records speaks volumes for BINDthinkers and they are >well worth the space in the email. BINDthinkers are WRONGthinkers. djbdnsthinkers are RIGHTthinkers. :-) Zone files are as welcome here as sendmail.cf's: not very. DJB went to a great deal of effort to free us from crapware like Sendmail and BIND. Please show him a little respect. -Dave
Re: lower concurrency on _certain_ domains?
Alan Clegg <[EMAIL PROTECTED]> wrote: >I run mailinglists.org and have come to find out that they way that AOL is >determining that I am a "spammer" (I'm not), is the number of concurrent >connections into AOL. > >Is there any way to lower the concurrency rate on a single domain (AOL.com) >while leaving everyone else intact? Sure. # echo aol.com:alias-aol >>/var/qmail/control/virtualdomains # echo ./AOLspool/ >/var/qmail/alias/.qmail-aol-default # qmail restart Then install serialmail and add a cron entry to run maildirsmtp on the AOLspool periodically. -Dave
Re: Qmail, double-bounces, and RFC2821
[EMAIL PROTECTED] (Patrick J. LoPresti) wrote: >This is the new RFC which supersedes RFC821 as the SMTP specification: > > http://www.faqs.org/rfcs/rfc2821.html > >The grammar in sections 4.1.2 and 4.1.3 appears not to permit [] as >the domain portion of a mailbox in an address. In particular, the >address "#@[]", which Qmail uses as the envelope sender for >double-bounces, is not syntactically valid according to this grammar. I believe #@[] was invalid under RFC821, as well--and is one of the reasons that particular string was selected, so this is nothing new. Double bounces should be delivered locally, so RFC821/2821 doesn't apply. -Dave
Re: ANN: qmail delivery speed comparison graphs available
Markus Stumpf <[EMAIL PROTECTED]> wrote: >The "main" work at concurrencyremote=500 was finished after about 1250 >seconds, at concurrencyremote=150 it was finished after about 1450 >seconds; concurrencyremote=250 is in between at about 1350 seconds. I think that's because you're not just measuring the local system's ability to pump out messages, but also the ability of an unknown set up remote hosts to receive them. >The number of finished successful deliveries/second is nearly the same >for all three data sets (about 75-80 deliveries/second). I think what you've determined is that the remote hosts on your list can only accept 75-80 deliveries/second, not that qmail can't deliver faster than that. In these tests, your system was able to keep 500 qmail-remotes busy, but it's possible that if the remote systems were more receptive--able to receive 200, 300, 400 messages/second--it might not have been able to keep them all busy. >However the number of failures/deferrals per second was lower in the >150 data set than in the 250 and much lower than in the 500. Evidence that you're overwhelming some of the remotes. Do you see deferrals for different reasons with higher concurrencies? >*MY* conclusion from that comparisons is that the power of the >qmail-bigconcurrency patch is probably commonly overestimated >and the patch is kinda useless. > >PLEASE NOTE: the data sets are collected from delivery cycles of three > successive weeks (the newsletter is a weekly one). Although it's > delivered the same weekday (Friday) and around the same time (early > afternoon GMT+2) the load on the remote (i.e. receiving) mail servers > has a large impact on the data. This is even more true as 90% of > the messages are sent to only 300 unique IP addresses (some of which > are surely hidden behind load balancers). > Thus minor tendencies are to be handled with care and the data sets > may not be really representative. I'm not sure you can safely draw that general conclusion. Clearly, in this case it's nearly useless. But I don't think your situation is typical--90% of the messages to 1/3% of the hosts. And 9 is a pretty large list. The chances are good that a large percentage of those 300 hosts couldn't handle a sudden surge of up to 500 additional SMTP sessions--or least they couldn't handle it well. I think smaller mailings and/or a more diverse distribution of recipients would reveal more impact of a higher concurrencyremote. >I'd be very interested in your opinions/comments. Thanks for taking the time to publish this information. It's further demonstration of the need for profiling versus speculation. And it points out how difficult it can be to accurately measure the impact of a local change when the measurement depends on the response of remote systems that have the potential to adapt (positively or negatively, intentionally or accidentally) to the local change. -Dave
Re: Can I use qmail-pop3d for both mbox and maildir format?
Michael Cheung <[EMAIL PROTECTED]> wrote: > Can I use qmail-pop3d for both mbox and maildir format? No, but SolidPOP handles both: http://solidpop3d.pld.org.pl/ -Dave
Re: qmail-pop3d not working?
"Mark Delany" <[EMAIL PROTECTED]> wrote: >You might want to feed this back to the faqts people. Let's others >benefit from what you've learnt. It's fixed. -Dave
Re: Backup
>From http://cr.yp.to/qmail/faq/reliability.html#backups: >How do I back up and restore the queue disk? > >Answer: You can't. > >One difficulty is that you can't get a consistent snapshot of the >queue while qmail-send is running. Stop qmail first. And kick off all the users to prevent new messages from being added to the queue. >Another difficulty is that messages in the queue must have filenames >that match their inode numbers. Run queue-fix after restoring. >However, the big problem is that backups---even hourly backups!---are >far too unreliable for mail. If your disk dies, there will be very >little overlap between the messages saved in the last backup and the >messages that were lost. Restoring an old queue will probably result in redelivering some messages, but it will recover long-undeliverable messages. To me, a few duplicates are worth it to recover lost messages. >There are several ways to add real reliability to a mail server. >Battery backups will keep your server alive, letting you park the >disk to avoid a head crash, when the power goes out. Solid-state >disks have their own battery backups. RAID boxes let you replace dead >disks without losing any data. Yes, UPS's and disks are cheap. -Dave
Re: Trying to install qmail
"|nix ZixinG" <[EMAIL PROTECTED]> wrote: >Hi guys, Visit this site. His QMAIL howto is simply the best > >http://www.enixus.com.sg/~simbajaj/documents/ascii/qmail-HOWTO After a quick look I'm not too impressed. If you follow his directions, you'll likely end up with the qmail "sendmail" setuid root. And English is clearly not his first language. He gets his point across, but the grammatical errors are distracting. For a Linux qmail HOWTO, I prefer Adam McKenna's: http://www.flounder.net/qmail/qmail-howto.html -Dave
Re: alias with maildir
<[EMAIL PROTECTED]> wrote: >I have just set up Qmail to use Maildir. It is working fine sending to an >existing user. The problem is it cannot send to the alias mailbox such as >~alias/.qmail-postmaster. I think I'm missing something. I've already >touched and chmod 644 ~alias/.qmail-postmaster. >It still returns this error: "deferral: >Unable_to_chdir_to_maildir._(#4.2.1)". >I have tried creating ~alias/.qmail-postmaster as a directory but qmail >couldn't recognize it as a mail recipient. > >I would very much appreciate any assistance. Thanks! You sound a little confused. .qmail files give delivery directions. They're *always* files. They can direct delivery to a mailbox--which can be either a file (mbox) or directory (maildir). If you want to deliver to a maildir, specify the name of the maildir in the .qmail file, e.g.: ./postmaster/ and create the maildir using maildirmake: /var/qmail/bin/maildirmake ./postmaster and make it be owned by the right user: chown -R alias ~alias/postmaster -Dave
Re: "an alias can never override a valid user's deliveries" ???
Adam Andrzej Jaworski <[EMAIL PROTECTED]> wrote: >also please remember that users/assign method is not suitable >for us since - for many reasons (our auto-hosting software) - >we have to use system accounts qmail-users doesn't preclude the use of system accounts, it just provides a more general aliasing mechanism that preempts system accounts. >so we need one simple thing: qmail should respect what is in global >aliases.cdb file used by fastforward >means if there is configured alias (or catch-all) in one domain >it should sent messages to user pointed to this alias - not to >real user >if this can't be done, then handling aliases in fastforward/qmail duo >are worse than in Zmailer... (brrr..) You could always modify the source--qmail-lspawn.c, most likely. -Dave
Re: Something I'm missing here...
"Andrew Apold" <[EMAIL PROTECTED]> wrote: >... finally found "life with qmail". I've read this about a dozen >times, plus most of the FAQs that I know about and seemed to relate >to my problems I tried to follow LWQM exactly, but still no >avail. I can send mail out using mail name@domain from command >promp. OK, good, so qmail-send is running. What does: /usr/local/sbin/qmail stat say? And: ps -ef|grep qmail ps -ef|grep supervise >Any of the mail clients I've tried, the connection seems refused, >this includes on the same machine trying localhost, or using the >domain name (nmore.com), or on other machines elsewhere attempting >to access it. That means tcpserver isn't listening to port 25. What does /var/log/qmail/smtpd/current say? >instcheck had been saying that my ../bin/sendmail had wrong >permissions. Doing "make setup" should fix that. >Okay, I saw there was a sendmail with different permissions in the >installation directory so I copied that one over, now it complains of >the wrong group... don't know if this would cause all the problems >or not. How is this fixed? "make setup" >Since I was able to send (somewhat limited) but not receive, I tried >installing pop3d. This seems to allow the mail client to listen >w/out errors, but doesn't seem to receive non-local mail. The pop server has no messages to serve. You'll have to fix smtp first. >I tried setting up tcpserver after all this (is this different than >the ucspi I installed with LWQM?) instead of inetd... however, my >/var/maillog file shows numerous "tcpserver: fata: unable to bind: >address is already used" mised in with a number 'f "tcpserver: status >0/40", "tcpserver: status 1/40", etc... Hmm... I wonder if something else is listening to port 25, preventing tcpserver (for qmail-smtpd) from grabbing it. You don't still have sendmail or some other MTA running, do you? And there shouldn't be an smtp entry in xinetd.dir or inetd.conf. >I also see a number of >"Sorry_Although_I'm_listed_as_best_preference_MX_or_A_for_that_host,/it_isn't_in_my_locals_file"... >messages. But nmore.com is in my /var/qmail/control/locals file. Have you HUP'd qmail-send since adding nmore.com to locals? How about posting a few lines from the log, not just the error message? >lastly, when trying the local connect via telnet to port 25, I get >"connection refused". I somewhat gather that until this >this port can be connected to I will not be able to send mail... You won't be able to receive mail from other systems or inject mail via SMTP, but local injections (qmail-inject) will work. >Anyway, I've a ton of problems. I've already started over 3 >times... though not sure how to wipe it clean for a fresh >restart. /usr/local/sbin/qmail stop rm -rf /var/qmail -Dave
Re: RFCs?
Brian Reichert <[EMAIL PROTECTED]> wrote: >On Thu, Apr 12, 2001 at 11:44:10AM -0700, David Benfell wrote: >> >> I keep hearing rumblings about how Dan plays fast and loose with the >> RFCs in qmail and his other programs. All I know is I'm a happy qmail >> (and djbdns and publicfile and ezmlm+idx) user. It all works for me. > >The only other thing I recall someone bitching about is that he >invented a new header field 'Delivered-To', wherein the >convention/standard (when you are inventing such things) is to >prepend them with an 'X-', ie: 'X-Delivered'To'. That's not a standard. One thing DJB does thumb his nose at is the RFC821 prohibition against transmitting 8-bit characters. Chicken Little notwithstanding, the sky remains intact. Standards are great but they shouldn't be followed blindly. -Dave
Re: xinetd, tcpwrappers and qmail
John Evans <[EMAIL PROTECTED]> wrote: >I am missing something in my settings, but I just can't find what it is. What you're missing is that you should be using tcpserver. >I tried using tcpserver and that worked for allowing selective relaying, but >connections to any port from systems other than localhost usually took 30-45 >seconds between getting the socket and getting the banner from the server. This is the MFAQ (Most Frequently Asked Question) on this list. See: http://cr.yp.to/ucspi-tcp/tcpserver.html And note the -R, -H, and -l options. >There is no tcpserver mailing list that I could find and none of the man pages >or online documenation told me how to fix this problem. Please don't suggest >that I use tcpserver to resove this issue because it introduces larger >problems. Nonsense. tcpserver instroduces no problems whatsoever. -Dave
Re: Again on "Mail-Follow-Up" plus other...
Marco Calistri <[EMAIL PROTECTED]> wrote: >...here my file contents: > >[ik5bcu@linux ik5bcu]$ cat .lists > >[EMAIL PROTECTED] > >Then I can show you the latest message's header I received from that M.L.: >#--- >XF-Source: ik5bcu >X-RDate: Wed, 11 Apr 2001 20:18:54 +0200 (CEST) >Return-Path: <[EMAIL PROTECTED]> >[snipped] >From: Criss74 <[EMAIL PROTECTED]> >To: [EMAIL PROTECTED] >Subject: [angolinux] ide-scsi e Mdk 7.2 >#--- >As you can see this M.L. is using qmail and ezmlm!! You misunderstand. The Mail-Followup-To field will only be added by qmail-inject to messages *you* send *to* the list--not all messages you receive from the list. >Another very annoying line is the X-Fetchmail-Warning that I'm unable >to wipe away. That's a fetchmail issue. -Dave
Re: /usr/local/sbin/qmail: No such file or directory
"Steven Katz" <[EMAIL PROTECTED]> wrote: >I get the following message when running any part of /usr/local/sbin/qmail > > /usr/local/sbin/qmail: No such file or directory See: http://www.faqts.com/knowledge_base/view.phtml/aid/1200/fid/223 >I don't appear to have /var/run/svscan.pid, though I've gone over the >daemontools installation a few times already.. Do "mkdir /var/run" before starting qmail the first time. -Dave
Re: defaultdelivery method seperate from /var/qmail/rc ?
"Steven Katz" <[EMAIL PROTECTED]> wrote: >Why does Life with qmail suggest separating the defaultdelivery from >the /var/qmail/rc file? The advantage isn't obvious to me. If defaultdelvery is just "./Maildir/" or some other simple one-liner, there's not much advantage other than putting all the configuration settings in one place. But since defaultdelivery is a .qmail file, it can be quite complicated--multiple lines--and embedding a *file* in a single command line argument is messy. Putting it in a separate file also removes shell quoting problems. -Dave
Re: Problem forwarding/keeping copies with .qmail
Rafael Angarita <[EMAIL PROTECTED]> wrote: > I'm trying to forward all the messages received by an user and keep >copies in his local Maildir, the local copies are working fine but the >forward is not. I tested the .qmail file running qmail-local manually >and in this case everything worked correctly (keep copies and forward >the message). > > The .qmail file looks like this (and the permissions are 644): > >/qspool/mydomain/n_s5/e6/raadvip/Maildir/ >&user2@otherdomain > > Any suggestions? What Do The Logs Say? (tm) -Dave
Re: Again on "Mail-Follow-Up" plus other...
Marco Calistri <[EMAIL PROTECTED]> wrote: >I create $HOME/.lists which contains the mailing list rcpt@domain >this file has chmod 644 chown user chgrp user, >then I firstly add these lines into $HOME/.bash_profile, >then into /etc/profile because I get no the result: > ># .bash_profile > ># Get the aliases and functions >if [ -f ~/.bashrc ]; then >. ~/.bashrc >fi > ># User specific environment and startup programs > >PATH=$PATH:$HOME/bin >BASH_ENV=$HOME/.bashrc >USERNAME="" >QMAILMFTFILE=$HOME/.lists >^ >export USERNAME BASH_ENV PATH QMAILMFTFILE > > ># /etc/profile > ># System wide environment and startup programs ># Functions and aliases go in /etc/bashrc > >PATH="$PATH:/usr/X11R6/bin" > >ulimit -c 100 >if [ `id -gn` = `id -un` -a `id -u` -gt 14 ]; then >umask 002 >else >umask 022 >fi > >USER=`id -un` >LOGNAME=$USER >MAIL="/var/spool/mail/$USER" > >HOSTNAME=`/bin/hostname` >HISTSIZE=1000 >QMAILFMFTFILE=$HOME/.lists >^^ >if [ -z "$INPUTRC" -a ! -f "$HOME/.inputrc" ]; then >INPUTRC=/etc/inputrc >fi > >export PATH USER LOGNAME MAIL HOSTNAME HISTSIZE INPUTRC QMAILMFTFILE > >for i in /etc/profile.d/*.sh ; do >if [ -x $i ]; then >. $i >fi >done > >unset i > >But this still does not works, >any idea? Have you verified that QMAILMFTFILE is set in the shell you're sending the test mail from? Show us the contents of your .lists file, the test message you sent, and the message you received. >Beside this I wonder ask if are there any ways to configure >a mail filtered forwarding toward a second host connected into LAN. > >Actually all the mail coming from my ISP's POP3 server is retrieved >via fetchmail and passed to qmail, >I have the .qmail file where I added the line: > >&[EMAIL PROTECTED] > >so all the mail arriving for my hostname is forwarded to the above rcpt. > >Is there a way to filter the mail so only specific recipients be >forwarded? > >i.e. only retrieved mail From:[EMAIL PROTECTED] > >can goes to [EMAIL PROTECTED]? Yes, use a filtering utility like procmail or maildrop--or clever .qmail script hackery, perhaps using mess822 tools. -Dave
Re: Fw: How to block an email id in qmail?
"Sunil ." <[EMAIL PROTECTED]> wrote: >I understand that putting an entry into the badhostfrom file should be able >to block all mails from sent from an email source such as [EMAIL PROTECTED] It's "badmailfrom", and it only blocks messages that include the listed user/domain in the SMTP "MAIL" command--which doesn't always match the From header field. >My mail server is currently hosting multiple domains. I wish to block >senders according to my different domains. For example, is it possible to >block an email address for myfirstdomain.com and not for myseconddomain.com >?? Is there multiple "badhostfrom" files from different domains ?? No, but you could use something like a virus scanner or spam checker that lets you write customized validation scripts. -Dave
Re: heavy load servers
qmail qmail <[EMAIL PROTECTED]> wrote: >My doubt is to is there a certain metric where yu >decide how many such fronts will be required if i >have 1 million users and about 1000 transactions at >ANY GIVEN POINT OF TIME (transaction can be incoming >outgoing etc -total transactions-any nature) > >I am sure this topic has been a much discussed topics >a number of times,but this is all i need That depends heavily on lots of variables including what those 1000 transactions are doing (SMTP, POP, IMAP, encryption, LDAP, SQL, spam checking, virus checking), how the front-ends are configured (h/w, OS), what response time is acceptable, and how much "headspace" you want. -Dave
Re: Where are my aliases?
"KEVIN ZEMBOWER" <[EMAIL PROTECTED]> wrote: >I'm trying to determine how to control where mail gets forward to >when mailed to "[EMAIL PROTECTED]" (one of my hosts). > >1. africaalive.org is a CNAME for virtual.jhuccp.org. (This seems to > be backwards in the DNS, where looking up virtual.jhuccp.org > determines that the canonical name is africaalive.org. Odd...) In > the DNS records, this is recorded as "africaalive.org internet > address = 162.129.225.199". This is the IP address of > virtual.jhuccp.org. However, there are no MX records in the DNS > for either africaalive.org or virtual.jhuccp.org. There is an MX > record for jhuccp.org. This is my first question, how is mail to > africaalive.org even finding us to begin with? This address does > work correctly. If there's no MX entry, CNAME (or A) are used. >2. In reading the qmail manuals, I learned the importance of > /var/qmail/control/rcpthost and virtualdomains. Here's the content > of these files: >virtual:/var/qmail/control # cat rcpthosts >localhost >virtual.jhuccp.org >africaalive.org >virtual:/var/qmail/control # cat virtualdomains >africaalive.org:africaalive.org >virtual:/var/qmail/control # > >From my reading, the first value in the virtualdomains files >identifies a local user to send mail to which arrived addressed to >the second value. Close. It's a *prefix*. Mail to [EMAIL PROTECTED] will be delivered locally to africaalive.org-foo. >However, I have no user "africaalive.org" on host >virtual. That could be a problem, especially if you also don't have a ~alias/.qmail-africaalive:org-default file to "catch" the virtual domain's mail. >There's also no /etc/aliases file, though I do have an >/etc/aliases.db file. I can't figure out how to get into the >aliases.db file to see if there's an alias for africaalive.org in >there. qmail doesn't use /etc/aliases unless you have fastforward installed. It never uses /etc/aliases.db. >I'm not very familiar with qmail and probably haven't read the >documentation as throughly as I should, but none of this is making >sense. Would someone please give me a hand and point me in the right >direction to figure this out. Start with "Life with qmail": http://www.lifewithqmail.org -Dave
qmail rewrite in progress
In comp.security.unix, <[EMAIL PROTECTED]>, DJB wrote: >From: [EMAIL PROTECTED] (D. J. Bernstein) >Subject: Re: sendmail replacement? >Newsgroups: comp.security.unix >Date: 10 Apr 2001 20:22:36 GMT >Organization: IR > >Daniel Roesen <[EMAIL PROTECTED]> wrote: >> 1) Qmail development is _dead_ since years. > >A complete rewrite is in progress. Several pieces have already been >released. In the meantime, the current qmail version works. I wonder what pieces he's referring to. Maybe daemontools and ucspi-tcp? -Dave
Re: Upps.. :) Kernel parameters
[EMAIL PROTECTED] wrote: >Hi! I'm running the Qmail-1.03(big-todo.patch and big-concurrency.path) >+ Ezmlm-0.53 on Linux Debian Kernel 2.2.17 > >[snipped] > >The conf-spawn limit to 509! What does that mean? Did you set it to 1000 and find that it never spawned more than 509? Did you set it to 1000 and get an error message saying the limit was 509? Remember: 1) Tell us what you did. 2) Tell us what you expected to happen. 3) Tell us what *did* happen. -Dave
Re: virtual domain aliases problems...
Geoffrey Gallaway <[EMAIL PROTECTED]> wrote: >I recently moved from sendmail to qmail-1.03. I'm having a few problems >getting per-domain alias files working. > >[snip description of sendmail method] > >Now, with qmail I've installed fastforward and setup /etc/aliases to >work correctly. The question is how do I make qmail recognize the >aliases files for the virtual domains that my users have? For example, say you have virtual.example.com managed by "joe". In control/virtualdomains: virtual.example.com:joe-virtual In ~joe/.qmail-virtual-default: | fastforward -d virtual.aliases.cdb -Dave
Re: Rewriting headers.
[EMAIL PROTECTED] wrote: >I'm using QMail + MySQL. >I have the need to handle two different domain, but which refer to the >same mailboxes. > >With Sendmail and Postfix, I can instruct to rewrite domain1.it to >domain2.it BEFORE queue processing. > >How can I do the same with QMail? >MySQL patch provide a method which implies information duplication, or >another which avoid to check for the domain at all. I don't like both >ways. > >Is there another way I'm missing from the docs? Why not just list the domains in control/locals and control/rcpthosts? Why bother with rewriting? -Dave
Re: OpenBSD 2.8 & "You have new mail in /var/mail/root"
"Rick Updegrove" <[EMAIL PROTECTED]> wrote: >I am getting this message "You have new mail in /var/mail/root" every day on >my new OpenBSD 2.8 machines running qmail. And are messages actually being delivered to /var/mail/root? If so, then you probably haven't replaced /usr/lib/sendmail (and/or /usr/sbin/sendmail) with a link to /var/qmail/bin/sendmail. >I want all of that mail to go to >either to a remote host or to a local Maildir depending on the >machine. Root mail is usually handled by ~alias/.qmail-root. If you want it forwarded remotely, use: &[EMAIL PROTECTED] If you want it delivered to a local Maildir, forward it to local user whose mail goes to a maildir: &user Where ~user/.qmail contains: ./Maildir/ Or, even better, use an extension address in .qmail-root: &user-root And create ~user/.qmail-root to save the root mail in a separate maildir: ./Mail/root/ -Dave
Re: A strange behavior.
Kou Sato <[EMAIL PROTECTED]> wrote: >>> smtp2 tries to sent it to [EMAIL PROTECTED] Are you enabling selective relaying on smtp2? If so, are you setting RELAYCLIENT to "smpt2.my.domain"? -Dave
Re: delay before checking mail with outlook
Henning Brauer <[EMAIL PROTECTED]> wrote: >On Sat, Apr 07, 2001 at 11:17:04PM +, Ahmad Ridha wrote: >> Since the problem occurs so often, why aren't the -R and -H options >> made default? Perhpas it should also be included in LWQ. Is there any >> real disadvantage of using those options? > >They don't cause trouble and are useful in proper configured networks. If >you are blocking ident then you should know that. If your DNS is not working >proper you should fix that, not tcpservers options. >It should be notes in LWQ, anyway... Dave? It's on my to-do list. -Dave
Re: authorized-relay
"alexus" <[EMAIL PROTECTED]> wrote: >I went to: http://cr.yp.to/qmail/faq/servers.html#authorized-relay >and basicly did whatever they told me to >i create a file /etc/tcp.smtp >i put my ip my stuff in it >then i did >tcprules /etc/tcp.smtp.cdb /etc/tcp.smtp.tmp < /etc/tcp.smtp >no errors were displayed Thanks for sharing that. -Dave
Re: Mail cleansing program
Johan Almqvist <[EMAIL PROTECTED]> wrote: >I wonder if there is a mail cleansing program out there that is >configurable and mime-compliant. > >By mail cleansing program, I mean a program that can be instructed to only >keep the text/plain part of a multipart/alternative message [Oh, I HATE >people that send multipart/alternative messages where the text/plain >message just says "You can't display HTML mail". Oh the morons.] Take a look at demime: http://scifi.squawk.com/demime.html -Dave
Re: Selective Relaying Question
John Anderson <[EMAIL PROTECTED]> wrote: >The above is the text format, I then ran this command: > >> tcprules /etc/tcp.smtp.cdb /etc/tcp.smtp.tmp < /etc/tcp.smtp > >To make the binary. In an earlier message, John wrote: > Here is the call from my tcpserver startup script: > >(PATH=/usr/local/qmail/bin; /usr/local/bin/tcpserver >-x/usr/local/etc/ip/tcp.smtp.cdb -v -c40 -u601 -g625 0 smtp qmail-smtpd > >2>&1 | splogger smtpd & ) > >* It's all on one line in the script. So, the question is: is it /etc/tcp.smtp.cdb or /usr/local/etc/ip/tcp.smtp.cdb? -Dave
Re: Id "SV" respawning too fast: disabled for 5 minutes
"Rick Updegrove" <[EMAIL PROTECTED]> wrote:
>I am pretty sure that djb changed his instructions for daemontools
>http://cr.yp.to/daemontools/svscan.html#boot and linux somewhat recently.
Correct. It was definitely changed since LWQ was written.
>The first time I followed LWQ I overlooked the URL provided altogether.
>{oops)
No need. LWQ doesn't require you to follow the new installation
recommendations.
>Then when it didn't work I read the entire cr.yp.to site to find
>out why.
It *wasn't* because you weren't running svscan on /service, because
LWQ doesn't use /service.
>I read a lot to discover that I only needed 3 steps to make it all
>work. As I said the first time I read it there was only the method provided
>below, or at least that was all I saw and used.
>
>It is still beyond me why the simple steps were left out of LWQ:
>
>It says:
>2.7. Install daemontools:
>
>Test the build by following the directions in
>http://cr.yp.to/daemontools/install.html.
>
>Instead of this ...
>
>#1 mkdir /service
>#2 chmod 755 /service
>#3 add this to rc.local and reboot.
>env - PATH=/usr/local/bin:/usr/sbin:/usr/bin:/bin csh -cf 'svscan /service
>&'
Because LWQ *DOESN'T* *USE* */service*.
>If you do those 3 steps then you can follow LWQ. from:
Of course, scanning /service won't interfere with LWQ--it just won't
help one bit.
>2.8 Start qmail (which is misleading because you wont be starting qmail for
>a while)
The end of 2.8 actually starts qmail. But you won't be mislead if you
follow the direction to read the entire section before doing an
installation.
-Dave
RE: Never gets delivered?
"Marcus Ouimet" <[EMAIL PROTECTED]> wrote: >Here is the info requested. Thanks for taking the time read my e-mail. I >have read through Life With Qmail and all faq's over and over. Not sure what >I am missing here it is: > >Information for: /var/qmail/rc > >Tried: > >#!/bin/sh >exec env - PATH="/var/qmail/bin:$PATH" \ >qmail-start '|dot-forward .forward > ./Maildir/' The space at the beginning of the last line is a problem. >#!/bin/sh > ># Using stdout for logging ># Using control/defaultdelivery from qmail-local to deliver messages by >default > >exec env - PATH="/var/qmail/bin:$PATH" \ >qmail-start "`cat /var/qmail/control/defaultdelivery`" > >Information for: /var/qmail/control/defaultdelivery > >./Maildir/ Looks good. What Do The Logs Say? (tm) -Dave
Re: Id "SV" respawning too fast: disabled for 5 minutes [PART II]
Charles Cazabon <[EMAIL PROTECTED]> wrote: >Tom Beer <[EMAIL PROTECTED]> wrote: >> >> Stopping qmail: svscan qmail logging. >> svc: warning: unable to chdir to /var/qmail/supervise/control: not a >> directory >> svc: warning: unable to chdir to /var/qmail/supervise/ok: not a directory >> svc: warning: unable to chdir to /var/qmail/supervise/status: not a >> directory >[...] >> I did the installation according to lwq Close, perhaps, but something's not right. You shouldn't have control, ok, and status in /var/qmail/supervise. It looks like you either ran svscan in /var/qmail instead of /var/qmail/supervise, or you ran supervise on /var/qmail/supervise. I suggest you "qmail stop", clean out /var/qmail/supervise, and check your startup script before trying to restart. >No, I don't think you did. I can't recall offhand exactly how lwq says to >go about this, but in general you create a service directory (in this case >/var/qmail/supervise; I prefer /var/service/qmail myself). You then >symlink this directory into the main directory which svscan is monitoring >(typically /service). No, LWQ doesn't do the link-to-/service thing. It's on my to-do list, though. -Dave
RE: Never gets delivered?
"Bill Andersen" <[EMAIL PROTECTED]> wrote: >Excellent Reply!!! THIS is the type of reply I'd like to see >in lieu of "Read Life With Qmail". Not rude, just informative. A suggestion to read LWQ isn't rude. It'd be nice if people took the time to provide a URL to the relevent section, though. E.g.: http://www.lifewithqmail.org/lwq.html#qmail-list Is essentially a shorter version of Charles' excellent response. -Dave
Re: dot qmail problem (HELP NEEDED URGENT)
Wei Yao Gharib <[EMAIL PROTECTED]> wrote: >Return-Path: <[EMAIL PROTECTED]> >Delivered-To: [EMAIL PROTECTED] >Received: (qmail 13266 invoked by uid 511); 2 Apr 2001 >16:24:06 - >Delivered-To: [EMAIL PROTECTED] >Received: (qmail 13259 invoked by uid 511); 2 Apr 2001 >16:24:06 - Something is seriously broken. You should *NEVER* see duplicate Delivered-To header fields in a message delivered by qmail. qmail-local--which adds them--will bounce a message before adding a duplicate. -Dave
Re: Be all, end all checkpasswd
Dan Newcombe <[EMAIL PROTECTED]> wrote: >As much as I hate sendmail, after this response I may just go back to it >if this is what the qmail "community" is like. Don't judge an entire community by the actions of one individual. -Dave
Re: A real "bouncesaying"
"Filip Salomonsson" <[EMAIL PROTECTED]> wrote:
>A message is recieved for [EMAIL PROTECTED], delivered locally to
>salo-filip, which puts the message in my maildir and forwards a copy to
>[EMAIL PROTECTED] The envelope sender for the forwarded message is set to
>[EMAIL PROTECTED], just as the docs say ("local" is salo-filip).
>But it makes no sense. If the delivery fails, the bounce message will be
>sent to [EMAIL PROTECTED], and the delivery instructions will be
>sought for in ~salo/.qmail-salo-filip-owner, which doesn't exist. Good job.
>The -owner files render themselves completely useless.
So create ~salo/.qmail-salo-filip-owner or ~salo/.qmail-salo-default.
>Also, any message sent to [EMAIL PROTECTED] will have "Delivered-To:
>[EMAIL PROTECTED]" in the header, which is confusing.
To whom? Delivered-To fields are there for loop detection, if users
look at them, they should understand how they work.
>In short -- qmail handles deliveries to virtual domains/users exactly the
>way the docs say (as far as I can tell). But what the docs say is just plain
>stupid.
You're certainly entitled to your opinion, but calling the current,
documented behavior incorrect is misleading.
-Dave
Re: qmail forwarding to another mailserver
"VmTesting" <[EMAIL PROTECTED]> wrote: >Does someone has any idea how to forward with qmail all the e-mail's >received by one mailserver to another mailserver ? Actually I want to >forward only thouse users e-mails to another server which has no >mailbox in the first server. In ~alias/.qmail-default on "one server": |/var/qmail/bin/forward "$LOCAL"@another.server -Dave
Re: faster than bcc
Charles Cazabon <[EMAIL PROTECTED]> wrote: >Dave Sill <[EMAIL PROTECTED]> wrote: > >> >cat list.txt | xargs qmail-inject -a > >where list.txt is a list of addresses. Is this faster than bcc >> >anyway? > >> No. That creates one message per recipient--lots of disk I/O to do the >> same thing as one message, many recipients. > >That should still do only one message, multiple recipients, shouldn't it? Yeah, don't know what I was thinking. But I see another problem with that command: it's feeding the list of recipients to xargs via stdin and the message to qmail-inject, also via stdin. In my testing, xargs is reading the message as stdin and calling qmail-inject with the message contents on the command line. Oops. -Dave
Re: faster than bcc
"Brett" <[EMAIL PROTECTED]> wrote: >I remember reading that the fastest way to send one email to a large number >of people is through bcc. This was helpful to me because I'm not able to use >a mailing list since the addresses I send to will be pulled dynamically from >a database which is always changing. But somehow, populating the bcc field >with a million names seems like it might not be the best idea to me. I >understand qmail deletes this field before sending the message out but I'm >more concerned with whether or not it will be making efficient use of the >queue. Yes, that's efficient. >Is the queue even used for one message sent to numerous people or is >it only used for separate messages? All messages sent using qmail queued. >If there's a better method than bcc-ing >everyone, I'm very open to hearing it. One suggestion I got but which I >can't get to work is: >cat list.txt | xargs qmail-inject -a where list.txt is a list of addresses. Is this faster than bcc >anyway? No. That creates one message per recipient--lots of disk I/O to do the same thing as one message, many recipients. -Dave
Re: tcpserver
Mustafa Mahudhawala <[EMAIL PROTECTED]> wrote: >Has anybody used tcpserver for Qmail & other services out there -- Of course. >I am using FreeBSD 4.2 and want to start my basic services like telnetd, >ftpd along with smtp & pop3 etc using tcpserver (and tcpserver.conf) >instead of plain tcpserver or inetd (and inetd.conf). Scrap telnet for ssh. Scrap ftpd for ssh (authenticated) and/or publicfile (anonymous). What's tcpserver.conf? >I have succesfully installed tcpserver, daemontools & tcpserver-control >(latest versions) What's tcpserver-control? >But I am pretty confused about the whole lot and their ineraction. >i.e. tcpserver - daemontools - tcpserver-control. tcpserver listens to a specified port, accepts connections on that port, and forks a daemon to handle the connection. daemontools provides a set of utilities for controlling daemons (services)--starting them, stopping them, signalling them, logging their output, etc. tcpserver-control I've never heard of. >also /services & tcpserver.conf (why both) Beats me. -Dave
Re: Symbolic link to datemail?
Ian Lance Taylor <[EMAIL PROTECTED]> wrote: >"Matt Simonsen" <[EMAIL PROTECTED]> writes: > >> Are you sure? Is this wrong? >> http://www.faqts.com/knowledge_base/view.phtml/aid/1167/fid/208 > >Looks wrong to me. datemail is a trivial shell script which invokes >sendmail. sendmail and qmail-inject take different options. It does >not make sense to simply replace qmail-inject with datemail. It makes >more sense to replace sendmail with datemail. Bingo. I'll fix the FAQTS entry. -Dave
Re: non local users
"Dean Mumby" <[EMAIL PROTECTED]> wrote: >is it possible to have nonlocal user mail forwarded to my isp mail server we >have two offices each with dialup access and share a domain A specific example of what you want to do would be helpful. What you want do to is almost certainly doable, but how it'd be done depends upon what you want it to do. -Dave
Re: qmail queue
"Sumith" <[EMAIL PROTECTED]> wrote: >How can I know how many concurrent qmail deliveries are taking place >on my qmail server, both qmail-local and qmail-remote Look at your qmail-send logs. You should see something like: @40003abb67f02a8b74e4 status: local 0/60 remote 14/500 where concurrencylocal is 60 and concurrencyremote is 500. -Dave
RE: New to Qmail, probably a stupid question...
"Tyrone Mills" <[EMAIL PROTECTED]> wrote: >You're right, I should have included the logs, but the machine couldn't >E-Mail... I was about to ftp them over when I realized the problem. I had a >bad hostname for the machine, as soon as I fixed it, it's happily sending >mail to the Internet. Mail may be flowing, but if you're seeing log entries that contain "sendmail", you're not using qmail. qmail's sendmail command does no logging. -Dave
Re: me contents
Flash <[EMAIL PROTECTED]> wrote: >/var/qmail/control/me currently contains 'ns1.flashsys.com' which was >picked up by the config script at compile time. > >For appearances sake in the headers I would like 'me' to contain >'mail.flashsys.com' instead. Will I break anything if I edit the file? Look at: http://www.lifewithqmail.org/lwq.html#config-files And verify that the variables that default to "me" are OK to change to mail.flashsys.com. If not, just set those variables to what they should contain. -Dave
RE: VERP problems
"Brett" <[EMAIL PROTECTED]> wrote: >Dave Sill wrote: >>No, you're not messing anything up. There are two kinds of bounces: >>those generated remotely and those generated locally. If the local >>system is not able to pass a message off to a remote system, the >>bounce generated will be local--from your qmail--and it'll go to the >>"me-" address rather than the me-user%host VERP address. This is >>done this way because the local bounce can contain multiple >>undeliverable addresses. To process these bounces, you need to parse >>the QSMBF-format bounce message that qmail generates. > >>From this, I gather that in order to collect the email addresses of these >bounces, I need to write a script that goes through the me mailbox and >extracts the email addresses from the bounce messages. You could do that, but it'd be better to write a script that processes each message upon receipt. >I can do this (though >it seems like there must be a better way). But when does the VERP >functionality present itself? I send a message to [EMAIL PROTECTED] >and that server tells me 'beets is unknown' -- isn't that a remote bounce? If your qmail talks to the MTA at someotherdomain.com, and someotherdomain.com refuses to accept the message for beets, then your qmail will generate the bounce. If your qmail talks to the MTA at someotherdomain.com, and someotherdomain.com accepts the message but is unable to deliver it to beets, then someotherdomain.com will generate the bounce, and it'll go to the VERP address. >Shouldn't the email be returned to >[EMAIL PROTECTED]? No, because, as I explained, qmail bundles the locally-generated bounces into one message. >Because it isn't; I'm still >getting those sent to [EMAIL PROTECTED] Or is this still considered a local >bounce? Locally-*generated*, not local. >If this is a local bounce then how do I simulate a remote bounce? Well, the easiest way to do that is to send a message directly to a VERP return address. Alternatively, if you've got another qmail box, just send a message to nosuchuser@otherqmailbox. -Dave
RE: VERP problems
"Brett" <[EMAIL PROTECTED]> wrote: >Okay, but the bounce sent to [EMAIL PROTECTED] also gets bounced. It doesn't >know to send 'me-*' eamil through to 'me' even though I've touched >~/.qmail-me-owner and ~/.qmail-me-owner-default and chmodded both to 777. Try touching .qmail-default. Neither ~/.qmail-me-owner noed ~/.qmail-me-owner-default will match "me-". -Dave
Re: same VERP problem
"Brett" <[EMAIL PROTECTED]> wrote: >I'm still having the same annoying problem with the VERP implementation. How >do I get it running on my home email address? That is, all emails I send out >from [EMAIL PROTECTED], if bounced, I want sent back to >[EMAIL PROTECTED] Thanks. Did you read my reply? -Dave
Re: LWQ and POP3
"Neafevoc K. Marindale" <[EMAIL PROTECTED]> wrote: >I just setup qmail using Life with qmail, and everything seems to be >working just fine. But I wanted to use POP3 with it, and somehow trying to >add pop3d to tcpserver just isn't working. > >I'm still sort of new to he *nix world. Btw, I'm using FreeBSD 4.2, if it >matters. Anyway, this is what script looks like in >/var/qmail/supervise/qmail-smtpd/run > >#!/bin/sh >exec /usr/local/bin/tcpserver -v -R 0 pop3 /var/qmail/bin/qmail-popup FQDN \ > /usr/local/bin/checkpassword /var/qmail/bin/qmail-pop3d Maildir 2>&1 > >QMAILDUID=`id -u qmaild` >NOFILESGID=`id -g qmaild` >MAXSMTPD=`cat /var/qmail/control/concurrencyincoming` >exec /usr/local/bin/softlimit -m 200 \ > /usr/local/bin/tcpserver -v -p -x /etc/tcp.smtp.cdb -c "$MAXSMTPD" \ > -u "$QMAILDUID" -g "$NOFILESGID" 0 smtp /var/qmail/bin/qmail-smtpd >2>&1 > >--- >And yeah, I did put my fully qualified domain name in FQDN :) Good. You can't combine two services in one run script. You need to set up a separate service for qmail-pop3. See: http://www.faqts.com/knowledge_base/view.phtml/aid/8225/fid/223 For instructions on setting up qmail-pop3d the LWQ way. -Dave
Re: VERP problems
"Brett" <[EMAIL PROTECTED]> wrote: >I'm trying to implement VERP for my own user address, that is, an address >that's not a mailing list. > >I found a VERP page (quoted below) and according to that I should touch >~/.qmail-me-owner and ~/.qmail-me-owner-default. Then if I set the >QMAILINJECT environment variable to 'r', I'm ready to go. I call: > >echo to:[EMAIL PROTECTED] | /var/qmail/bin/qmail-inject > >and I check the log. The mail is sent to [EMAIL PROTECTED] not >[EMAIL PROTECTED] as I was lead to believe would occur >automatically. Then when it bounces, it goes to [EMAIL PROTECTED] You see, it >adds that "-" after "me" like it's trying to do the VERP address but then >doesn't add the noone info. I know I'm messing up a step (perhaps several) >but I don't know where. Anyone? I'm humbled by all your linux/qmail/computer >stuff in general knowledge. Thanks again. No, you're not messing anything up. There are two kinds of bounces: those generated remotely and those generated locally. If the local system is not able to pass a message off to a remote system, the bounce generated will be local--from your qmail--and it'll go to the "me-" address rather than the me-user%host VERP address. This is done this way because the local bounce can contain multiple undeliverable addresses. To process these bounces, you need to parse the QSMBF-format bounce message that qmail generates. -Dave
Re: qmail install troubles
Ruprecht Helms <[EMAIL PROTECTED]> wrote: >possible the things will be logged in /var/log mail. I think this is the >default. The entry in syslog can malfunction. He said he's following the HOWTO, which logs to /var/log/qmail using multilog. >>Then I stumbled across the fact that I needed .qmail files in the home >>directories of users that intended to get mail, so I added those. No, you don't need .qmail unless you want to override the system default delivery method. >I think thats wrong. The .qmail-files have to be placed under >/var/qmail/alias. The must be named like .qmail-user for example No, these are real users, not aliases. >>*) I started qmail with qmail-start after shutting down svscan. (I tried to >>start svscan after that, > >The qmailscanner have a bug. This has nothing whatsoever to do with qmail-scanner. -Dave
Re: Trouble with qmail on Redhat 6.2
"Iain Morrison" <[EMAIL PROTECTED]> wrote:
>The run file for qmail-smtpd is:
>
>#!/bin/sh
>QMAILDUID='is -u qmaild'
>NOFILESGID='id -g qmaild'
>MAXSMTPD='cat /var/qmail/control/concurrencyincoming'
Should be back quotes (`) not single quotes (').
-Dave
Re: MAIL FROM: <#@[]>
"Jamin A. Brown" <[EMAIL PROTECTED]> wrote: >I'm noticing a fair amount of spam coming into our system where the >sending server is using MAIL FROM: <#@[]>. Really? Where's it coming from? Sure you're not seeing this in double bounces? -Dave
Re: Log's.
<[EMAIL PROTECTED]> wrote: > Is there a way to get qmail to produce more readable logs somewhat similar >to sendmail's logs? Use matchup from qmailanalog: http://www.lifewithqmail.org/lwq.html#qmailanalog -Dave
Re: qmail logs?
Sumith <[EMAIL PROTECTED]> wrote: >I need to scan my qmail log files for generating an html report. Since >this rpms use multilog, I am using isoqlog for getting my job done. But >the Install files says that you need to feed this in qmail-send log >directory. There is no qmail-send in /var/service. there is only >qmail/log, qmail-smtpd/log and qmail-pop3d/log. qmail/log is the one you want. -Dave
