inetd
As instructed by the installation guide, I placed an entry for smtp into inetd.conf. However, the entry: smtpstream tcp nowait qmaild /var/qmail/bin/tcp-env \ tcp-env /var/qmail/bin/qmail-smtpd doesn't seem to pay any attention to /etc/hosts.deny. I tried prefacing it with tcpd, but that didn't do much good either. Suggestions? -- Todd A. Jacobs Network Systems Engineer
virtual email problem
Hello, I'm having this kind of error message when delivering to a virtual email: 1999-10-11 14:41:34.825523500 starting delivery 12402: msg 165908 to local [EMAIL PROTECTED] 1999-10-11 14:41:34.825537500 status: local 1/10 remote 20/20 1999-10-11 14:41:34.851102500 delivery 12402: failure: Sorry,_no_mailbox_here_by_that_name._(#5.1.1)/ I noticed that all virtual emails with '.' (i.e. civil.engg) has this error. Is there a work-around on this? I just migrated from Sendmail to Qmail and never expected this would happen. Thanks. _Bench
Re: inetd
inetd is not recommended anymore. One feature of inetd which is heavily used by tcp-wrappers is that it passes the first argument as argv[0] which is usually the command itself. Therefore you have to remove the single tcp-env after the command line, this will read: smtp stream tcp nowait qmaild /path/to/tcpd /var/qmail/bin/tcp-env /var/qmail/bin/qmail-smtpd Thomas Heisenberg may have slept here... - T h o m a s Z e h e t b a u e r ( TZ251 ) PGP encrypted mail preferred - KeyID 96FFCB89 mail [EMAIL PROTECTED] - PGP signature
Re: Selective relaying and ORBS
Sorry to cause a worry. The problem turned out to be the % hack, but not on the qmail box. It acts as a relay for another box running sendmail. It was the sendmail doing the %hack and then forwarding the message back to the qmail box for deleviery. Thanks for the help all the same. John. John Newbigin wrote: I just received a message from the ORBS database. It seems that qmail has a bug.feature which allows relaying of messages in the form jn%it.swin.edu.au@[1.2.3.4] Where 1.2.3.4 is the IP address of my mail server, not for it.swin.edu.au. (I don't want everyone on the list to try it :). The machine should accept mail for 1.2.3.4, but the message is actualy sent to [EMAIL PROTECTED] The mail relay should only accept mail for [EMAIL PROTECTED] I have tcpd set up to allow relaying only from machines inside 1.2.3.0 Is there a way to dissable this feature/bug. If you want to test your system, use the telnet service from here http://maps.vix.com/tsi/ar-test.html I am sure that there are many people with a simalar setup which could pose a large spam risk. I would appreciate a speedy reply. John. -- Information Technology Innovation Group Swinburne University. Melbourne, Australia http://uranus.it.swin.edu.au/~jn -- Information Technology Innovation Group Swinburne University. Melbourne, Australia http://uranus.it.swin.edu.au/~jn
Re: virtual email problem
On Mon, 11 Oct 1999, Benjamin de los Angeles Jr. wrote: I noticed that all virtual emails with '.' (i.e. civil.engg) has this error. Is there a work-around on this? I just migrated from Sendmail to Qmail and never expected this would happen. It's documented. Use ':' instead of '.' when setting up local aliases, and the incoming dots will get handled properly. -- Todd A. Jacobs Network Systems Engineer
Re: inetd
On Mon, 11 Oct 1999 [EMAIL PROTECTED] wrote: One feature of inetd which is heavily used by tcp-wrappers is that it passes the first argument as argv[0] which is usually the command itself. Therefore you have to remove the single tcp-env after the command line, this will read: smtp stream tcp nowait qmaild /path/to/tcpd /var/qmail/bin/tcp-env /var/qmail/bin/qmail-smtpd I tried your suggestion, but the same thing happened as before: the remote site connects, but the localhost closes the connection after about 3 seconds. I *did* read the install guides, and while it recommends tcpserver for heavily-used environments, my needs aren't so great. I really don't want to have to run a seperate service for this. -- Todd A. Jacobs Network Systems Engineer
Re: problem with svscan in daemontools 0.61
George Hong writes: 1. I have qmail, qmail-smtpd, qmail-pop3d directories under directory /var/lock/qmailsvc with run script in each directory. When I run svscan in /var/lock/qmailsvc, the processes will all be invoked and work. If I put it in the script, it will give the error message and fails: Are you sure that svscan can find supervise in $PATH? 2. The second question is that it doesn't write to the log file, all the message will be displayed at the console window. svscan takes care of DIR/log only when DIR is sticky. -- Tetsu Ushijima
Re: virtual email problem
Thanks, but now I'm trying to give a supervised qmail-send a HUP signal by svc -h /var/supervise/qmail/send but it won't work, my virtualdomains file is not reread. Regards, _Bench On Mon, 11 Oct 1999, Todd A. Jacobs wrote: On Mon, 11 Oct 1999, Benjamin de los Angeles Jr. wrote: I noticed that all virtual emails with '.' (i.e. civil.engg) has this error. Is there a work-around on this? I just migrated from Sendmail to Qmail and never expected this would happen. It's documented. Use ':' instead of '.' when setting up local aliases, and the incoming dots will get handled properly. -- Todd A. Jacobs Network Systems Engineer
Re: Shadow Password and checkpassword
Ng Hak Beng [EMAIL PROTECTED] schrieb/wrote: After looking through the archive, is checkpassword able to authenticate shadow passwords? I've got a RH 6 box running qmail, but I don't seem to be able to authenticate through pop3. Yes, it works with shadow passwords. Have you installed checkpassword (which is aspearate package) and checked all programme paths and paramters? -- Claus Andre Faerber http://www.faerber.muc.de PGP: ID=1024/527CADCD FP=12 20 49 F3 E1 04 9E 9E 25 56 69 A5 C6 A0 C9 DC
qmail Digest 11 Oct 1999 10:00:06 -0000 Issue 786
qmail Digest 11 Oct 1999 10:00:06 - Issue 786
Topics (messages 31441 through 31488):
Re: Beware when patching Solaris machines
31441 by: Harald Hanche-Olsen
31442 by: Stig Sandbeck Mathisen
Files and Directories ownership for Qmail
31443 by: Subba Rao
Re: Queue stalls
31444 by: Jos Backus
Qmail won't start
31445 by: Subba Rao
Supervise command
31446 by: Subba Rao
31447 by: Magnus Bodin
31450 by: Subba Rao
31469 by: Magnus Bodin
Test
31448 by: David Summers
31449 by: David Summers
Starting as a daemon in rc*
31451 by: Todd A. Jacobs
31470 by: Magnus Bodin
daemontools 0.61
31452 by: B. Engineer
31453 by: Frank D. Cringle
Security considerations of chown qmaill
31454 by: Todd A. Jacobs
David Sill's startup script
31455 by: Subba Rao
No man pages installed?
31456 by: Todd A. Jacobs
31457 by: Markus Stumpf
31459 by: Todd A. Jacobs
Qmailanalog Equivalent
31458 by: Karl Lellman
Address Substitution
31460 by: Subba Rao
31461 by: Todd A. Jacobs
31462 by: Subba Rao
31477 by: Todd A. Jacobs
getting qmail to retry
31463 by: Phil Howard
31465 by: Sam
31466 by: Phil Howard
31468 by: Sam
31475 by: Phil Howard
qmailanalog documentation
31464 by: Ben Beuchler
qmail-inject: fatal: qq read error (#4.3.0)
31467 by: Vince Vielhaber
ECHOMAIL/MENTADENT
31471 by: Robert
control/{locals,rcpthosts,virtualdomains}
31472 by: Franck PORCHER
31473 by: Magnus Bodin
Qmail-Inject error related to Datemail
31474 by: Jon Lurås
Selective relaying and ORBS
31476 by: John Newbigin
31478 by: Ken Jones
31479 by: John Newbigin
31483 by: John Newbigin
inetd
31480 by: Todd A. Jacobs
31482 by: thomasz.hostmaster.org
31485 by: Todd A. Jacobs
virtual email problem
31481 by: Benjamin de los Angeles Jr.
31484 by: Todd A. Jacobs
31487 by: Benjamin de los Angeles Jr.
Re: problem with svscan in daemontools 0.61
31486 by: Tetsu Ushijima
Re: Shadow Password and checkpassword
31488 by: Claus Färber
Administrivia:
To subscribe to the digest, e-mail:
[EMAIL PROTECTED]
To unsubscribe from the digest, e-mail:
[EMAIL PROTECTED]
To bug my human owner, e-mail:
[EMAIL PROTECTED]
To post to the list, e-mail:
[EMAIL PROTECTED]
--
+ Giles Lean [EMAIL PROTECTED]:
| On Thu, 07 Oct 1999 00:35:51 +0200 Harald Hanche-Olsen wrote:
|
| Now, one or more of these patches "upgraded" /usr/lib/sendmail
|
| I make my startup scripts remove /usr/lib/sendmail and re-create the
| symlink that I want, just in case.
Good idea! Now, why didn't I think of that simple solution?
| The introduction of a new startup file is harder to deal with, of
| course.
Well, one could just have a script that runs
rm -f /etc/rc?.d/[SK]??sendmail
as early as possible.
Russ, something for the tips section on .qmail.org?
- Harald
* Harald Hanche-Olsen (Thu, Oct 07, 1999 at 12:35:51AM +0200)
Our sysadmin installed a bunch of patches on our Solaris machines
today - basically, he just got a cluster of recommended patches and
installed them all.
Now, one or more of these patches "upgraded" /usr/lib/sendmail (was a
symlink to /var/qmail/bin/sendmail, became a "real" sendmail). But
not only that; the patch most helpfully installed the file
/etc/rc2.d/S88sendmail for us. Came time to reboot the machine, and
lo and behold, we now had a running sendmail daemon, which started
rejecting all kinds of incoming mail. (It got to the smtp port before
tcpserver+qmail-smtpd did.)
To prevent sendmail from starting at boot, remove
/etc/sendmail.cf, as the /etc/init.d/sendmail script exits if
that does not exist.
As Giles Lean mentioned: If you run Solaris with sonething else
than Solaris stock sendmail installed, you need to check at
every boot (and after every patch) that it hasn't "repaired" the
sendmail installation.
If you're feeling _really_ paranoid, make sure these commands
are in the script used to start, stop, restart and reload qmail
(if you use such a thing), and not only in a script run only at
boot. (Not every Solaris patch package requires a reboot. You
might be surprised one day. :-)
--
SSM - Stig Sandbeck Mathisen
Trust the Computer, the Computer is your Friend
This is my 3rd attempt at installing and getting to qmail to work.
I was distracted with different work during the previous 2 attempts,
When I execute the command at #9 in the INSTALL, the "rc" script
exits immediately. I am doing this as root.
When I list the contents of /var/qmail directory, all the directories ownership
is under ROOT:QMAIL.
Is this the way the file ownership should
Re: qmail-inject: fatal: qq read error (#4.3.0)
On Sun, 10 Oct 1999, Vince Vielhaber wrote: What are some possible causes for this error? qmail-inject: fatal: qq read error (#4.3.0) Friday everything was fine, today I can't send mail. The above was from /var/qmail/bin/mailsubj, but I get the same from pine. Mail is coming in just fine it's just locally generated mail (and it's not going thru smtp). I've run make setup check figuring something may have changed, no go. There's plenty of disk space too. Anyone have an idea? Vince. Following up to my own.. There was an odd message in the queue consisting of only a Received line and a dot. It was also the only message there, so I dumped the entire queue directory and did a make setup check and all is well again. Vince. -- == Vince Vielhaber -- KA8CSH email: [EMAIL PROTECTED] flame-mail: /dev/null # include std/disclaimers.h Have you seen http://www.pop4.net? Online Campground Directoryhttp://www.camping-usa.com Online Giftshop Superstorehttp://www.cloudninegifts.com ==
dot before @
Hi I have this problem: A customer has an virtual domain on our mailserver (qmail-ldap 1.03, ldap has no nothing to do with it) but we forward all mail to an external address (Netscape Messaging Server). His email address on the remote server is [EMAIL PROTECTED] (yes, with an dot before the at). OK, so far so good and it works. BUT as soon as the message enters our qmail system the local part gets quoted, it looks then like this: "vonbueren.rm."@bluewin.ch. Now the remote server doesn't like that and tells me "550 Invalid recipient". Who is wrong now? qmail for quoting the local part (which is legal AFAIK) or is it Netscape's Messaging Server for not decoding the quoted local part? I don't have a problem telling the customer he is wrong but I want to be sure that I'm right. :-) -- Andre
Anti Spamming
Hi Can any one tell me a solution for blocking mails on subject. I have a customer who gets wierd mails form different sites , the mails originate from different site everytime , thus i am not able to use the badmail from feature as it is not a fixed site. Any clue or help would be highly appreciated. Thanks in advance FONR mailto:[EMAIL PROTECTED]
Re: control/{locals,rcpthosts,virtualdomains}
Franck PORCHER [EMAIL PROTECTED] wrote on Mon, 11 Oct 1999: What would be the best way to configure qmail to have this specific address ([EMAIL PROTECTED]) remotely delivered to my ISP (say "mail.pf"), so any local mail to [EMAIL PROTECTED] would eventually end-up in his remote mailbox. ? Well, if there is no local user called "jean", you can create a file ~alias/.qmail-jean and put the address [EMAIL PROTECTED] (or whatever) there. Any email to [EMAIL PROTECTED] will get forwarded to [EMAIL PROTECTED] I thought of putting [EMAIL PROTECTED]:alias-myisp in "control/virtualdomains", No, you can't put usernames in control/virtualdomains. You can only use full domain names. List the domains which should be handled virtually. The delivery of those domains is controlled by the specified user (in your case, ~alias-myisp, the ~alias/.qmail-myisp-* files). Hope this helps, Mikko -- // Mikko Hänninen, aka. Wizzu // [EMAIL PROTECTED] // http://www.iki.fi/wiz/ // The Corrs list maintainer // net.freak // DALnet IRC operator / // Interests: roleplaying, Linux, the Net, fantasy scifi, the Corrs / "Apple" (c) 6024 b.c., Adam Eve
Re: control/{locals,rcpthosts,virtualdomains}
Mikko Hänninen writes: Franck PORCHER [EMAIL PROTECTED] wrote on Mon, 11 Oct 1999: I thought of putting [EMAIL PROTECTED]:alias-myisp in "control/virtualdomains", No, you can't put usernames in control/virtualdomains. As of qmail 1.03, you can. It's the replacement for recipientmap. The purpose of this feature is to be able to override addresses which would otherwise be sent elsewhere. -- -russ nelson [EMAIL PROTECTED] http://russnelson.com Crynwr sells support for free software | PGPok | Government schools are so 521 Pleasant Valley Rd. | +1 315 268 1925 voice | bad that any rank amateur Potsdam, NY 13676-3213 | +1 315 268 9201 FAX | can outdo them. Homeschool!
Re: getting qmail to retry
Phil Howard [EMAIL PROTECTED] schrieb/wrote: I understand that it is a permanent failure code. But clearly a full mailbox is not a true permanent situation. Usually, this is upon the receiving MTA to decide. If it thinks that it is not really permanent, it will send a 452 response instead of 552. What I was looking for is if there was a table of response codes and how to act when receiving them. Because of scattered documentation for qmail that means I haven't yet found everything, ... Well, if you write or modify an implementation of a protocol, you should read and understand the protocol specification. For SMTP, this is RFC 821 and ist designated successor draft-ietf-drums- smtpup-10.txt: ftp://ftp.isi.edu/in-notes/rfc821.txt http://www.ietf.org/internet-drafts/draft-ietf-drums-smtpud-10.txt And yes, you will have to hack qmail-remote for this. -- Claus Andre Faerber http://www.faerber.muc.de PGP: ID=1024/527CADCD FP=12 20 49 F3 E1 04 9E 9E 25 56 69 A5 C6 A0 C9 DC
Re: Sqwebmail and IMAP
Sam [EMAIL PROTECTED] schrieb/wrote: Then what you will have to ask yourself is whether you want all your folders shared by every one of your incoming maildirs. I could consider the proposal of storing all folders in ../Mail, however what I don't like about this approach is that you're now in conflict with your mail apps who use $HOME/Mail to store traditional mailbox-file folders. Which, when patched, will look for and store maildirs there, won't they? And if you do use maildirs, all of your MUAs should be able to handle maildirs or you won'tbe able to access your messages no matter where you store them. If you think of maildirs as an alternative to the mailbox _file_ format, ~/Mail/ is the obvious solution. For folders that should contain both messages and subdirs, you could create a subdirectory named ".default" to hold messages that look as if they were stored in the parent folder. This is compatible with MUAs that don't expect to see subfolders in maildirs (such as mutt). If you then fake a link from ~/Mail/.default/ or ~/Mail/INBOX/ (depends on the protocol you're using/implementing) to $MAILDIR, you have a complete hierarchical namespace. -- Claus Andre Faerber http://www.faerber.muc.de PGP: ID=1024/527CADCD FP=12 20 49 F3 E1 04 9E 9E 25 56 69 A5 C6 A0 C9 DC
Re: Anti Spamming
On Mon, Oct 11, 1999 at 06:17:24PM +0530, FONR wrote: Hi Can any one tell me a solution for blocking mails on subject. I have a customer who gets wierd mails form different sites , the mails originate from different site everytime , thus i am not able to use the badmail from feature as it is not a fixed site. Any clue or help would be highly appreciated. Although I think blocking mail on subject is a really bad idea, I would have installed procmail and give a .procmailrc as a present to my customer: #--- MAILDIR=$HOME/Mail DEFAULT=$HOME/Mailbox :0: * ^Subject:.*broccoli.* /dev/null #--- (or if you use Maildir, substitute maildrop for procmail) -- magnus -- MOST useless 1998 * http://x42.com/
About relaying after POP
Hi all: Okay, last week I sent an email asking about how to configure Bruce Guenter's "relay-ctrl" program to allow relaying after POP. This is just to confirm that it's working now, and that the cause of the previous malfunction was an error on my part: I had thought that "/var/spool/relay-ctrl", which the program needs to operate, was a file, when it was a directory. Once I created said directory, it worked without problems. Just in case it might be useful as reference for someone in the future... Paulo Jan. DDnet.
Re: inetd
don't use inetd but use tcpserver, see qmail-howto http://www.flounder.net/qmail/qmail-howto.html marco leeflang "Todd A. Jacobs" wrote: As instructed by the installation guide, I placed an entry for smtp into inetd.conf. However, the entry: smtpstream tcp nowait qmaild /var/qmail/bin/tcp-env \ tcp-env /var/qmail/bin/qmail-smtpd doesn't seem to pay any attention to /etc/hosts.deny. I tried prefacing it with tcpd, but that didn't do much good either. Suggestions? -- Todd A. Jacobs Network Systems Engineer
Re: problem with svscan in daemontools 0.61
Is /usr/local/bin in PATH at the time the initscript is run? Mate
Re: dot before @
On Mon, Oct 11, 1999 at 02:06:34PM +0200, Andre Oppermann [EMAIL PROTECTED] wrote: I have this problem: His email address on the remote server is [EMAIL PROTECTED] (yes, with an dot before the at). The above is an illegal encoding of the address: [EMAIL PROTECTED] Dots are required to have words on both sides in the local part of the address. OK, so far so good and it works. BUT as soon as the message enters our qmail system the local part gets quoted, it looks then like this: "vonbueren.rm."@bluewin.ch. That is a valid rfc 821 encoding of the address: [EMAIL PROTECTED] Now the remote server doesn't like that and tells me "550 Invalid recipient". Who is wrong now? qmail for quoting the local part (which is legal AFAIK) or is it Netscape's Messaging Server for not decoding the quoted local part? Assuming there is a valid user of vonbueren.rm. at bluewin.ch, the Netscape server is broken. However it may be that the person is advertising the wrong email address for themselves.
Qmail 1.01 ignores percenthack settings
Folks, I have Qmail 1.01 with several patches (Qmail antispam and a fix for \n termination) According to qmail-showctl, the percenthack is disabled. However, it works for any IP on the server except for the actual fqdn of the mail host. When I send a message to [EMAIL PROTECTED] (the official name) I get a bounce saying no such user. When I send a message to [EMAIL PROTECTED] (a virtual web host on same machine) it sends the message. I've tried with an empty percenthack file and no percenthack file. I can't seem to disable percenthacks and now I'm on the ORBS list. Is this a known issue with 1.01 or am I missing something? I want to turn it off globally. Thanks, Craig
inetd
The problem seems to lie somewhere with tcp-env. Here is a line from my logs: Oct 10 23:23:57 tjacobs tcp-env[1184]: refused connect from shell11.ba.best.com So, it seems like tcp-env is actually refusing the connection. Any ideas on how to debug this further? -- Todd A. Jacobs Network Systems Engineer
those damn hackers
Hello: Yesterday was the first time I got to test my qmail system with the big to-do patch applied. Problem: Some $%^* hijacked a T1 line somewhere and started spamming using a return address that points to my system. The sheer number of bounces generated, slows legitimate mail down on my system by 6 hrs. I had applied the big to-do patch in hopes of fixing that. My local concurrency is set to 40 and remote to 120. I had 4000 messages in my mail queue but qmail was not delivering mail for about 3 hrs. I had about 45 qmail-queue processes. The machine had plenty of juice, the load av. never shot up over 1.5-2.0. Local/Remote concurrency never shot up, logs showed a max of 2/40 and 6/120. Can anyone explain this? I want qmail to chew/hog the cpu and deliver the mail. What am I forgetting to tune?? Thanks Burzin
Re: those damn hackers
What was your memory usage? What was your disk i/o like? Bandwidth to the net? Could be any number of things. Anything in your regular system logs during that time that might provide a clue? On Mon, 11 Oct 1999, B. Engineer wrote: Hello: Yesterday was the first time I got to test my qmail system with the big to-do patch applied. Problem: Some $%^* hijacked a T1 line somewhere and started spamming using a return address that points to my system. The sheer number of bounces generated, slows legitimate mail down on my system by 6 hrs. I had applied the big to-do patch in hopes of fixing that. My local concurrency is set to 40 and remote to 120. I had 4000 messages in my mail queue but qmail was not delivering mail for about 3 hrs. I had about 45 qmail-queue processes. The machine had plenty of juice, the load av. never shot up over 1.5-2.0. Local/Remote concurrency never shot up, logs showed a max of 2/40 and 6/120. Can anyone explain this? I want qmail to chew/hog the cpu and deliver the mail. What am I forgetting to tune?? Thanks Burzin - Timothy L. Mayo mailto:[EMAIL PROTECTED] Senior Systems Administrator localconnect(sm) http://www.localconnect.net/ The National Business Network Inc. http://www.nb.net/ One Monroeville Center, Suite 850 Monroeville, PA 15146 (412) 810- Phone (412) 810-8886 Fax
Removing messages from the queue (another one)
Hi there, Hopefully someone can help me with a problem we're having with (probably) qmail. Main system feature is : Solaris 2.6 / Webshield SMTP As part of the Webshield virus scanner, a version of qmail appears to have been installed. We use sendmail as the main connection to the Internet. The qmail system appears to have a number of messages which can't be delivered, and since these are multi-megabyte in size, they quickly fill up the 300Mb of free space we have in the root partition. The question is, can I delete these messages from the queue directory structure? I've tried deleting the files manually, but while I can temporarilly remove them from the mess/nn subdirectory, they re-appear sometime later. The only other reference to these files is in the intd directory. Again I've tried deleting them from there. Even stopping qmail, deleting the files (they went from both intd and mess subdirs) and restarting qmail. They're starting to come back ... where else are these damned messages stored? The fact is they are junk and can be deleted. I suspect that there is a delivery problem (eg server not responding/not accepting the messages) so they're not being bounced as undeliverable. There isn't the disk space available to have qmail timeout these messages gracefully after the 40 failed attempts. I've yet to try changing the file message date on the file in the mess subdirs. Does anyone have any other suggestions. I note from all the other questions relating to message deletions, that the intd directory rarely gets a mention. Is this something uniqe to the fact we're running Webshield? Thanks for any assistance you can give. Wallace Nicoll. -- == Wallace Nicoll [EMAIL PROTECTED] City of Edinburgh Council IT Services, Chesser House, 500 Gorgie Road,Phone : 0131 469 5343 Edinburgh, EH11 3YJ, ScotlandFax : 0131 469 5335 [From overseas [P]+441314695343 [F]+441314695335 ] ==
Re: dot before @
Andre Oppermann [EMAIL PROTECTED] schrieb/wrote: Who is wrong now? qmail for quoting the local part (which is legal AFAIK) or is it Netscape's Messaging Server for not decoding the quoted local part? It's Netscape again. Local parts that are not dot-atom strings (which can't start or end with a dot) must be encoded, which qmail does correctly. A server not accepting local-parts in encoded form is seriously broken. -- Claus Andre Faerber http://www.faerber.muc.de PGP: ID=1024/527CADCD FP=12 20 49 F3 E1 04 9E 9E 25 56 69 A5 C6 A0 C9 DC
Re: those damn hackers
On Mon, 11 Oct 1999, Timothy L. Mayo wrote: What was your memory usage? What was your disk i/o like? Bandwidth to the net? Could be any number of things. Anything in your regular system logs during that time that might provide a clue? I was not thrashing. I beleive I had 400M of free memory. I am not sure about the disk i/o. bandwidth to the net was plentiful. My queue is on a local disk but the actual user mail boxes are on a NFS drive. Nothing extraordinary in the logs. On Mon, 11 Oct 1999, B. Engineer wrote: Hello: Yesterday was the first time I got to test my qmail system with the big to-do patch applied. Problem: Some $%^* hijacked a T1 line somewhere and started spamming using a return address that points to my system. The sheer number of bounces generated, slows legitimate mail down on my system by 6 hrs. I had applied the big to-do patch in hopes of fixing that. My local concurrency is set to 40 and remote to 120. I had 4000 messages in my mail queue but qmail was not delivering mail for about 3 hrs. I had about 45 qmail-queue processes. The machine had plenty of juice, the load av. never shot up over 1.5-2.0. Local/Remote concurrency never shot up, logs showed a max of 2/40 and 6/120. Can anyone explain this? I want qmail to chew/hog the cpu and deliver the mail. What am I forgetting to tune?? Thanks Burzin - Timothy L. Mayo mailto:[EMAIL PROTECTED] Senior Systems Administrator localconnect(sm) http://www.localconnect.net/ The National Business Network Inc.http://www.nb.net/ One Monroeville Center, Suite 850 Monroeville, PA 15146 (412) 810- Phone (412) 810-8886 Fax
Re: dot before @
Claus Färber wrote: Andre Oppermann [EMAIL PROTECTED] schrieb/wrote: Who is wrong now? qmail for quoting the local part (which is legal AFAIK) or is it Netscape's Messaging Server for not decoding the quoted local part? It's Netscape again. Local parts that are not dot-atom strings (which can't start or end with a dot) must be encoded, which qmail does correctly. A server not accepting local-parts in encoded form is seriously broken. Ahh, great, that is what I wanted to hear! :-) BTW, the time on your workstation looks pretty wrong, almost 19 hours behind. Cheers -- Andre
Re: Sqwebmail and IMAP
Most MUAs are now using IMAP, so this is quickly becoming irrelevant. IMAP is not appropriate for an ISP, because the ISP wants to get rid of the email. POP is not appropriate for a campus environment, because it's better to control mail backups on a central server, and because IMAP works with multiple clients (e.g. desktops and laptops, or work machines and home machines). I don't see either protocol going away. -- -russ nelson [EMAIL PROTECTED] http://russnelson.com Crynwr sells support for free software | PGPok | Government schools are so 521 Pleasant Valley Rd. | +1 315 268 1925 voice | bad that any rank amateur Potsdam, NY 13676-3213 | +1 315 268 9201 FAX | can outdo them. Homeschool!
Re: dot before @
On Mon, Oct 11, 1999 at 07:27:37PM +0200, Andre Oppermann wrote: Claus Färber wrote: Andre Oppermann [EMAIL PROTECTED] schrieb/wrote: Who is wrong now? qmail for quoting the local part (which is legal AFAIK) or is it Netscape's Messaging Server for not decoding the quoted local part? It's Netscape again. Local parts that are not dot-atom strings (which can't start or end with a dot) must be encoded, which qmail does correctly. A server not accepting local-parts in encoded form is seriously broken. Ahh, great, that is what I wanted to hear! :-) BTW, the time on your workstation looks pretty wrong, almost 19 hours behind. More like 13 hours. -- Brad Shelton On Line Exchange http://online-isp.com
Re: getting qmail to retry
Sam [EMAIL PROTECTED] schrieb/wrote: On 11 Oct 1999, ([ISO-8859-1] Claus Färber) wrote: http://www.ietf.org/internet-drafts/draft-ietf-drums-smtpud-10.txt That draft doesn't exist. http://www.ietf.org/internet-drafts/draft-ietf-drums-smtpupd-10.txt ^ Sorry, mistyped the URI. On second thought, I really don't want to know what these people want to do with SMTP. Ugh, what a frightening thought... It's not a new version of SMTP if that is what you're afraid of. It only collects some important extensions (such as Extended SMTP/EHLO) and clarifications. -- Claus Andre Faerber http://www.faerber.muc.de PGP: ID=1024/527CADCD FP=12 20 49 F3 E1 04 9E 9E 25 56 69 A5 C6 A0 C9 DC
Re: Sqwebmail and IMAP
Sam [EMAIL PROTECTED] schrieb/wrote: And how would you propose handling a virtual mailbox farm, mailboxes that have no dedicated system userid assigned to them? It's not exactly obvious, is it? Where would you put mailbox files then? Simply put your maildirs there. This is no less obvious if you consider maildirs a replacement for mbox files. Most MUAs are now using IMAP, so this is quickly becoming irrelevant. Then simply do whatever your imapd does and don't worry about compatibility. On the other hand, maybe there are different IMAP servers, web gateways etc. that should use the same strucutre. In other words: Why use an incompatible format if you can use one that is already there? No longer relevant. Any MUA worth its salt is capable of using IMAP, right now, no matter how ugly IMAP really is. So, all you have to do is standardize on an IMAP server, Yes, and the best solution IMO is to use the "standard" that has already been set by user agents. -- Claus Andre Faerber http://www.faerber.muc.de PGP: ID=1024/527CADCD FP=12 20 49 F3 E1 04 9E 9E 25 56 69 A5 C6 A0 C9 DC
Re: getting qmail to retry
=?ISO-8859-1?Q?Claus_F=E4rber?= writes: On second thought, I really don't want to know what these people want to do with SMTP. Ugh, what a frightening thought... It's not a new version of SMTP if that is what you're afraid of. It only collects some important extensions (such as Extended SMTP/EHLO) and clarifications. No, it does more than just that. I just read it. My initial suspicions were correct. -- Sam
Re: dot before @
Brad Shelton [EMAIL PROTECTED] schrieb/wrote: BTW, the time on your workstation looks pretty wrong, almost 19 hours behind. More like 13 hours. Well, exactly time-of-day hours. (My UA is configured to always send 00:00:00 - for privacy reasons.) -- Claus Andre Faerber http://www.faerber.muc.de PGP: ID=1024/527CADCD FP=12 20 49 F3 E1 04 9E 9E 25 56 69 A5 C6 A0 C9 DC
Re: Sqwebmail and IMAP
Russell Nelson [EMAIL PROTECTED] schrieb/wrote: Most MUAs are now using IMAP, so this is quickly becoming irrelevant. IMAP is not appropriate for an ISP, because the ISP wants to get rid of the email. Depends on the ISP. Some ISPs consider that additional value and do even provide Webmail -- or mutt over ssh. ;-) -- Claus Andre Faerber http://www.faerber.muc.de PGP: ID=1024/527CADCD FP=12 20 49 F3 E1 04 9E 9E 25 56 69 A5 C6 A0 C9 DC
alias header mods causing problems
I set up a simple alias something like: [EMAIL PROTECTED] to forward to [EMAIL PROTECTED] (which pages me) and it just seems to blackhole. Syslog shows a successful delivery to their smtp server, I get no bounce message, and they don't respond to any questions about it. The only thing I can think of is they filter on the To: header, presumably as an anti-spam measure. As I intend to be VERY judicious about who gets this address, I'm not so concerned about spam. Is there a fairly simple way to modify the outgoing header of an alias to preserve the To: address of the recipient? TIA,
Re: Qmail-Inject error related to Datemail
On Mon, 11 Oct 1999, [ISO-8859-1] Jon Lurås wrote: Hello! I have a problem, here is what my qmail log says: 939620707.238895 status: local 1/10 remote 0/20 939620710.595702 delivery 1: success: qmail- inject:_fatal:_read_error/did_1+0+1/ 939620710.620806 status: local 0/10 remote 0/20 The first time I got this error was with the Vacation program from Peter Samuel. The Vacation program uses Datemail. When I removed Vacation from the .qmail file and used Datemail directly I still got the error. I have tried with Forward in the .qmail and this works okay. I am quite sure that this problem has something to do with permissions. I have look at all the permissions in the /var/qmail/bin and in the /home/user/Maildir/ with no success so far. The system is a Redhat 6.0 and I used the qmail-1.03-14ucspi.src.rpm for installation. Just to expand on Jon's problem (we've gone through quite a bit of offline debugging outside the list). The problem occurs whenever qmail runs a program from a .qmail file that calls datemail. eg | vacation jon or | /var/qmail/bin/datemail -t /home/jon/msg Both of these fail. Jon, three more things you might try: 1) Double check the permissions on /var/qmail/control/*. ALl the files in that directory MUST be readable by everyone. If qmail-inject cannot open /var/qamil/control/me (for example) it will die. When you did your manual test of datemail what user were you? If you were root it would have worked, if you were some other user and it failed, then that could be your problem. 2) modify vacation so that it uses qmail-inject (modify the Makefile and run make install) 3) recompile datemail Regards Peter -- Peter Samuel[EMAIL PROTECTED] Technical Consultantor at present: eServ. Pty Ltd [EMAIL PROTECTED] Phone: +61 2 9206 3410 Fax: +61 2 9281 1301 "If you kill all your unhappy customers, you'll only have happy ones left"
Re: Sqwebmail and IMAP
=?ISO-8859-1?Q?Claus_F=E4rber?= writes: Russell Nelson [EMAIL PROTECTED] schrieb/wrote: Most MUAs are now using IMAP, so this is quickly becoming irrelevant. IMAP is not appropriate for an ISP, because the ISP wants to get rid of the email. Depends on the ISP. Some ISPs consider that additional value and do even provide Webmail -- or mutt over ssh. ;-) I think that most ISPs are reluctant to offer IMAP because UW-IMAP server is such a bloated pig. I know for a fact that that's why at least one major national ISP claimed was the major reason they declined to offer it. -- Sam
qmail fail when start with supervise?
I seems to have problem running qmail with supervise. when I start qmail using supervise, it start off working fine, but after a while it would begin to fail. mail are not delivered and preprocessed. restarting qmail make qmail start deliverying mail again but after a while the problem would come back again. I am running qmail 1.03 (compiled from source) with the qmail.init script contained in the package qmail-run-4.tar.gz. Redhat Linux 6.0 kernel 2.12, SMP, 512Mb ram, and lots of traffic. any idea what went wrong? any suggstion would be appreciated. Thanks. Victor.
Re: Sqwebmail and IMAP
I think that most ISPs are reluctant to offer IMAP because UW-IMAP server is such a bloated pig. I know for a fact that that's why at least one major national ISP claimed was the major reason they declined to offer it. There has also been a history of security problems with UW IMAP. "bloat" I can live with, root security exploits I can not. I haven't seen any reports of UW IMAP exploits for awhile though. Tim
Re: Sqwebmail and IMAP
Sam writes: I think that most ISPs are reluctant to offer IMAP because UW-IMAP server is such a bloated pig. In my experience, the IMAP protocol is the bloated pig. -- -russ nelson [EMAIL PROTECTED] http://russnelson.com Crynwr sells support for free software | PGPok | Government schools are so 521 Pleasant Valley Rd. | +1 315 268 1925 voice | bad that any rank amateur Potsdam, NY 13676-3213 | +1 315 268 9201 FAX | can outdo them. Homeschool!
Yes, inetd DOES work!
Inetd works fine. Nowhere in the FAQ does it say it doesn't. And I got it to work on my system...eventually. The problem seems to have been that inetd (or possibly tcpd) is very picky about spacing when parsing certain command lines. The following (from the FAQ, BTW) worked fine: smtp stream tcp nowait qmaild /usr/sbin/tcpd /var/qmail/bin/tcp-env /var/qmail/bin/qmail-smtpd For some reason, spacing it with tabs like other lines in inetd.conf caused it to misbehave. Luckily, that's all finished now, and it's been a very polite daemon ever since. Remember today's lesson: perseverence! :) -- Todd A. Jacobs Network Systems Engineer
