qmail, Maildir, IMAP, and MS Outlook
Before folks start flaming me, I know Outlook sucks and I know that Microsoft has never written a decent piece of code. With that said... I am using qmail, because it is the best mail server out there. I would like to be able to configure MS Outlook so that it interacts with qmail the same way it does with Exchange. Or at least similar in the respect that one can manage folders and move mail around and it all stays on the server. My understanding is that IMAP is the solution. I have installed courier-IMAP, but from that mailing list I have learned that Outlook is not a standard MUA with respect it IMAP, or anything else for that matter. Does anyone know of a IMAP server that get along with Outlook 2000 and that works with Maildir/? Sam
Log entry: success: did_0+0+0???
Good Morning to all, especially those burning the midnite oil! This evening I caught my qmail/vpopmail server not doing it's job. I would like to keep it from happening in the future, and to help fill in some blank spots as to what really makes this thing work. This server runs about 10 virtual domains, but only handles maybe 20 - 100 messages per hour. Light usage, I would guess. For about the last 30 hours or so, it appears that all incoming mail has been accepted for my domain 'sasnak.net', and then vaporized. All other domains mail has been delivered successfully. All log entries show this for 'sasnak.net' delivery 28: success: did_0+0+0/ and the messages are nowhere to be found. A search of the mailing list caused me to look at permissions/ownerships, so I created a new domain (test.com) and compared these things. Nothing turned up. Out of desperation, I tried echo to: [EMAIL PROTECTED] | /var/qmail/bin/qmail-inject and the messages was delivered properly. I thought maybe tcpserver qmail-smtp might have been causing it, but before going any further, I tried sending myself a message via sqwebmail, and it worked. It previously had not been working. All the incoming mail has been delivered correctly since then. My specific questions are these. Where did the mail go during this time? What caused it to start working? Not my qmail-inject, I'm sure. How do I keep it from happening again? Where is there more info on the "success: did_0+0+0" and "success: did_0+0+1" log messages? I have seen a few other numbers or combinations in here and would like to know what they mean. As a "probably not important" footnote, I had installed BigBrother on this server in the last two weeks, but had made no changes recently. As part of my troubleshooting, I had rebooted the machine and had not restarted BigBrother about one hour before this started working again. Thank You, Sam Laffere Just a clip of the logs: Mar 24 23:10:30 moe qmail: 985497030.206191 info msg 112050: bytes 289 from [EMAIL PROTECTED] qp 980 uid 1008 Mar 24 23:10:30 moe qmail: 985497030.214839 starting delivery 28: msg 112050 to local [EMAIL PROTECTED] Mar 24 23:10:30 moe qmail: 985497030.215062 status: local 1/10 remote 0/20 Mar 24 23:10:30 moe qmail: 985497030.226354 delivery 28: success: did_0+0+0/ Mar 24 23:10:30 moe qmail: 985497030.226584 status: local 0/10 remote 0/20 Mar 24 23:10:30 moe qmail: 985497030.226741 end msg 112050 Mar 24 23:13:19 moe qmail: 985497199.789656 new msg 112050 Mar 24 23:13:19 moe qmail: 985497199.790402 info msg 112050: bytes 291 from [EMAIL PROTECTED] qp 1021 uid 1008 Mar 24 23:13:19 moe qmail: 985497199.798631 starting delivery 29: msg 112050 to local [EMAIL PROTECTED] Mar 24 23:13:19 moe qmail: 985497199.799290 status: local 1/10 remote 0/20 Mar 24 23:13:19 moe qmail: 985497199.26 delivery 29: success: did_0+0+1/ Mar 24 23:13:19 moe qmail: 985497199.889097 status: local 0/10 remote 0/20 Mar 24 23:13:19 moe qmail: 985497199.889254 end msg 112050 Mar 24 23:14:16 moe qmail: 985497256.084798 new msg 112050 Mar 24 23:14:16 moe qmail: 985497256.085545 info msg 112050: bytes 293 from [EMAIL PROTECTED] qp 1041 uid 1008 Mar 24 23:14:16 moe qmail: 985497256.092490 starting delivery 30: msg 112050 to local [EMAIL PROTECTED] Mar 24 23:14:16 moe qmail: 985497256.092706 status: local 1/10 remote 0/20 Mar 24 23:14:16 moe qmail: 985497256.126467 delivery 30: success: did_0+0+0/ Mar 24 23:14:16 moe qmail: 985497256.126758 status: local 0/10 remote 0/20 Mar 24 23:14:16 moe qmail: 985497256.126914 end msg 112050
Re: Time zones in Qmail.
How do I change the timezone information that qmail puts in the received header? Qmail is running on openbsd 2.8. There is a patch for the Qmail source that addresses this issue over at http://www.qmail.org/ I had someone in sales ask for this patch [1], and I was able to apply this patch without any problems. - Sam [1] Sales people are nortorious for wanting to have a time stamp for the exact time they sent or received an email. In their time zone.
Re: Bogus Popularity claims (sendmail.org's reply)
[Snip. Typical cluless marketing BS about people moving form UNIX to Windows 2000, since Windows 2000 is so obviously more secure, scalale, and low-cost for running a SMTP server, than, say a Linux+Qmail or a OpenBSD+Qmail setup] Jan. 25, 2000 This is out of date. http://www.sirana.com/smtp/results.asp The whole domain sirana.com is dead right now. I guess marketing BS about how Windows 2000 is going to replace perfectly secure and scalable Qmail systems had no reality to it. Hence, it could not survive the dot-com bloodbath. MailSite 4 I love their claims of scalibility with their mail server. "UNIX-like scalability at a fraction of the cost". Hurrumph. How much does it cost to put Linux and Qmail on an old Pentium or Pentium II? They claim their mail server is secure, but the security is not up to par with Qmail's security: http://www.securityfocus.com/bid/1244 - Sam
Re: qmail with mysql patch - solaris
On Wed, 31 Jan 2001, Rudel Sun-woo wrote: however, when i run qmail-getpw after compiling, i get this error message: Segmentation Fault (Memory Dump) Error please help! In summary: * Use truss to get a sense of where the seg fault is happening * Compile the program with the '-g' switch and analyze the core file with dbm * Try compiling it with gcc instead, which can be obtained over at http://sunfreeware.com. - Sam
Re: pop3 / vhosts
On Tue, 30 Jan 2001, Gonalo Gomes wrote:
"Mailbox" mailbox format, i've added "defusion.org:goncalo" to
virtualdomains and rcpthosts control file's
Hopefully, the line in rcpthosts is:
defusion.org
now my problem is:
i want create a pop3 accounts, [EMAIL PROTECTED] and,
[EMAIL PROTECTED] as a fetch-all
* Create a local user named rik on your machine
* ~goncalo/.qmail-rik needs to point to Rik's email address, e.g.
give this the file the contents 'rik' (no quotes!)
* Have a ~goncalo/.qmail-default which points mail to goncalo's mailbox
('goncalo')
- Sam
Re: Secure IMAP server
Get a life, Sam. Really. Sigh, oh, sigh. I haven't heard a word from you in three years, so I thought that you, like me, completely forgot about it. For the other members of the list, I am sorry this personal spat, which I thought I had resolved with Robin three years ago, has been taken to this list. I could post details, but, you know, there is nothing I dislike seeing more on the internet than someone else's flame war. Since I do not think Robin is willing to really listen to me, and since I don't exactly have free time these days, I will simply filter Robin's mail to my spam filter. Since I do, now and again, check the mail that my spam filter stops, I will still read Robin's mail, should be be really interested in resolving this issue at some time in the future. Sorry to waste people's time with this flame war. Take care, Robin, and I hope you find what you are looking for. I apologized for engaging in that flame war three years ago, and I apologize to you again. I really do not want to see any anger you may have stop you from finding your bliss. - Sam
Re: Error: #4.4.2 - connected but connection died
On Mon, 29 Jan 2001, Joel Gautschi wrote: hi, I get this error when user try to send a message to freesurf.ch. Is this my problem, or is it the problem of freesurf.ch? cya Joel Jan 29 11:30:57 joshua qmail: 980764257.483799 delivery 1: deferral: Connected_to_194.230.0.8_but_connection_died._(#4.4.2)/ This comes up because either you, or the ISP you are talking to has a flakey internet connection which dies before the message can be sent. How large are these messages that keep getting deferred? A lot of places can not handle 20 meg attachments and what not. - Sam (Who recently had our entire system upgraded so people could send us 100 meg attachments)
Re: qmail or postfix for high volume mailing list?
Oh boy, since this is cross-posted to both the qmail and to the Postfix list, this could become a holy war. I myself have never used Postfix, but have used Qmail. My general sense: * Postfix and Qmail both are very hi-performance MTAs * Qmail apprently has slightly better performance for mailing list stuff, Postfix has slightly more performance for indivudal mailboxes. * Postfix is more open-source than Qmail * Postfix is easier to configure than Qmail * Qmail is more flexible than Postfix You will be happy with whatever choice you make. And oh, I would up your RAM to 128 megs. - Sam Can someone tell me: Should I use qmail or postfix to run this discussion list?
Re: unsubscribe ??
Kevin asked: how do I unsubscribe? there is no info on qmail.org?? Normally, we charge a one-time fee of $59.95 for this service, as Peter has explained. However, I am offering a special contest, since it is the year 2001 (a Qmail odyssey). The winner of this contest will get a message from the Qmail list server asking for their subscription to be confirmed. In order to enter this contest, simply reply to this message or send an entry form to [EMAIL PROTECTED] I wish you the best of luck! And, oh, Peter, you know that Dan's server runs Open-BSD, so those Russian thermonuclear devices will not harm the server. He just has to enter (and hopefully win) the contest, just like everyone else has to. - Sam
Re: filter
Hello! I'm a new user of qmail. I need filter a direction [EMAIL PROTECTED], how can I do it? I am not sure what you are asking, but I assume that you need to filter mail sent to [EMAIL PROTECTED] The method of doing this depends on whether yyy.zzz is a virtualdomain, or is the name of the mail server in question. For simplicity's sake, I will assume the latter. Assuming that xxx is a user on the machine yyy.zzz, make a file in xxx's home directory called .qmail. Put in that file: |/path/to/filter/program If this does not meet your needs, I assume that you speak Spanish far better than I do. In that case, the Spanish Qmail docs are here: http://www.es.qmail.org/ The English docs are at: http://www.qmail.org/ - Sam
Re: QSBMF -
On Mon, 29 Jan 2001, Michael T. Babcock wrote: It would be nice if someone convinced Microsoft et. al. (in the Windows E-mail client world) to support the reading and parsing of QSBMF in the same way Outlook already does this for Exchange server based E-mail. I don't think will happen any time soon. Microsoft knows that there is a lot of money in the server business. They know that many technically minded people do not like Microsoft. So, they go to some effort to make their client software make their own proprietary, expensive, low-performance servers look more attractive to the end user using Microsoft software than any non-Microsoft product that performs the same functions. They figure, if enough end-users demand Microsoft servers so "They can get more helpful bounce messages in Exchange" or what-not, that some shops will make the migration. Look at Front Page extensions. Not that this is any threat to Qmail. As long as end-users subscribe to mailing lists on Egroups [1], people can and will complain if a Microsoft client can't handle a Qmail server correctly. - Sam [1] I believe Egroups is one of the most visible Qmail installations out there.
Re: Qwest.net Qmail - online presentation..
[Chris: We're discussing your presentation on the Qmail list] On Sat, 27 Jan 2001, Steve Fulton wrote: http://www.users.qwest.net/~presentations/cmikk/ I notice that Chris Mikkelson and the people at qwest.net use multiple qmail-sends on multiple queues, with a note that qmail-send is the big bottleneck. I wonder if they are using the big concurrency patch. Once the big concurrency patch is installed, it is trivial to get a concurrency of 500. The 500 number is based on Linux's limits--I would not be surprised if FreeBSD has far bigger limits. This means we can send out 500 messages at any given instant. Let us suppose that 99% of the messages can be delivered to the remote machine in one second, and 1% of the messages take 60 seconds (one minute) to deliver or time out. [1] With this simplified model, our imaginary high-traffic mail server can handle a continuous stream of the maximum concurrency of our qmail-send process multiplied by .625. Which means a concurrency of 500 can handle about 300 messages a second, which is well over a million messages a day. In fact, with a concurrency of 500, a heavily loaded mail server should handle over a million messages in an hour. - Sam [1] 60 seconds is how long qmail-remote will wait before giving up on a dead host.
Re: Newbie... couple of basic questions...
I been having problems with sending out e-mail (i.e. not at all) OK, some things to check: Is /usr/sbin/sendmail and /usr/lib/sendmail a symlink to /var/qmail/bin/sendmail Are the qmail processes (which you start with '/var/qmail/rc ' in /etc/rc.d/rc.local) running. Run 'ps -ef | grep qmail' and see if Qmail is there. And, since you mentioned that you are a Newbie sysadmin using RH7, please, pretty please update (or get rid of) the various remote root exploits that RedHat 7 comes with. More information at: http://www.redhat.com/support/errata/rh7-errata-security.html A Linux box that can be remotely rooted is a headache to the entire internet community. - Sam
Re: webmail solution
What about using a simple http server that has cgi-bin support, such as thttpd? More info: http://www.acme.com/software/thttpd/ - Sam I need something that doesn't require a full-featured http server (e.g. Apache) to be installed on the mail server (my mail server and web server are 2 different machines).
Re: Secure IMAP server
On Sun, 28 Jan 2001, Andy Bradford wrote: For more on its security I believe there is a document called SECURITY in the code tree somewhere which discusses it's approach to security---you might have a look at that. The only security document I could find in the source tarball for courier-0.30.0 has this note: This document discloses security-oriented issues regarding the SqWebMail CGI application. However, the web pages make references to Courier's security model. The writers of Courier are a pedantic bunch. They reject mail with 8-bit info in the headers and will not send mail to places with "improperly configured MX records". - Sam
Re: DotFiles
I am not sure what you are asking. ~username/.qmail is the file that determines how to process mail sent to [EMAIL PROTECTED] (where yourmachine.example.org is your machine, e.g. globalred.com). ~username/.qmail-foo is the file the determines how to process mail sent to [EMAIL PROTECTED] Now, if /var/qmail/control/virtualdomains has a line like this: heaven.af.mil:username The mail sent to [EMAIL PROTECTED] will be processed in qmail as [EMAIL PROTECTED] (the ~username/.qmail-foo file). And mail sent to any undefined address @heaven.af.mil will be processed as [EMAIL PROTECTED] (the ~username/.qmail-default file). Read the relevent Qmail docs, FAQs, and man pages for more information. - Sam Hi, I install qmail Memphis version with dt-run services with virtualdomains using assign file. And I have a little problem: The file .qmail is of the user is processed but the files .qmail-jkljklsdfsdjkl no. Any person can say me why??? Thanks.
Re: Qmail with FreeBSD very very slow!
Get rid of it. sendmail is much better now. Sam [EMAIL PROTECTED] wrote: Hi! Delivery of 200 local emails: FreeBSD 4.2: 300 Sec FreeBSD 4.0: 70 Sec SuSE Linux : 6 Sec /var/qmail/lock/trigger has the right permission settings! I'm sure something is wrong with *MY* FreeBSD Setup!! Any ideas? Thank you in advance! joe output of my disklabel: # /dev/ad0c: type: ESDI disk: ad0s1 label: flags: bytes/sector: 512 sectors/track: 63 tracks/cylinder: 255 sectors/cylinder: 16065 cylinders: 1866 sectors/unit: 29993292 rpm: 3600 interleave: 1 trackskew: 0 cylinderskew: 0 headswitch: 0 # milliseconds track-to-track seek: 0 # milliseconds drivedata: 0 8 partitions: # size offset fstype [fsize bsize bps/cpg] a: 2048000 0 4.2BSD 1024 8192 16 # (Cyl. 0 - 127*) b: 1228800 2048000 swap # (Cyl. 127*- 203*) c: 29993292 0 unused 0 0 # (Cyl. 0 - 1866*) e: 12288000 3276800 4.2BSD 1024 8192 16 # (Cyl. 203*- 968*) f: 4096000 15564800 4.2BSD 1024 8192 16 # (Cyl. 968*- 1223*) g: 10332492 19660800 4.2BSD 1024 8192 16 # (Cyl. 1223*- 1866*) dmesg: FreeBSD 4.2-RELEASE #0: Mon Nov 20 13:02:55 GMT 2000 [EMAIL PROTECTED]:/usr/src/sys/compile/GENERIC Timecounter "i8254" frequency 1193182 Hz CPU: AMD Athlon(tm) Processor (700.03-MHz 686-class CPU) Origin = "AuthenticAMD" Id = 0x621 Stepping = 1 Features=0x183f9ffFPU,VME,DE,PSE,TSC,MSR,PAE,MCE,CX8,SEP,MTRR,PGE,MCA,CMOV, PAT,PSE36,MMX,FXSR> AMD Features=0xc040AMIE,DSP,3DNow!> real memory = 134201344 (131056K bytes) config> di sn0 config> di lnc0 config> di ie0 config> di fe0 config> di cs0 config> di bt0 config> di aic0 config> di aha0 config> di adv0 config> q avail memory = 126373888 (123412K bytes) Preloaded elf kernel "kernel" at 0xc0436000. Preloaded userconfig_script "/boot/kernel.conf" at 0xc043609c. Pentium Pro MTRR support enabled md0: Malloc disk npx0: math processor> on motherboard npx0: INT 16 interface pcib0: Host to PCI bridge> on motherboard pci0: PCI bus> on pcib0 pcib2: VIA 82C598MVP (Apollo MVP3) PCI-PCI (AGP) bridge> at device 1.0 on pci0 pci1: PCI bus> on pcib2 pci1: ATI Mach64-GD graphics accelerator> at 0.0 irq 11 isab0: VIA 82C686 PCI-ISA bridge> at device 4.0 on pci0 isa0: ISA bus> on isab0 atapci0: VIA 82C686 ATA66 controller> port 0xb800-0xb80f at device 4.1 on pci0 ata0: at 0x1f0 irq 14 on atapci0 ata1: at 0x170 irq 15 on atapci0 chip2: VIA 82C686 AC97 Audio> port 0xa000-0xa003,0xa400-0xa403,0xa800-0xa8ff irq 10 at device 4.5 on pci0 rl0: RealTek 8139 10/100BaseTX> port 0x9400-0x94ff mem 0xe180-0xe18000ff irq 5 at device 13.0 on pci0 rl0: Ethernet address: 00:00:21:f8:d0:70 miibus0: MII bus> on rl0 rlphy0: RealTek internal media interface> on miibus0 rlphy0: 10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, auto pcib1: Host to PCI bridge> on motherboard pci2: PCI bus> on pcib1 fdc0: NEC 72065B or clone> at port 0x3f0-0x3f5,0x3f7 irq 6 drq 2 on isa0 fdc0: FIFO enabled, 8 bytes threshold fd0: 1440-KB 3.5" drive> on fdc0 drive 0 atkbdc0: Keyboard controller (i8042)> at port 0x60,0x64 on isa0 atkbd0: AT Keyboard> flags 0x1 irq 1 on atkbdc0 kbd0 at atkbd0 psm0: PS/2 Mouse> irq 12 on atkbdc0 psm0: model IntelliMouse, device ID 3 vga0: Generic ISA VGA> at port 0x3c0-0x3df iomem 0xa-0xb on isa0 sc0: System console> at flags 0x100 on isa0 sc0: VGA 16 virtual consoles, flags=0x300> sio0 at port 0x3f8-0x3ff irq 4 flags 0x10 on isa0 sio0: type 16550A sio1 at port 0x2f8-0x2ff irq 3 on isa0 sio1: type 16550A ppc0: Parallel port> at port 0x378-0x37f irq 7 on isa0 ppc0: SMC-like chipset (ECP/EPP/PS2/NIBBLE) in COMPATIBLE mode ppc0: FIFO with 16/16/8 bytes threshold plip0: PLIP network interface> on ppbus0 lpt0: Printer> on ppbus0 lpt0: Interrupt-driven port ppi0: Parallel I/O> on ppbus0 ad0: 14649MB IBM-DTLA-307015> [29765/16/63] at ata0-master UDMA66 acd0: CDROM ASUS CD-S400/A> at ata1-master using PIO4 Mounting root from ufs:/dev/ad0s1a -- Sam Wun Firewalls / Security Software Engineer (Snr) Electronic Commerce eSec Limited Phone: +61 3 83715376 (Direct) Mobile: 0403 381 621 mailto:[EMAIL PROTECTED] C++/JAVA/UNIX/OOP/OOD
Re: No,there are 144000 mails in my queue!!!
JF, I just had to deal with the same problem. It was a dictionary spam is what somebody called it. On my server, they where in the remote outgoing queue, but I believe the fix is the same. Keep in mind, I had never worked with python, and the little script was a python script. Luckily, my server already had python installed. The non-existant documentation meant I had to trial and error this, but here is a summary of what I did. Go to this location, and get this script onto your server, I put mine in /var/qmail/bin. http://www.redwoodsoft.com/~dru/programs/mailRemove.py Make it executable. chmod +x mailRemove.py Create the directory filter under qmail/queue. Mine was like this mkdir /var/qmail/queue/filter Next run the script in a test-only mode. You can CTRL-C out of it. python mailRemove.py [search-string] Since all my spam flood was from [EMAIL PROTECTED] my command looked like this, python mailRemove.py registrar If this runs, then you can do this for real. It moves the spam into the filter directory. I halted both qmail-send and smtp before doing this. Like this. python mailRemove.py --real registrar I had 28000 spams, and it took about 5 hours to remove 18000 of these. This server was only a 486/100, 32meg ram. Hopefully it will be lots faster on a better machine. While I am here, I wish to thank Mark and Markus for your help yesterday regarding my problem. Sam - Original Message - From: "jf" [EMAIL PROTECTED] To: [EMAIL PROTECTED] Sent: Friday, December 15, 2000 9:09 AM Subject: No,there are 144000 mails in my queue!!! Most of them are the same. Pls tell me how to deal with it. I have put the mail from address to the badmailfrom,but it wouldn't stop. I hate Sparm === ΪÄã¶ø½¨£¬ÎªÄã¶øÉ裬ÈÃÄã´«µÝÕæÐÄÕæÒâ 163.netºØ¿¨Õ¾£¨http://ecard.163.net£© 163µç×ÓÓʾÖȫзîÏ×£¬¾«²ÊÎÞÏ޵ĵç×Ӻؿ¨Õ¾¡£ ===
Re: Secondary MX (Was: Mail flood in queue)
Thanks for the input. Here is how it turned out, and my summary of the situation. I own both servers, and have been trying to figure out the best implimentation of redundancy. By having the secondary server in place, the primary server was slowed down, but it never failed to accept or deliver mail the whole time. Granted, while the secondary was trying to feed into the primary, some new incoming was pushed off onto the secondary. I feel that this put very little legitimate mail at risk. Keep in mind, I did not know for sure that I could dump the spam, yet. I only knew that if I waited long enuf, it would eventually clear out. My mistake was that I had two virtual domains running on that secondary server throughout all of this. Lack of time(read as lazyness) is the only reason that I had never moved them off of this particular server. Incoming mail for these two domains was working fine, but outgoing mail was being held up in the queue. Lesson here is do not put primary functions on a secondary machine. It removes your ability to just turn it off while you think about the problem. I responded to 'jf' on his problem, and the fix I used is listed there. My feeling is that this old 486 I used as a secondary MX cost me almost nothing and saved my butt by giving some options I would not have had otherwise. It has been great when my dedicated line customers have had to be down for a bit, or their servers have gone down to be able to cache their mail, and tell them that as soon as their server is back up, that I can provide them all their 'lost' mail. Sam - Original Message - From: "Harald Hanche-Olsen" [EMAIL PROTECTED] To: [EMAIL PROTECTED] Sent: Friday, December 15, 2000 6:51 AM Subject: Secondary MX (Was: Mail flood in queue) + "Mark Delany" [EMAIL PROTECTED]: | My qmail server is the secondary MX for domain tri.net. | mx1.tri.net got flooded with about 28,000 invalid user emails, which | overflowed onto my qmail secondary server, mx2.tri.net. | | (As an aside. This re-raises the question of whether it is good | practise to be a secondary MX for another site. I generally think it's | a bad idea...) At least if you do, it's very helpful if the two sites have identical policies with regards to such things as relaying, checking envelope sender domains and the like. And it's a lot better if the primary MX does like qmail and accepts mail even for non-existing users, or else the secondary MX gets saddled with creating bounce messages on behalf of the other domain. And that is bad indeed. Been there, done that, got the T-shirt. - Harald
Mail flood in queue
Help, I've been mail flooded to invalid users. My apologies for the length of this, but I'm trying to be complete. The background is as follows. My qmail server is the secondary MX for domain tri.net. mx1.tri.net got flooded with about 28,000 invalid user emails, which overflowed onto my qmail secondary server, mx2.tri.net. As qmail.remote is sending them from mx2.tri.net to mx1.tri.net, one of two things is happening: 1. Fails because of unavailable socket on mx1.tri.net. 2. Log entry as follows- Dec 14 16:43:14 radius qmail: 976812194.440027 delivery 5510: failure: 205.153.244.6_does_not_like_recipient./Remote_host_said:_550_bail [EMAIL PROTECTED]..._User_unknown/Giving_up_on_205.153.244.6./ My qstat does not seem to be getting smaller. My qread looks as follows. clip 12 Dec 2000 21:58:59 GMT #53728 15374 remote [EMAIL PROTECTED] 12 Dec 2000 22:24:01 GMT #53751 15462 remote [EMAIL PROTECTED] 12 Dec 2000 12:53:05 GMT #53774 1146 [EMAIL PROTECTED] bouncing remote [EMAIL PROTECTED] remote [EMAIL PROTECTED] remote [EMAIL PROTECTED] remote [EMAIL PROTECTED] remote [EMAIL PROTECTED] remote [EMAIL PROTECTED] done remote [EMAIL PROTECTED] remote [EMAIL PROTECTED] done remote [EMAIL PROTECTED] done remote [EMAIL PROTECTED] done remote [EMAIL PROTECTED] done remote [EMAIL PROTECTED] done remote [EMAIL PROTECTED] 13 Dec 2000 00:18:33 GMT #54073 33878 [EMAIL PROTECTED] remote [EMAIL PROTECTED] clip My questions are as follows. Because of the 'giving_up' message, is it still retrying the same bad address again? Is there a 'filter' I can install to prevent qmail-remote from sending the emails from '[EMAIL PROTECTED]' on to mx1.tri.net? What does the 'done' mean on some of the messages in the qread dump? And will they clean out automagicly? Any help will be appreciated. Some 'good' email has been trapped in the queue, such as the last entry in the qread dump. But if I have to, I could completely dump the queue as a last resort. Thanks in advance. Sam
pop/imap connection error from MS window98.
Hi, I got qmail installed and running successfully between my local hosts. I have also installed tcpserver to run pop3 thru the commandline: /usr/local/bin/tcpserver 0 pop3 /var/qmail/bin/qmail-popup pop.rock.com \ /usr/local/bin/checkvpw /var/qmail/bin/qmail-pop3d Maildir and imap running thru the command: #!/bin/sh - . /usr/local/etc/imapd.config case x$IMAPDSTART in x[yY]*) /usr/local/libexec/courier-imap/imapd.rc start ;; esac MS window98 failed with the pop3 and imap wiht the err msg: connection disconnected by server ... Can anyone tell me what may be wrong with my FreeBSD setting? Thanks Sam.
/etc/skel and ./Maildir .qmail
hi, Can anyone tell me how to assign ./Maildir and .qmail files to a new user account using /etc/skel? Thanks Sam.
Connection reset by server
I have installed qmail server in my FreeBSD 4.1.1-stable box, I've also got tcpserver, courier-imap running, ipfilter and IPsec running as well. IPsec is running between my cllient and server box. The following diagram illustrate the my basic networking: Client (FreeBSD 4.1-stable) - Server (FreeBSD 4.1.1-stable) -Internet (sendmail)(Qmail server) sec.rock.comfastline.rock.com I don't think ipfilter and IPSec blocks the connection, because server box (FreeBSD 4.1.1-stable) can send email to the client machine (FreeBSD 4.1-stable). The problem is the client box cannot send email to the server. Whenever it sends email, an error msg will be raised by sendmail with the "Connection reset by server" err msg. Besides, server can client can ping each other, and client can ping and lynx outside wild wild internet websites. I can send emails within my server box. email can be sent to theh client box. Here is the error msg from /var/log/maillog: Oct 2 14:58:04 sec sendmail[2205]: e91M8Zv00283: [EMAIL PROTECTED], ct laddr=swun (1000/1000), delay=05:49:29, xdelay=00:00:00, mailer=esmtp, pri=12008 14, relay=fastline.rock.com., dsn=4.0.0, stat=Deferred: Connection reset by fast line.rock.com. My nmap -v in my client machine shows: Port State Service 22/tcp openssh 25/tcp opensmtp 111/tcpopensunrpc 587/tcpopensubmission Nmap -v in the server machine shows: Port State Service 22/tcp openssh 25/tcp opensmtp 53/tcp opendomain 110/tcpopenpop-3 143/tcpopenimap2 5432/tcp openpostgres 6000/tcp openX11 I run tcpserver with: /usr/local/bin/tcpserver -x/usr/local/etc/tcp.smtp.cdb \ -u$QMAILDUID -g$NOFILESGID 0 smtp /var/qmail/bin/rblsmtpd\ /var/qmail/bin/qmail-smtpd 21 The portmap_enable and sendmail_enable are set to NO in file /etc/rc.conf. Can anyone tell me what may be wrong with it? Thanks Sam.
Re: Connection reset by server
I forgot to mention that the client box can send email to the wild wild internet. Sam Wun wrote: I have installed qmail server in my FreeBSD 4.1.1-stable box, I've also got tcpserver, courier-imap running, ipfilter and IPsec running as well. IPsec is running between my cllient and server box. The following diagram illustrate the my basic networking: Client (FreeBSD 4.1-stable) - Server (FreeBSD 4.1.1-stable) -Internet (sendmail)(Qmail server) sec.rock.comfastline.rock.com I don't think ipfilter and IPSec blocks the connection, because server box (FreeBSD 4.1.1-stable) can send email to the client machine (FreeBSD 4.1-stable). The problem is the client box cannot send email to the server. Whenever it sends email, an error msg will be raised by sendmail with the "Connection reset by server" err msg. Besides, server can client can ping each other, and client can ping and lynx outside wild wild internet websites. I can send emails within my server box. email can be sent to theh client box. Here is the error msg from /var/log/maillog: Oct 2 14:58:04 sec sendmail[2205]: e91M8Zv00283: [EMAIL PROTECTED], ct laddr=swun (1000/1000), delay=05:49:29, xdelay=00:00:00, mailer=esmtp, pri=12008 14, relay=fastline.rock.com., dsn=4.0.0, stat=Deferred: Connection reset by fast line.rock.com. My nmap -v in my client machine shows: Port State Service 22/tcp openssh 25/tcp opensmtp 111/tcpopensunrpc 587/tcpopensubmission Nmap -v in the server machine shows: Port State Service 22/tcp openssh 25/tcp opensmtp 53/tcp opendomain 110/tcpopenpop-3 143/tcpopenimap2 5432/tcp openpostgres 6000/tcp openX11 I run tcpserver with: /usr/local/bin/tcpserver -x/usr/local/etc/tcp.smtp.cdb \ -u$QMAILDUID -g$NOFILESGID 0 smtp /var/qmail/bin/rblsmtpd\ /var/qmail/bin/qmail-smtpd 21 The portmap_enable and sendmail_enable are set to NO in file /etc/rc.conf. Can anyone tell me what may be wrong with it? Thanks Sam.
how to get off the mailing list?
Can someone enlighten me as to how to remove myself from this mailing list?
Re: duplicating sendmail's virtusertable
Ben Beuchler wrote: On Fri, Jul 28, 2000 at 08:52:16PM -0400, Sam Carleton wrote: I am switching over to qmail from sendmail. I am no expert in sendmail, I simply know that sendmail's virtusertable would allow incoming mail sent to [EMAIL PROTECTED] to be mapped to [EMAIL PROTECTED] I need to do this with qmail, how do I go about doing that? I also need to change the from header from [EMAIL PROTECTED] to [EMAIL PROTECTED] I am trying to stealth my user account because it is the only account able to su in as root. I would prefer if folks do not know the user name on the account:) (No, it isn't sam, that is simply my example g) Both of these can be accomplished using fastforward, available from http://www.qmail.org. I have installed fastforward and I am aliasing incoming mail from sam.carleton@domain to sam@domain, but I do not have a clue as to how to use fastforward to change the From: header on out going mail from sam@domain to sam.carleton@domain. Can someone enlighten me? sam
duplicating sendmail's virtusertable
I am switching over to qmail from sendmail. I am no expert in sendmail, I simply know that sendmail's virtusertable would allow incoming mail sent to [EMAIL PROTECTED] to be mapped to [EMAIL PROTECTED] I need to do this with qmail, how do I go about doing that? I also need to change the from header from [EMAIL PROTECTED] to [EMAIL PROTECTED] I am trying to stealth my user account because it is the only account able to su in as root. I would prefer if folks do not know the user name on the account:) (No, it isn't sam, that is simply my example g) Sam
Re: single quotes in RCPT
Adam McKenna writes: I am investigating a problem on our local lan. The problem seems to stem from netscape sending RCPT TO: lines in the following manner: RCPT TO: '[EMAIL PROTECTED]' The qmail server responds: Sorry, I couldn't find any host named flounder.net'. (#5.1.2) I am pretty sure that Netscape is violating RFC 822 by sending single quotes inside the brackets, but I can't find the specific part of the RFC that specifies that only double quotes should be used. There's no mention of single quotes anywhere in RFC822, therefore they should not be treated as anything special, so this is interpreted as an address 'adam on host flounder.net', and, since flounder.net' is an invalid domain address, the recipient is rejected. Having said that, I've never seen Messenger act this way. Forget about RFCs, something's screwy in Messenger.
Re: Maildir and procmail and safecat
[EMAIL PROTECTED] writes:
[mrsam@ny mrsam]$ cat t.c
#include stdio.h
charbuf[8192];
int main(int argc, char **argv)
{
int i;
char*p;
memset(buf, 0, sizeof(buf));
p=buf;
for (i=0; isizeof(buf); i++)
*p++=0;
write(1, sizeof(buf), 1);
return (0);
}
(Did you try running this program - the second param
to write should be an address, not a size_t)?
Perhaps you haven't noticed the time() output, right there in the middle
of my post.
I did. It's way too small to indicate anything but noise.
On Solaris an empty program issues some 19 system calls including
2 opens. A write() of 1 byte surely gets lost in the noise.
There's a saying down there in Washington, DC, that goes something like
this:
"A few million here, a few million there, pretty soon you'll be talking
real money."
After I cleaned up the typos, I averaged .11 seconds in ten sample runs
(versus .14). For one message, it's nothing. But when you're pumping
through hundreds of thousands of messages per day, that's nothing to sneeze
at.
It's unfortunate to see that the "wasteful, bloated, inefficient code is
OK, as long as you have a fast CPU" mantra being adopted by anyone else
other than Microsoft.
I recall that the original excuse for this absurd logic was that it's too
gosh darn difficult to properly check the return value from a
multicharacter write() call.
My heart bleeds for you.
--
Sam
Re: Maildir and procmail and safecat
Paul Jarc writes:
Sam writes:
[EMAIL PROTECTED] writes:
On Solaris an empty program issues some 19 system calls including
2 opens. A write() of 1 byte surely gets lost in the noise.
After I cleaned up the typos, I averaged .11 seconds in ten sample runs
(versus .14).
But with what kind of distribution? Scale up your tests - many more
writes per run. Then it'll be clearer that the effects we see are
coming from the writes, and not from constant overhead.
The overhead is pretty clear. The reason that I had the redundant buffer
clear in the "one write" version is so that both benchmarks had the same
setup overhead.
Ok, fine, looks like I have to bury this issue once and for all. Fine.
[mrsam@ny mrsam]$ cat prog1.c
#include stdio.h
#define CNT 1000
int main(int argc, char **argv)
{
int i, j;
char*p;
charbuf[BUFSIZ];
memset(buf, 0, sizeof(buf));
for (j=0; jCNT; j++)
{
p=buf;
for (i=0; isizeof(buf); i++)
*p++=0;
write(1, buf, sizeof(buf));
}
return (0);
}
This should accurately emulate how putc buffers one character at a time,
until it's full, and write()s out the buffer.
My BUFSIZ is 8192 bytes, and that's the size of the stdio buffer.
[mrsam@ny mrsam]$ cat prog2.c
#include stdio.h
#define CNT 1000
int main(int argc, char **argv)
{
int i, j;
for (j=0; jCNT; j++)
{
for (i=0; iBUFSIZ; i++)
write(1, "", 1);
}
return (0);
}
And that, I would think, would accurately emulate the one-character-at-a-
time-because-we're-too-lazy-to-check-the-return-code "logic".
Here's the box:
[root@ny 10remove-sendmail]# uname -a
Linux ny.email-scan.com 2.2.12-20smp #1 SMP Mon Sep 27 10:34:45 EDT 1999
i686 unknown
This is a dual-Pentium box. Red Hat 6.1 distro+all the latest patches.
Ready for the benchmarks?
[mrsam@ny mrsam]$ time ./prog1 /dev/null
0.23user 0.00system 0:00.22elapsed 102%CPU (0avgtext+0avgdata
0maxresident)k
0inputs+0outputs (76major+10minor)pagefaults 0swaps
[mrsam@ny mrsam]$ time ./prog2 /dev/null
3.72user 6.66system 0:10.36elapsed 100%CPU (0avgtext+0avgdata
0maxresident)k
0inputs+0outputs (75major+9minor)pagefaults 0swaps
And just to make sure that we're comparing apples with apples, and that I
did not blow the logic again:
[mrsam@ny mrsam]$ ./prog1 | wc -c
8192000
[mrsam@ny mrsam]$ ./prog2 | wc -c
8192000
Ok now, so to add everything up:
[mrsam@ny mrsam]$ bc
bc 1.05
Copyright 1991, 1992, 1993, 1994, 1997, 1998 Free Software Foundation, Inc.
This is free software with ABSOLUTELY NO WARRANTY.
For details type `warranty'.
scale=6
10.36 / .22
47.090909
So, it seems that you pay almost a 50x penalty for the convenience of not
properly checking the return code from write().
Have a nice day.
--
Sam
Re: Header to tell qmail an email is in HTML format...
Guillermo Villasana Cardoza writes: So... should I add a blank line after the normail headers??? No, you need to educate yourself a bit more how E-mail works. Until you have a fairly good understanding how an arbitrary E-mail message gets from point A to point B, what software is involved, and what each piece of software does, you will only confuse yourself even more. Start with the following documents: RFC 821, RFC 822, RFC 2045. -- Sam
Re: Egg on my face
On Fri, 11 Feb 2000, Dave Sill wrote: [EMAIL PROTECTED] wrote: False. Mail will not be lost if if rename() or link() (depending on Who said anything about the message already being on the filesystem? If it's not, then qmail hasn't accepted responsibility for delivering the message, so the sender, either local or remote, should resend it. As far as Qmail knows, the message has been written out.
Re: imap, CRAM-MD5
On Fri, 11 Feb 2000, Dave Sill wrote: the password. But CRAM-MD5 does something different...some sort of "keyed md5". Anyone know how to manually generate the proper response? RFC 2104
Re: qmail-imap, cyrus imap, qmail
Dave Sill writes: [EMAIL PROTECTED] wrote: Someone tracked this one down and confirmed it to be a bug in Netscape Messenger's IMAP client. And the "fix" is to wait for Time/Warner/CNN/AOL/Netscape to release a working Messenger, and get all 50 million users to install it, rather than accommodating the bug in the handful of courier-imap servers? And tolerating sheer incompetence, and lack of due diligence, on the part of commercial software vendors is how we got into this situation in the first place. I've already given both Messenger and Outlook Express enough slack when it could be reasonably argued that there is a difference of opinion as to what IMAP4rev1 is actually saying, which I consider to be the worst written RFC I have ever read - but that's another story. However, when there's a failure in implementing a rather clear and unambiguous portion of the protocol, working around that particular problem is going to get the lowest priority. I'll fix Netscape's bugs when I have the time for it. But for now, I have better things to do. Until then, and I hate to say it, people should use Outlook Express's IMAP client. -- Sam
Re: Deliveried-To: ?
[EMAIL PROTECTED] writes: Is qmail expected to add a Delivered-To header of the form: Delivered-To: user@domain.com@domain.com ? Well, normally you expect to see a Delivered-To: [EMAIL PROTECTED] If this is expeted, why and what meaning does it have? The Delivered-To: header is expected, but if you see these kinds of funny addresses in there, something is seriously fubared in your setup. -- Sam
Re: Changing Password
On Sat, 5 Feb 2000, Md. Sifat Ullah Patwary wrote: Hi all! I use qmail-pop3 for my pop users. They can check their mail, but they cannot change their password from pop clients (sya from eudora). What can I do? Please help.. Nothing. The POP3 protocol does not specify any way for anyone to change any password.
Re: workaround for port 25 block? (fwd)
On Sat, 5 Feb 2000, Brian R wrote: In fact, I'm looking into DSL to run some stuff, which I'll mention on some of Dan's lists, once I put on my firesuit and anchor the chains down :-) Last time I checked, DSL provider speakeasy.net's TOS/AUP explicitly allows their customers to run any server their heart desires, as long as it doesn't suck up gobs of bandwidth. I think that this is a very reasonable policy. Time Warner cable in Manhattan is about to start a huge marketing campaign to push their cable modem service[1], which looks like to be RoadRunner. Screw them. [1] Yes, folks, until just a few short weeks ago, cable modem service has not been available in Manhattan.
Re: IMAP command
[EMAIL PROTECTED] writes: I am looking for references of IMAP comand line, so I can try it via telnet to port 143 , where I could find it? RFC 2060. -- Sam
Re: Odd question
On Fri, 21 Jan 2000, Juan E Suris wrote: virtual domain (same IP), domain2.com. Is there an environment variable that I can read to know if the remote computer requested a connection for domain.com or domain2.com? No. If you alias multiple IPs, though, to the same box, you can read TCPLOCALIP.
Re: POP password checking
On Fri, 21 Jan 2000, Jacob Joseph wrote: I'm having trouble getting qmail-popd to accept my password. What could be causing the trouble. The user is in the assign file and I have run qmail-newu and then restarted qmail. I've delivered a message to the user for testing, but I can't see anything in that user's directory with ls -al nor can I get in with pop. Any ideas? AFAIK qmail-pop3d does not read assign, and it authenticates against the system username only.
Re: courier imap and shared folders
On Mon, 17 Jan 2000, Samuel Gisiger wrote: support courier imap shared folders? No, not yet, at least. What you can do, though, is set up a separate account, and use that as shared folders. Most IMAP clients can access multiple servers.
Re: Guidelines for large mail installations
On Mon, 17 Jan 2000, Brian Baquiran wrote: Hi, We're setting up a big Qmail installation. It is projected that the number of users will be in the hundreds of thousands within a couple of months. Our current idea is to have one big NFS server, and a lot of lightweight SMTP/POP3 servers that mount their /var/qmail/ and /home/vpopmail from the NFS server. Is this OK? How should I go about this? Almost. You cannot have the actual mail queue on NFS, or Bad Things Will Happen[tm]. What you want to do is to have a separate Qmail install on each swerver. You can even install Qmail one one machine, verify that it works, then just tar up everything under /var/qmail, and unpack the tarball on each swerver (of course, there cannot be any messages in the queue directory when you do that). If you want to, /var/qmail/bin can be a soft link to an NFS directory, but that doesn't really buy you much. You can also set /var/qmail/control to a soft link to a shared NFS directory, if all your swervers are configured identically. Even if you have one or two control files that need to be different for each machine, such as "me", you can have /var/qmail/control/me to be a soft link to /etc/qmail/me, for example, and create this file on each machine, initializing it to its hostname.
Re: Server Water Sprinkler
On Sun, 16 Jan 2000, Mike wrote: I was wondering if someone could tell me how to send mail to one outgoing RehHat server, and make that server round robbin to 10 other smtp servers? I mail about 250,000 emails a night, and the subscriber base is expected to grow 50 fold over the next 6 months and I am trying to gear up for it. I just want to send 1 email to one server somehow have it grab the list off of a SQL database on the same server, and distribute it to the other 10 as load-balanced as possible for delivery. Any suggestions. I have like 70 different ideas on the whole project, but cannot think of a way to accomplish this paticular task. Add an entry on the RedHat server to smtproutes, that points to an internal DNS record. Then, initialize your DNS server and put 10 A records for this hostname. Each individual message will then be sent to a randomly chosen IP address, one out of 10, balancing the load.
Re: Server Water Sprinkler
On Sun, 16 Jan 2000, Mike wrote: If I set this up in DNS, what would happen if an outgoing server in the cluster went down? Also how effective would the load balancing be? Add an entry on the RedHat server to smtproutes, that points to an internal DNS record. Then, initialize your DNS server and put 10 A records for this hostname. Each individual message will then be sent to a randomly chosen IP address, one out of 10, balancing the load. Most deliveries will be unaffected. Simple arithmetic shows that 10% of the time the message will have the unavailable IP address picked. When the connection attempt fails, the relay will simply switch to another server. If the unavailable server is still up, but not running SMTP, the switchover will be almost instantaneous, because it will refuse the connection immediately. If the server is completely dead, there will be a delay of about a minute for the connection to time out. Note that most TCP/IP stacks will allow you to bind multiple IP addresses to the same interface. If the server is going to be offline, simply bind its IP address to one of the other available machines, until you fix the server. Of course, that machine will now get twice its regular load, so this should be simply used as a stopgap measure, and if the server is going to be down for a prolonged period of time, its IP address should simply be removed from the DNS record until it's fixed.
Re: looking for a web-mail solution reading directely into theMaildirs
On Sat, 15 Jan 2000, Olivier M. wrote: On Sat, Jan 15, 2000 at 03:21:21PM -0500, Sam wrote: Thanks for your post. Well, Sqwebmail seems to be nice if use a standard qmail system with only one account per uid, or a system with vpopmail. But _again_ (like Courrier-IMAP), it won't work with Bruce Guenter's vmailmgrd package. : Or is there a way ? Not entirely true. Both sqwebmail and Courier-IMAP can access virtual accounts - implemented by a GDBM or DB database - and can see each other's folders. "not entierly true" ? well, it works or it doesn't work... and actually, I can't 'vmailmgr' and 'vpopmail' are not the only ways to implement virtual accounts. If you want to implement and define virtual accounts, the capability is there. That implementation is based on a GDBM or DB database, and the different implementation was due to the fact that a much more flexible, more generic, approach was required. For example, AFAIK, neither vpopmail nor vmailmgr are capable of supporting CRAM-MD5 IMAP authentication. make it work on my server, and I never read that anybody is using it with vmailmgrd (which is not compatible with vpopmail). Or is there a (little) probability to make it work ? that would be great... Of course it's possible to make it work, if you want to implement it yourself. Both sqwebmail and Courier-IMAP can be easily extended to support any other reasonable authentication mechanism, but you have to invest the time and effort to write the code yourself. I have no need for vmailmgr, because I have an alternate solution that works better for me.
Re: Maildir format
On Fri, 14 Jan 2000, Ondøej Surý wrote: From libc-client4.7 documentation: --strip-- The Maildir format used by qmail has all of the performance disadvantages of mh noted above, with the additional problem that the files are renamed in order to change their status so you end up having to rescan the directory frequently the current names (particularly in a shared mailbox scenario). It doesn't scale, and it represents a support nightmare; it will therefore never be supported in the official distribution. Maildir support code for c-client is available from third parties; but, if you use it, it is entirely at your own risk (read: don't complain about how poorly it performs or bugs). --strip-- Could someone comment this? Certainly. As the author of a Maildir IMAP server, that kicks the living daylights out of UW-IMAP in terms of performance and resource footprint, I can unequivocally state that there is a very tiny grain of truth in there, but 99% of that dissertation is complete bunk.
Re: Maildir format
On Fri, 14 Jan 2000, Russell Nelson wrote: =?iso-8859-2?Q?Ond=F8ej=20Sur=FD?= writes: Could someone comment this? Yeah. Mark Crispin doesn't like Dan Bernstein; therefore anything Dan Bernstein does has technical problems which "don't scale" and are "a support nightmare." Mark doesn't want to hear what I have to say about IMAP (which Mark invented). Maybe if I just sent him the piles of hair I wrenched out of my head while reading the IMAP spec, he'd get the point? Na.. He thinks that all the stupid design decisions he made (e.g. having three string representations) were necessary. I concur. RFC 2060 is a joke. I had to read it at least half a dozen times before I was able to figure out what it was actually trying to say.
Re: Maildir format
On Fri, 14 Jan 2000, Russell Nelson wrote: Mikko Hänninen writes: But, the commentary completely misses the good points and the purpose of Maildirs: that they're ideal for incoming mail delivery, especially when the folder is accesses over NFS (whether "access" delivery or reading or both). Maildir format is not something you should be using for email archival, or for very large mail folders. However, the lack of locking requirement is a big win over NFS. Right, and any scalable email system is going to use NFS. Therefore the question in my mind is not "What should be used for large folders instead of Maildirs?" but instead "What must be done to make Maildirs more efficient"? One way to do that would be for Dan to change the Maildir specification so that a Maildir may have multiple "cur" directories. Then, keep a CDB containing a subset of the message headers. No need to. Try opening a 1,000 message Maildir with Pine or Netscape Messenger (Outhouse Excuse would probably work too) connected to Courier-IMAP. The initial folder open should take less than 10 seconds, depending upon your hardware. Subsequent folder opens will be almost instantaneous, and, at there won't be any noticeable delays in browsing the maildir. And the only thing that Courier-IMAP caches are the UIDs of each individual message, which is refreshed with a single directory scan. Pine never asks for headers of every message, and Netscape Messenger caches the headers by itself. It seems that the original IMAP implementation by uwimap was so piss-poor performance-wise, that pretty much all IMAP clients either do some form of caching themselves, or are very carefull not to issue any IMAP requests that might bog down the server.
Re: persistent connections for qmail file programs
Peter Gradwell writes: Hi ya, If I have a perl script, in a .qmail- file, which connects to a mysql database, has anyone considered how to make the mysql connection persistent. Would it be at all possible to have persistence in the program run by a .qmail file? or am i totally mad? Sure. Anything is possible. Run your Perl script permanently in the background, and have a small Perl stub executed from .qmail that connects to the background daemon via a socket or a pipe, and does what it has to do. -- Sam
Re: off-topic: Dan's engineering methods
Len Budney writes: Apologies for this slightly off-topic post. Has Dan has revealed enough about his engineering methods for others to duplicate them? Does anybody want to, possibly producing sharable tools? There are already existing tools out there that produce perfectly reusable and recyclable code, which have been battleproven, and can easily handle huge projects made out of modular parts. I have four projects, in which an average of 50% of the code is shared amongst all four of them, and is organized into about a dozen different subdirectories. The big open question for me is: 1. What does he use for source control, given that he builds in one directory, and bundles the same libraries with many packages? How is the repository organized? CVS etc. like hierarchies. Initially RCS worked fine for me. In each directory of a shared module, I simply set RCS to be a soft link pointing to a common directory. However, lately due to increased complexity I upgraded to CVS, so that changes to any shared code can be automatically propagated via one cvs update, instead of having to remember to RCS co each individual file from the shared RCS repository, for each project. Any time I switch projects I just do a cvs update, and I'm all set. And, because CVS is just a shell on top of RCS, moving to CVS was virtually a no-op. 2. The ezmlm package contains files of form *=* which give a strong hint how his makefiles are generated [2]. That's nasically a simplified version of what autoconf and automake does. They are standardized tools that everyone knows how to use. There's an initial steep learning curve, but, after a while, it becomes as natural as breathing. 3. Dan appears to track "functional units" of code, and appears to incorporate them into projects as units [5]. Perhaps using CVS modules or the like? Easily handled via CVS, with autoconf and automake. Take a look at sqwebmail - http://www.inter7.com/sqwebmail/, courier-imap - http://www.inter7.com/courierimap/, and maildrop - http://www.flounder.net/~mrsam/maildrop/. All three tools reuse about a dozen functional modules, which are stored only once, in a single repository. At any given time, actually, there might be very minor differences in the same module within each individual package simply due to the fact I don't package them as a tarball simultaneously, but only when there's a functional upgrade. But, ignoring those minor differences, although the base source code within all three projects is identical, in some cases the autoconf/automake scripts end up configuring the same module quite differently. For example, look at the authlib library. Because Courier-IMAP includes the libhmac module, authlib detects it and compiles some code that implements CRAM-MD5 authentication, which uses the code from libhmac. The same authlib module does not compile the CRAM-MD5 code when it is packaged as part of sqwebmail, because sqwebmail does not include the libhmac library, and it has no need for CRAM-MD5 authentication. I just noticed that maildrop does not include the md5 module, because I haven't worked on maildrop for a while, and haven't updated it. Therefore, the userdb virtual account module can only set crypted passwords for the userdb virtual account database. Simply adding the md5 module to the maildrop build will result in userdb reconfiguring itself to offer an option of storing passwords encrypted with the MD5 hash function, permitting longer passwords. 4. All sources go into one directory; Perhaps because recursion defeats make's dependency checks [3,4]? Perhaps because many tools don't like to build things in subdirectories? Perhaps because his packages are pretty small, so it just doesn't matter? It's quite convenient to package standalone modules as individual subdirectory that can be plonked into any project, and have a top-level configure script configure it. autoconf and automake have the necessary resources to build a module hierarchy, so there's no need to badger djb for this tools, since equivalent capabilities have been available in autoconf and automake for years... -- Sam
Re: 7 bit ascii qmail
Len Budney writes: I should have kept reading... Sam [EMAIL PROTECTED] wrote: I will be happy to point to you to a shitload of documented cases where, in the past, AOL has certainly dropped a lot of legitimate mail. Their subscriber rolls keep on growing. If you actually mean "dropped", then you're describing unforgiveable incompetence. If you really meant to say "bounced", then you're describing a policy descision--and slandering AOL. Sue me. -- Sam P.S. I think I need to check if there's a full moon out tonite.
Re: 7 bit ascii qmail
[iso-8859-1] Mikko_Hänninen writes: Holger Hug [EMAIL PROTECTED] wrote on Tue, 04 Jan 2000: Is there any possibility to cause qmail to convert a deliberate character set into "US-ASCII" before sending them off ? Not in qmail itself, I believe. At the moment, I don't have an idea where to start. Perhaps there is a possibility to install a script ? How are the emails created? By injecting them into the queue with qmail-inject? If that's the case, you could insert another script in front of that, which changes the emails accordingly before calling qmail-inject. If the emails are sent "remotely", via SMTP, then you need to fix the sending the end. Or perhaps set up a special SMTP port or something which runs a script on the emails, but that sounds like it's getting complex. Anyway, you likely do need to get this fixed *before* qmail sees the emails, however they are getting to it. Correct, but only because this is a Qmail bug. What he's probably talking about is that when Qmail receives an 8-bit message (a foreign character set), and it gets relayed to a foreign server that is not capable of receiving 8BITMIME mail, Qmail will not downshift the message to 7-bit encoding. As a result, a few firewalls/mail gateways will end up rejecting the message. There aren't very many of them that are like that, but they are out there. If mail is generated locally, the only way to fix this is to put a stub around qmail-inject that translates all 8-bit mail to 7-bit encoding before running the real qmail-inject. If the mail originates via an SMTP MUA, you have to use the RELAYCLIENT hack to pipe the message through a translator. A pain in the ass, and you shouldn't have to do this nonsense. This is something that should be handled automatically by qmail-remote. -- Sam
Re: 7 bit ascii qmail
Fred Lindberg writes: On Tue, 04 Jan 2000 23:04:40 GMT, Sam wrote: Correct, but only because this is a Qmail bug. Nonconformance with archaic very US-centric part of rfc. Anyone in a I wouldn't describe all of RFCs 2045-2048 as "archaic". RFC 821 is certainly not archaic, and it has a blanked prohibition against all non-7bit mail. RFCs 2045-2048 allow this restrictions to be relaxed, in certain situations, and under controlled conditions. But you can't have your cake, and eat it too. If you want to send 8-bit mail, please play by the rules. domain with a few extra chars in the charset has done away with non-8-bit-capable servers a long time ago. A pain in the ass, and you shouldn't have to do this nonsense. This is something that should be handled automatically by qmail-remote. Or by retiring the outdated servers. Sometimes being right is better than being correct. RFC 2045-2048 *is* the right way to do this. In fact, strictly-conformant servers have every right to reject 8bit mail that is not received with the 8BITMIME extension. -- Sam
Re: 7 bit ascii qmail
Matthew Brown writes: Sam wrote: What he's probably talking about is that when Qmail receives an 8-bit message (a foreign character set), and it gets relayed to a foreign server that is not capable of receiving 8BITMIME mail, Qmail will not downshift the message to 7-bit encoding. [snipped: how to set your system up to do this] A pain in the ass, and you shouldn't have to do this nonsense. This is something that should be handled automatically by qmail-remote. Qmail behaves the way it does deliberately; see http://www.ornl.gov/its/archives/mailing-lists/qmail/1998/02/msg00566.html for Dan's word on the subject. In essence, his argument is: 1) 7-bit-only servers and clients are dying out anyway Next time you get pulled over for speeding, tell the cop that nobody drives under the speed limit anymore, and see how well that goes. 2) Nobody else implements the standard correctly I wouldn't say that. 3) 8BITMIME/quoted-printable is a gross hack and no better a solution than getting rid of the last remaining 7bit servers [apologies if I misstated the arguments] For example, Sendmail doesn't correctly follow the standard (it does 8-7 conversion for MIME messages, but not for unlabelled messages containing 8-bit characters). The correct way to handle that is to reject them in the first place. -- Sam
Re: Delivery bug?
Bill Ataras writes: If I send a mail to "[EMAIL PROTECTED],[EMAIL PROTECTED]" virt receives his mail properly, but [EMAIL PROTECTED] is not bounced as I would expect. When I look at the maillog qmail says: starting delivery 73: msg 376980 to local [EMAIL PROTECTED],[EMAIL PROTECTED] Jan 4 23:29:06 frodo qmail: 947057346.691573 status: local 1/10 remote 0/20 Jan 4 23:29:06 frodo qmail: 947057346.751821 delivery 73: success What's the deal with the "[EMAIL PROTECTED]" ? Looks like your MUA is buggy. Qmail received mail addressed to [EMAIL PROTECTED],[EMAIL PROTECTED], so it delivered the mail to one, not two addresses. Pray tell us which crapware exactly that cannot properly parse RFC 822? -- Sam
Re: 7 bit ascii qmail
Matthew Brown writes: 2) Nobody else implements the standard correctly I wouldn't say that. For nobody, substitute 'almost nobody'. Sendmail, the most popular MTA on the Internet, does not implement the standard correctly. Qmail does not. Exim does not. I'm sure many others do not. The difference is that sendmail makes a halfhearted attempt at compliance, and qmail doesn't. Agreed. Now, which one would you rather have? The correct way to handle that is to reject them in the first place. Are you seriously suggesting that, for the sake of these saintly, antiquated 7 bit only mailservers, we should drop people's emails on the floor? No, and that's the whole point. If you forward it along without encoding it as quoted-printable, it *WILL* be dropped on the floor. Also, let me put it this way: is there any MTA out there that only accepts 7bit mail that should not be upgraded for many other reasons? Yes. aol.com. As long as their 7bit mail relay handles almost a hundred million messages per day, I think it's pretty safe to say that it does its job as it should. It's possible that AOL's mail relays will properly handle transparent 8bit mail now, I really don't know. But even if they do, if they suddenly decide that they want to make their relays fully RFC-compliant, they're going to do it, and they will start dropping your non-compliant mail on the floor, whether you like it, or not. And there's not a damn thing you will be able to do about it. -- Sam
Re: How do I empty the mailbox?
Kristina writes: Is there a command where I can delete all past messages in a users mailbox, eg. /home/kristina/Mailbox. ? Yes - delete this file. -- Sam
Re: FW: stopping the inward executable E- mail attachments in Qmail
On Fri, 31 Dec 1999, Arumugam Thiruppathi wrote: Hi How should I stop all the incoming executable Email attachments thru Qmail server. Could any one help me in configuring the same. Only by writing an external filter, and funneling all mail through the external filter. This is not, exactly, a trivial job, and will require extensive modifications of your Qmail setup. The specific steps are highly dependent on your particular and unique Qmail configuration. You'll have to arrange for Qmail to divert all mail to an external program. Then, you will have to write this external program, that parses the message according to RFC 2045, in order to detect attachments. Afterwards, the message needs to be reinjected into the mail queue, with the recipient envelope address slightly altered so that the mail ends up being delivered to its original recipient, somehow. Depending on your particular qmail setup, this may be accomplished by reconfigured control/smtproutes, control/virtualdomains, or by having a second instance of Qmail compiled and running, or via any one of several other ways. The right approach depends, again, upon your individual situation, which only you know. Hopefully you just didn't realize that you have to implement this within the next 24 hours. You should've started on this at least a month ago. Mail servers, generally, do not care -- and should not care -- about message contents (except in very few isolated situations) so implementing something like that would clearly require major work.
Re: Sendmail vs Qmail?
Russell Nelson writes: Sam writes: On Sat, 18 Dec 1999, Russell Nelson wrote: Why would this happen after installing eliminate-dups? You want to hand-hold all the PHBs who can barely put together a Powerpoint presentation, and tell them how to install a unix filter? If you can't figure out how to make it easy for them, then you have to turn in your Sysadmin merit badge. Are you really saying that it is now necessary to jump through hoops in order to support Qmail on the back-end? Why should I figure out anything, just for the sake of switching to Qmail? There's no need for me to figure out how to make it easy. It's already easy: sendmail takes care of those things for me, automatically. -- Sam
Re: Sendmail vs Qmail?
Russell Nelson writes: Sam writes: Are you really saying that it is now necessary to jump through hoops in order to support Qmail on the back-end? Why should I figure out anything, just for the sake of switching to Qmail? There's no need for me to figure out how to make it easy. It's already easy: sendmail takes care of those things for me, automatically. Nonsense. Sendmail makes a "90%" attempt at the job. When it expands aliases, it eliminates any duplicates it can detect. However, it can only detect alias expansions on the same host. Once you leave that host (for example when moving from the department workgroup server and going to the enterprise server), no attempt is made to suppress duplicate alias expansions. Well, that's still 90% better than what Qmail does. And, with mailing lists being managed in one place, that goes up to 100%. There is no concept of a "workgroup" versus "enterprise" server. There are just a bunch of honking servers, who all have the access to the same exact set of monster alias files. I'm not sure, but the actual aliases may actually be kept in NIS or LDAP, or they may be periodically updated from a central server, but the point is that whichever server gets the mail, the server has complete access to all mailing list aliases, and can completely expand the recipient list all by itself. Furthermore, the PHBs don't exactly have access to a shell server, where they can install procmail recipes or forwarding. Even nobody in IT does that because, frankly, there's no need to. Mail gets delivered to a central IMAP server, and anyone can access their mailbox from any office, so there's very little need for any forwarding. Sendmail also makes no attempt to delete duplicates caused by multiple SMTP deliveries. There is a small but nonzero period of time when a connection failure must result in a second delivery even though the first was successful. This is a well-known (although infrequent) problem which sendmail makes no attempt to solve. Eliminate-dups solves both of those problems. Eliminate-dups is a solution in search of a problem. Duplicates due to SMTP window failures are mostly theoretical than anything else. If you have a flaky connection, you are likely to fail long before you get to this point. I do not ever recall receiving a duplicate message that was traced to this problem. The actual window of vulnerability is as small as you can possibly get. Then, with your internal network having a pretty good track record of stability, to calculate the actual probability of a duplicated message, you'd have to go pretty far past the decimal point. If anyone has ever logged a dupe, and confirmed that this was the reason for it, please raise your hand. I'm not comfortable with the notion that the way to eliminate duplicates with 100% certainty is, first, to generate a whole bunch of them, and then to eliminate them on the delivery end. Seems to be a bit wasteful to me. eliminate-dups can also be argued to be a useful tool to eliminate duplicate copies of reply-to-alls from your mailing list manages. Yet, in actual practice, I found that to be a non-issue as well, as long as you are already filtering your mailing list mail. It seems to me that when you develop a need for something like that, you are probably already filtering your mailing lists, and may not end up reading all of it. I doubt I'm the only one who reads every message in every mailing list. I usually flush 90% of everything straight into the trash. I actually welcome a carbon copy that goes straight into my INBOX, instead of being shuffled aside into the mailing list folder. If I feel the need to respond, it helps me to go in and fish out the mailing list copy, and reply to that too. Yet, actually I tend to avoid doing that myself, when I reply. I think I'm in the minority here, as far as that's concerned. -- Sam
Re: Two questions: Return-Path rewriting and AUTH packets
Mike van der Velden writes: There are two outstanding questions: First, when a user on a Windows client machine uses Netscape Mail 4.7 to send a message, the sender and return-path both say "[EMAIL PROTECTED]". However, when using Pegasus Mail 3.1.2 to send the same message, the return path says "[EMAIL PROTECTED]" while the sender's address still says "[EMAIL PROTECTED]". Several remote sites refuse to receive e-mail where the sender and return-path don't match. This address re-writing never happened when the mail server was Exchange running under NT, but it has become a problem since we switched to qmail running under Solaris. The "return path" is specified solely by MUA, so this is entirely a Pegasus Mail configuration issue. It is possible that other mail servers take it upon themselves to rewrite the return address, but they should not really do that, and it's none of their jobs. Tell your lusers to fix their mail software's configuration. Additionally, refusing to accept mail for this reason is rather dumb, unless the REAL reason why your mail is being rejected is because the actual return path is nonresolvable in DNS. Only THEN does rejecting such mail is perfectly valid. Otherwise, this is not your problem, but rather unwarranted paranoia on the part of a bunch of wankers who don't know any better. Second, the firewall people have started to complain that ever since the switch-over to qmail, they are seeing a lot of "auth" packets to and from the qmail server to various remote sites. They want to know what is going on. What sort of extra packets does qmail send out? Are some of these "auth" communications initiated by outside systems? Qmail sends an ident (or auth) packets in response to any incoming connection request. Any ident/auth response received gets recorded in the headers. In certain situations, this information may be required in order to track down any external source of abuse. This should ALWAYS be done in response to an unauthenticated incoming connections, and the fact that few other mail relays do it by default only indicates their unacceptable default security settings. Tell your spooks that the auth/ident packets are designed to make their own lives either. -- Sam
Re: Sendmail vs Qmail?
Troy Frericks writes: If somebody sent a memo to "A-project" and "Management-A", and I was a member of both lists, I would expect to receive two emails so I could get them archived in my appropriate mail folder (. I would hope you could disable this 'feature' in sendmail if you wanted. You'll definitely think otherwise if you start getting three or four copies of every memo.
Re: Sendmail vs Qmail?
On Sat, 18 Dec 1999, Russell Nelson wrote: Sam writes: Troy Frericks writes: If somebody sent a memo to "A-project" and "Management-A", and I was a member of both lists, I would expect to receive two emails so I could get them archived in my appropriate mail folder (. I would hope you could disable this 'feature' in sendmail if you wanted. You'll definitely think otherwise if you start getting three or four copies of every memo. Why would this happen after installing eliminate-dups? You want to hand-hold all the PHBs who can barely put together a Powerpoint presentation, and tell them how to install a unix filter? Life's too short.
Re: Sendmail vs Qmail?
On 17 Dec 1999, Petr Novotny wrote: -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On 17 Dec 99, at 7:28, [EMAIL PROTECTED] wrote: The inability to do header rewriting without making two trips through the queue causes a severe performance hit, if you are doing anything other than low volume. Rewriting headers of all messages is a severe performance hit. Or Only for sendmail. Qmail, and other mailers, can do it with very little expense. can you instruct sendmail not to? I couldn't find how. That is forwarding with only one trip through the queue. You mean reading "aliases" before delivering, and therefore deciding to forward immediately? Maybe with some tweaking, the current virtualdomains code might do that. Also aliasing as in mailing lists. One nice feature of sendmail is that it dedups addresses after expanding them. This is one reason Qmail will never be used in any enterprise-scale system. The large international 800 pound gorilla I currently consult for uses alias-based mailing lists rather extensively. Pretty much everyone gets subscribed to at least a dozen mailing lists as part of the company's welcome wagon. There's a mailing list for everyone on the same floor in the building, a mailing list for everyone on any floor in the same building, a mailing list for everyone in all the building in the same city, a mailing list for everyone who works on the same continent, and a mailing list of everyone in the firm. On top of that, there are multiple mailing lists that loosely mirror all the steps on the corporate ladder, and mailing lists for everyone in the same business unit or IT unit. Additionally, pretty much every IT project has its own mailing list. Every application that the firm has installed anywhere also has a mailing list for its users. There's even a mailing list for everyone who uses internal and external news servers (both use authentication, and the mailing list automatically consists of everyone who used the news server in the last 90 days). There are individual servers which also keep track of who logs on to them, and a mailing list is made out of that info too. This is done so that whenever the engineering group takes a server, application, or a particular network, down for maintenance, everyone who can potentially be affected by the down time is aware of it. Now, you can't run something like that with Qmail and ezmlm. Pretty much any kind of memo is sent out to at least three or four mailing lists. Since everything is kept as, basically, one huge mail alias file, sendmail dedups the recipient list after expanding it (and, yes, as long as you run a sendmail farm on a large enough ring of big honking UNIX boxes with more CPUs than most people have fingers on their hands, the performance is quite acceptable). This is an absolute requirement for any enterprise-scale environment. If everyone started to get three or four copies of the same memo, this would get old pretty quickly.
Re: How to control message ?
On Sat, 18 Dec 1999, Jason Huang wrote: Hi All ! My boss told me he wanna control outgoing and incoming mail. He want to allow or delete each mail. It seems terrible ,but ... How can I config my qmail ?? You can't. I suggest that you start looking for a new job. Your boss is an idiot. I don't know about you, but I don't like to work for idiots.
Re: Noticed a single that has a back door open-relay
Monte Mitzelfelt writes: MAIL FROM:spamtest 250 ok RCPT TO:[EMAIL PROTECTED] 553 Sorry, you can't relay through me (#5.7.1) RSET 250 flushed MAIL FROM: 250 ok RCPT TO:[EMAIL PROTECTED] 250 ok DATA 354 go ahead (message body) 250 ok 945215583 qp 29881 Does anyone know how this could be setup like that? This is a custom hack of some kind. Note that the no-relay message is not the standard message you get from plain vanilla qmail. -- Sam
Re: Hotmail
Monte Mitzelfelt writes: I find it easier to do something like echo "@hotmail.com" /var/qmail/control/badmailfrom That doesn't clean out your queue of outgoing crap, or did I miss something there? Easier is nice when it works, but I tend to prefer effective over easy. This way they get complaints about your service which on average they care fairly little about, not about their screwed up service which is causing us grief. Well, you can always temporarily put hotmail.com into smtproutes for 127.0.0.1, then rehup qmail-send. This will immediately bounce everything that's queued up for hotmail.com, after a minor expenditure in CPU time and disk space, as the crap rotates through the queue, a couple of times, before it finally figures out where it wants to go. The sender will get an obnoxious bounce, but your queue will be clear. -- Sam
Re: using procmail with qmail+/Maildir+vpopmail
On Sun, 12 Dec 1999, J. Ivan Juanes Prieto wrote: Also, procmail doesn't deliver directly to maildir-format mailboxes. There's a patch available that implements maildir delivery in procmail. Procmail 3.14 can allegedly deliver to maildirs. The code, however, is completely unreadable, just like most of procmail's code.
Re: make errors
Brock M. Eastman writes: qmail-local.c:1: sys/types.h: No such file or directory qmail-local.c:2: sys/stat.h: No such file or directory make: *** [qmail-local.o] Error 1 You have a corrupted installation. Some your key files are missing. Reformat and reinstall the entire O/S.
Re: Fw: failure notice
On Fri, 10 Dec 1999, Racer X wrote: can someone tell me what's wrong with the headers that would cause the message to bounce like so? i'm curious to know because this is an autoresponder that's generating the "bad" headers. [ snip ] [EMAIL PROTECTED]: 143.183.152.22 failed after I sent the message. Remote host said: 553 Header error --- Below this line is the original bounce. Return-Path: Received: (qmail 11920 invoked by uid 257); 10 Dec 1999 14:42:28 -0800 Date: 10 Dec 1999 22:42:28 - Message-ID: 944865748.11916.blah Your Message-ID: header violates RFC 822.
Re: Hotmail
On 10 Dec 1999, Monte Mitzelfelt wrote: It looks like Hotmail may be cutting off messages that exceed their size limit, by issuing a 500 error in the middle of the DATA session. This doesn't seem right to me, but qmail doesn't seem to see it. This backs up my clients outbound queue, not too bad, but worse that I'd like. It does issue a SIZE if you say EHLO to it. Are there any patches for SIZE? What's the right answer here. The right answer is to firewall all incoming and outgoing mail from Hotmail, until they fix their mail server to comply with RFC 821.
Re: Filtering on MAIL FROM:
Markus Stumpf writes: On Wed, Dec 08, 1999 at 11:02:16AM -0600, Bruno Wolff III wrote: Another problem is that some places have started blocking messages with empty envelope sender addresses, because some spammers use them to get past the domain blocking. Yeah, but one must be really a stupid sysadmin to do this. Right. So, what else is new. -- Sam
Re: Old messages in Maildir/tmp
Fred Backman writes: Why do I have old messages (as in 3-4 days old) in Maildir/tmp? Shouldn't these be moved to Maildir/new at delivery? If this isn't always the case, can someone please explain why they haven't been moved and also when, if ever, they will be. Stuff in tmp is partially-delivered mail where the delivery had to be aborted for some reason -- process killed for some reason, etc... It should be deleted after 1-2 days. Whatever reads from the Maildir is responsible for deleting stale stuff out of tmp. I wouldn't worry too much if its 3-4 days old, but if you see stuff older than that, and you do actually read mail from that Maildir, whatever software you're using needs to be fixed. -- Sam
Re: Filtering on MAIL FROM:
Stefaan A Eeckels writes: Hi list, I've got a colleague who claims that many ISPs (he lives in Canada, so probably Canadian ISPs) refuse mail based on the MAIL FROM: command. To me, that seems inane and futile, but as I'm not an ISP, and don't work for one either, I'm solliciting the views of people in the know. Only true to a limited extent. Most ISPs reject MAIL FROM:s that are clearly bogus, but that's about it. The qmail connection being that I'm running qmail on our corporate server, and he wants me to basically make it an open relay so he can use the SMTP server from his portable (he's on the road a lot, uses a lot of different ISP while on the road, wants his mail to look as if it comes from the corporate server, and can't/won't give me a range of IP addresses). Refusing mail that doesn't come from our domain is of course dimwitted, as we would not be receiving a lot of mail :-). He pretends this can be done with Exchange or Notes - I guess it's BS, but I don't know these animals... It's BS. In any case, he's a director of the joint, and threatens to migrate to Exchange (he's a big Exchange fan) if this can't be done. My solution would be to patch qmail-smtpd to *require* a auth before accepting any further commands, and to run it on another port. Does this sound OK? Sounds about right. I would also recommend that you start looking for another job, where people who obviously know zilch about technical issues are kept as far away from equipment as possible. Probably the best response to your PHB's drivel would probably to mention, casually, that although MSexchange has vaguely similar sounding features, it's for use on internal LANs only, and nobody uses them on the Internet because it makes it possible for hackers to break into the computer and destroy all documents. That should fix him. -- Sam
Re: Cleaning the queue
"Bob C. Ruddy" wrote: I have a bunch of messages 500+ sitting in my queue for an address that doesn't exist. Is there a way I can dequeue all messages queued up for that email address? The answer depends on the actual reason why it's stuck. You can always try to add an smtproutes entry to 127.0.0.1 for this domain, then hupping qmail-send. With a properly-configured Qmail this will result in all mail queued up for this domain to be immediately bounced, after which you can remove the smtproutes entry.
Re: maildrop (generic) filter question
Subba Rao writes:
On 0, Subba Rao [EMAIL PROTECTED] wrote:
if(^/(To|Cc): .*(jack||bob).*/ ){
to "!jack bob"
}
The above will foward any mail received by either jack OR bob to both jack AND bob.
I am assuming that's is the goal you are trying to acheive i.e. to send the mail to
both of them, even if it is addressed to only one of them. (I don't know why you
would want to do that. ;-) ).
The operator used for To and Cc, is a bitwise operator, where as for bob and jack,
we
are using logical operators.
The OR operator ( || ) is for 2 expressions. The correct syntax should be
if(^/(To|Cc): .*(jack|bob).*/ ){
to "!jack bob"
}
Congratulations. Any time either jack or bob receives a message, both of
them will now receive a copy of it.
That's not what the guy wants.
Re: maildrop (generic) filter question
Subba Rao writes:
On 0, Sam [EMAIL PROTECTED] wrote:
The OR operator ( || ) is for 2 expressions. The correct syntax should be
if(^/(To|Cc): .*(jack|bob).*/ ){
to "!jack bob"
}
Congratulations. Any time either jack or bob receives a message, both of
them will now receive a copy of it.
That's not what the guy wants.
Ok here it is.
if(^/(To|Cc): .*(jackbob).*/ ) {
to "!jack bob"
}
When there's a To: or Cc: header that contains the string 'jackbob',
verbatim, forward the message to both of them.
carries no special meaning in regular expressions.
if(^/(To): .*(jack|bob).*/ ^/Cc: .*(jack|bob).*/ ) {
to "!jack bob"
}
If there's a To: header containing either jack, or bob, and that there is a
Cc: header containing either jack, or bob, forward the message to both of
them.
According to these rules, if a message contains the following header:
To: jack, bob
The message will be discarded, because it meets neither conditions.
What you really want to do is very simple:
if (hasaddr("[EMAIL PROTECTED]"))
{
cc "! jack"
}
if (hasaddr("[EMAIL PROTECTED]"))
{
cc "! bob"
}
# Rest of the filtering instructions
Re: Any Decent IMAP server?
Thomas Neumann writes: Philip Gabbert [EMAIL PROTECTED] writes: Does anybody have any suggestions on a good IMAP server? I've gotten courier-imap installed and running, but my IMAP clients (Netscape Communicator 4.7 on RedHat Linux and Outlook Express 5.0 on a Mac) are getting an error back from courier-imap: "Error in IMAP command received by server". This seems to be a generic error message that is used when any is sent wrong to the server. Did you strictly follow the hints given at URL:http://www.inter7.com/courierimap/README.imap.html on how to configure Netscape for IMAP? Works for me (modulo creating subfolders, but thats a Netscape bug). Creating or deleting subfolders works for me with Communicator 4.7. It's still very, very buggy. When I try to delete a folder, the stupid thing asks me, literally: "Do you really want to delete folder '(null)'?" -- Sam
Re: Problem compiling courier-imap
Stefan Osterman writes: More problems... Configure is done making the Makefiles but when I try to make I get this bash# make Making all in numlib Making all in bdbobj gcc -DHAVE_CONFIG_H -I. -I. -I. -g -O2 -c bdbobj2.c bdbobj2.c: In function `bdbobj_firstkey': bdbobj2.c:24: too few arguments to function *** Error code 1 make: Fatal error: Command failed for target `bdbobj2.o' Current working directory /eggandbacon/usr/users/stv/courier-imap-0.18/bdbobj *** Error code 1 make: Fatal error: Command failed for target `all-recursive' I configured to use BerkelyDB2 No problems here with "Sleepycat Software: DB 2.4.14: (6/2/98)". -- Sam
Re: Qmail and Ident.
Warren Beckett writes: Hi all. I have been watching my qmail logs and parallel with logs from other firewall and noticed that the qmail box is generate a large number of ident lookups. Does anyone know what is cause this, and how do I stop it. Standard behavior of tcpserver. man tcpserver will tell you how to turn it off, if it bothers you. But, there are some good reasons not to, because any ident response gets recorded in the headers, and there are certain fringe situations where source of abuse can only be determined with the help of ident data. -- Sam
Re: quoted-printable encoding
On Thu, 25 Nov 1999, Masuo Gates wrote: Hello, Is there a patch to automatically decode quoted-printable and remove the: Content-Transfer-Encoding: quoted-printable header? No. Qmail never edits message contents.
RE: Hmmm... Corel Linux
On Thu, 25 Nov 1999, Peter Cavender wrote: If that is the case, I may very well ditch RH for my co-lo...I have two floppies worth of "mods" to my base RH 6.1. Does Corel include all the extra goodies: checkpasswd,ucspi-tcp,daemontools,etc?? Does the .deb extension mean they are using the Debian installer thingey? Corel distro is based on Debian. You should be able to install any Debian pkg on top of Corel.
Re: Limiting incoming connections
Russell Nelson writes: Michael Cunningham writes: My boss would like me to find out if it is possible to limit the number of incoming connections qmail will accept to a specific number? Bandwidth is a huge issue here and incoming smtp connections are sucking a lot of it. Unfortunatly we dont have a lot of bucks to upgrade right now.. thus we need to figure out how we can control incoming smtp connections. If you reject incoming smtp connections, they'll just be back later, and you'll be out the bandwidth it took to reject them in the first place. Unless you have a reason to believe that bandwidth later (as in: hours later) is cheaper than bandwidth now, you'd do better to accept the message the first time. Well, when you get suddenly hit with a crapload of connections from the same source, dropping them makes a lot of sense. Most MTAs will dutifully try again later, at which point you hope you won't be as busy as you are now. tcpserver will, of course, limit the total number of sessions overall. My tcp daemon, assuming that I've correctly implemented asynchronous zombie reaping, can also limit the maximum number of connections from the same C block, or from the same IP address. It is included in courier-IMAP, but can perfectly function all by itself, replacing all of tcpserver's functionality. -- Sam
Re: Sorting incoming mail.
Tristan Hannover writes: Hello, I have done that, it works now, but the mail is delivered to /var/mail... How can I squeeze ./Mailbox in there somehow? [root@ny root]# cat /etc/maildroprc DEFAULT="./Maildir" [root@ny root]# ./Mailbox wil work just as well. Alternatively, edit maildrop/config.h, and stick it into the define for DEFAULT_DEF. -- Sam
Re: Sorting incoming mail.
On Fri, 12 Nov 1999, Tristan Hannover wrote: Hello, I was curious if anyone uses maildrop (or equivalents) to sort incoming mail to various folders (depending on subject, from, to), or even rewrite various headers on demand. And if so, would anyone please show me the correct to integrate maildrop into qmail? Maildrop's homepage shows its setup for sendmail, but makes no references for qmail. I tried to use the procmail startup files, and when replaced procmail with maildrop string (for piping incoming messages to it), my qmail no longer receives any mail. Use the startup command in Qmail's INSTALL, except replace ./Maildir with '| /usr/local/bin/maildrop', including the single quotes.
Re: Maildrop samples
On Fri, 12 Nov 1999, Jay Swackhamer wrote: From: Keith Burdis [EMAIL PROTECTED] There are some examples in the maildropex(5) man page. There are dozens more examples in the qmail-uce anti-spam package on Mr.Sam's page. http://www.geocities.com/SiliconValley/Peaks/5799/qmail-uce.html This sounds like a good time for me to mention that I'm not going to maintain this code for much longer. If anyone wants to pick up the ball, feel free to do so. The simple reason is that I'm in the process of migrating away from Qmail, so at some point around Y2K I will no longer need to use that code myself. I should clarify that this is in regards to Qmail and the qmail-uce patch only. I'm still actively using, maintaining, and developing maildrop.
Re: Prepatched IMAP anyone?
Mirko Zeibig writes: On Wed, Nov 10, 1999 at 03:55:27PM -0500, Denis Voitenko wrote: I have consistently failed to patch the IMAP source successfully so that it could work with Maildir. Does anyone have an already patched source that he'd be willing to share with me? If this is a new system you might want to give mrsam's courier-imapd a chance which will work with Maildir *only* and seems to be smaller/faster than UW's. Take a look at freshmeat.net and look for courier and imap to get the URL (wasn't it posted to the list a few days back, then?). Sorry, but could not find the URL in the source quikly. The URL is http://www.inter7.com/courierimap/ One word of caution is that Netscape's IMAP client is horribly broken, and it often sends IMAP commands that explicitly break the syntax specified in RFC 2060. I suppose that other IMAP servers grudgingly have been written to accomodate Netscape's crap, but I'd rather have Netscape fix their broken code instead. As long as you're not using Netscape Communicator, it'll be OK. -- Sam
Re: qmail remote delivery logic
David Dyer-Bennet writes: Sam [EMAIL PROTECTED] writes on 8 November 1999 at 17:39:02 -0500 Pard'n me, but how does an additional DNS lookup for every recipient end up reducing the overall amount of DNS traffic? qmail does fewer DNS lookups than sendmail, and that should be Not always. I just described the situation where it does not. -- Sam
Re: qmail remote delivery logic
Stefan Paletta writes: Sam wrote/schrieb/scribsit: different domains will result in only 5,000 DNS queries. Meanwhile, each instance of qmail-remote should diligently issue a DNS query - for a grand sum of 10,000 queries overall. When we're talking about lists of that size, you will for sure have the resources to handle 5000, 1 or 10 DNS queries compared to the resources you need for actually sending the messages. My experiences show, that for lists of up to 1 recipients, qmail will already have finished lots of deliveries when the first lookups on bad/unreachable addresses get a timeout. With serialized lookups everything will just sit idle for ages. I all boils down, as you said in another mail, to that qmail opimizes for delivery time and optimizes bandwidth usage at the upper end. Well, I wouldn't say that. Not exactly. Qmail optimizes delivery time, and requires reasonable (but not too great) bandwidth in situations involving medium to moderately high volumes of mail. Qmail will also do pretty well when the mail volume is low, although there are certain pathological situations where Qmail will fail miserably with low mail volume. Also, Qmail will do poorly in the extreme upper end of the range, where your mail volume goes through the roof. That's mostly a result due to a combination of factors: namely excessive amounts of DNS queries, and a lot of excessive TCP/IP traffic because Qmail does not recycle TCP/IP connections, nor does it batch same-domain recipients in any way. Also, the fact that its limited to 255 concurrent qmail-remotes also comes into play, at one point. Sure, you can argue that all you have to do is to put in a dozen of OC-3s to handle the excessive amounts of bandwidth, and solve the 255 qmail-remote issue by instead splitting the mail traffic across multiple servers, in parallel. However, multiple servers still adds up to the same amount of bandwidth via your pipes, and no amount of bandwidth will affect the fact that a few hops away, most your traffic gets squeezed through a single T-1, or even a T-3. -- Sam
Re: qmail remote delivery logic
Russell Nelson writes: Jim B writes: Can someone point me at the location of a document that explains why qmail would deliver, for example, a msg to 5 recipients at the same remote domain with 5 individual smtp connections instead of one smtp connection and multiple RCPT TOs? Because it's faster. Only under certain conditions. Try sending a 1 MB attachment to a dozen recipients.
Re: qmail remote delivery logic
On Sun, 7 Nov 1999, Russell Nelson wrote: Sam writes: Russell Nelson writes: Jim B writes: Can someone point me at the location of a document that explains why qmail would deliver, for example, a msg to 5 recipients at the same remote domain with 5 individual smtp connections instead of one smtp connection and multiple RCPT TOs? Because it's faster. Only under certain conditions. Try sending a 1 MB attachment to a dozen recipients. Have you? Yes. Even off a T1, there's a measurable difference between ~10 MB and ~1 MB worth of traffic.
Re: Bounce refused due to empty From, resulting in double bounced. Workaround?
Pavel Ganelin writes: I looked through a lot of E-mail qmail archive discussing it, but I did not see any solution. We have domain A and run qmail-smtp server to relay E-mails for domain B. When a user X from domain B sends a message to the wrong address using our qmail server The messages bounced and qmail sends a message to X@B with From: The SMPT server on B refuses to accept it (null from, spam filtering in action I assume) and it ends double bouncing to me as postmaster@A. I saw a lot of messages that I should mail postmaster@B a copy of RFC :-) My usual solution for this situation is to blacklist the idiots with a very descriptive error message: 517-Your mail server, [hostname] violates RFC 822. 517 See URL:ftp://ftp.isi.edu/in-notes/rfc822.txt My response to any subsequent inquiries is that the sending mail server has a problem. If necessary, I am always ready to launch into a very extensive discussion regarding fine points of RFC 822, RFC 821, RFC 2045, and other favorite topics of mine. Sooner or later, the problem usually fixes itself :-) -- Sam
Re: qmail - PMDF weirdness
David L. Nicol writes: The situation is, that messages for certain (but not all) recipients on a VMS-PMDF system do not get delivered from qmail. PMDF issues odd error messages or drops the connections, on only these users. Messages to other users go through fine. I have a sloppy working fix of setting up a smtproute to the PMDF box through a relay running (boo, hiss) sendmail. Messages to these same users neither bounce nor hang up in sendmail's queue: these users don't have full mailboxes or something like that. Does anyone have an idea what might be happening and how to fix it? [ snip ] The messages involved in these failed delivery attempts were identical to messages to other PMDF users which went through without difficulty. The question is "how identical are they"? If they are the same exact message - but with multiple recipients, then I have no answer. Otherwise, my guess would be that the troublesome messages are 8bit MIME messages, and the PMDF box does not accept 8bit MIME mail. Qmail violates a certain RFC whose number I'm sure someone remembers better than I do, and attempts to deliver an 8bit message without downshifting it to quoted-printable encoding, to a relay that does not advertise support for 8bit MIME messages. Result: undefined behavior. I've seen it happen. -- Sam
Re: methods for ETRN
[EMAIL PROTECTED] writes: Some of our clients use ETRN to get their mail. I'm wondering what are my choices of solutions to implement this feature into qmail. The only thing I have found is at http://defiant.cqc.com/~pacman/projects/qmail-etrn/. Is anyone using this? If so, how's it working for you? Any and all solutions are appreciated. The final long-term solution is to get your clients to use an alternative mail arrangement. ETRN is a solution in search of a problem. Even though someone is maintaining ETRN workaround and hacks right now does not mean that this will always be that way. If your clients do not have a permanent Internet connection, they should use a more appropriate protocol than SMTP in order to download their mail. -- Sam
Re: methods for ETRN
Pashinin writes: Recommend, please, protocol instead SMTP in such case. UUCP. -- Sam
Re: methods for ETRN
Pashinin writes: As I think, POP3 or IMAP accounts is the best way for users, but not for organizations. Besides, why POP3 better SMTP for feeding large mail stream over unstable, slow connection ? No kind of mail stream should be fed over an unstable, slow connection. If you want reliable mail delivery, use a permanent, reliable transport, and run SMTP on top of it. If you have part time connectivity, use any kind of a part time mail transfer protocol, such as POP3, IMAP, or UUCP. -- Sam
Re: Winsock Failures Under RedHat 6.1
John K. Chester writes: works fine except for one server which has great trouble sending mail to my server. It's running NTMail under Windows NT 4.0. On my end, I see a log entry in /var/log/qmail-smtpd/, but no entry in /var/log/qmail/. On the sending end, I see that the connection attempt was terminated by a Winsock error. Oh The spooky thing? 30 seconds after this email appeared in my inbox, an email which the problem server has been trying to send me since 20:00 GMT yesterday appeared. Many of the emails it tries to send me do eventually appear, usually some time the following day. Check the DNS and the ident port on the IP address this is coming from. It's possible that the DNS is cocked up and the ident query stalls long enough for NT to toss its cookies most of the time, and requeue the message for another delivery attempt. But, once in a blue moon, the beast might get distracted by something else, and by the time it finishes, you've timed out and sent the banner. -- Sam
Re: SMTP Help.
On Sat, 16 Oct 1999, Larry H. Raab wrote: Well...the question I asked is if it was an OK place to put it. If INETD.CONF isn't a boot script could you tell me a better place to put it that might be a boot script? You will find that in the documentation for your specific operating system. Different systems use different boot scripts.
Re: Wrong date when qmail is called from /bin/mail
Todd A. Jacobs writes: My date offset seems to have aquired a problem since I moved from sendmail to qmail when mailing from the command-line using /bin/mail under Red Hat 6.0. I get the following date: Date: 16 Oct 1999 23:55:55 - while sending from pine returns: Date: Sat, 16 Oct 1999 16:57:35 -0700 (PDT) Any ideas as to what's wrong, and how I can fix it? There's nothing wrong, and nothing to fix. Both datestamps accurately reflect the local time of about 4:57PM US Pacific Daylight Time.
