Re: Selective Relaying Question
On Wed, Apr 04, 2001 at 11:17:25AM -0400, John Anderson wrote: Here is what I used to make the tcp.smtp.cdb file: 192.168.:allow 192.168.:allow,RELAYCLIENT="" :allow The above is the text format, I then ran this command: tcprules /etc/tcp.smtp.cdb /etc/tcp.smtp.tmp /etc/tcp.smtp It's interesting that you run this command on files in /etc but your startup script tells tcpserver that the .cdb file is in /usr/local/etc/ip .
Re: Symbolic link to datemail?
On Mon, Mar 26, 2001 at 10:54:20AM -0800, Matt Simonsen wrote: Unfortunately, there is no MUA since qmail-inject is being called from various scripts. Here's the output you requested, Charles. [root@wrapguy bin]# ls -l | grep qmail-inject lrwxrwxrwx1 root qmail 8 Mar 26 10:48 qmail-inject - datemail -rwxr-xr-x1 root qmail 34748 Mar 19 10:44 qmail-inject.orig You are lucky that qmail's sendmail wrapper takes different arguments than qmail-inject. Otherwise you'd be in an endless loop. datemail calls, through a symlink, /var/qmail/bin/sendmail. /var/qmail/bin/sendmail calls qmail-inject. You've set up qmail-inject to be a link to datemail. Oops. You're getting your error because, after /var/qmail/bin/sendmail has parsed sendmail's arguments it calls qmail-inject with arguments translated appropriately. One of those is -H. What ends up happening is, because of the above-mentioned loop, /var/qmail/bin/sendmail gets called again but this time with arguments for qmail-inject. Since they don't make sense, /var/qmail/bin/sendmail errors out. This is just a diagnosis. People have already suggested solutions for you. Tim
Re: How to use passwd.cdb in a PERL Script
On Sat, Mar 24, 2001 at 02:10:40AM +0100, Philipp Homan wrote: Hi, My question is rather simple: How do I use a passwd.cdb file in a perl script? I'd like to open it with tie and check usernames/passwds in the script. Any ideas? There's a Perl module available from CPAN called CDB_File that does what you're looking for. Tim
Re: Supervise logging - RH 6.2
On Wed, Mar 21, 2001 at 03:22:32PM -, Iain Morrison wrote: The logging for Qmail is set to use multilog for both qmail-smtp and the qmail-send programs. Only trouble is that supervise is not able to start them for some reason so all logging goes to the console. [snip...] Any ideas??? Try this: $ ls -ld /var/qmail/supervise/* drwxr-xr-t 4 root qmail 512 Mar 19 16:32 /var/qmail/supervise/qmail-send drwxr-xr-t 4 root qmail 512 Mar 19 16:40 /var/qmail/supervise/qmail-smtpd The 't' in 'drwxr-xr-xt' means that the directory has the sticky bit set. Check yours. If it doesn't have that bit set, set it with: # chmod +t /var/qmail/supervise/* That will cause svscan to execute the 'run' script in qmail-send/log and qmail-smtpd/log. I'm not sure if that is enough to connect your logging output to the multilog input, so if the logging continues to show up on the console: # svc -dx /service/qmail-* Tim
Re: tcpserver rblsmtpd
On Wed, Mar 21, 2001 at 02:44:33PM -0800, Brad Dameron wrote: Anyone have a good example of using the tcpserver rblsmtpd with qmail? /usr/local/bin/tcpserver -x/var/qmail/tcp.smtp.cdb -R -v -u82 -g81 0 smtp \ /usr/local/bin/rblsmtpd -r 'relays.mail-abuse.org:Open relay problem - see URL:http://www.mail-abuse.org/cgi-bin/nph-rss?query=%IP%' \ -r dialups.mail-abuse.org -r blackholes.mail-abuse.org \ /var/qmail/bin/qmail-smtpd 21 | /var/qmail/bin/splogger smtpd 2 Please let me know what the best way to use the rblsmtpd program is. Get the patch to use A records from www.qmail.org. It's called ucspi-rss.diff . Apply it and rebuild ucspi-tcp. Use the above command line (or something similar). Note that, for the relays.mail-abuse.org list (also known as the RSS), you *must* follow the host name with a colon and a text string, as above. The %IP% is replaced by the IP address of the listed host. Thank you. You're welcome. Hope that's helpful. Tim
Re: Qmail not writing to syslog
On Sat, Mar 17, 2001 at 12:08:25PM -0500, Chris Johnson wrote: On Sat, Mar 17, 2001 at 11:57:56AM -0500, Todd Goldenbaum wrote: I'm trying to get qmail running under redhat 7. I installed qmail via the 'life with qmail' page and it appears to be running fine. However, in attempting some of the tests in 'TEST.deliver', I noticed that there is nothing about qmail being written to /var/log/syslog. If you set things up like "Life with qmail" tells you, then you don't use syslog to log. Quite true. Look in /var/qmail/supervise/qmail-send/log/main for logs, which will have been put there by multilog. Actually, an LWQ install has the logs in /var/log/qmail and /var/log/qmail/smtpd. Tim
Re: Why does POP3 log inetd ... exit status 1
On Fri, Mar 16, 2001 at 10:51:59PM +0100, Milivoj Ivkovic wrote: Thank you for the replies. Why are you running with inetd anyway? [...] I would make the switch to tcpserver (check out www.lifewithqmail.org for It is Life with Qmail which I used for help in my setup. It says: "Typically, qmail-popup is run via inetd or tcpserver" "For a busier service, use tcpserver instead." So using inetd seems right in my case. tcpserver works better than inetd for not-so-busy cases, too :) In case that matters, I'm not using qmail for smtp (but postfix), only qmail-popup for pop3. !!! Does Postfix deliver to maildirs or Unix mailboxes? If not to maildirs, then qmail's pop3 service can't possibly work. That might explain your exit 1. Well, what else can I say? I wouldn't have thought my problem to be so esoteric. On the contrary, people subscribed to this list and running Postfix are an extremely rare breed! Tim
Re: system-aliases not found
On Thu, Mar 15, 2001 at 11:54:23PM -0800, Eric Pretorious wrote: From: Ahmad Ridha [EMAIL PROTECTED] Subject: Re: system-aliases not found Date: Fri, 16 Mar 2001 14:28:49 +0700 1) Is 'eric' an existing username? 2) Is 'eric' able to receive e-mails addressed to him directly ([EMAIL PROTECTED])? Does he have the proper mailbox as mentioned in his .qmail file (or the default delivery one)? Ahmad: Yes - 'eric' is an existing username. Yes - 'eric' is able to receive mail sent to 'eric', 'eric@charlie', '[EMAIL PROTECTED]', '[EMAIL PROTECTED]' in the Mailbox in /home/eric. Can you show us the contents of these files: /var/qmail/control/me .../defaulthost .../defaultdomain Tim
Re: Redirect email!
On Sun, Mar 11, 2001 at 04:13:04PM -0500, Kirti S. Bajwa wrote: Having explained it, I don't believe, "LWQ" or any other write-up discusses this type of problem, if it does can you point the section where this type of situation is covered in "LWQ". That's correct. You need help for whichever mail software is installed on ns1.mydomain.com. Most likely sendmail is installed by default. Again, my question is; how email messages generated on ns1.mydomain.com can be sent to ns2.mydomain, which has qmail on it and ns1.mydomain.com is listed in /var/qmail/control/local? I'm not a sendmail guy - perhaps someone on the list can help. You could also try man sendmail or try to dig up some other sendmail docs. Tim
Re: POP3 is driving me crazy!!!
On Wed, Mar 07, 2001 at 06:18:33PM -0500, Kirti S. Bajwa wrote: For the last two days I have done nothing else but to setup "pop3" to run under qmail. I installed qmail by following "qmail-HOWTO" (http://www.flunder.net/qmail/qmail-howto.html) procedure. "svscan" is starting qmail from "/service" directory. I have two directories "/var/qmail/supervise/qmail-send" "/var/qmail/supervise/qmail-smtpd" which has "run" scripts to start each of these service (as outlined in "qmail-HOWTO"). My question is "where" to add the script to start pop3. For the last two Your first try, below, looks pretty good. But... did you remember to ln -s /var/qmail/supervise/qmail-pop3 /service/ You have to make a link in the /service directory for svscan to notice it. [snip...] First Try: === I added a new directory as follows: /var/qmail/supervise/qmail-send (existing directory) /var/qmail/supervise/qmail-smtpd(existing directory) /var/qmail/supervise/qmail-pop3 (new directory) In the new directory I added a "run" script with the following to start pop3: #!/bin/sh exec /usr/local/bin/tcpserver -v -R 0 pop3 /var/qmail/bin/qmail-popup mail.tibonline.net \ /bin/checkpassword /var/qmail/bin/qmail-pop3d Maildir 21 | \ /var/qmail/bin/splogger pop3d Tim
Re: Simple Question???
On Wed, Mar 07, 2001 at 09:13:24PM -0500, Kirti S. Bajwa wrote: [snip] I am having problem connecting to qmail. Each time I try to make a connection from MS Outlook, I get a response that the connection is refused because of an invalid userid or password. How did you install qmail? Did you follow Life With Qmail? Did you patch it? And when you say that you have trouble connecting, do you mean when you try to *send* mail or when you try to *retrieve* mail? Also do I need to install "qmail" on both computers? No. Thanks. Kirti Tim
Re: virtual domain procmail
On Sat, Mar 03, 2001 at 11:07:42AM +0700, Agi Subagio wrote: Agi Subagio [EMAIL PROTECTED] wrote: If i run TEST.deliver and deliver locally to any users at domain 'testing.com', still i have the same unsucessful result like this : [root@mail agi]# echo to : [EMAIL PROTECTED] | /var/qmail/bin/qmail-inject new msg 216 info msg 216: bytes 210 from [EMAIL PROTECTED] qp 1570 uid 0 starting delivery 17: msg 216 to local [EMAIL PROTECTED] Remove testing.com and mail.testing.com from /var/qmail/control/locals. Tim
Re: Problem with rss?
On Fri, Mar 02, 2001 at 10:54:56PM -0800, Todd A. Jacobs wrote: I'm running the following script as /var/qmail/supervise/qmail-smtpd/run. As you can see, rblsmtpd is setup to query all three mail-abuse.org services. However, when testing using [EMAIL PROTECTED], the RSS lookup is apparently failing. Has anyone else had a similar problem, or have some ideas about how I can debug this further? #!/bin/sh # This is /var/qmail/supervise/qmail-smtpd/run 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 /usr/local/bin/rblsmtpd \ /usr/local/bin/rblsmtpd -rdialups.mail-abuse.org \ /usr/local/bin/rblsmtpd -rrelays.mail-abuse.org \ /var/qmail/bin/qmail-smtpd 21 Well, first, you could try simplifying it a bit 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 /usr/local/bin/rblsmtpd \ -rdialups.mail-abuse.org -rrelays.mail-abuse.org -rblackholes.mail-abuse.org \ /var/qmail/bin/qmail-smtpd 21 You don't need three invocations of rblsmtpd. Next, you need to get a patch for rblsmtpd. MAPS removed all the TXT records in the RSS zone and now only replies to A record queries. rblsmtpd only understands TXT records. See the second bullet at http://www.qmail.org/top.html#spam Tim
Re: thoughts for future qmail
On Tue, Jan 02, 2001 at 10:12:43PM -0500, Russell Nelson wrote: David Benfell writes: In theory, I have QMTP up on parts-unknown.org. I had already Also in theory, so do I. Russ, please add catseye.net to your list. Don't worry about that. I'll send a confirmation message to all 20+ people who told me about their qmtp servers, once I've gotten the code working. If you get the message "with QMTP", then you know your qmtpd server is working. Looking forward to this :) -thl
Re: Arg! relay problems
On Wed, Dec 20, 2000 at 05:28:52PM -0500, [EMAIL PROTECTED] wrote: I'm having one heck of a time getting qmail-smtpd to allow mu users to send mail. my /etc/tcp.smtp file looks as such. 127.0.0.1:allow,RELAYCLIENT="" 216.177.2.:allow,RELAYCLIENT="" :allow then after saving that i run tcprules tcp.smtp.cdb tcp.smtp.temp tcp.smtp and that goes through ok when i run tcprulescheck /etc/tcp.smtp.cdb i get this. rule : allow connection Try tcprulescheck /etc/tcp.smtp.cdb 216.177.2.1 -- 1 can be any valid IP address on your site. man tcprulescheck for more information. what givesthen i connect to usaexpress.net:25 i get dropped . any ideas? ~kurth -thl
Re: a little more insight!
On Wed, Dec 20, 2000 at 06:07:16PM -0500, [EMAIL PROTECTED] wrote:
diggin thru my logs i find this in /var/log/qmail/smtpd
977352942.017873 tcpserver: ok 4501 usa.usaexpress.net:206.183.143.244:25
zmamail02.zma.compaq.com:161.114.64.102::2564
977352942.017928 tcpserver: warning: dropping connection, unable to run
/var/qmail/bin/qmail-smtpd-wrapper: exec format error
977352942.018301 tcpserver: end 4501 status 28416
977352942.018400 tcpserver: status: 23/40
the contents of qmail-smtpd-wrapper is as follows.
Is this a cut-n-paste or did you type it into your mail message by hand?
If this is really what the script looks like, try adding a "!" after the
"#", as indicated.
usa:/var/qmail/bin# cat qmail-smtpd-wrapper
#/bin/bash
^- add ! here, so it looks like this:
#!/bin/bash
ulimit -d 1024
exec /var/qmail/bin/qmail-smtpd ${1+"$@"}
usa:/var/qmail/bin#
i have a feeling that it may be caused by this line in my
/etc/init.d/qmail file
supervise /var/supervise/qmail/smtpd tcpserver -v
-x/etc/tcp.smtp.cdb -u$QMAILDUID -g$NOFILESGID
0 smtp /var/qmail-smtpd-wrapper 21
| setuser qmaill accustamp | setuser qmaill cyclog /var/log/qmail/smtpd
the above is all on one line.
i'm at wits end with this..can anyone help me out?
~kurth
-thl
Re: seeking rblsmtpd -r option clarification
On Sat, Dec 16, 2000 at 06:26:45PM -0500, Chris Hardie wrote:
Greetings. I'm seeking clarification on use of the "-r" option of
rblsmtpd, described here:
http://cr.yp.to/ucspi-tcp/rblsmtpd.html
The issue at hand is whether or not you can specify multiple blackhole
lists with one call, or if you have to chain calls to rblsmtpd.
You can, at least with the latest rblsmtpd. You don't mention which
version of ucspi-tcp you're using... The latest is 0.88. The page you
reference above is for the rblsmtpd in the 0.88 distribution.
I've had some reports that you can use multiple -r's, e.g.
rblsmtpd -rrelays.orbs.org -rrbl.maps.vix.com
This is, in fact, the correct syntax.
However, user Mike Silbersack had a different experience and did some
further research into the issue and sent me this:
[snip partial main() listing...]
I think this would indicate that repeating use of -r wouldn't work as
expected.
The code you showed only allows one -r switch. However, that is not the
code from ucspi-tcp 0.88. The following is the relevant piece of main()
from 0.88:
main(int argc,char **argv,char **envp)
{
int flagwantdefaultrbl = 1;
char *x;
int opt;
ip_init();
x = env_get("RBLSMTPD");
if (x) {
if (!*x)
decision = 1;
else if (*x == '-') {
if (!stralloc_copys(text,x + 1)) nomem();
decision = 3;
}
else {
if (!stralloc_copys(text,x)) nomem();
decision = 2;
}
}
while ((opt = getopt(argc,argv,"bBcCt:r:a:")) != opteof)
switch(opt) {
case 'b': flagrblbounce = 1; break;
case 'B': flagrblbounce = 0; break;
case 'c': flagfailclosed = 1; break;
case 'C': flagfailclosed = 0; break;
case 't': scan_ulong(optarg,timeout); break;
case 'r': rbl(optarg); flagwantdefaultrbl = 0; break;
case 'a': antirbl(optarg); break;
default: usage();
}
argv += optind;
if (!*argv) usage();
if (flagwantdefaultrbl) rbl("rbl.maps.vix.com");
if (decision = 2) rblsmtpd();
...
}
Can anyone clarify what's really supposed to happen, what really
does happen, and what it all means in a larger existential context?
Hopefully I've addressed the first two questions, anyhow :)
Thanks,
Chris
-thl
Re: IPCHAINS and Qmail
On Sun, Dec 10, 2000 at 01:31:54AM -0700, Sean Reifschneider wrote: On Sun, Dec 10, 2000 at 02:51:24AM -0500, Steve Manes wrote: Dec 10 01:02:49 meg kernel: Packet log: output REJECT eth0 PROTO=6 166.84.147. 124:3687 206.26.89.202:25 L=1064 S=0x00 I=46413 F=0x T=64 (#37) Dec 10 01:02:55 meg kernel: Packet log: output REJECT eth0 PROTO=6 166.84.147. 124:4396 204.242.84.1:25 L=60 S=0x00 I=46421 F=0x T=64 SYN (#37) Any idea what's causing this? ipchains is blocking incoming connections to port 25/tcp. You know, the e-mail port. Er, it looks like exactly the opposite. ipchains is blocking _outgoing_ connections _to_ port 25 on other machines. Steve's IP is 166.84.147.124. I don't use ipchains and don't know how to fix this. Hopefully someone can tell you how to open up the ports qmail needs for output. -thl
Re: Procmail weirdness
On Thu, Dec 07, 2000 at 11:25:39PM -0200, Francisco Jen Ou wrote: The weirdness is just this: procmail says recipies OK (forwarded to [EMAIL PROTECTED]), but qmail-local delivers a copy to original recipient. How are you calling procmail? In a .qmail file? From the qmail-start command line? Please show us the whole file. -thl
Re: long timeout after connecting
On Sun, Nov 26, 2000 at 11:56:32PM +0100, megadesign wrote: hello all, can anybody help me with my problem please ? (on the begining, sorry for my very bad english...) No problem! You've explained your problem better than many native English speakers on this list. i have one machine 'ikarus.visimpex.cz' on my local network (without dns), where qmail-pop3d and qmail-smtpd is running (all via tcpserver). i tried to connect to account 'user' from other machine (same network) with windows os and outlook_express mail client (pop3 and smtp server=ikarus.visimpex.cz). connecting to ikarus for new mails is ok, but before new messages are received (or sended) there is too long timeout. outl_express display message like "connected, but server has no reaction after 60sec. wait or cancel ?". after click on 'wait' is another long timeout (40+ sec), but client receive and send all messages in the end. ping between this machines is ok (10s). why there is so big timeout ? As others have indicated, you will want to use the -R and -H flags on the tcpserver command line. If your machine cannot find it's own name through a DNS lookup, you will also want to add -l0 to tcpserver's command line. That's a lowercase 'L' and the digit 0. man tcpserver for more information on all three of those flags. thank you. You're welcome - I hope this helps. mega -thl
Re: qmail won't deliver emails?
On Tue, Nov 21, 2000 at 03:54:26PM -0500, Collin B. McClendon wrote: Hello all, I'm puzzled by this error, it looks like my syntax is correct and qmail sends mail just fine. I have a proper hostname etc. I'm trying to deliver to a host called listserv.investorlinks.com. I have an mx record for the domain that points to a different host, I'm just trying to delivery mail directly to this host. I just changed the reverse DNS from q.investorlinks.com to listserv.investorlinks.com, any ideas? Here is the error: I'm thinking somehow qmail-local is being called incorrectly, but I can't be sure. I've set up Mailbox as a link to mbox... -Collin Hi. This is the qmail-send program at listserv.investorlinks.com. I'm afraid I wasn't able to deliver your message to the following addresses. This is a permanent error; I've given up. Sorry it didn't work out. [EMAIL PROTECTED]: qmail-local: usage: qmail-local [ -nN ] user homedir local dash ext domain sender aliasempty Qmail doesn't deliver to root. Perhaps you're missing a ~alias/.qmail-root file that forwards root's mail to somewhere useful, like the system administrator (which might be you!). These days there are too many setups to shake a stick at, but the alias user's home directory is usually /var/qmail/alias. Read the INSTALL.alias file in the qmail source distribution for more details. -thl
Re: Information
On Wed, Nov 15, 2000 at 11:33:22AM -0200, Cleiton Luiz Siqueira wrote: Hi all, I just started using qmail 1.03 a week ago too, I have had some Welcome! problems with it, and I've not found in the FAQ the solutions for these problems. [snip authentication stuff...] My problems are with SMTP. I installed the "qmail-1_03.tgz" package in a FreeBSD 3.4 Box. When I send a message for a local user, this message doesn't get in the mailbox. And the qmail-send answer me that the mailbox doesn't exist, but the mailbox exist, and it is with the right permissions. I use qmail with maildir option. Ok. The domain is in the locals, me and rcpthosts files. I've started pop3 and smtp in the inetd.conf file with the follow lines: pop3 stream tcp nowait root /var/qmail/bin/qmail-popup qmail-popup ab.com.br /bin/checkpassword /var/qmail/bin/qmail-pop3d Maildir smtp stream tcp nowait qmaild /var/qmail/bin/tcp-env tcp-env /var/qmail/bin/qmail-smtpd Ok, although tcpserver is recommended these days rather than inetd. I've run qmail on FreeBSD 3.3, 3.4, 3.5 and 4.x with tcpserver and I prefer that configuration. I use the shell script in the /usr/local/etc/rc.d/qmaild.sh with the follow lines: #!/bin/sh # Using splogger to send the log through syslog. # Using qmail-local to deliver messages to ~/Mailbox by default. exec env - PATH="/var/qmail/bin:$PATH" \ qmail-start ./Maildir splogger qmail ^ The first argument to qmail-start tells qmail how to deliver local mail. In your case, you've said to deliver it to a mbox-style mailbox called Maildir in the user's home directory, *not* a maildir. If you add a trailing slash, like this: ./Maildir/, you are saying to deliver to a maildir-style directory named Maildir in the users home directory. If your users have .qmail files in their home directories, they can specify different delivery instructions. Otherwise, the default delivery instruction from the qmail-start command-line is followed. If there is no mbox file named $HOME/Maildir, then qmail is correct - the mailbox doesn't exist. Add the slash at the end and see if that works better. Another thing is when I send a message from the local network to other domains, it answers me that these domains aren't in the rcpthosts files, but it's is very strange!!! You need to enable selective relaying. See http://web.infoave.net/~dsill/lwq.html#relaying for information on how to configure this. Can you imagine if I put in the rcpthosts files whole the domains that exist in the Internet networking? The rcpthosts file should contain only domains that you want to receive mail *for*. NOT domains you want to send mail *to*. Again, to allow other machines to use your qmail installation to send mail, you must enable relaying for those machines. See above. I understood that the rcpthosts file is to avoid spam from the other networks, and not to filter the destination addresses. If you could help me about it I would thank. Regards Cleiton. -thl
Re: perl script acting funny
On Sun, Nov 12, 2000 at 12:55:08PM -0500, Peter Green wrote: also sprach fabrice: /usr/lib/sendmail -t -f [EMAIL PROTECTED] You might as well add this header line: print MAIL "Return-Path: ...\n"; You can, though it won't do anything. It will be overwritten by the sendmail I think what Fabrice is saying is that specifying the Return-Path header is an alternative to using the -f switch on the sendmail/qmail-inject command line. If you provide the Return-Path header to qmail-inject, it will use the address(es) specified there as the envelope sender, which is not quite the same as not doing anything. :) program with either [EMAIL PROTECTED] (the literal user and machine name where the mail is originating) or the argument to the ``-f'' flag as specified above. Does the sendmail wrapper ignore Return-Path and instead use [EMAIL PROTECTED]? Certainly qmail-inject doesn't, but I haven't experimented with /var/qmail/bin/sendmail to check The man page for qmail-inject(8) (which is what the sendmail wrapper really calls) says that ``Return-Path is deleted in any case''. This is true, but only *after* processing it and using it to set the envelope sender. man qmail-header and see the SENDER ADDRESSES section. Also, note that the -f option will override this behavior, as will having an 's' in the QMAILINJECT environment, etc., etc. /pg -thl
Re: Setup Problem Life With Qmail
On Sat, Nov 11, 2000 at 12:36:47AM -0600, Jeff Lacy wrote: Hello everyone, I am new to qmail, so please forgive my ignorance. I tried to install qmail using life with qmail under RH7. When I run /etc/rd.d/init.d/qmail, it seems to start okay. Every 10 seconds something accesses the disk. I think it is multilog. I probably have a little typo in one of the /var/qmail/supervise run files. I looked, but I can't see it. Could someone please help me? Pleae reply to my email address, [EMAIL PROTECTED] Thanks. /var/log/qmail/current looks like: (I removed a zillion lines like these, though) @40003a0cdf972be071dc alert: cannot start: unable to read controls @40003a0cdf9736ead48c alert: cannot start: unable to read controls @40003a0cdf98063ce6a4 alert: cannot start: unable to read controls @40003a0cdf981131061c alert: cannot start: unable to read controls @40003a0cdf981c2ebab4 alert: cannot start: unable to read controls @40003a0cdf98271d7744 alert: cannot start: unable to read controls @40003a0cdf983237f30c alert: cannot start: unable to read controls @40003a0cdf990406f7bc alert: cannot start: unable to read controls @40003a0cdf990efc8664 alert: cannot start: unable to read controls @40003a0cdf9917857df4 alert: cannot start: unable to read controls @40003a0cdf992287b6cc alert: cannot start: unable to read controls @40003a0cdf992d8fa494 alert: cannot start: unable to read controls @40003a0cdf9a128b3eec alert: cannot start: unable to read controls [snip qmail-showctl output...] This usually means that qmail can't read the control/ directory. Because, for security reasons, qmail doesn't run as root, the qmail user needs access to control/. On my installation, the control/ directory permissions/ownership look like this: drwxr-xr-x 2 rootqmail - 512 Aug 15 23:37 control/ and the contents of that directory is: -rw-r--r-- 1 root qmail - 12 Jan 27 2000 defaultdomain -rw-r--r-- 1 root qmail - 12 Jan 27 2000 defaulthost -rw-r--r-- 1 root qmail - 70 Jul 12 12:22 locals -rw-r--r-- 1 root qmail - 17 Jan 29 2000 me -rw-r--r-- 1 root qmail - 12 Jan 27 2000 plusdomain -rw-r--r-- 1 root qmail - 24 Aug 15 23:36 rcpthosts -rw-r--r-- 1 root qmail - 26 Aug 15 23:35 virtualdomains Note how everything is group-readable and owned by the qmail group. Check your permissions, make necessary changes and let us know if that works. -thl
Re: very slow delivery
On Sun, Nov 12, 2000 at 03:13:16PM +1100, Jesse Reynolds wrote: Hi I am having the same problem, where it takes 20 minutes for mail to be delivered, whether it's remote to local, local to remote, or local to local. It seems that indeed the permissions on the trigger file are wrong, mine is: prw--- 1 qmails qmail 0 Oct 23 02:27 /var/qmail/queue/lock/trigger Now, it has been taking 20 minutes to delever ever since I installed it. So presumably my installation didn't work properly, or has bugs in it. I'm using the FreeBSD ports collection to install qmail. I used the FreeBSD port on FreeBSD 3.3 and my perms were set correctly. This might be a bug in a later version of the port. I'd send a note to the ports mailing list and CC the maintainer of the qmail port. I am confused about Magnus's suggestion on how to fix it, ie do a "make setup" from the qmail source. Would it not be enough to manually fix the permissions with chmod? I don't know about this, but I suspect you are correct. If I cd to /usr/ports/mail/qmail and do "make setup" it response with "don't know how to make setup". You would have to run "make extract" in /usr/ports/mail/qmail, then cd to work/qmail-1.03 and run the "make setup". The ports collection has its own set of makefiles that create a subdirectory tree and run the actual software's make. The ports make system doesn't understand the setup or check targets. Cheers Jesse PS, this would be an excellent thing to have in the FAQ! It seems many people are having this problem. True. -thl
Re: No delivery
On Fri, Nov 10, 2000 at 04:52:54PM +0100, Pierre-Yves Deslandes wrote: Ok thanks for help about aliases. Yet, I've got a new problem ... I created some users recently with good passwords, with good directories e.g.~user/.qmail ./Maildir (like others users for whom it works) and a maildirmake Maildir (too) a qmail restart And when i send them mails, qmail says me there's no mailbox, Why ??? In your .qmail file, you can specify either a Maildir or a traditional Unix mailbox (mbox) where qmail should deliver the mail. If you write ./Maildir/, qmail assumes that it should deliver to a Maildir. If you write ./Maildir (without the trailing slash), qmail assumes you mean a mailbox. Check you .qmail file for the trailing slash and "man dot-qmail" for more information. Thanks Pierre-Yves Deslandes I hope that helps, -thl
Re: what is the process for adding a new user to qmail for Linux?
On Tue, Nov 07, 2000 at 12:56:38PM -0600, Robert Eric Pearse wrote: i've checked /var/log/syslog and /var/log/maillog. neither are coughing up messages from qmail-smptd. but, i am able to send messages to other users on that machine. so, it must be a problem with the user configuration. If you ran maildirmake as root, that could be a problem. The user needs to own the maildir (and it's subdirectories). Permissions should be 700. pearse Tim
Re: SMTP/POP3 problems
On Fri, Oct 27, 2000 at 09:19:19AM -0500, [EMAIL PROTECTED] wrote: I have installed qmail for the first time and the install has gone extremely smooth until now. I have run into two problems that I can't seem to solve and have not been able to find solutions on the list. My network currently consists of RedHat Linux 6.2 running a P90 server with 64 MB of RAM. This server does not currently have any access to the Internet since it is being setup for testing purposes only. /etc/resolv.conf is empty and there is no default gateway set. So at this point in your testing you have no DNS. Qmail (tcpserver, really) doesn't read /etc/hosts. You need to use 2 switches on the tcpserver line to handle this: -H and -l (ell, not one). The -H switch is necessary to prevent tcpserver from trying to look up the /sender's/ hostname. The -l is used to set the local host name; that is, the name of the host that tcpserver is running on, since tcpserver can't look that up, either. Finally, a third switch, -R, is used to prevent tcpserver from trying to retrieve "ident" information (this is the TCPREMOTEINFO mentioned in various parts of qmail / ucspi-tcp documentation). Use -H, -R and -l on the tcpserver command-line for qmail-smtpd. /usr/local/bin/tcpserver -v -R -H -lmyhost.nea.org ... The first problem I am having is that I cannot telnet to port 25 on the server. I will receive the message Connected to 127.0.0.1 Escape Character is ^]. Then, I do not receive any more messages and end up killing the process. If you receive the "Escape Character..." message, then you *have* successfully telnetted to port 25. At that point tcpserver is attempting to look up, as mentioned above, various things in DNS. The timeouts are fairly long, so it looks as if nothing's happening. [snip...] The second problem I have run into is with the pop3 protocol. Again, I was able to complete the test locally as outlined in Life with qmail. In this case, I am able to telnet to port 110 on the server without any problems, but e-mail clients such as Star Office, Outlook, Outlook Express, and Eudora will not connect. Eudora, prompts for my password and then returns an error message stating "Connection Timed Out (10060). Again, tcpserver is trying to do DNS lookups. Use the same three switches on the tcpserver line that runs qmail-popup. [snip...] Any help would be greatly appreciated. Thanks in advance, Jay HTH Tim -- Timothy Legant [EMAIL PROTECTED]
Re: Description of filename in Maildir/cur
On Wed, Oct 18, 2000 at 05:05:06PM -0400, Reid Sutherland wrote: 971829536.26305.simple:2,ST 971856803.14682.simple:2,T 971871879.5249.simple:2,RST The first part is I'm guessing is unix time(). Second part is the inode? Third, host. Now what's this 2? And what's T, ST, and RST? http://cr.yp.to/proto/maildir.html thanks -reid Tim
Re: Can't get qmail to function properly!
On Thu, Oct 19, 2000 at 02:16:45AM -0300, Vinko Vrsalovic wrote: [snip...] I have installed and configured qmail and it works _only_ if I connect locally to the server (ie telnet localhost 25), otherwise This is probably because the server knows its own IP address. See below. I have to wait between 1:30 and 2 minutes for the welcome message to appear, and then it doesn't get the rules that i set in tcp.smtp and i can deliver locally only. Since you mention the tcp.smtp rules file I assume you're using tcpserver. By default, tcpserver attempts to look up the hostname of the sending box before passing control to qmail-smtpd. It also tries to get ident information. If you don't run an internal DNS server it won't be able to get the former. It will time out waiting for the DNS response. Most likely your internal machines aren't running any form of identd either, so it will also time out on the latter. You should use the -R and -H options on the command line of the tcpserver that controls qmail-smtpd. Those options will prevent tcpserver from attempting to look up either the hostname or the ident information. man tcpserver for more information. [snip...] Thanks, Vinko HTH, Tim
Re: installing qmail tshirt-HELP please respond!!!
On Wed, Oct 11, 2000 at 10:48:37AM -0400, Andy Meuse wrote: Hey all, I got my qmail tshirt and I put it on according to the directions in Dave's LWQT, but the big logo is on the front of the shirt. How can I get the big qmail logo to be on the back and the little one to be on the front? I've tried taking it off and switching it around, and the logo is in the right place but then the shirt is inside out. Then when I take it off and put it on again I'm back where I started. I think it's a relaying problem between my ears. Any thoughts? -=Andy What Do The Logos Say?(tm) -- Tim
Re: Procmail and maildir format
On Sat, Sep 30, 2000 at 06:05:56PM +, Subba Rao wrote: I am in the process of moving from maildrop to procmail. The MTA on my system is Qmail, therfore I chose to use Maildir format for my mail. Procmail has been compiled to point to my spool at $HOME/Maildir The fetchmailrc is invoking procmail fine, but it does not write to the $HOME/Maildir/new directory. Instead it is dropping the mail in the literal $HOME/Maildir/ directory. The LOGFILE too is written to $HOME/Maildir/ directory. [snip...] How can I make Procmail deliver mail in maildir format? The version of procmail on my system is v3.15 You must specify a '/' at the end of the name of the maildir to alert procmail that your desired delivery mailbox is, in fact, a maildir. For example, my .procmailrc includes the following recipe to process messages to this list: :0 * ^TO_qmail Qmail/ Qmail is the name of the maildir in MAILDIR ($HOME/Mail, in my case). Procmail automatically delivers to the new/ directory within the specified mailbox. Procmail variables are as follows, PATH=$HOME/bin:/usr/bin:/usr/ucb:/bin:/usr/local/bin:. MAILDIR=$HOME/Maildir DEFAULT=$MAILDIR LOGFILE=procmail.log LOCKFILE=$HOME/.lockmail VERBOSE=yes You probably will need to change DEFAULT to say DEFAULT=$MAILDIR/ if you plan on some mail falling off the end of your processing and getting delivered to the default drop. Thanks for any pointers or info. Hope this helped. Subba Rao [EMAIL PROTECTED] http://pws.prserv.net/truemax/ Tim -- Timothy Legant [EMAIL PROTECTED]
Re: Alias Support Question
On Fri, Sep 01, 2000 at 11:04:10AM -0500, tom.sarratt.jr wrote: [snip...] Rights to the .qmail-postmaster file: access params:0664 owner:alias group:qmail [snip...] According to INSTALL.alias, you should create the ~alias/.qmail-XXX files by touching them. Presumably you *wouldn't* be logged in as alias, so the owner wouldn't be alias. Maybe that doesn't matter, but upon inspection, I find all my ~alias/.qmail-XXX files are owned by root:qmail. Also, and more importantly, the dot-qmail man page says: If .qmail is world-writable or group-writable, qmail-local stops and indicates a temporary failure. Your permissions are group writable. chmod 644 .qmail-postmaster and see if the delivery works. Tim -- Tim Legant [EMAIL PROTECTED]
