FLUSH QUEUE
HI ALL, IS there a way of flushing the qmail queue - PLEASE HELP!!! Many thanks _Tonino
Re: FLUSH QUEUE
At 10:51 27/01/00 +0200, the wonderful TAG said: HI ALL, IS there a way of flushing the qmail queue - PLEASE HELP!!! kill -ALRM qmail-send or, if you're using memphis RPMS: /etc/rc.d/inet.d/qmail.init alrm all explained at http://cr.yp.to/qmail/faq/admin.html#queuerun peter -- peter at gradwell dot com; online @ http://www.gradwell.com/
Re: open relay problem
At 01:16 27.1.2000 -0500, you wrote: | Hi | I'm a new qmail user having a problem with relays. I'm using tcpserver | with 3 domains in rcpthosts and the following in etc/tcp.smtp | | 192.168.1.:allow,RELAYCLIENT="" | 127.:allow,RELAYCLIENT="" | | According to what I've read, this should allow only users with 192.168.1.* | to use my server as a relay. But when I test remotely, the test messages | are allowed through. | | Any input would be much appriciated. | Thanks | Jeff Yayayaya.. but hmmm.. maybe you need a default allow rule in there eh? 192.168.1.:allow,RELAYCLIENT="" 127.:allow,RELAYCLIENT="" :allow Hi, try my SPAMCONTROL Patch I posted into this group recently. However, I really advise everybody NOT to use the LOOPBACK address to be included in the relaying control mechanism. Its easy enough to fake that. regards, erwin. +---+ | fffhh Dr. Erwin Hoffmann | | ff hh| | ffeee ccc ooomm mm mm Wiener Weg 8 | | fff ee ee hh hh cc oo oo mmm mm mm 50858 Koeln| | ff ee eee hh hh cc oo oo mm mm mm| | ff eee hh hh cc oo oo mm mm mm Tel 0221 484 4923 | | ff hh hhccc ooomm mm mm Fax 0221 484 4924 | +---+
Re: big fat qmail-command hole
On Wed, Jan 26, 2000 at 09:41:34PM -0800, Faried Nawaz wrote: Russell Nelson wrote: Faried Nawaz writes: And how does someone with /bin/false as their shell put commands in their .qmail files? The sysadmin put /bin/false into /etc/shells, and now ftp lets them deposit files in their home directory. Well, yes -- that's what I imagine happened. An admin error. The only time I saw someone place /bin/false in /etc/shells was when they had a sendmail-based mailhost and wanted to allow people to run procmail from their .forwards. Home directories and /var/mail were shared between the client machines and the mailhost. Perhaps this sysadmin upgraded from sendmail and didn't fix /etc/shells. Oh and procmail doesn't allow people to execute stuff thru /bin/sh? :) (Though "| xterm -display myhost:0" worked great, too!) :) Greetz, Peter. -- Peter van Dijk - student/sysadmin/ircoper/madly in love/pretending coder | | 'C makes it easy to shoot yourself in the foot; | C++ makes it harder, but when you do it blows your whole leg off.' | Bjarne Stroustrup, Inventor of C++
smtp authentication
Hi everyone! Is it possible to set qmail to only allow authenticated smtp session to send messages ?? RFC 2554 Any hints?
Re: Duplicates on outbound mail, not inbound
We use qmail to send out large subscriber emagazine/newsletter mailings (2 million messages/week), and we seem to have a problem with some subscribers getting duplicates. I have seen fixes for duplicates on inbound mail, but does anyone know how to address our problem on outbound mail. Onelist and Hotmail don't seem to have a dupe problem. The problem is sporadic and unpredictable. Sometimes the duplicates have the same time stamp, and other times they are separated by an hour (message sent back into the cue as undelivered?). Any thoughts? 1) Is the message-id the same for the dupes? 2) Given two dupes with the same message-id, how do their Received: paths compare? 3) Consider the likelihood that with any large subscriber base, you'll get people who have no clue what their email address is and who are probably signed up three times with four different AOL "screen names." The key is to find a victim who can forward you full copies of the headers, including Received:, Message-ID:, To:, Delivered-To: (if present), etc. etc. Once you have that, you can find many problems with just that evidence, and if theproblem does go back to your logs you'll have enough info to correlate with your logs and find out what happened. Greg
Failed Relay test 6 ?
Hi, I received a message from orbs.org that our mailhost is relay server. I thought I fixed the problem by installing ucspi-tcp-0.84 but when I checked our mailhost on http://www.abuse.net/relay.html I got the following relay error: Relay test 6 RSET 250 flushed MAIL FROM:spamtest@[193.58.204.195] 250 ok RCPT TO:relaytest%abuse.net@[193.58.204.195] 250 ok Can anyone help me on this because I don't know what to do. Regards, Erwin van Kroonenburg [EMAIL PROTECTED]
Re: Failed Relay test 6 ?
On Thu, Jan 27, 2000 at 11:46:19AM +0100, [EMAIL PROTECTED] wrote: On Thu, Jan 27, 2000 at 11:38:20AM +0100, Erwin van Kroonenburg wrote: Hi, I received a message from orbs.org that our mailhost is relay server. I thought I fixed the problem by installing ucspi-tcp-0.84 but when I checked our mailhost on http://www.abuse.net/relay.html I got the following relay error: Relay test 6 RSET 250 flushed MAIL FROM:spamtest@[193.58.204.195] 250 ok RCPT TO:relaytest%abuse.net@[193.58.204.195] 250 ok Can anyone help me on this because I don't know what to do. [snip] So, get an abuse.net account and use _that_ to test, only to see that your host _is_ secure now :) Luckily, the ORBS-tester is a bit more reliable than this. I marked your host 'secure' at ORBS (after doing a bit of testing myself) and it's now marked 'closed but pending retest', which is good :) Greetz, Peter. -- Peter van Dijk - student/sysadmin/ircoper/madly in love/pretending coder | | 'C makes it easy to shoot yourself in the foot; | C++ makes it harder, but when you do it blows your whole leg off.' | Bjarne Stroustrup, Inventor of C++
qmail Digest 27 Jan 2000 11:00:01 -0000 Issue 893
qmail Digest 27 Jan 2000 11:00:01 - Issue 893 Topics (messages 36122 through 36219): Re: SetEnv QMAILSUSER not working in Apache conf 36122 by: Vince Vielhaber 36132 by: Chris Hardie qmail and dnscache 36123 by: Petr Novotny 36131 by: iv0 36133 by: Petr Novotny 36135 by: Dave Sill Message delivery failure question 36124 by: Randolph S. Kahle 36125 by: Petr Novotny 36127 by: Randy Kahle Unique domain, several mail server 36126 by: Andrea Verni 36160 by: Faried Nawaz 36163 by: Russell Nelson Mail Stuck In Bin 36128 by: Jeff Russell smtp authentication 36129 by: Thomas Schachner 36215 by: Thomas Schachner More setup questions 36130 by: Joe Millay Re: Any way to log and correlate qmail-smtpd/qmail-send IP addresses? 36134 by: asheiduk.hawo.stw.uni-erlangen.de qtools available 36136 by: William E. Baxter Re: remote root qmail-pop with vpopmail advisory and exploit with patch (fwd) 36137 by: Derek Callaway 36139 by: Petr Novotny 36140 by: Russell Nelson 36141 by: Pavel Kankovsky 36142 by: Russell Nelson 36143 by: Petr Novotny 36144 by: Pavel Kankovsky 36146 by: Mads E Eilertsen is turning off mail relaying correct? 36138 by: Eric Long 36179 by: Sam Re: Duplicates on outbound mail, not inbound 36145 by: Kevin Lee 36147 by: Mark Delany 36217 by: Greg Owen Re: Scenario 36148 by: Dave Sill Re: Adding Users when Installing (NEWBIE) 36149 by: Dave Sill Re: Help starting qmail... 36150 by: Dave Sill Re: Problems with Subscription 36151 by: Dave Sill Re: pop3 check failed 36152 by: Dave Sill How do I limit outbound SMTP threads? 36153 by: Randolph S. Kahle 36155 by: Charles Cazabon Re: qmail aliases 36154 by: Mike Denka 36162 by: Giles Lean 36165 by: Faried Nawaz cc messages are splited in severals deliveries 36156 by: dsmail.linux.highnet.com.br 36157 by: Charles Cazabon 36158 by: dsmail.linux.highnet.com.br 36159 by: Russell Nelson 36164 by: Russell Nelson 36174 by: Charles Cazabon 36180 by: Sam Funny but sad... 36161 by: Petr Novotny 36166 by: Faried Nawaz 36167 by: Russell Nelson 36168 by: Giles Lean 36169 by: Petr Novotny 36170 by: Giles Lean 36171 by: Paul Schinder 36173 by: Russell Nelson open relay problem 36172 by: Jeff Mayes 36181 by: Sam 36186 by: Len Budney 36204 by: Keith Warno 36206 by: Adam McKenna 36213 by: Dr. Erwin Hoffmann Re: Strange queue behaviour] 36175 by: Chris Readle maildir delivery code in perl 36176 by: Nathan J. Mehl 36192 by: John White Re: Strange queue behaviour]] 36177 by: Patterner Daemontools.61 initscripts? 36178 by: Bill Rogers 36182 by: Vincent Schonau 36188 by: Jon Rust Restrict Times 36183 by: Director tecnico del Nodo Nicarao -- Juan Navas 36184 by: Mark Delany 36185 by: Vince Vielhaber 36187 by: Stephen Mills 36189 by: Len Budney 36190 by: David Mandala Re: Truncating large attachments in bounced mail 36191 by: Peter Green 36194 by: David Cunningham procmail problems 36193 by: Eric LaLonde 36208 by: Deke Clinger Re: What MUA do you use? 36195 by: Mark E. Drummond 36196 by: Mark E. Drummond 36209 by: Martin Lesser About offline 36197 by: Md. Sifat Ullah Patwary 36207 by: Martin Lesser big fat qmail-command hole 36198 by: Stig Hackvän 36201 by: Faried Nawaz 36202 by: Russell Nelson 36203 by: Faried Nawaz 36214 by: petervd.vuurwerk.nl subdomain qmail locals 36199 by: Scott Beck ($BL5Bj(B) 36200 by: masayuki sakai Restricting cc and recipients: 36205 by: TAG VIRTUAL DOMAIN 36210 by: ruchandra.hss.hns.com FLUSH QUEUE 36211 by: TAG 36212 by: Peter Gradwell Failed Relay test 6 ? 36216 by: Erwin van Kroonenburg 36218 by: petervd.vuurwerk.nl 36219 by: petervd.vuurwerk.nl Administrivia: To unsubscribe from the digest, e-mail: [EMAIL PROTECTED] To subscribe to the digest, e-mail: [EMAIL PROTECTED] To bug my human owner, e-mail: [EMAIL PROTECTED] To post to the list, e-mail: [EMAIL PROTECTED] -- On Wed, 26 Jan 2000, Chris Hardie wrote: I've tried this to no avail. As the above part of my message indicates, it seems the environment variables aren't even being set, let alone used. I did notice that when I upgraded from 1.3b5 to 1.3.9 (internal server) that SetEnv
How to watch the current receiving messages?
Hi, With qmail-qread, qmail-qstat and qmHandle, I can watch the queue, but how can I see the current open stmp session that are receiving messages? And how can I get more information about these messages? Best regards, Ari
Re: remote root qmail-pop with vpopmail advisory and exploit with patch (fwd)
Pavel Kankovsky wrote: On Wed, 26 Jan 2000, Russell Nelson wrote: 2. qmail-send is run as root? Yup. Well, qmail-start is run as root. Along the line it gives up its rootness, becoming qmail-send, and leaving only qmail-lspawn running as root. Login is run as root. It switches to my privs and execs my login shell. Therefore my login shell is run as root. Right? :) Login is run as root. Once you've entered a correct username/password pair, it switches to that user, so it isn't running as root any more. Your login shell runs as your user. It wouldn't make sense otherwise. Maybe this was a troll after all... -- Peter Haworth [EMAIL PROTECTED] "I have yet to see any problem, however complicated, which, when you looked at it the right way, did not become still more complicated." -- Poul Anderson
Loopback? Was: open relay problem
On Thu, Jan 27, 2000 at 10:02:45AM +0100, Dr. Erwin Hoffmann wrote: Hi, try my SPAMCONTROL Patch I posted into this group recently. However, I really advise everybody NOT to use the LOOPBACK address to be included in the relaying control mechanism. Its easy enough to fake that. It's easy enough to fake a loopback address for packets coming in on a non-loopback device? This is not a qmail issue; this should be dealt with somewhere along the way by network filtering. Something like: ipchains -I accept 1 -S 127.0.0.1 -i !lo -j DENY theoretically should do the trick (untested). /pg -- Peter Green Gospel Communications Network, SysAdmin [EMAIL PROTECTED]
broadcast message
HI, Is there a way of sending all users a broadcast message?? --Many thans Tonino
Outlook address book oddity
Hi This is more of a petty annoyance than anything else, but I'd like to know if anyone else has experienced it. I recently was contacted by a user saying that they were getting bounce messages back each time they tried to send mail to a particular local address. Upon further investigation it turns out that although this recipient's email address in her Outlook address book was spelt correctly, there was a space after the last character. When I checked the qmail logs, this space appears as a question mark at causing the message to bounce. Anyone have any ideas? When I type a space after an email address directly in the 'TO' field it goes OK suggesting this is more than likely a flaw in Outlook. Any ideas??? ta Si
Annoyance
I just noticed in my logs that a specific host, mrelay0.starwave.com keeps opening a smtp connection every minute or so. Should I just outright deny this connection from connecting or is there a way to find out what is going on? Nothing shows up in my logs as far as something being delivered. Thanks in advance Tim Hunter CIMx Company [EMAIL PROTECTED] http://www.cimx.com
Re: Annoyance
Peter Green [EMAIL PROTECTED] wrote: On Thu, Jan 27, 2000 at 10:39:46AM -0500, Tim Hunter wrote: I just noticed in my logs that a specific host, mrelay0.starwave.com keeps opening a smtp connection every minute or so. Should I just outright deny this connection from connecting or is there a way to find out what is going on? Nothing shows up in my logs as far as something being delivered. Isn't that the kind of behavior that happens when a bare LF is found? Yeah, except well-behaved MTA's don't try to resend every minute. This can be debugged using recordio to record the SMTP session. See the FAQ. -Dave
Re: Annoyance
On Thu, Jan 27, 2000 at 10:39:46AM -0500, Tim Hunter wrote: I just noticed in my logs that a specific host, mrelay0.starwave.com keeps opening a smtp connection every minute or so. Should I just outright deny this connection from connecting or is there a way to find out what is going on? Nothing shows up in my logs as far as something being delivered. Isn't that the kind of behavior that happens when a bare LF is found? I'm seeing it a lot from www.projectorcentral.com (which is using Cold Fusion...). /pg -- Peter Green Gospel Communications Network, SysAdmin [EMAIL PROTECTED]
Re: Outlook address book oddity
Any ideas??? Encourage your users to hate Outlook ... Regards, Frank
Re: Outlook address book oddity
[EMAIL PROTECTED] wrote: This is more of a petty annoyance than anything else, but I'd like to know if anyone else has experienced it. I recently was contacted by a user saying that they were getting bounce messages back each time they tried to send mail to a particular local address. Upon further investigation it turns out that although this recipient's email address in her Outlook address book was spelt correctly, there was a space after the last character. When I checked the qmail logs, this space appears as a question mark at causing the message to bounce. My address is "[EMAIL PROTECTED]", not "[EMAIL PROTECTED] ". If you use the latter, you should expect it to fail. The space is converted to a "?" in the logs because all non-printable characters are displayed as ?'s. The message isn't failing because of the conversion done for the log. Anyone have any ideas? When I type a space after an email address directly in the 'TO' field it goes OK suggesting this is more than likely a flaw in Outlook. Your MUA strips trailing whitespace. One can argue that Outlook should also do that, but one can also argue that users should enter addresses correctly. Of course, any s/w that expects the user to do the right thing is either broken or rude. ½ :-) -Dave
Re: problems with 'mail' (procmail?)
"Eric LaLonde" [EMAIL PROTECTED] wrote: I've moved the file /var/spool/mail/user to ~user/Mailbox and made a symbolic link back to /var/spool/mail/user, but it doesn't seem to stay. It will say that I have new mail in /var/spool/mail/user, and then when i go to view that mail via 'mail', it gives me this message: This text is part of the internal format of your mail folder, and is not a real message. It is created automatically by the mail system software. If deleted, important folder data will be lost, and it will be re-created with the data reset to initial values. I then quit out of mail, it saves it to mbox, and then the link /var/spool/mail/user is gone. This line is in my maillog: Jan 25 13:36:52 damacles procmail[5961]: Renamed bogus "/var/spool/mail/root" into "/var/spool/mail/BOGUS.root.VUJ" Why is this happening, and why aren't my links sticking, and what should i do? Procmail doesn't like the symlink in /var/spool/mail so it renames it. The fix is to read INSTALL.mbox and follow the directions for configuring the mail reader to look directly in ~user/Mailbox. -Dave
Re: Queue Problem
[EMAIL PROTECTED] wrote: When I sent to a mailing list it ques the entire list (175,000 addresses) then the que takes forever (24 hours) to deliver. Anyway to speed this up? The server is a dedicated P 450, 128Meg, RedHat. Dedicated to qmail. 1. Increase concurrencyremote. Rebuild with conf-spawn set to 255 before raising it past 120. Install the "big concurrency" patch if you need to go past 255. 2. Put the queue on a fast disk on a dedicated SCSI interface. 3. Install dnscache. I can do 175k deliveries on my list server in ~3 hours, and I haven't done (2) yet. -Dave
Re: qmail-pop3d: unable to write pipe
John White [EMAIL PROTECTED] wrote: Symptoms: users can issue USER and PASS commands, but an immediate -ERR unable to write pipe is issued. contents of /service/qmail-pop3d/run: #!/bin/sh /usr/local/bin/tcpserver -v 0 pop3 /var/qmail/bin/qmail-popup \ triceratops.com /bin/checkpassword /var/qmail/bin/qmail-pop3d Maildir 21 Any ideas? I think you need to "exec" tcpserver. -Dave
Re: Message delivery failure question
"Randolph S. Kahle" [EMAIL PROTECTED] wrote: "[...] deferral: Connected_to_151.xxx.x.xx_but_connection_died._(#4.4.2)/" The email is being send to an address person_name@company.com that works when I send the email through another SMTP server. So, I thought this might be a DNS problem. I switched my resolv.conf to point to the DNS that the working SMTP server uses and this does not seem to fix the problem. It could still be a DNS problem. The other MTA might be lenient about DNS misconfiguration than qmail. Post the details and let a DNS expert check it out. -Dave
Re: Annoyance
On Thu, Jan 27, 2000 at 10:39:46AM -0500, Tim Hunter wrote: I just noticed in my logs that a specific host, mrelay0.starwave.com keeps opening a smtp connection every minute or so. Should I just outright deny this connection from connecting or is there a way to find out what is going on? Nothing shows up in my logs as far as something being delivered. I had that same host doing that to me. It's sending a message with bare linefeeds in it. I just cut them off with tcpserver. Chris
Re: [Fwd: Strange queue behaviour]
Chris Readle [EMAIL PROTECTED] writes: Chris Readle wrote: I'm having a bit of strand queue behaviour. Basically I've got 50+ (I think 54, without looking) local-bound messages in the queue that I cannot get to flush no matter what I try. I've tried sending an ALRM, a HUP, stopping and restarting qmail and rebooting the server. The messages are still there. Everything else seems to be running great and new messages are going in and out with no problems, but these message justs won't deliver. Any ideas? chris Show us what the logs say when you try to flush the queue.
Getting proper mail notifications
Greetings! I am using qmail with FreeBSD 3.3, and when my users telnet in, ssh in or login from a terminal, it does not tell them they have new mail, when they do (in the case of ssh, it says "no mail" regardless). I am using /home/user/Mailbox for delivery. For telnet, I'm using telnetd via inetd, and sshd2 for ssh connections. I RTFAQ, and didn't see anything that specifically addressed that issue. What do I need to change? Thanks for your help!
Re: Annoyance
They may be sending a bare linefeed in the message. Qmail seems to have this problem. From what I understand it's not gonna be fixed bacause it's the other server's fault not a qmail problem. Paul Farber Farber Technology [EMAIL PROTECTED] Ph 570-628-5303 Fax 570-628-5545 On Thu, 27 Jan 2000, Tim Hunter wrote: I just noticed in my logs that a specific host, mrelay0.starwave.com keeps opening a smtp connection every minute or so. Should I just outright deny this connection from connecting or is there a way to find out what is going on? Nothing shows up in my logs as far as something being delivered. Thanks in advance Tim Hunter CIMx Company [EMAIL PROTECTED] http://www.cimx.com
Re: Getting proper mail notifications
On Thu, Jan 27, 2000 at 09:12:44AM -0800, Scott Schappell wrote: Greetings! I am using qmail with FreeBSD 3.3, and when my users telnet in, ssh in or login from a terminal, it does not tell them they have new mail, when they do (in the case of ssh, it says "no mail" regardless). I am using /home/user/Mailbox for delivery. For telnet, I'm using telnetd via inetd, and sshd2 for ssh connections. I RTFAQ, and didn't see anything that specifically addressed that issue. What do I need to change? This is a Unix issue more than a qmail issue. Firstly you need to work out what it is that tells you whether you have mail or not. Can I suggest you look at the characteristics of the shell you are running - especially wrt anything to do with email? Once you've done that work, you might explore whether that characteristic can be modified to look at your Mailbox. If you do that work and find out what to do, you might want to post your results here to help future people with the same question. Regards.
Re: Getting proper mail notifications
Scott Schappell [EMAIL PROTECTED] wrote: I am using qmail with FreeBSD 3.3, and when my users telnet in, ssh in or login from a terminal, it does not tell them they have new mail, when they do (in the case of ssh, it says "no mail" regardless). I am using /home/user/Mailbox for delivery. For telnet, I'm using telnetd via inetd, and sshd2 for ssh connections. I RTFAQ, and didn't see anything that specifically addressed that issue. What do I need to change? Write a script for your system-wide .bashrc which does something like "Check the contents of $HOME/Mailbox for new messages and print 'You have new mail' if there is any". If you deliver to $HOME/Maildir/, all you have to do is check whether there are any files in $HOME/Maildir/new/ . Charles -- Charles Cazabon [EMAIL PROTECTED] Any opinions expressed are just that -- my opinions.
Re: What MUA do you use?
From: "Mark E. Drummond" [EMAIL PROTECTED] Date: Wed, 26 Jan 2000 23:16:20 -0500 Wrong-o! Want to send a nicely formatted proposal (with appropriate highlights etc) to the department director so you can get funding for that million dollar server upgrade project? Good luck doing it in plain text. And tables? Sounds like a job for PDF. It'll even look the same everywhere. Chris -- Chris Garrigues virCIO http://www.DeepEddy.Com/~cwg/ http://www.virCIO.Com +1 512 432 4046 +1 512 374 0500 4314 Avenue C O- Austin, TX 78751-3709 My email address is an experiment in SPAM elimination. For an explanation of what we're doing, see http://www.DeepEddy.Com/tms.html Nobody ever got fired for buying Microsoft, but they could get fired for relying on Microsoft. PGP signature
Re: Getting proper mail notifications
"Scott Schappell" [EMAIL PROTECTED] writes: I am using qmail with FreeBSD 3.3, and when my users telnet in, ssh in or login from a terminal, it does not tell them they have new mail, when they do (in the case of ssh, it says "no mail" regardless). I am using /home/user/Mailbox for delivery. For telnet, I'm using telnetd via inetd, and sshd2 for ssh connections. I RTFAQ, and didn't see anything that specifically addressed that issue. What do I need to change? In /etc/profile, add MAIL=$HOME/Mailbox export MAIL Add something similar to /etc/csh.cshrc. (Be sure and educate the users, too!)
Re: Mail Stuck In Bin
"Jeff Russell" [EMAIL PROTECTED] wrote: This account is not on the list, but if you could respond to this I'd appreciate it. I'm not sure if this is qmail or not, but I can't send messages outside of our firewall, nor can I get messages in. What happens when you try? They disappear? They bounce? However, I am able to email interoffice. So qmail is functioning, but only partially. I have checked our firewall processes, and the web server and SMTP mail is running. I then checked var/qmail/bin for any messages, and there are sixty-two preprocessed messages. ( I am not sure if these are the messages from outside). Look at them. I have also gone directly to my Maildir and tried to list messages from there, but it doesn't list anything. In fact no ones does. Clearly, I am able to get on the net, so I don't believe that this is a firewall problem. If anyone has any clue, I'd appreciate it. Thanks! One obvious thing to do would be to look at your qmail-send logs. You might also run qmail-showctl and post the results. -Dave
Re: smtp authentication
Thomas Schachner [EMAIL PROTECTED] wrote: Is it possible to set qmail to only allow authenticated smtp session to send messages ?? RFC 2554 I don't know if it's RFC 2554, but there are patches on www.qmail.org that implement SMTP authentication. -Dave
Re: qmail delivery slowdown under high load
On Tue, 25 Jan 2000, Andras Tudos - Computronic, C3 wrote: At 2000.01.24 20:58, Monday, you wrote: On 24/01 19:28, Andras Tudos - Computronic, C3 wrote: I have an operational theory question: when the load in a qmail setup [...snip...] not occur in a sendmail or other MTA based system. What operating system? Are you using Maildir or mailbox? Solaris 2.6 and Maildir. But I think the answer was given already: the problem is the flat queue/todo folder and the solution is the big-todo patch. Of course the most important is to have enough I/O to be able to deliver without filling up the queue: the disk subsystem was the real bottleneck, which is being upgraded now. If you use online disk-suite to create a logging file-system you will find the write-performance of Maildir will increase significantly as directory write operations no-longer become synchronous. This will speedup local delivery under high loads. RjL == You know that. I know that. But when || Austin, Texas you talk to a monkey you have to || Email: [EMAIL PROTECTED] grunt and wave your arms -ck ||
Re: More setup questions
Joe Millay [EMAIL PROTECTED] wrote: QUESTION #1: The [LWQ] instructions say there should be a file named INSTALL.ids in the source directory. I couldn't find it, so per the instructions I added: alias:*:7790:2108::/var/qmail/alias:/bin/true qmaild:*:7791:2108::/var/qmail:/bin/true qmaill:*:7792:2108::/var/qmail:/bin/true qmailp:*:7793:2108::/var/qmail:/bin/true qmailq:*:7794:2107::/var/qmail:/bin/true qmailr:*:7795:2107::/var/qmail:/bin/true qmails:*:7796:2107::/var/qmail:/bin/true to the /etc/passwd file. I did the "make setup check" command and the "./config-fast the.full.hostname" command. Both seemed to work fine. NOW, I have a file named INSTALL.ids in the /usr/local/src/qmail/qmail-1.03/ directory. So, should I edit that file now? No. It's documentation, not a config file. QUESTION #2: I am getting ready to install ucspi-tcp and daemontools, but I am not sure what they do, or if I really need to do so. Can anyone help with this? You don't need to be sure of what they do to install them. If you want to follow the LWQ directions, they're absolutely mandatory. If you want to satisfy your curiosity about what they do, it's right there in LWQ, specifically at: http://Web.InfoAve.Net/~dsill/lwq.html#daemontools http://Web.InfoAve.Net/~dsill/lwq.html#ucspi-tcp QUESTION #3: I've read forward in the instructions and I see that I will add users like the following: =address:user:uid:gid:directory:dash:extension: You *could* do that, but if you think you *must*, you're mistaken. You don't need to use qmail-users to allow normal users to receive mail. The instructions say that the directory /var/qmail/users contains a series of configuration files, but mine is empty (the directory contains no files). Am I to create the config files, or will they be setup later? I am extremely confused about this portion of the setup. qmail-users is optional. *If* you want to use it, you'll need to populate /var/qmail/users. -Dave
Re: subdomain qmail locals
Scott Beck [EMAIL PROTECTED] wrote: How do I set *.domain as a local delivery in /var/qmail/control/locals or do I need to do something entirly different? There's no wildcard mechanism for control/locals. You'll need to list all of the domains. -Dave
Re: VIRTUAL DOMAIN
[EMAIL PROTECTED] wrote: Question: How can i configure same name for two different domains. As alias in QMAIL directory forwards the mail only through the user name and it doesn't see the domain name. I feel the problem can be sorted out by " Virtual Domain " concept. Kindly suggest is this the right solution if yes, how it can be implemented. Yes, this is what virtual domains are used for. See: http://Web.InfoAve.Net/~dsill/lwq.html#virtual-domains -Dave
Re: What MUA do you use?
"Chris Garrigues" [EMAIL PROTECTED] wrote: Sounds like a job for PDF. It'll even look the same everywhere. Or a URL pointing to HTML on a local web server. -Dave
Qmail behaviour
Hi Is it possible to stop qmail sending or receiving email if the from: and to: fields contain incomplete addresses i.e. username and not [EMAIL PROTECTED] Your help is really appreciated.
Re: [Fwd: Strange queue behaviour]
Faried Nawaz wrote: Chris Readle [EMAIL PROTECTED] writes: Chris Readle wrote: I'm having a bit of strand queue behaviour. Basically I've got 50+ (I think 54, without looking) local-bound messages in the queue that I cannot get to flush no matter what I try. I've tried sending an ALRM, a HUP, stopping and restarting qmail and rebooting the server. The messages are still there. Everything else seems to be running great and new messages are going in and out with no problems, but these message justs won't deliver. Any ideas? chris Show us what the logs say when you try to flush the queue. I think I see the problem, nowI'm getting message has wrong owner and unable to switch to directoryI'll attach the relevant log portion. chris 948992273.168662 starting delivery 121: msg 230524 to local [EMAIL PROTECTED] 948992273.168675 status: local 1/20 remote 0/30 948992273.171009 delivery 121: deferral: Unable_to_switch_to_/home/chris:_access_denied._(#4.3.0)/ 948992273.171024 status: local 0/20 remote 0/30 948992396.674129 starting delivery 122: msg 230525 to local [EMAIL PROTECTED] 948992396.674143 status: local 1/20 remote 0/30 948992396.674150 starting delivery 123: msg 230524 to local [EMAIL PROTECTED] 948992396.674162 status: local 2/20 remote 0/30 948992396.693089 starting delivery 124: msg 230532 to local [EMAIL PROTECTED] 948992396.693103 status: local 3/20 remote 0/30 948992396.693110 delivery 122: deferral: Unable_to_switch_to_/home/chris:_access_denied._(#4.3.0)/ 948992396.693124 status: local 2/20 remote 0/30 948992396.693131 delivery 123: deferral: Unable_to_switch_to_/home/chris:_access_denied._(#4.3.0)/ 948992396.693145 status: local 1/20 remote 0/30 948992396.693152 starting delivery 125: msg 230522 to local [EMAIL PROTECTED] 948992396.693164 status: local 2/20 remote 0/30 948992396.709790 starting delivery 126: msg 232574 to local [EMAIL PROTECTED] 948992396.709803 status: local 3/20 remote 0/30 948992396.709811 delivery 124: deferral: Unable_to_switch_to_/home/chris:_access_denied._(#4.3.0)/ 948992396.709825 status: local 2/20 remote 0/30 948992396.709832 delivery 125: deferral: Unable_to_switch_to_/home/chris:_access_denied._(#4.3.0)/ 948992396.709846 status: local 1/20 remote 0/30 948992396.728920 starting delivery 127: msg 232568 to local [EMAIL PROTECTED] 948992396.728933 status: local 2/20 remote 0/30 948992396.728940 delivery 126: deferral: Sorry,_message_has_wrong_owner._(#4.3.5)/ 948992396.728952 status: local 1/20 remote 0/30 948992396.750439 starting delivery 128: msg 232590 to local [EMAIL PROTECTED] 948992396.750452 status: local 2/20 remote 0/30 948992396.750459 delivery 127: deferral: Sorry,_message_has_wrong_owner._(#4.3.5)/ 948992396.750471 status: local 1/20 remote 0/30 948992396.768174 starting delivery 129: msg 232601 to local [EMAIL PROTECTED] 948992396.768187 status: local 2/20 remote 0/30 948992396.768194 delivery 128: deferral: Sorry,_message_has_wrong_owner._(#4.3.5)/ 948992396.768206 status: local 1/20 remote 0/30 948992396.772692 starting delivery 130: msg 230533 to local [EMAIL PROTECTED] 948992396.772705 status: local 2/20 remote 0/30 948992396.772712 delivery 129: deferral: Sorry,_message_has_wrong_owner._(#4.3.5)/ 948992396.772724 status: local 1/20 remote 0/30 948992396.786670 starting delivery 131: msg 232600 to local [EMAIL PROTECTED] 948992396.786683 status: local 2/20 remote 0/30 948992396.786690 delivery 130: deferral: Unable_to_switch_to_/home/chris:_access_denied._(#4.3.0)/ 948992396.786704 status: local 1/20 remote 0/30 948992396.787520 starting delivery 132: msg 232577 to local [EMAIL PROTECTED] 948992396.787533 status: local 2/20 remote 0/30 948992396.787540 delivery 131: deferral: Sorry,_message_has_wrong_owner._(#4.3.5)/ 948992396.787551 status: local 1/20 remote 0/30 948992396.802177 starting delivery 133: msg 232604 to local [EMAIL PROTECTED] 948992396.802190 status: local 2/20 remote 0/30 948992396.802197 delivery 132: deferral: Sorry,_message_has_wrong_owner._(#4.3.5)/ 948992396.802208 status: local 1/20 remote 0/30 948992396.820684 starting delivery 134: msg 232591 to local [EMAIL PROTECTED] 948992396.820697 status: local 2/20 remote 0/30 948992396.820704 delivery 133: deferral: Sorry,_message_has_wrong_owner._(#4.3.5)/ 948992396.820716 status: local 1/20 remote 0/30 948992396.839303 starting delivery 135: msg 232575 to local [EMAIL PROTECTED] 948992396.839316 status: local 2/20 remote 0/30 948992396.839323 delivery 134: deferral: Sorry,_message_has_wrong_owner._(#4.3.5)/ 948992396.839335 status: local 1/20 remote 0/30 948992396.840144 starting delivery 136: msg 232581 to local [EMAIL PROTECTED] 948992396.840157 status: local 2/20 remote 0/30 948992396.840164 delivery 135: deferral: Sorry,_message_has_wrong_owner._(#4.3.5)/ 948992396.840176 status: local 1/20 remote 0/30 948992396.859953 starting delivery 137: msg 230531 to local [EMAIL PROTECTED] 948992396.859967 status: local
Re: Qmail behaviour
"Adil Tahiri" [EMAIL PROTECTED] wrote: Is it possible to stop qmail sending or receiving email if the from: and to: fields contain incomplete addresses i.e. username and not [EMAIL PROTECTED] qmail doesn't look at the From: or To: fields. It uses the SMTP envelope addresses. There's no easy way to filter them for incomplete specifications. Perhaps the SPAMCONTROL patch posted recently does. Dr. Hoffman? -Dave
Re: [FIXED] Getting proper mail notifications
Thanks for all the suggestions and answers. In the end, though, I tried the simple fix of: # ln -s /home/user/Mailbox user # chown user file # chgrp group user # chmod 500 user and it worked just fine, whether connecting via telnet, ssh or a term. Only odd thing I noticed was that the owner of the symlinks was changed to root and group mail, and the permissions were changed to u=rx g=rx o=rx, however, as long as the Mailbox file in the users home directory is set properly, it still can't be viewed by others were someone to try to % cat /var/mail/archon. Sure, it's not elegant, but it worked :) Thanks again!
Re: subdomain qmail locals
On Thu, Jan 27, 2000 at 12:48:51PM -0500, Dave Sill wrote: Scott Beck [EMAIL PROTECTED] wrote: How do I set *.domain as a local delivery in /var/qmail/control/locals or do I need to do something entirly different? There's no wildcard mechanism for control/locals. You'll need to list all of the domains. You could give my patch a try, which adds regular expressions to control/locals. But I have no numbers on performance issues. Look at http://beteigeuze.cs.tu-berlin.de/linux/qmail/ Greetings -- Robert Sander
Re: subdomain qmail locals
I sent this separately to Robert, then realized he wasn't the original questioner :). From what I noticed, in my locals file all it says is: localhost silvertree.org And any mail addressed to user@sub.silvertree.org gets delivered as a local. As an example, I have the following hosts: tintagel mordred arthur ygraine and mail sent to [EMAIL PROTECTED] still gets delivered to the qmail box, and tintagel's machine is still being built :). My understanding is that the entry "silvertree.org" equates to "*.silvertree.org", at least that's I gleaned from the brief FAQ entry. Of course, I also may not be understanding his question. That also has to assume the MX entry is correct for his domain, that all mail goes to that machine. In my example: silvertree.org IN MX 10 arthur.silvertree.org. The FAQ I am referencing is: http://cr.yp.to/qmail/faq/incominghost.html#local Hope that helps. Scott - Original Message - From: "Robert Sander" [EMAIL PROTECTED] To: [EMAIL PROTECTED] Sent: Thursday, January 27, 2000 10:53 AM Subject: Re: subdomain qmail locals On Thu, Jan 27, 2000 at 12:48:51PM -0500, Dave Sill wrote: Scott Beck [EMAIL PROTECTED] wrote: How do I set *.domain as a local delivery in /var/qmail/control/locals or do I need to do something entirly different? There's no wildcard mechanism for control/locals. You'll need to list all of the domains. You could give my patch a try, which adds regular expressions to control/locals. But I have no numbers on performance issues. Look at http://beteigeuze.cs.tu-berlin.de/linux/qmail/ Greetings -- Robert Sander
Supervise won't kill tcpserver
Using the straight script out of LWQ a: script stop will kill smtpd and pop3 supervise, but not the underlying tcpserver and then restarting doesn't work becasue the port is bound. Here's the run files: #!/bin/sh QMAILDUID=`id -u qmaild` NOFILESGID=`id -g qmaild` exec /usr/local/bin/softlimit -m 200 \ /usr/local/bin/tcpserver -v -p -x /etc/tcprules.d/qmail-smtpd.cdb \ -u $QMAILDUID -g $NOFILESGID 0 smtp /var/qmail/bin/qmail-smtpd 21 \ |/usr/local/bin/tai64n |/usr/local/bin/tai64nlocal and #!/bin/sh exec env PATH="/var/qmail/bin:$PATH" \ /usr/local/bin/softlimit -m 200 \ /usr/local/bin/tcpserver -v -R 0 pop-3 qmail-popup famvid.com \ checkpassword qmail-pop3d Maildir 21 \ |/usr/local/bin/tai64n |/usr/local/bin/tai64nlocal Thanks in advance, Bill Get your own FREE, personal Netscape WebMail account today at http://webmail.netscape.com.
RE: What MUA do you use?
Mark E. Drummond wrote: Wrong-o! Want to send a nicely formatted proposal (with appropriate highlights etc) to the department director so you can get funding for that million dollar server upgrade project? Good luck doing it in plain text. And tables? Actually, I've never seen anyone do anything USEFUL like that with it. Real business stuff like that either gets sent as an attached Word or Excel doc, or a PDF. Or paper. You don't just knock up a million dollar proposal on the fly in an email editor, y'know. -Matt -- Matt Brown UNIX Administrator tickets.com Phone: (714) 327-5571 --- Email: [EMAIL PROTECTED]
Mail stuck in queue - what to do about it?
I have 36 messages which appear to be permanently stuck in the queue, I'm running qmail 1.03 with the holdremote patch on Mandrake Linux 6.1. Normally everything runs quite smoothly but I sent a *lot* of mail (by my standards!) last night, probably a few hundred messages in ten minutes or so and these 36 messages have 'stuck'. Most of the messages were to the same destination so I can't see what's special about these. qmail-qstat reports:- messages in queue: 36 messages in queue but not yet preprocessed: 0 qmail-qread reports:- 26 Jan 2000 21:31:44 GMT #20516 1597 [EMAIL PROTECTED] remote [EMAIL PROTECTED] 26 Jan 2000 21:31:44 GMT #20517 1612 [EMAIL PROTECTED] remote [EMAIL PROTECTED] 26 Jan 2000 21:31:45 GMT #20518 2339 [EMAIL PROTECTED] remote [EMAIL PROTECTED] 26 Jan 2000 21:31:45 GMT #20519 3708 [EMAIL PROTECTED] remote [EMAIL PROTECTED] [plus lots more similar] I have tried 'kill -ALRM qmail-send' but that doesn't seem to encourage anything to happen. What do I have to do to get rid of these messages? It doesn't matter too much if there lost even. -- Chris Green ([EMAIL PROTECTED]) Home: [EMAIL PROTECTED] Work: [EMAIL PROTECTED] WWW: http://www.isbd.co.uk/
Re: Mail stuck in queue - what to do about it?
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On 27 Jan 00, at 20:31, Chris Green wrote: I have tried 'kill -ALRM qmail-send' but that doesn't seem to encourage anything to happen. Try running qmail-tcpok _before_ ALRMing qmail-send. What do I have to do to get rid of these messages? It doesn't matter too much if there lost even. Why does it matter then that they're in queue? If they're undeliverable for a week, they'll get deleted (bounced) anyway. -BEGIN PGP SIGNATURE- Version: PGP 6.0.2 -- QDPGP 2.60 Comment: http://community.wow.net/grt/qdpgp.html iQA/AwUBOJC7LlMwP8g7qbw/EQInMACg+g6ygPCq5/X4AmAjtyBwjQ2zXiMAoPUu uwMrydreqnTFg17Z6FOX+fCh =YD2n -END PGP SIGNATURE- -- Petr Novotny, ANTEK CS [EMAIL PROTECTED] http://www.antek.cz PGP key ID: 0x3BA9BC3F -- Don't you know there ain't no devil there's just God when he's drunk. [Tom Waits]
Re: Mail stuck in queue - what to do about it?
On Thu, Jan 27, 2000 at 09:39:58PM -, Petr Novotny wrote: -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On 27 Jan 00, at 20:31, Chris Green wrote: I have tried 'kill -ALRM qmail-send' but that doesn't seem to encourage anything to happen. Try running qmail-tcpok _before_ ALRMing qmail-send. Nothing interesting happens. What do I have to do to get rid of these messages? It doesn't matter too much if there lost even. Why does it matter then that they're in queue? If they're undeliverable for a week, they'll get deleted (bounced) anyway. A good point, maybe I'll just forget about them until they get sent back to me. -- Chris Green ([EMAIL PROTECTED]) Home: [EMAIL PROTECTED] Work: [EMAIL PROTECTED] WWW: http://www.isbd.co.uk/
Re: [Fwd: Strange queue behaviour]
Chris Readle wrote: Faried Nawaz wrote: Chris Readle [EMAIL PROTECTED] writes: Chris Readle wrote: I'm having a bit of strand queue behaviour. Basically I've got 50+ (I think 54, without looking) local-bound messages in the queue that I cannot get to flush no matter what I try. I've tried sending an ALRM, a HUP, stopping and restarting qmail and rebooting the server. The messages are still there. Everything else seems to be running great and new messages are going in and out with no problems, but these message justs won't deliver. Any ideas? chris Show us what the logs say when you try to flush the queue. I think I see the problem, nowI'm getting message has wrong owner and unable to switch to directoryI'll attach the relevant log portion. chris I think I should also mention that new messages to these email addresses go through with nary a problem. One of them is the address that I use to send and receive to the list from! :) chris 948992273.168662 starting delivery 121: msg 230524 to local [EMAIL PROTECTED] 948992273.168675 status: local 1/20 remote 0/30 948992273.171009 delivery 121: deferral: Unable_to_switch_to_/home/chris:_access_denied._(#4.3.0)/ 948992273.171024 status: local 0/20 remote 0/30 948992396.674129 starting delivery 122: msg 230525 to local [EMAIL PROTECTED] 948992396.674143 status: local 1/20 remote 0/30 948992396.674150 starting delivery 123: msg 230524 to local [EMAIL PROTECTED] 948992396.674162 status: local 2/20 remote 0/30 948992396.693089 starting delivery 124: msg 230532 to local [EMAIL PROTECTED] 948992396.693103 status: local 3/20 remote 0/30 948992396.693110 delivery 122: deferral: Unable_to_switch_to_/home/chris:_access_denied._(#4.3.0)/ 948992396.693124 status: local 2/20 remote 0/30 948992396.693131 delivery 123: deferral: Unable_to_switch_to_/home/chris:_access_denied._(#4.3.0)/ 948992396.693145 status: local 1/20 remote 0/30 948992396.693152 starting delivery 125: msg 230522 to local [EMAIL PROTECTED] 948992396.693164 status: local 2/20 remote 0/30 948992396.709790 starting delivery 126: msg 232574 to local [EMAIL PROTECTED] 948992396.709803 status: local 3/20 remote 0/30 948992396.709811 delivery 124: deferral: Unable_to_switch_to_/home/chris:_access_denied._(#4.3.0)/ 948992396.709825 status: local 2/20 remote 0/30 948992396.709832 delivery 125: deferral: Unable_to_switch_to_/home/chris:_access_denied._(#4.3.0)/ 948992396.709846 status: local 1/20 remote 0/30 948992396.728920 starting delivery 127: msg 232568 to local [EMAIL PROTECTED] 948992396.728933 status: local 2/20 remote 0/30 948992396.728940 delivery 126: deferral: Sorry,_message_has_wrong_owner._(#4.3.5)/ 948992396.728952 status: local 1/20 remote 0/30 948992396.750439 starting delivery 128: msg 232590 to local [EMAIL PROTECTED] 948992396.750452 status: local 2/20 remote 0/30 948992396.750459 delivery 127: deferral: Sorry,_message_has_wrong_owner._(#4.3.5)/ 948992396.750471 status: local 1/20 remote 0/30 948992396.768174 starting delivery 129: msg 232601 to local [EMAIL PROTECTED] 948992396.768187 status: local 2/20 remote 0/30 948992396.768194 delivery 128: deferral: Sorry,_message_has_wrong_owner._(#4.3.5)/ 948992396.768206 status: local 1/20 remote 0/30 948992396.772692 starting delivery 130: msg 230533 to local [EMAIL PROTECTED] 948992396.772705 status: local 2/20 remote 0/30 948992396.772712 delivery 129: deferral: Sorry,_message_has_wrong_owner._(#4.3.5)/ 948992396.772724 status: local 1/20 remote 0/30 948992396.786670 starting delivery 131: msg 232600 to local [EMAIL PROTECTED] 948992396.786683 status: local 2/20 remote 0/30 948992396.786690 delivery 130: deferral: Unable_to_switch_to_/home/chris:_access_denied._(#4.3.0)/ 948992396.786704 status: local 1/20 remote 0/30 948992396.787520 starting delivery 132: msg 232577 to local [EMAIL PROTECTED] 948992396.787533 status: local 2/20 remote 0/30 948992396.787540 delivery 131: deferral: Sorry,_message_has_wrong_owner._(#4.3.5)/ 948992396.787551 status: local 1/20 remote 0/30 948992396.802177 starting delivery 133: msg 232604 to local [EMAIL PROTECTED] 948992396.802190 status: local 2/20 remote 0/30 948992396.802197 delivery 132: deferral: Sorry,_message_has_wrong_owner._(#4.3.5)/ 948992396.802208 status: local 1/20 remote 0/30 948992396.820684 starting delivery 134: msg 232591 to local [EMAIL PROTECTED] 948992396.820697 status: local 2/20 remote 0/30 948992396.820704 delivery 133: deferral: Sorry,_message_has_wrong_owner._(#4.3.5)/ 948992396.820716 status: local 1/20 remote 0/30 948992396.839303 starting delivery 135: msg 232575 to local [EMAIL PROTECTED] 948992396.839316 status: local 2/20 remote 0/30 948992396.839323 delivery 134: deferral: Sorry,_message_has_wrong_owner._(#4.3.5)/ 948992396.839335 status: local 1/20 remote
Re: Mail stuck in queue - what to do about it?
On Thu, Jan 27, 2000 at 12:39:11PM -0800, Mark Delany wrote: On Thu, Jan 27, 2000 at 08:31:09PM +, Chris Green wrote: I have 36 messages which appear to be permanently stuck in the queue, I'm running qmail 1.03 with the holdremote patch on Mandrake Linux 6.1. Normally everything runs quite smoothly but I sent a *lot* of mail (by my standards!) last night, probably a few hundred messages in ten minutes or so and these 36 messages have 'stuck'. Most of the messages were to the same destination so I can't see what's special about these. What did you conclude from looking at the log messages associated with sending these messages? Do the log messages indicate a reason why they might be "stuck"? Is it a reason that you can fix? Is it a reason that someone else is likely to fix? Aha, a good point, sorry! They have been 'deferred' because the sender domain doesn't resolve, I 'bounced' them using mutt so the From: address doesn't change and they were originally from a domain that no longer exists! Thanks for your help - I must remember to look in the logs next time, a bit like RTFM but it's RTFL. -- Chris Green ([EMAIL PROTECTED]) Home: [EMAIL PROTECTED] Work: [EMAIL PROTECTED] WWW: http://www.isbd.co.uk/
DNS
Hi All! How can I get the MX record for my domain? I don't have direct access to the DNS. Thanks JES
Re: DNS
* Juan E Suris ([EMAIL PROTECTED]) [27 Jan 2000 18:47]: How can I get the MX record for my domain? I don't have direct access to the DNS. If you mean: How do I register the MX record for my domain: When you registered the domain, there were at least two DNS entries. Get the person(s) who operate/own these machines to add a MX record for your domain that points to the _name_ of your machine. If you mean: What machine does the MX record for my domain point to: Use either of the following two commands: % host -t mx domain.name or if this fails: % host -t a domain.name -- Quist ConsultingEmail: [EMAIL PROTECTED] 219 Donlea DriveVoice: +1.416.696.7600 Toronto ON M4G 2N1 Fax: +1.416.978.6620 CANADA WWW: http://www.quist.on.ca
Re: DNS
Thanks. My problems is that remote mail is not arriving. The qmail logs shows no SMTP acitivity what so ever, so this lead me to think that the MX is wrong, but to my untrained eye it seems right. [suris@domain qmail]# host -t mx domain.com domain.com.domain.com is a nickname for www.domain.com www.domain.com mail is handled (pri=10) by mail.domain.com where mail.domain.com has same IP as domain.com. All TEST.local tests passed. Any suggestions. JES How can I get the MX record for my domain? I don't have direct access to the DNS. If you mean: How do I register the MX record for my domain: When you registered the domain, there were at least two DNS entries. Get the person(s) who operate/own these machines to add a MX record for your domain that points to the _name_ of your machine. If you mean: What machine does the MX record for my domain point to: Use either of the following two commands: % host -t mx domain.name or if this fails: % host -t a domain.name -- Quist Consulting Email: [EMAIL PROTECTED] 219 Donlea Drive Voice: +1.416.696.7600 Toronto ON M4G 2N1 Fax: +1.416.978.6620 CANADA WWW: http://www.quist.on.ca
Re: DNS
On Thu, Jan 27, 2000 at 07:25:09PM -0500, Juan E Suris wrote: Thanks. My problems is that remote mail is not arriving. The qmail logs shows no SMTP acitivity what so ever, so this lead me to think that the MX is wrong, but to my untrained eye it seems right. [suris@domain qmail]# host -t mx domain.com domain.com.domain.com is a nickname for www.domain.com www.domain.com mail is handled (pri=10) by mail.domain.com where mail.domain.com has same IP as domain.com. It is *really* annoying when someone asks a question about suspected DNS problems, and then disguises his domain name with a phoney one. Anyway, in your case it looks like you have your MX record pointing at a CNAME. Don't do that. Chris
Re: DNS
Anyway, in your case it looks like you have your MX record pointing at a CNAME. Don't do that. And, of course, fire your DNS admin. BIND will complain very clearly in the logs if you're pointing MX at a CNAME. If they haven't been watching the logs, then they are asking for very large problems. steve
Re: DNS
I am sorry if I was annoying, but my server has not been security tested yet so I don't want to make it public until it is. When the time is right I will not be so _annoying_. CNAME? JES On Thu, Jan 27, 2000 at 07:25:09PM -0500, Juan E Suris wrote: Thanks. My problems is that remote mail is not arriving. The qmail logs shows no SMTP acitivity what so ever, so this lead me to think that the MX is wrong, but to my untrained eye it seems right. [suris@domain qmail]# host -t mx domain.com domain.com.domain.com is a nickname for www.domain.com www.domain.com mail is handled (pri=10) by mail.domain.com where mail.domain.com has same IP as domain.com. It is *really* annoying when someone asks a question about suspected DNS problems, and then disguises his domain name with a phoney one. Anyway, in your case it looks like you have your MX record pointing at a CNAME. Don't do that. Chris
RE: FLUSH QUEUE
Title: RE: FLUSH QUEUE properly reading the documentation will reveil that if you send an ALRM to qmail-send daemon, it will then start flushing the queue, although qmail will do this automatically after a while of idling --Stephen -Original Message- From: root [mailto:root]On Behalf Of TAG Sent: Thursday, January 27, 2000 7:52 PM To: [EMAIL PROTECTED] Subject: FLUSH QUEUE HI ALL, IS there a way of flushing the qmail queue - PLEASE HELP!!! Many thanks _Tonino
Re: big fat qmail-command hole
On Wed, Jan 26, 2000 at 09:23:39PM -0800, Faried Nawaz wrote:
Stig Hackvän wrote:
qmail invokes commands with /bin/sh regardless of the user's login shell, so even
if a user has /bin/false for a shell, that user's .qmail file can be used to gain
shell access.
And how does someone with /bin/false as their shell put commands in their
.qmail files?
ftp is one way.
i consider this to be a qmail bug.
I consider it a site-specific administrative problem.
is it reasonable to use the shell field of the password database to permit or deny
shell access to a username. qmail should respect this.
stig
--
Stig... Friend of Hacking ... 707-987-3236 work@home
Hackvän ... http://hackvan.com ... 415-264-8754 mobile
We are {b}Org ... http://brainofstig.AI ... [EMAIL PROTECTED]
Re: big fat qmail-command hole
It's probably not a good idea to be using an ftp config that allows users
with non-real shells to log in. That's generally considered a Bad Thing
(tm). If you really want something that supports virtual-style users well,
look into NcFTPd. It's (mostly) commercial, and closed-soruce, but it does
the job very well.
At 11:07 PM 1/27/00 , you wrote:
On Wed, Jan 26, 2000 at 09:23:39PM -0800, Faried Nawaz wrote:
Stig Hackvän wrote:
qmail invokes commands with /bin/sh regardless of the user's login
shell, so even if a user has /bin/false for a shell, that user's .qmail file
can be used to gain shell access.
And how does someone with /bin/false as their shell put commands in their
.qmail files?
ftp is one way.
i consider this to be a qmail bug.
I consider it a site-specific administrative problem.
is it reasonable to use the shell field of the password database to permit
or deny
shell access to a username. qmail should respect this.
stig
--
Stig... Friend of Hacking ... 707-987-3236 work@home
Hackvän ... http://hackvan.com ... 415-264-8754 mobile
We are {b}Org ... http://brainofstig.AI ... [EMAIL PROTECTED]
---
Phil Genera [EMAIL PROTECTED]
Sysadmin, http://www.troop474.org/
Upgrade causing temporary failure
I recently "upgraded" to the latest versions of ucspi-tcp and daemontools on my qmail based MX. Although it seems to be operating just fine, I get the following messages on the console: supervise: fatal: unable to acquire qmail-send/supervise/lock: temporary failure supervise: fatal: unable to acquire log/supervise/lock: temporary failure supervise: fatal: unable to acquire qmail-smtpd/supervise/lock: temporary failure supervise: fatal: unable to acquire log/supervise/lock: temporary failure Here is one of the directories in question: ls -l /var/qmail/supervise/qmail-send/supervise total 2 prw--- 1 root other 0 Jan 27 23:34 control| -rw--- 1 root other 0 Jan 27 23:30 lock prw--- 1 root other 0 Jan 27 23:30 ok| -rw-r--r-- 1 root other 18 Jan 27 23:35 status This is on Solaris 7. Compared against my Slackware Linux box, everything looks the same. The 2 are set up identically. -- ___ Mark Drummond|ICQ#19153754|mailto:[EMAIL PROTECTED] Gang Warily|http://signals.rmc.ca/
Re: What MUA do you use?
Chris Garrigues wrote: Sounds like a job for PDF. It'll even look the same everywhere. PDF is very nice, I'd love to see it as a defacto standard, if not PS, but Acrobat costs $$$ and I refuse to spend $$$ on something when a perfectly good (free) alternative is available. Not only do I work at a cash strapped educational institution, it's a government cash strapped educational instituion! We have standardised (for better or worse) on Netscape Communicator so there is generally no problem with the content being rendered wrong. -- ___ Mark Drummond|ICQ#19153754|mailto:[EMAIL PROTECTED] Gang Warily|http://signals.rmc.ca/
Re: big fat qmail-command hole
On Thu, Jan 27, 2000 at 08:07:28PM -0800, Stig Hackvän wrote: is it reasonable to use the shell field of the password database to permit or deny shell access to a username. qmail should respect this. The problem, as I see it, is that qmail is more flexible than e.g. sendmail and not only uses the regular passwd db /etc/passwd to get the users homedir. This means that all users may not even have an regular "account" on the machine which is actually does the receiving/delivering pert of the MT process. What could be done is, however is to patch qmail-local to honour (i.e. let them override the default "/bin/sh") the shells in /etc/passwd for those users that actually _have_ regular accounts. For really paranoid implementations, this patch could be made to DENY (default to /bin/false) shell for those who lack shell in /etc/passwd. One question arise: Is there ANY security issues WHATSOEVER to use the shell defined in /etc/passwd? Only root should be able to change /etc/passwd. So if root assignes a cracked shell to a user, then this is not a problem in qmail-land? I leave the patching as an exercise to the reader. /magnus -- http://x42.com/
Re: subdomain qmail locals
On 27-Jan-00 Scott Schappell wrote: SNIP That also has to assume the MX entry is correct for his domain, that all mail goes to that machine. In my example: silvertree.org IN MX 10 arthur.silvertree.org. The FAQ I am referencing is: http://cr.yp.to/qmail/faq/incominghost.html#local SNIP I have read this FAQ but failed to understand it because I did not know what they meant by DNS entry. Maybe I should explain the situation a little better. I am not the server administrator. I am just a Perl programmer trying to make things work correctly for a program I wrote. The server administrator told me the only way to get mail from anyone@sub.domain was to add an entry in /var/qmail/control/locals for each sub.domain. I did not believe him because the amount of entries in that file could be over 3000 (eek) so I tested it and my test email was bounced. I sent an email to [EMAIL PROTECTED] domain was entered in /var/qmail/control/locals but sub.domain was not. There was a line in /etc/aliases.cdb for [EMAIL PROTECTED] to be delivered to me@domain and the email bounced. The log said that qmail was not trying to deliver it locally. The program I am writting will just need to set up forwards for people that do not have an actual local email account just a subdomain account. I guess what my question should have been was where do I need to make entries when someone signs up for an email forward account? The forwards will be done with fastforward and I have already made the script that writes them to /etc/aliases.cdb. Sorry for the confusion Scott - E-Mail:Scott Beck [EMAIL PROTECTED] Address: 3542 Pine Bettle Ln. Sulphur La. 70663 Phone: (318) 527-9518 Date: 27-Jan-00 Time: 23:40:16 -
Re: subdomain qmail locals
On 27-Jan-00 Robert Sander wrote: On Thu, Jan 27, 2000 at 12:48:51PM -0500, Dave Sill wrote: Scott Beck [EMAIL PROTECTED] wrote: How do I set *.domain as a local delivery in /var/qmail/control/locals or do I need to do something entirly different? There's no wildcard mechanism for control/locals. You'll need to list all of the domains. You could give my patch a try, which adds regular expressions to control/locals. But I have no numbers on performance issues. Look at http://beteigeuze.cs.tu-berlin.de/linux/qmail/ Greetings -- Robert Sander I just downloaded that patch. You said you do not have any benchmark results from it but do you think is will be faster to do ^([^\.]+\.)?domain$ or list 3000 sub.domain. Both at this point are an option. Thanks Scott - E-Mail:Scott Beck [EMAIL PROTECTED] Address: 3542 Pine Bettle Ln. Sulphur La. 70663 Phone: (318) 527-9518 Date: 28-Jan-00 Time: 00:19:34 -
Sleeping qmail
Hi, I am working on qmail-1.03 on red-hat linux 6.1. I accidently deleted files named 1, 2, 3, etc from /var/qmail/queue/local and mess. now qmail shows: Jan 28 12:09:57 alok qmail: 949041597.388541 alert: unable to opendir mess/0, sleeping... Jan 28 12:10:07 alok qmail: 949041607.398535 alert: unable to opendir mess/0, sleeping... and does not accept any messages for delivery. I re-created the files and folders in above directories, but they were of no use. Is there a way to solve this problem. thanks Alok
Re: Duplicates on outbound mail, not inbound
The DNScache package includes a dnstrace tool that's designed to debug these problems. ``dnstrace 15 briefme.com 192.5.5.241'' shows that * one of the briefme.com servers is down; * one of the servers says briefme.com MX remove-it.com; * the other three servers listed by the parent say briefme.com MX mail.remove-it.com and briefme.com MX 209.191.19.113; and * yet another server, not listed by the parent but listed by some of the children, also says briefme.com MX mail.remove-it.com and briefme.com MX 209.191.19.113. There are, by the way, many subscribers to the qmail list whose domains show similar inconsistencies between DNS servers. Mark Delany writes: I get different results when querying that domain with dnscache and bind. Random in both cases. An initial query to an empty cache is more likely to get the mail.remove-it.com and 209.191.19.113 results, because that's available from three out of the four immediately accessible servers; but a query to an active cache is more likely to get the other result, which has a much larger TTL. ---Dan
Open Relay
Sir, I am using Qmail and I want to receive mail for "mynet.com.pk" and want to forward it to our another mailserver "welcome.mynet.com.pk" for relaying. But I want to make the Qmail an open relay too. So i deleted recpthosts to make open relay. I put "mynet.com.pk" in locals but not in rcpthosts. I put ":welcome.mynet.com.pk" in smtproutes. Now what i get problem is that, whenever I receive mail for "mynet.com.pk" Qmail tries to deliver it locally and doeasn't forward it to "welcome.mynet.com.pk". Would you plz. tell me that how to do this ?
