qmail Digest 31 May 2000 10:00:01 -0000 Issue 1018
Topics (messages 42469 through 42528):
Scanning outgoing attachments
42469 by: Jean-Baptiste Jacquemard
Re: vpopmail + qmail
42470 by: Christian Wiese
42478 by: clemensF
42481 by: Christian Wiese
MDaemon delivery "protocol timeout"
42471 by: Lee Haw Ling
Re: A good book for qmail
42472 by: qmail.col7.metta.lk
42473 by: Ali Sahin
42474 by: Peter van Dijk
Re: qmail-smtp problem
42475 by: Greg Owen
re:re: qmail-smtp problem
42476 by: Tore Micaelsen
Re: A Good Book On Qmail
42477 by: Rodney Edwards
42490 by: Russ Allbery
42492 by: John R. Levine
Re: help - very slow POP3 mail retrieval
42479 by: clemensF
42485 by: chuck
42487 by: Greg Jorgensen
Re: qmail + vpopmail error
42480 by: Christian Wiese
qmail-smtpd and stunnel
42482 by: Johan Almqvist
Backup logs
42483 by: Paul Aviles
42484 by: J. I. Sendoro
42486 by: clemensF
42488 by: Paul Aviles
Re: Qpopper 2.53 remote problem, user can gain gid=mail (fwd)
42489 by: Russ Allbery
42494 by: John Gonzalez/netMDC admin
Re: i-love-you-letter - Claus Farber.
42491 by: Russ Allbery
DRAFT RFD - comp.mail.qmail - Comments Sought (Was: qmail advocacy questions)
42493 by: Darren Wyn Rees
42496 by: Peter van Dijk
42508 by: Russ Allbery
42511 by: Peter van Dijk
42512 by: Magnus Bodin
42521 by: Russ Allbery
How to achieve better logging
42495 by: Kost, Kathy
This is strange..
42497 by: Vince Vielhaber
42498 by: Peter van Dijk
42500 by: Vince Vielhaber
42502 by: Peter van Dijk
42509 by: clemensF
42514 by: Rogerio Brito
Qmail: problems with SMTP e Qmailadmin
42499 by: Edilmar Alves
Migrating to Qmail, Maildir issues
42501 by: net admin
42510 by: clemensF
How to pipe qmail into another program
42503 by: Steve Quezadas
42504 by: Peter van Dijk
Re: Binary distribution
42505 by: Mate Wierdl
doc tarballs
42506 by: Mate Wierdl
Help adding taglines to relayed messages.
42507 by: Dave Potter
42513 by: Peter Samuel
42523 by: clemensF
How to install virtualdomains in qmail
42515 by: Rupak Joshi
Modifying qmail-remote
42516 by: Jean-Baptiste Jacquemard
42518 by: Peter Samuel
42520 by: Bruce Guenter
42522 by: Jean-Baptiste Jacquemard
42524 by: Peter Samuel
42525 by: Peter Samuel
qmail features
42517 by: Dung Nguyen
42519 by: Peter Samuel
pop3 Log file?
42526 by: Marco Benetton
42527 by: Petr Novotny
qmail Server
42528 by: Nguyen Hong Son
Administrivia:
To unsubscribe from the digest, e-mail:
[EMAIL PROTECTED]
To subscribe to the digest, e-mail:
[EMAIL PROTECTED]
To bug my human owner, e-mail:
[EMAIL PROTECTED]
To post to the list, e-mail:
[EMAIL PROTECTED]
----------------------------------------------------------------------
Hello, I would like to scan all outgoing traffic and log the attachments file names, and accessory, the size of the attached file. Please help me, I don't know how to do that. -- Jean-Baptiste Jacquemard ======================== J. POLLAK & Cie SNC 4, rue de la Bourse 75002 PARIS
Hi Toni, please tell us what kind of qmail package and what Linux distribution do you use.
On some systems the POP3 service in /etc/services is called pop3, but qmail-pop3d uses pop-3.
So please have a look at the /etc/services and check out what is writen there under port 110.
If there is an entry like pop3 change it to pop-3 and try to run your qmail-pop3d server again.e.g. /etc/services
-------------------------------------------
pop-3 110/tcp pop-3 # POP version 3
pop-3 110/udp pop-3
-------------------------------------------Greetings
Christian
Toni schrieb:
Hi, I have a problem, I have a Linux server with qmail-smtp and vpopmail-pop3.When I restart the server, the pop3 server is not running and I must stop the smtp service, start the pop3 service and restart the smtp service.But, the system don't give me any error, only I execute netstat -l and the pop3 service is not in the list of the active services. Have you a solution for this error?
> Christian Wiese: > please tell us what kind of qmail package and what Linux distribution do > you use. > On some systems the POP3 service in /etc/services is called pop3, but > qmail-pop3d uses pop-3. > So please have a look at the /etc/services and check out what is writen > there under port 110. > If there is an entry like pop3 change it to pop-3 and try to run your > qmail-pop3d server again. wow! you almost had me there, mr. wiese. barely had i finished reading your posting, when the times found me digging thru qmail, ucspi-tcp and the daemontools. i realized that nowhere does the source depend on internal name<->service-port guessing. as a matter of fact somewhere in the first lines of tcpserver.c/main the service name/number is scanned and handed to getservbyname, which eventually (might) return the tcp port to watch. but your advice is to the point, i just want to add that it might be saver not to *change* these lines in /etc/services, but to *add* them: programs might appear which insist on looking for the name `pop3'. > e.g. /etc/services > > ------------------------------------------- > pop-3 110/tcp pop-3 # POP version 3 > pop-3 110/udp pop-3 > ------------------------------------------- ------------------------------------------- pop-3 110/tcp pop-3 # POP version 3 pop-3 110/udp pop-3 pop3 110/tcp pop-3 # POP version 3 pop3 110/udp pop-3 ------------------------------------------- -- Valerian Q. Farthingsworthe-Jones III
Hi Clemens, thank you for your suggestions. You're right. Surely it will be better to add "pop-3" to the /etcservices insteed of changing pop3 to pop-3. Anyway, I think the provided informations will help Toni to solve his problem. greetings christian clemensF schrieb: > > Christian Wiese: > > > please tell us what kind of qmail package and what Linux distribution do > > you use. > > On some systems the POP3 service in /etc/services is called pop3, but > > qmail-pop3d uses pop-3. > > So please have a look at the /etc/services and check out what is writen > > there under port 110. > > If there is an entry like pop3 change it to pop-3 and try to run your > > qmail-pop3d server again. > > wow! you almost had me there, mr. wiese. barely had i finished reading > your posting, when the times found me digging thru qmail, ucspi-tcp and the > daemontools. i realized that nowhere does the source depend on internal > name<->service-port guessing. as a matter of fact somewhere in the first > lines of tcpserver.c/main the service name/number is scanned and handed to > getservbyname, which eventually (might) return the tcp port to watch. > > but your advice is to the point, i just want to add that it might be saver > not to *change* these lines in /etc/services, but to *add* them: programs > might appear which insist on looking for the name `pop3'. > > > e.g. /etc/services > > > > ------------------------------------------- > > pop-3 110/tcp pop-3 # POP version 3 > > pop-3 110/udp pop-3 > > ------------------------------------------- > > ------------------------------------------- > pop-3 110/tcp pop-3 # POP version 3 > pop-3 110/udp pop-3 > pop3 110/tcp pop-3 # POP version 3 > pop3 110/udp pop-3 > ------------------------------------------- > > -- > Valerian Q. Farthingsworthe-Jones III
Hi, Has anyone encounter delivery failure from MDaemon.v3.0.4.R? Is it a MDaemon's problem or Qmail's? Thanks. .david -----Original Message----- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]] Sent: Sunday, May 28, 2000 1:34 PM To: Postmaster Subject: Permanent Delivery Failure The attached message had PERMANENT fatal delivery errors! After one or more unsuccessful delivery attempts the attached message has been removed from the mail queue on this server. The number and frequency of delivery attempts are determined by local configuration parameters. YOUR MESSAGE WAS NOT DELIVERED! --- Partial Session Transcript --- MX-record resolution of [wahsin.com.sg] in progress (DNS Server: 203.126.216.162)... P=010 D=wahsin.com.sg TTL=(720) MX=[mail.wahsin.com.sg] {203.127.120.227} Attempting MX: P=010 D=wahsin.com.sg TTL=(720) MX=[mail.wahsin.com.sg] {203.127.120.227} Attempting SMTP connection to [203.127.120.227 : 25] Waiting for socket connection... Socket connection established Waiting for protocol initiation... 30 second wait for protocol timeout exceeded. This message is 2 days old; it has 0 days left to get delivered [EMAIL PROTECTED] will be informed that this delivery attempt failed --- End Transcript --- : Message contains [1] file attachments
On Thu, May 18, 2000 at 11:57:31AM +0100, [EMAIL PROTECTED] wrote: Hi, I have been on this list for about a year, and it has made a very good book on Qmail by now. Jacob > Can anyone recommend a good all round book for qmail?
Then probably a next question could be like this: Where can I obtain the archive of this mailing list? -Ali > [EMAIL PROTECTED] wrote: > > Hi, > > I have been on this list for about a year, > and it has made a very good book on Qmail by now. > > Jacob > > > Can anyone recommend a good all round book for qmail? > >
On Tue, May 30, 2000 at 03:15:09PM +0300, Ali Sahin wrote: > Then probably a next question could be like this: > > Where can I obtain the archive of this mailing list? www.qmail.org has links to 2 or 3 archives. Greetz, Peter. -- [EMAIL PROTECTED] - Peter van Dijk [student:developer:madly in love]
> Have a strange problem with qmail-smtpd.. when i use pine > to send a mail from my mailserver..it stands for a long > time waiting before it sends the mail, same when i telnet > to port 25 from the mailserver to the mailserver...it takes > a while before the "220 hostname ESMTP" comes up.. > > But if i send or telnet from another host it goes right away... > > Anyone have a pointer what might be wrong? You are probably starting qmail-smtpd using tcpserver, and the default "-r" option is causing it to attempt to connect to the ident server on the host you are connecting from. Unless you specify "-R" in your tcpserver command line, it will do this, and then will wait for 26 seconds if there is no ident server answering the call. (You can read all about this in the tcpserver man page). You can fix this by turning off the TCPREMOTEINFO (ident) checks, or by running ident on your mailserver. -- gowen -- Greg Owen -- [EMAIL PROTECTED]
No, found my problem. missed a name in /var/qmail/control/locals had: mydomain.dom server.mydomain.dom ; but missed "mail.mydomain.dom" which is the name i have for the mail-server... :) But Thanks for your time! Tore ----- Original Message ----- From: Greg Owen <[EMAIL PROTECTED]> To: qmail mailing list <[EMAIL PROTECTED]> Sent: Tuesday, May 30, 2000 3:31 PM Subject: RE: qmail-smtp problem > > Have a strange problem with qmail-smtpd.. when i use pine > > to send a mail from my mailserver..it stands for a long > > time waiting before it sends the mail, same when i telnet > > to port 25 from the mailserver to the mailserver...it takes > > a while before the "220 hostname ESMTP" comes up.. > > > > But if i send or telnet from another host it goes right away... > > > > Anyone have a pointer what might be wrong? > > You are probably starting qmail-smtpd using tcpserver, and the > default "-r" option is causing it to attempt to connect to the ident server > on the host you are connecting from. Unless you specify "-R" in your > tcpserver command line, it will do this, and then will wait for 26 seconds > if there is no ident server answering the call. (You can read all about > this in the tcpserver man page). > > You can fix this by turning off the TCPREMOTEINFO (ident) checks, or > by running ident on your mailserver. > > -- > gowen -- Greg Owen -- [EMAIL PROTECTED] >
Qmail & ezmlm is now getting so popular that someone has to get their arse in gear and get a book to print. The Idea is a certain winner so com'on O'reilly, Que, or Sam's if your listening in get your finger out guys where drowning out here.
Rodney Edwards <[EMAIL PROTECTED]> writes: > Qmail & ezmlm is now getting so popular that someone has to get their > arse in gear and get a book to print. The Idea is a certain winner so > com'on O'reilly, Que, or Sam's if your listening in get your finger out > guys where drowning out here. I don't believe that publisher interest is the hold-up. To publish a book, someone has to write it first, and one would hope that the people doing so would actually know a decent amount about qmail. :) Those people are somewhat rare; qmail hasn't been around for that long yet. -- Russ Allbery ([EMAIL PROTECTED]) <http://www.eyrie.org/~eagle/>
>> Qmail & ezmlm is now getting so popular that someone has to get their >> arse in gear and get a book to print. The Idea is a certain winner so >> com'on O'reilly, Que, or Sam's if your listening in get your finger out >> guys where drowning out here. > >I don't believe that publisher interest is the hold-up. If Russ and I got our butts in gear and wrote the book, Tim O'Reilly would be overjoyed to publish it. (Tim and I discussed this just last week.) I hope we can get it written this summer, which would make the book come out sometime near the end of the year. -- John R. Levine, IECC, POB 727, Trumansburg NY 14886 +1 607 387 6869 [EMAIL PROTECTED], Village Trustee and Sewer Commissioner, http://iecc.com/johnl, Member, Provisional board, Coalition Against Unsolicited Commercial E-mail
> Greg Jorgensen: > I manage a server at a small business. The server is a P133 with 32 > megs of RAM, running RedHat 6.1, Samba, and qmail 1.03. There are > only five users connected to the server, all running Windows 98, and > they are very light users. The entire office gets maybe 20 emails a > day. > > For some reason email messages longer than just a few lines take a > VERY long time to download, with numerous "server timeout" messages. > This is not specifically a qmail problem (see my tests below), but > I'm hoping someone will have some clues. try tcpdump(8). i've had a similiar problem articulating itself as continuous denials to finally establish connections, thereby forcing clients to an endless search for fallbacks which didn't behave differently. tell us what "tcpdump | tcpshow" answers. or maybe leave out tcpshow. make the -s<buffer> option large enough to capture large packets. -- clemens
Greg, I had a similar problem a few months back. Turns out that the permissions/ownership on my Maildirs were kludged. I suspect you may have a similar problem. Are you using user accounts or virtual domains? regards, Chuck Werbick The Wirehouse Internet Cafe Greg Jorgensen writes: > I manage a server at a small business. The server is a P133 with 32 > megs of RAM, running RedHat 6.1, Samba, and qmail 1.03. There are > only five users connected to the server, all running Windows 98, and > they are very light users. The entire office gets maybe 20 emails a > day. > > For some reason email messages longer than just a few lines take a > VERY long time to download, with numerous "server timeout" messages. > This is not specifically a qmail problem (see my tests below), but > I'm hoping someone will have some clues. > > The qmail-pop3d .run file (running from supervise) is: > > tcpserver -H -R -l server.local.net 0 110 \ > qmail-popup server.local.net \ > checkpassword qmail-pop3d Maildir 2>&1 \ > splogger pop3d > > (I've tried this with & without splogger, tcpserver, and supervise.) > > Sending a message approx. 100K locally (never leaves the LAN) can > take 5-10 minutes to retrieve. A message with several large > attachments can take HOURS to download. > > These are all of the things I've tried, to no avail. As far as I can > tell nothing has an effect. > > * Sending the message is fast, so SMTP service and overall network > performance are OK. > > * Copying the same file to/from the server (onto a Samba share) is > fast. > > * DNS checked and re-checked; all workstations see each other, and > pings to/from the server are under 1ms. > > * Replaced qmail-qpop3d with gnu-pop3d. > > * Replaced entire qmail setup with postfix/gnu-pop3d. > > * Stopped all unnecessary services. Stopped Samba. > > * We're using MS Outlook Express. Downloaded Eudora 4.3 and tried it. > > Same problem. In fact telnetting to port 110 and retrieving the > message is slow. > > * Authenticating to qmail-pop3d works OK, so there's no problem or > reverse-DNS lookup problem. It's the actual message retrieval that > takes a long time and/or times out. > > * NIC diagnostics are OK. Nothing unusual in the Linux boot messages > or logs. > > * Replaced the NIC in the server. > > * Disconnected all workstations and the firewall (WebRamp 700s) from > the switch (Bay Networks 10/100 8-port) so just the server and one > workstation were connected. > > > I have searched Deja and used Google to scour the web but I haven't > found anyone else reporting this problem. I've tried everything I can > > think of. Please post suggestions here or send email. > > Thanks! > > Greg Jorgensen > Programmer, pedant, raconteur > Portland, Oregon USA > gregj#pobox.com > >
chuck wrote: > > Greg, > I had a similar problem a few months back. Turns out that the > permissions/ownership on my Maildirs were kludged. I suspect you may have a > similar problem. Are you using user accounts or virtual domains? No virtual domains, only user accounts. It's a normal RedHat 6.1 install, so PAM and shadow passwords are enabled. I've checked the permissions and they look good (but please tell me what you are using). This problem happens on all user accounts so if there is a permissions problem every account has it. It's not an authentication issue because I can telnet to port 110, login, and retrieve a message. The authentication works fine and there's no delay at all. But when I retrieve a big message I can actually see it stall out. After the first chunk of the message the server spits it out in little pieces with long delays in between. I suspected pop3d was starved for memory, but stopping Samba frees up lots of RAM, and top is showing plenty of RAM available (over 8 megs) and 98% CPU idle. At first I suspected a bad NIC or cable somewhere on the LAN, but I think I've eliminated that possibility. I also double-checked my DNS settings and all looks OK (the mail server also runs DNS). SMTP is more sensitive to bad DNS than pop3d, and there is no delay sending mail from the clients to the server, or from the server out to other SMTP servers. I'm still stumped. Thanks! Greg Jorgensen [EMAIL PROTECTED] > > regards, > Chuck Werbick > The Wirehouse Internet Cafe > > > Greg Jorgensen writes: > > > I manage a server at a small business. The server is a P133 with 32 > > megs of RAM, running RedHat 6.1, Samba, and qmail 1.03. There are > > only five users connected to the server, all running Windows 98, and > > they are very light users. The entire office gets maybe 20 emails a > > day. > > > > For some reason email messages longer than just a few lines take a > > VERY long time to download, with numerous "server timeout" messages. > > This is not specifically a qmail problem (see my tests below), but > > I'm hoping someone will have some clues. > > > > The qmail-pop3d .run file (running from supervise) is: > > > > tcpserver -H -R -l server.local.net 0 110 \ > > qmail-popup server.local.net \ > > checkpassword qmail-pop3d Maildir 2>&1 \ > > splogger pop3d > > > > (I've tried this with & without splogger, tcpserver, and supervise.) > > > > Sending a message approx. 100K locally (never leaves the LAN) can > > take 5-10 minutes to retrieve. A message with several large > > attachments can take HOURS to download. > > > > These are all of the things I've tried, to no avail. As far as I can > > tell nothing has an effect. > > > > * Sending the message is fast, so SMTP service and overall network > > performance are OK. > > > > * Copying the same file to/from the server (onto a Samba share) is > > fast. > > > > * DNS checked and re-checked; all workstations see each other, and > > pings to/from the server are under 1ms. > > > > * Replaced qmail-qpop3d with gnu-pop3d. > > > > * Replaced entire qmail setup with postfix/gnu-pop3d. > > > > * Stopped all unnecessary services. Stopped Samba. > > > > * We're using MS Outlook Express. Downloaded Eudora 4.3 and tried it. > > > > Same problem. In fact telnetting to port 110 and retrieving the > > message is slow. > > > > * Authenticating to qmail-pop3d works OK, so there's no problem or > > reverse-DNS lookup problem. It's the actual message retrieval that > > takes a long time and/or times out. > > > > * NIC diagnostics are OK. Nothing unusual in the Linux boot messages > > or logs. > > > > * Replaced the NIC in the server. > > > > * Disconnected all workstations and the firewall (WebRamp 700s) from > > the switch (Bay Networks 10/100 8-port) so just the server and one > > workstation were connected. > > > > > > I have searched Deja and used Google to scour the web but I haven't > > found anyone else reporting this problem. I've tried everything I can > > > > think of. Please post suggestions here or send email. > > > > Thanks! > > > > Greg Jorgensen > > Programmer, pedant, raconteur > > Portland, Oregon USA > > gregj#pobox.com > > > > > > >
Hi Andy, thank you very much for your help. It seems to function :))) Greetings Christian Andy Grimberg schrieb: > Yeah I just had this problem and Drazen Ferencic on the vpopmail list > helped. Here's the solution: > > In cron.hourly there is a script that the rpm installs. If you remove > this script everything will start working properly. Basically the > script checks on an hourly basis looking for if new _users_ were added > to the machine and cleaning up the users CDB. The drawback to this is > that it cleans it of any VD that vpopmail adds in. > > -Andy- > > On Mon, 29 May 2000, you wrote: > > Hi all, > > > > I've installed qmail (RPM from Bruce) and vpopmail 3.4.11-2. > > Authentication is done via MySQL 3.22.32-1 > > I've installed the first virtualdomain and added the first user, and > > everything is ok. > > After some time I get the message "Sorry,no mailbox here by that name" > > for the same user. > > If I delete the virtualdomain and add the domain and the user again, the > > user is able to get messages for a short time, and I'll get the error > > message again. > > Does anybody knows what's going wrong ? > > > > Thank you, > > > > Christian > -- > Andrew J. Grimberg > Programmer > WebSuite.com > 206-988-2233 > ------------------------------------------------------- > > -- > Andrew J. Grimberg > Programmer > WebSuite.com > 206-988-2233
Hi! I'm using stunnel (with -n smtp) to do smtp-over-ssl (or TLS). However, there is one problem: I can't get the Recieved: line to show the host that originally connected - at least not with stunnel in port forwarding mode. Maybe I should run qmail-smtpd from stunnel's command line, with tcpserver (wich i like) running stunnel (and thus setting the ENV correctly)? Yeah, I'll try that. Okay, I kinda answered my own question... Any hints/tips/pointers before i start (BTW: same problem with apache...) -Johan -- Johan Almqvist
Hi Do not think i'm intervene you to get your answer, but can you please give me tips on how to back up all autox-going mails. Regards J. I. Sendoro The Network Is The Computer On Tue, May 30, 2000 at 01:52:33PM -0400, Paul Aviles wrote: > I know how to create backups for all incoming and outgoing messages by modifying the >extra.h file, but it is possible to target only certain accounts to do the backup on? > This box has multiple virtual domains and one of them wants to track incoming and >outgoing only for certain accounts. Using the extra.h copies everything for all >virtual domains. Is this possible with qmail? > > Thanks > > -pa >
> Paul Aviles: > I know how to create backups for all incoming and outgoing messages > by modifying the extra.h file, but it is possible to target only > certain accounts to do the backup on? This box has multiple virtual > domains and one of them wants to track incoming and outgoing only for > certain accounts. Using the extra.h copies everything for all virtual > domains. Is this possible with qmail? you might consider using sgrep (structured text grep) *afterwards*, i.e. logg everything and choose later. -- clemens
Brian, I forsee a couple of issues with this approach. If John Doe (the user that will contain all messages incomming and outgoing) receives a message, he will get a second copy. If John Doe sends mail, he will get also a copy. If you have aliases associated with the domain like [EMAIL PROTECTED] he will also get a copy. I like your idea of kinda having a validation rule, but I have no clue on how to do it. Any pointers? Also, this does impose an extra load on the server, but I guess there is no way to change that right? thanks -pa ----- Original Message ----- From: Brian Johnson <[EMAIL PROTECTED]> To: Paul Aviles <[EMAIL PROTECTED]> Sent: Tuesday, May 30, 2000 2:18 PM Subject: Re: Backup logs > > Paul Aviles wrote: > > I know how to create backups for all incoming and outgoing messages by > > modifying the extra.h file, but it is possible to target only certain > > accounts to do the backup on? This box has multiple virtual domains > > and one of them wants to track incoming and outgoing only for certain > > accounts. Using the extra.h copies everything for all virtual domains. > > Is this possible with qmail? > > make a .qmail file for the user the logs go to that calls a script that > looks at the to and from names in the e-mail and if it matches one of > the addresses you want to log have it write it to a file, otherwise have > it discard the message.. >
John Gonzalez/netMDC admin <[EMAIL PROTECTED]> writes: > Qpopper works fine for us, there is also a server-mode directive to > change this default behavior to be more like a regular pop server, it > will NOT copy the file and cause chunking on the HD. We use qpopper currently in a high-volume environment, but I definitely wouldn't describe it as "fine." We have a bunch of local patches to try to reduce the amount of completely pointless work that it does by default (or even the slightly non-pointless but still very time consuming stuff, like updating Status headers, which isn't necessary in our particular environment), and it's still a total hog. We're looking at switching to Cyrus instead for a variety of reasons, including better support for Kerberos, a better on-disk storage format, integration with IMAP (which we're starting to need), a better way of managing users, and in general a cleaner and seemingly more reliable package. -- Russ Allbery ([EMAIL PROTECTED]) <http://www.eyrie.org/~eagle/>
On 30 May 2000, Russ Allbery wrote: >John Gonzalez/netMDC admin <[EMAIL PROTECTED]> writes: > >> Qpopper works fine for us, there is also a server-mode directive to >> change this default behavior to be more like a regular pop server, it >> will NOT copy the file and cause chunking on the HD. > >We use qpopper currently in a high-volume environment, but I definitely >wouldn't describe it as "fine." We have a bunch of local patches to try Like i said originally... we use qpopper, and it works fine for us. Your mileage however, may vary. We are a small shop, and dont have many customer accounts on this box. It serves our virtual domains well, and on our busy server where our dialup account mail is stored, we use maildir and qpop-3d. There isnt enough traffic to max out the box, and i believe that even a poorly coded pop3 server should be able to handle a light load =) I'm not in a position to stress test the box, i have neither the time, nor the customer base, nor the will or want to do it just for shits and grins... But, as always, everyones needs are different. It filled a gap when we first started, and aside from the security flaws that pop up somewhat regularly, we've been quite happy. Besides, the price was right =) -- _ __ _____ __ _________ ______________ /_______ ___ ____ /______ John Gonzalez/Net.Tech __ __ \ __ \ __/_ __ `__ \/ __ /_ ___/ MDC Computers/netMDC! _ / / / `__/ /_ / / / / / / /_/ / / /__ (505)437-7600/fax-437-3052 /_/ /_/\___/\__/ /_/ /_/ /_/\__,_/ \___/ http://www.netmdc.com [---------------------------------------------[system info]-----------] 5:55pm up 19 days, 23:21, 4 users, load average: 0.53, 0.48, 0.43
dsr <[EMAIL PROTECTED]> writes: > Claus has been attaching a signature to his messages which looks like an > attachment to a borken mail reader, but not to any compliant mail > reader. This isn't an entirely fair characterization, in my opinion. He's adding a signature which looks roughly like a uuencoded section, although would fail a detailed regex check. Many people, myself included, are using mail readers that have an *option* to scan the body for uuencoded segments and "convert" them on display to attachments, treating them the same as MIME attachments, for convenience in dealing with legacy encoded messages. Claus's signature also fools Gnus to the degree of showing up as an attachment. I think this is harmless; I just ignore it. Sure, it could use a more detailed check (like making sure each line except the second to the last starts with M), but that would also make it slower, and I really don't mind the false positives. (And I do mind having the body scanning be slower.) In other words, it's possible for Claus's signature to show up as an attachment in a non-borken mail reader; it's just not a big deal. -- Russ Allbery ([EMAIL PROTECTED]) <http://www.eyrie.org/~eagle/>
Below, I've quoted a DRAFT RFD proposal for comp.mail.qmail. I have every intention of mailing this to isc.org within the next fortnight, pending some further feedback, clarifications and checks. Here is your collective opportunity to comment on this draft. Darren -=-=-=-=-=-= THIS IS A DRAFT -=-=-=-=-=-=-=- NOTES : I prefer using lowercase 'q' in qmail. But for the sake of grammatical correctness, in the RFD I've used 'Q'. I'm unsure on a couple of dates... and I'd like clarification on the things I've {bracketted} with '{'. Please comment on what 'newsgroup line' you prefer. I prefer the first one listed. ---------------------8<------------CUT-HERE----------->8--------------------- From: Darren Wyn Rees <[EMAIL PROTECTED]> Subject: RFD: comp.mail.qmail To: Qmail Discussion List <[EMAIL PROTECTED]> Newsgroups: news.groups.newgroups,news.groups,comp.mail.misc Followup-To: news.groups REQUEST FOR DISCUSSION (RFD) unmoderated group comp.mail.qmail This is a formal Request For Discussion (RFD) for the creation of a comp.mail.qmail. This is not a Call for Votes (CFV); you cannot vote at this time. Procedural details are below. Newsgroup line: comp.mail.qmail {The Qmail MTA software.} {Qmail mailer.} {Discussion of the Qmail mailer.} {Discussion of the Qmail MTA.} RATIONALE: comp.mail.qmail Qmail (http://www.qmail.org) is a secure mailer or MTA (mail transport agent) developed by Daniel J. Bernstein since {1996}. Discussion on the Qmail project has been focussed in the Qmail list ([EMAIL PROTECTED]) which has received over {40,000} messages since {1996/1997}. Currently there is no Qmail newsgroup and Qmail-related discussion occurs on a number of other newsgroups eg. comp.mail.(sendmail|misc). comp.mail.qmail would enable people to share Qmail knowledge and ideas. CHARTER: comp.mail.qmail The newsgroup comp.mail.qmail is for discussion of the Qmail mail transport agent (MTA) software. This newsgroup is a worldwide resource for Qmail users and developers. Discussions on other mail (MTA) software may occur, however, pointless 'flame wars' about which MTA is best should be avoided. Commercial postings and announcements of new products and services are allowed provided they are directly relevant to Qmail. comp.mail.qmail will not be moderated. Expected topics of discussion will include but are not limited to : * installation of Qmail * upgrading from another MTA to Qmail * running & maintenance * development * performance issues & testing * support (commercial or otherwise) * qmail and MLMs (eg. ezmlm, http://www.ezmlm.org) * use of Qmail with other software (eg. MUAs) Inappropriate posts will include : * flaming * spam * binaries, attachments or other encoded date (eg. graphics, HTML) * off-topic (not related to qmail) or offensive postings Small patches may be distributed here, but large files should be placed on users' homepages or FTP site. END CHARTER PROCEDURE: [ THIS IS A DRAFT RFD/PROPOSAL ] This is a request for discussion, not a call for votes. In this phase of the process, any potential problems with the proposed newsgroups should be raised and resolved. The discussion period will continue for a minimum of 21 days (starting from when the first RFD for this proposal is posted to news.announce.newgroups), after which a Call For Votes (CFV) may be posted by a neutral vote taker if the discussion warrants it. Please do not attempt to vote until this happens. All discussion of this proposal should be posted to news.groups. This RFD attempts to comply fully with the Usenet newsgroup creation guidelines outlined in "How to Create a New Usenet Newsgroup" and "How to Format and Submit a New Group Proposal". Please refer to these documents (available in news.announce.newgroups) if you have any questions about the process. DISTRIBUTION: This RFD has been posted to the following newsgroups: comp.mail.misc And the following e-mail lists: [EMAIL PROTECTED] (Qmail discussion list) Proponent: Darren Wyn Rees <[EMAIL PROTECTED]> [THIS WAS A DRAFT RFD/PROPOSAL] ---------------------8<------------CUT-HERE----------->8--------------------- -- this is my .sig, show me yours
On Tue, May 30, 2000 at 10:55:28PM +0000, Darren Wyn Rees wrote: [snip] > -=-=-=-=-=-= THIS IS A DRAFT -=-=-=-=-=-=-=- > > NOTES : I prefer using lowercase 'q' in qmail. But for the sake > of grammatical correctness, in the RFD I've used 'Q'. Even grammatical correctness would dictate a lowercase q, since the name of the program in question has been devised with a lowercase q. > Please comment on what 'newsgroup line' you prefer. I prefer the > first one listed. > > ---------------------8<------------CUT-HERE----------->8--------------------- > From: Darren Wyn Rees <[EMAIL PROTECTED]> > Subject: RFD: comp.mail.qmail > To: Qmail Discussion List <[EMAIL PROTECTED]> > Newsgroups: news.groups.newgroups,news.groups,comp.mail.misc > Followup-To: news.groups > > REQUEST FOR DISCUSSION (RFD) > unmoderated group comp.mail.qmail > > This is a formal Request For Discussion (RFD) for the creation of a > comp.mail.qmail. This is not a Call for Votes (CFV); you cannot vote > at this time. Procedural details are below. > > Newsgroup line: > comp.mail.qmail {The Qmail MTA software.} > {Qmail mailer.} > {Discussion of the Qmail mailer.} I'd pick this one, yes. > {Discussion of the Qmail MTA.} > > RATIONALE: comp.mail.qmail > > Qmail (http://www.qmail.org) is a secure mailer or MTA (mail transport > agent) developed by Daniel J. Bernstein since {1996}. 19960124 qmail 0.70, beta. is what the changelog says. Don't know about anything before that. > Discussion on the Qmail project has been focussed in the Qmail list > ([EMAIL PROTECTED]) which has received over {40,000} messages > since {1996/1997}. Lowercase q's, IMnsHO, everywhere, _even_ at the start of sentences. I can only find that the list switched to ezmlm in Feb 1997. > Currently there is no Qmail newsgroup and Qmail-related discussion > occurs on a number of other newsgroups eg. comp.mail.(sendmail|misc). Perhaps mention the mailinglist here? [snip] > > Inappropriate posts will include : > > * flaming > * spam > * binaries, attachments or other encoded date (eg. graphics, HTML) With possible exclusion of small patches for problems that are discussed? > Small patches may be distributed here, but large files > should be placed on users' homepages or FTP site. Ok :) Looks nice, overally. Good plan, anyway :) Greetz, Peter. -- [EMAIL PROTECTED] - Peter van Dijk [student:developer:madly in love]
Darren Wyn Rees <[EMAIL PROTECTED]> writes: > Below, I've quoted a DRAFT RFD proposal for comp.mail.qmail. I'm not sure this is a good idea, mostly because I don't see the distinction between the newsgroup and this mailing list and I also don't expect the people using the mailing list to really want to move to a newsgroup. Without the core of people on this mailing list that know qmail very well and answer most of the questions, the newsgroup is unlikely to be all that useful, and I haven't heard much indication that those people would really prefer a newsgroup. -- Russ Allbery ([EMAIL PROTECTED]) <http://www.eyrie.org/~eagle/>
On Tue, May 30, 2000 at 10:18:39PM -0700, Russ Allbery wrote: > Darren Wyn Rees <[EMAIL PROTECTED]> writes: > > > Below, I've quoted a DRAFT RFD proposal for comp.mail.qmail. > > I'm not sure this is a good idea, mostly because I don't see the > distinction between the newsgroup and this mailing list and I also don't > expect the people using the mailing list to really want to move to a > newsgroup. Without the core of people on this mailing list that know > qmail very well and answer most of the questions, the newsgroup is > unlikely to be all that useful, and I haven't heard much indication that > those people would really prefer a newsgroup. That is true. I currently do not read news, and also do not know when I will be reading news again. What value will it add besides the mailinglist? Greetz, Peter. -- [EMAIL PROTECTED] - Peter van Dijk [student:developer:madly in love]
On Wed, May 31, 2000 at 07:33:32AM +0200, Peter van Dijk wrote: > > That is true. I currently do not read news, and also do not know when I > will be reading news again. What value will it add besides the mailinglist? You can get a lot of nice mail from people selling things to you ;-) I personally will never post to that newsgroup with my real mail address. I'll keep using the mailinglists. Isn't the general shift nowadays (since 1994 and forward) from news to mailinglists just because of the big problem with spam-address-collectors on usenet? /magnus -- http://x42.com/
Magnus Bodin <[EMAIL PROTECTED]> writes: > Isn't the general shift nowadays (since 1994 and forward) from news to > mailinglists just because of the big problem with > spam-address-collectors on usenet? If that's the case, you're all already doomed; this mailing list has been gated to two or three different newsgroups for years now. I've noticed because my messages to it keep showing up in Deja. That's common for most large mailing lists. In my personal experience, Usenet is slightly more of a harvesting risk than large and well-known mailing lists but it isn't *that* significant. Pretty much everything pales in comparison to web harvesting now, actually. (And of late, I get a reasonable amount of Chinese spam and almost no other spam; I'm down to averaging around five pieces of spam a day and I do essentially no filtering. But .edu addresses seem to have a very different spam pattern than .com addresses.) I'm a huge fan of Usenet for a lot of things, and an advocate of Usenet, but it's also my experience that technical fora tend to start as either newsgroups or mailing lists and generally don't move well from one to another. You couldn't turn, say, comp.unix.programmer into a mailing list without losing a lot of the strong points of the group, and similarly I don't think this mailing list would convert to a newsgroup well. And I don't think there's enough qmail discussion to really warrant both this mailing list and a Big Eight newsgroup. -- Russ Allbery ([EMAIL PROTECTED]) <http://www.eyrie.org/~eagle/>
Title: How to achieve better logging
Hi folks,
We are running qmail with tcpserver and rblsmtpd under Linux. I'm actually used to running sendmail and
am used to its particular style of logging. In sendmail, if I'm using an rbl for filtering out spammers, I'm used to
seeing in the maillog the log of the address denied/rejected. Is there a way to do this with qmail? Right
now I don't see anything and I'm not sure if it's because nothing is being rejected or because it's just
designed not to log. I was looking for some configuration information in order to make the logging more
verbose for rblsmtpd but haven't located any.Thanks for any ideas here.
Kathy Kost
[EMAIL PROTECTED]
I have two customers that are running stock qmail-1.03 that are having the same problem. You can send mail to them either with an MUA, mailsubj or telnetting straight to port 25. Look at the logs on the local machine right afterward and it says the remote host accepted the mail (I double checked the address to make sure it was the right place and not an MX). I also looked in the queue and the mail was there. The problem is that it takes a long time (we're talking minutes not seconds) for the mail to get delivered to the local mailbox. It also happens if a local user sends mail to a local user. To answer the usual question, there is nothing in the logs until it gets around to delivering the mail. But when it does it delivers all the mail that's stuck. I've gone over all the files in /var/qmail/control and they're correct. Neither machine is running DNS but both are able to look up names (including their own) without delay from the nameservers that are listed in resolv.conf. Anyone have a suggestion? Vince. -- ========================================================================== Vince Vielhaber -- KA8CSH email: [EMAIL PROTECTED] http://www.pop4.net 128K ISDN from $22.00/mo - 56K Dialup from $16.00/mo at Pop4 Networking Online Campground Directory http://www.camping-usa.com Online Giftshop Superstore http://www.cloudninegifts.com ==========================================================================
On Tue, May 30, 2000 at 08:40:09PM -0400, Vince Vielhaber wrote: > The problem is that it takes a long time (we're talking minutes not > seconds) for the mail to get delivered to the local mailbox. It > also happens if a local user sends mail to a local user. To answer > the usual question, there is nothing in the logs until it gets around > to delivering the mail. But when it does it delivers all the mail > that's stuck. I've gone over all the files in /var/qmail/control > and they're correct. Neither machine is running DNS but both are > able to look up names (including their own) without delay from the > nameservers that are listed in resolv.conf. > > Anyone have a suggestion? Permissions on /var/qmail/queue/lock/trigger no doubt. Should look like: prw--w--w- 1 qmails qmail 0 May 30 13:13 trigger| Greetz, Peter. -- [EMAIL PROTECTED] - Peter van Dijk [student:developer:madly in love]
On Wed, 31 May 2000, Peter van Dijk wrote: > On Tue, May 30, 2000 at 08:40:09PM -0400, Vince Vielhaber wrote: > > The problem is that it takes a long time (we're talking minutes not > > seconds) for the mail to get delivered to the local mailbox. It > > also happens if a local user sends mail to a local user. To answer > > the usual question, there is nothing in the logs until it gets around > > to delivering the mail. But when it does it delivers all the mail > > that's stuck. I've gone over all the files in /var/qmail/control > > and they're correct. Neither machine is running DNS but both are > > able to look up names (including their own) without delay from the > > nameservers that are listed in resolv.conf. > > > > Anyone have a suggestion? > > Permissions on /var/qmail/queue/lock/trigger no doubt. > > Should look like: > prw--w--w- 1 qmails qmail 0 May 30 13:13 trigger| > > Greetz, Peter. > You hit that one on the head! That was the fix. Thanks! Vince. -- ========================================================================== Vince Vielhaber -- KA8CSH email: [EMAIL PROTECTED] http://www.pop4.net 128K ISDN from $22.00/mo - 56K Dialup from $16.00/mo at Pop4 Networking Online Campground Directory http://www.camping-usa.com Online Giftshop Superstore http://www.cloudninegifts.com ==========================================================================
On Tue, May 30, 2000 at 09:11:20PM -0400, Vince Vielhaber wrote: [snip] > > Permissions on /var/qmail/queue/lock/trigger no doubt. > > > > Should look like: > > prw--w--w- 1 qmails qmail 0 May 30 13:13 trigger| > > > > Greetz, Peter. > > > > You hit that one on the head! That was the fix. That's why I said "no doubt" ;) > Thanks! You're welcome! Greetz, Peter. -- [EMAIL PROTECTED] - Peter van Dijk [student:developer:madly in love]
> Vince Vielhaber: > I have two customers that are running stock qmail-1.03 that are having > the same problem. > > The problem is that it takes a long time (we're talking minutes not > seconds) for the mail to get delivered to the local mailbox. It > also happens if a local user sends mail to a local user. To answer what does a packet trace with tcpdump show? -- clemens
On May 30 2000, Vince Vielhaber wrote: [trigger problem diagnostic] > You hit that one on the head! That was the fix. Yeah, that's a pretty standard problem. Another one is that if your pop server is importing the Maildirs by NFS from another machine and their clocks are not synchronized, then qmail-pop3d won't tell the client about messages with timestamps in the future. What could be a motivation for this behaviour? (I haven't looked at the sources to see if it is a technical matter or just "policy"). []s, Roger... -- =-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-= Rogerio Brito - [EMAIL PROTECTED] - http://www.ime.usp.br/~rbrito/ Nectar homepage: http://www.linux.ime.usp.br/~rbrito/nectar/ =-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=
Hi all, I'd like to solve the following problems: 1. SMTP: I configured tcp.smtp like this, to accept e-mails only for these IP subnets: 192.168.0.:allow,RELAYCLIENT="" 192.168.1.:allow,RELAYCLIENT="" 200.241.184.:allow,RELAYCLIENT="" However, I entered from other ISP, with address 200.212.255.25 and SMTP sents my email. I boot Linux but the same behaviour continues to occurr. 2. QMailAdmin: for 10, 20, 50 users, I think QMailAdmin is very nice. However, I already have more than 600 users, and when I enter with postmaster, to administer the email accounts, I have to spent more than FIVE minutes, using Netscape. I'm using the "graphical interface" from lynx, cause performance !!! Is there a way to change the HTML skeleton pages to show only the buttons, NOT the users list. I think the access may be faster than. 2. QMailAdmin II: I created some users (+/- 103 users) into a domain. All Maildir folders was created into .../domains/fes.br/ (fes.br is my domain). After these 103, folders like 0/, 1/, ... was created automatically by QMail. At this point, no problems! However, if one of these new users created into these folders try to use QMailAdmin to change password, the system arises an exception talking about "There already is a user logged with postmaster" (something like this) and the new doesnt get to change your password. I have to change password user per user, with postmaster account. The major users were created with QMailAdmin and some with vadduser. Both users arises the exception. The strange is: the first users created get to change password into Web QMailAdmin...
Hi Folks; I just spent a day and half preparing my heavly used Sendmail mailserver to migrate to Qmail. Compiled and configured: -- Qmail-1.03 -- ucspi-tcp-0.88 -- fastforward-0.51 -- checkpassword-0.81 all the above tested OK (except checkpassword because Qmail is not running yet). Also I setup config files: ../control/rcpthosts (all my children) ../control/virtualdomains (My cousins and virtualdomains) ../control/defaulthost (Masquerading) ../control/locals (Me, myself and I) /etc/tcp.smtp (Few hosts allowed to relay) The BIG questions is that all the users are now using /var/mail format for mail delivery, some users don't have local account on the mail server (POP3 dialup users) the rest have local accounts/homedirs on the mailserver but still use /var/mail format. I want to convert all mail delivery format to ~user/Maildir but how can I do that for those users that aready use /var/mail delivery and don't have local homedirs? How do I make a transparent switch and have all user to confirm to ~user/Maildir format? I thought that I've masterd the beast, and now comes another switch! Thanks alot Dan
> net admin: > I want to convert all mail delivery format to ~user/Maildir but how can I > do that for those users that aready use /var/mail delivery and don't have > local homedirs? that's easy. give them homedirs. -- clemens
# Start daemons.
echo -n "Starting qmail: "
csh -cf '/var/qmail/rc &'
touch /var/lock/subsys/qmail
echo
;;
. . .And the rc file (the important one I would imagine) is:
exec env - PATH="/var/qmail/bin:$PATH" \
qmail-start ./Mailbox splogger qmailBottom line: how do I pipe dmail in this? I don't find qmail-lspawn anywhere!
On Tue, May 30, 2000 at 06:26:37PM -0700, Steve Quezadas wrote: [snip] > > exec env - PATH="/var/qmail/bin:$PATH" \ > qmail-start ./Mailbox splogger qmail > > Bottom line: how do I pipe dmail in this? I don't find qmail-lspawn anywhere! Replace the './Mailbox' part with whatever you want. It's the part qmail-lspawn gets passed on. Greetz, Peter. -- [EMAIL PROTECTED] - Peter van Dijk [student:developer:madly in love]
Lars Uffman has made a binary distribution which includes both Linux and Solaris. I do not know where he is, he has not answered my emails regarding this; still here is the contact address for the binary package: [EMAIL PROTECTED] I remark that I also made a binary package for Linux, but the kit I used can be used to build a binary distr for Solaris too: ftp://moni.msci.memphis.edu/pub/qmail/var-qmail/ In particular: ftp://moni.msci.memphis.edu/pub/qmail/var-qmail/var-qmail-create-2.tar If you cannot reach Lars, then I probably can make a binary distribution for Solaris---somebody just has to tell me the "endianness" of Solaris. Mate
I made four tarballs from the docs found at cr.yp.to. The tarballs are ftp://moni.msci.memphis.edu/pub/doc/daemontools-0.70-doc-0.01.tar.gz ftp://moni.msci.memphis.edu/pub/doc/dnscache-1.00-doc-0.01.tar.gz ftp://moni.msci.memphis.edu/pub/doc/publicfile-0.52-doc-0.01.tar.gz ftp://moni.msci.memphis.edu/pub/doc/ucspi-tcp-0.88-doc-0.01.tar.gz They all install the way it is suggested by the instructions for the dnscache doc tarball, so you will get commands.html, libraries.html and packages.html The file ftp://moni.msci.memphis.edu/pub/doc/README.doc tells you about the tools in the tarballs you can use to update these docs. Mate -- --- Mate Wierdl | Dept. of Math. Sciences | University of Memphis
Hello, I've been searching through this list's archives and haven't been able to find where anyone has yet attempted to do the exact same thing I'm trying to. What I have set up is a standalone smtp server running qmail, and its sole purpose is to relay mail to other machines that handle the local delivery. Rather than modify configurations on each of the local servers, I'm trying to figure out the best way to have qmail on the relay machine call a custom program which will append to the body of a message a tagline that looks similar to Yahoo/Hotmail's taglines. Has anyone specifically done this yet? Looking at the source files, the best place I could come up with for inserting my own mods to the body of each message is in qmail-queue. If anyone has suggestions concerning putting a mod inside qmail-queue or if it should go into another file, any feedback would be great. Thanks! dave
On Tue, 30 May 2000, Dave Potter wrote: > Hello, > > I've been searching through this list's archives and haven't been able to > find where anyone has yet attempted to do the exact same thing I'm trying > to. > > What I have set up is a standalone smtp server running qmail, and its sole > purpose is to relay mail to other machines that handle the local delivery. > Rather than modify configurations on each of the local servers, I'm trying > to figure out the best way to have qmail on the relay machine call a > custom program which will append to the body of a message a tagline that > looks similar to Yahoo/Hotmail's taglines. > > Has anyone specifically done this yet? Looking at the source files, the > best place I could come up with for inserting my own mods to the body of > each message is in qmail-queue. If anyone has suggestions concerning > putting a mod inside qmail-queue or if it should go into another file, any > feedback would be great. Thanks! Write your own qmail-queue wrapper program. This should behave to the calling program as if it was the real qmail-queue (see the qmail-queue man page for details of the interface). After reading the message body, append your taglines, then call the real qmail-queue.orig progam. This is how Jason Haar's scan4virus works. Regards Peter ---------- Peter Samuel [EMAIL PROTECTED] Technical Consultant or at present: eServ. Pty Ltd [EMAIL PROTECTED] Phone: +61 2 9206 3410 Fax: +61 2 9281 1301 "If you kill all your unhappy customers, you'll only have happy ones left"
> Dave Potter: > Rather than modify configurations on each of the local servers, I'm trying > to figure out the best way to have qmail on the relay machine call a > custom program which will append to the body of a message a tagline that > looks similar to Yahoo/Hotmail's taglines. that's not difficult: put "| ( cat; cat <my-custom-footer> ) | qmail-inject" into the appropriate .qmail. the parenthezised expression takes the original message on stdin and appends some file to it, piping the result into qmail-inject. -- clemens
Hello, I have moved qmail-remote to qmail-remote.real I made a shell script named qmail-remote, with the same permissions which contains: #!/bin/sh exec /var/qmail/bin/qmail-remote.real "$*" But when I try to send a message, I got this from Mailer Daemon: <[EMAIL PROTECTED]>: Unable to run qmail-remote. Any idea? For information: dns:/var/qmail/bin# ls -l qmail-remote qmail-remote.real -rwx--x--x 1 root root 112 May 31 08:11 qmail-remote* -rwx--x--x 1 root root 21796 May 30 14:34 qmail-remote.real* -- Jean-Baptiste Jacquemard ======================== J. POLLAK & Cie SNC 4, rue de la Bourse 75002 PARIS
On Wed, 31 May 2000, Jean-Baptiste Jacquemard wrote: > Hello, > I have moved qmail-remote to qmail-remote.real > I made a shell script named qmail-remote, with the same permissions > which contains: > > #!/bin/sh > exec /var/qmail/bin/qmail-remote.real "$*" > > But when I try to send a message, I got this from Mailer Daemon: > <[EMAIL PROTECTED]>: > Unable to run qmail-remote. > > Any idea? Did you read the qmail-queue man page? qmail-queue behaves differently to "traditional" programs in that it reads from BOTH file descriptor 0 AND file descriptor 1. You need to make use of the pipe() call to call qmail-queue. A simple exec won't work. Have a look at Jason Haar's scan4virus package, his perl program does the correct thing. I too have a simple perl qmail-queue wrapper. Let me tidy it up and I'll post it to the list. It currently does nothing, but can be used to do whatever wrapping you feel is appropriate (provided you can write the code to do it). Regards Peter ---------- Peter Samuel [EMAIL PROTECTED] Technical Consultant or at present: eServ. Pty Ltd [EMAIL PROTECTED] Phone: +61 2 9206 3410 Fax: +61 2 9281 1301 "If you kill all your unhappy customers, you'll only have happy ones left"
On Wed, May 31, 2000 at 08:24:08AM +0200, Jean-Baptiste Jacquemard wrote: > I have moved qmail-remote to qmail-remote.real > I made a shell script named qmail-remote, with the same permissions > which contains: > > #!/bin/sh > exec /var/qmail/bin/qmail-remote.real "$*" > > But when I try to send a message, I got this from Mailer Daemon: > <[EMAIL PROTECTED]>: > Unable to run qmail-remote. > > Any idea? > For information: > dns:/var/qmail/bin# ls -l qmail-remote qmail-remote.real > -rwx--x--x 1 root root 112 May 31 08:11 qmail-remote* > -rwx--x--x 1 root root 21796 May 30 14:34 > qmail-remote.real* IIRC, qmail-remote is executed as user "qmailr", which doesn't have read permission on your new shell script. Shell scripts require read permission to execute. -- Bruce Guenter <[EMAIL PROTECTED]> http://em.ca/~bruceg/
Yes, it works now. Thank you for your help, and thanks to Peter Samuel too. Bruce Guenter wrote: > IIRC, qmail-remote is executed as user "qmailr", which doesn't have read > permission on your new shell script. Shell scripts require read > permission to execute. > -- > Bruce Guenter <[EMAIL PROTECTED]> http://em.ca/~bruceg/ -- Jean-Baptiste Jacquemard ======================== J. POLLAK & Cie SNC 4, rue de la Bourse 75002 PARIS
On Wed, 31 May 2000, Peter Samuel wrote: > > I too have a simple Pierl qmail-queue wrapper. Let me tidy it up and > I'll post it to the list. It currently does nothing, but can be used > to do whatever wrapping you feel is appropriate (provided you can > write the code to do it). I have attached qmail-queue-wrapper.pl. It is a generic qmail-queue wrapper. It currently does nothing to a message except add an extra header of the form Received: (qmail-queue-wrapper 24590 invoked from network); 31 May 2000 07:16:44 -0000 It then simply hands the message over to the real qmail-queue. If you know perl, you can modify it to do whatever you want - just don't come crying to me if it doesn't work after you've modified it. To install: install perl if you haven't got it on your system choose a non production system to test this on choose a quiet time save the perl file in /var/qmail/bin/qmail-queue-wrapper.pl stop qmail-smtpd stop qmail-qmqpd stop qmail cd /var/qmail/bin vi qmail-queue-wrapper.pl change the first line #!/pkgs/bin/perl -w to reflect where your perl binary really lives chown root qmail-queue-wrapper.pl chgrp qmail qmail-queue-wrapper.pl chmod 755 /tmp/qmail-queue-wrapper.pl # The wrapper program should NOT be setuid!!! mv qmail-queue qmail-queue.orig; mv qmail-queue-wrapper.pl qmail-queue start qmail start qmail-qmqpd start qmail-smtpd There is a small chance that mail injected into the queue via qmail-inject (and it's friends sendmail and datemail) will attempt to call qmail-queue between the "mv" commands above. That's why you should choose a quiet time. Regards Peter ---------- Peter Samuel [EMAIL PROTECTED] Technical Consultant or at present: eServ. Pty Ltd [EMAIL PROTECTED] Phone: +61 2 9206 3410 Fax: +61 2 9281 1301 "If you kill all your unhappy customers, you'll only have happy ones left"#!/pkgs/bin/perl -w # # $Id: qmail-queue-wrapper.pl,v 1.1 2000/05/31 07:20:37 psamuel Exp $ # # qmail-queue wrapper program. # # This program should be used when you wish to manipulate a mail # message BEFORE it is placed in the queue. Possible uses include: # # - header rewriting # - Firstname.Lastname replacements # - virus scanning # - anything else you can think of # # There are at least 2 ways of using this program: # # 1) Replace the original qmail-queue with this program: # # mv /var/qmail/bin/qmail-queue /var/qmail/bin/qmail-queue.orig # cp qmail-queue-wrapper /var/qmail/bin/qmail-queue # # Change the value of $qmailqueue below, to reflect the new name of # the original qmail-queue program. For example # # my $qmailqueue = "/var/qmail/bin/qmail-queue.orig"; # # 2) Recompile qmail with Bruce Guenter's QMAILQUEUE patch. (See # http://www.qmail.org/qmailqueue-patch). Then any program that # needs to use this program can be called with the environment # variable QMAILQUEUE set to /var/qmail/bin/qmail-queue-wrapper # # How does it work? The interface to the real qmail-queue is simple: # # - the body of the message is read from file descriptor 0 # - the envelope details are read from file descriptor 1. # # qmail-queue-wrapper also adheres to the same interface. After doing # whatever manipulations are necessary, it calls the real qmail-queue # and provides the message body on file descriptor 0 and the envelope # details on file descriptor 1. # # Exit codes conform to those mentioned in the qmail-queue(8) manual page. # ########################################################################### require 5; use strict; my $child; my $debug = 0; my $envelope; my %errors; my @months; my $new_received_header; my $qmailqueue = "/var/qmail/bin/qmail-queue.orig"; my @recipients; my $sender; ########################################################################### &initialise(); if ($child = fork()) { # Parent my $timeout = 86400; # See qmail-queue.c, line 20 alarm($timeout); &fatal(82) unless close MESSAGE_READER; &fatal(82) unless close ENVELOPE_READER; &process_message(); &process_envelope(); # Wait for the child to terminate waitpid($child, 0); # Return with the exit status of the child exit($? % 255); } elsif (defined $child) { # Child &fatal(82) unless close MESSAGE_WRITER; &fatal(82) unless close ENVELOPE_WRITER; &fatal(82) unless defined open(STDIN, "<&MESSAGE_READER"); &fatal(82) unless defined open(STDOUT, "<&ENVELOPE_READER"); if ($debug) { &debug_message("$$: Reading message from STDIN\n\n"); while (<STDIN>) { &debug_message("$$: $_"); } &fatal(82) unless close MESSAGE_READER; &debug_message("\n$$: ####################\n\n"); &debug_message("$$: Reading envelope from STDOUT\n"); while (<ENVELOPE_READER>) { s/\0/ /g; &debug_message("$$: $_\n"); } &fatal(82) unless close ENVELOPE_READER; exit(0); } else { unless (exec $qmailqueue) { # We shouldn't be here unless the exec failed &fatal(82); } } } else { # Unable to fork &fatal(82); } ########################################################################### sub initialise { &prepare_months(); &prepare_error_messages(); &ignore_signals(); &catch_signals(); &generate_new_received_header(); &setup_pipes(); } sub prepare_months { @months = ( "Jan", "Feb", "Mar", "Apr", "May", "Jun", "Jul", "Aug", "Sep", "Oct", "Nov", "Dec", ); } sub prepare_error_messages { # These are the exit codes and their meanings, as defined by the # real qmail-queue manual page. Many are not used by either the # real qmail-queue or this wrapper program. %errors = ( 11 => "Address too long", 31 => "Mail server permanently refuses to send " . "the message to any recipients", # Not used by qmail-queue, but can be used by # programs offering the same interface 51 => "Out of memory", 52 => "Timeout", 53 => "Write error; e.g., disk full", 54 => "Unable to read the message or envelope", 55 => "Unable to read a configuration file", # Not used by qmail-queue 56 => "Problem making a network connection from this host", # Not used by qmail-queue 61 => "Problem with the qmail home directory", 62 => "Problem with the queue directory", 63 => "Problem with queue/pid", 64 => "Problem with queue/mess", 65 => "Problem with queue/intd", 66 => "Problem with queue/todo", 71 => "Mail server temporarily refuses to send " . "the message to any recipients", # Not used by qmail-queue 72 => "Connection to mail server timed out", # Not used by qmail-queue 73 => "Connection to mail server rejected", # Not used by qmail-queue 74 => "Connection to mail server succeeded, but " . "communication failed", # Not used by qmail-queue 81 => "Internal bug; e.g., segmentation fault", 82 => "System resource problem", # Undefined in qmail-queue. Specific to this # wrapper program. 91 => "Envelope format error", ); } sub ignore_signals { # The real qmail-queue ignores a bunch of signals, so we will too. # Ensure all signals are not being blocked. foreach (keys %SIG) { $SIG{$_} = 'DEFAULT'; } # Ignore those signals that the real qmail-queue ignores. $SIG{'PIPE'} = 'IGNORE'; $SIG{'VTALRM'} = 'IGNORE'; $SIG{'PROF'} = 'IGNORE'; $SIG{'QUIT'} = 'IGNORE'; $SIG{'INT'} = 'IGNORE'; $SIG{'HUP'} = 'IGNORE'; $SIG{'XCPU'} = 'IGNORE' if (defined $SIG{'XCPU'}); $SIG{'XFSZ'} = 'IGNORE' if (defined $SIG{'XFSZ'}); } sub catch_signals { # The real qmail-queue catches a few signals, so we will too. $SIG{'ALRM'} = \&timeout; $SIG{'ILL'} = \&internal_bug; $SIG{'ABRT'} = \&internal_bug; $SIG{'FPE'} = \&internal_bug; $SIG{'BUS'} = \&internal_bug; $SIG{'SEGV'} = \&internal_bug; $SIG{'SYS'} = \&internal_bug if (defined $SIG{'SYS'}); $SIG{'EMT'} = \&internal_bug if (defined $SIG{'EMT'}); } sub timeout { &fatal(52); } sub internal_bug { &fatal(81); } sub generate_new_received_header { # Generate a Received: header of the form: # Received: (qmail 28672 invoked by alias); 16 Feb 2000 03:49:51 -0000 my @user = getpwuid($<); my @date = gmtime(); my $user; if ($user[0] eq "alias") { $user = "by alias"; } elsif ($user[0] eq "qmaild") { $user = "from network"; } elsif ($user[0] eq "qmails") { $user = "for bounce"; } elsif (scalar @user == 0) { # This should never happen - ie the real user id should # always have a password entry. $user = "by uid $<"; } else { $user = "by uid $user[2]"; } $date[5] += 1900; my $date = "$date[3] $months[$date[4]] $date[5]"; my $time = sprintf("%02d:%02d:%02d", $date[2], $date[1], $date[0]); $new_received_header = "Received: (qmail-queue-wrapper $$ invoked $user); $date $time -0000"; } sub setup_pipes { &fatal(82) unless pipe(MESSAGE_READER, MESSAGE_WRITER); &fatal(82) unless pipe(ENVELOPE_READER, ENVELOPE_WRITER); select(MESSAGE_WRITER); $| = 1; select(ENVELOPE_WRITER); $| = 1; } sub debug_message { my ($message) = @_; print STDERR "$message"; } sub fatal { my ($errno) = @_; &debug_message("$errors{$errno}\n") if $debug; exit($errno); } sub process_message { # If you plan on doing serious massaging of the message body, such # as virus scanning or MIME conversions, you should probably write # the message to a temporary file here. Once you have finished your # massaging you can read from the file. You could slurp the message # into memory but that may be a resource problem for you. Caveat # emptor! print MESSAGE_WRITER "$new_received_header\n"; while (<STDIN>) { print MESSAGE_WRITER; } &fatal(82) unless close MESSAGE_WRITER; } sub process_envelope { &read_envelope(); # If you don't want to do any rigourous checking of the envelope, # simply comment out the &check_envelope() statement. The real # qmail-queue will perform the same checks anyway. &check_envelope(); &close_envelope(); print ENVELOPE_WRITER "$envelope"; &fatal(82) unless close ENVELOPE_WRITER; } sub read_envelope { # Read the message envelope from file descriptor 1. At startup this is # already assigned to the Perl filehandle STDOUT. # Duplicate file descriptor 1 for reading &fatal(54) unless defined open(DUP_STDOUT, "<&STDOUT"); # Extract the envelope details. The stripping of the leading 'F' # and 'T' characters will be performed later. $envelope = <DUP_STDOUT>; } sub check_envelope { # There MUST be some envelope details. &fatal(54) unless defined $envelope; # The envelope details MUST be terminated by two NULLS. &fatal(54) if ($envelope !~ /\0\0$/); ($sender, @recipients) = split(/\0/, $envelope); # If there are no recipients, we should exit here. However, the # real qmail-queue will quite happily accept messages with no # recipients, so we will too. # The sender address MUST begin with an 'F' and the recipient # address(es) MUST begin with a 'T'. &fatal(91) if ($sender !~ /^F/); foreach (@recipients) { &fatal(91) if ($_ !~ /^T/); } # None of the addresses may be greater than $address_length # characters. (Remember that each address has an extra leading # character at this stage, so it's just a "greater than" test, # rather than a "greater than or equal to" test). my $address_length = 1003; # See qmail-queue.c, line 21 foreach ($sender, @recipients) { &fatal(11) if (length($_) > $address_length); } # The sender AND recipient address(es) should contain a username, # an @ sign and a fully qualified domain name. However, the real # qmail-queue does not enforce this, so we won't either. } sub close_envelope { # Close duplicated STDOUT &fatal(54) unless close DUP_STDOUT; }
On Wed, 31 May 2000, Jean-Baptiste Jacquemard wrote: > Yes, it works now. > Thank you for your help, and thanks to Peter Samuel too. It will also teach me to READ things more carefully. I thought you were talking about qmail-queue. In fact I thought you were the person taling about adding taglines to all messages. Repeats to himself "I must read things carefully" "I must read things carefully" "I must read things carefully" ... Regards Peter ---------- Peter Samuel [EMAIL PROTECTED] Technical Consultant or at present: eServ. Pty Ltd [EMAIL PROTECTED] Phone: +61 2 9206 3410 Fax: +61 2 9281 1301 "If you kill all your unhappy customers, you'll only have happy ones left"
Dear all I am a newer with this mailing list.I've got qmail-1.03 and I want to migrate to qmail, so I have some questions about qmail features _ Does qmail support IMAP4 ,LDAP , MIME ? and do I need some more patches ? _ Does qmail have ability avoiding Junk mail (spam) ? _ Does qmail allow administrator to control the limit of the messsages for different users ? Thank you very much __________________________________________________ Do You Yahoo!? Send instant messages & get email alerts with Yahoo! Messenger. http://im.yahoo.com/
On Tue, 30 May 2000, Dung Nguyen wrote: > Dear all > I am a newer with this mailing list.I've got > qmail-1.03 and I want to migrate to qmail, so I have > some questions about qmail features > _ Does qmail support IMAP4 ,LDAP , MIME ? and do I IMAPx - no. However this is a mail user agent issue and qmail is a mail transport agent. There are patches to the UW imapd that allow it to support qmail's Maildir/ format. There is also Courier IMAP which is a separate imap deamon that supports Maildir/ format. Look for pointers to these on http://www.qmail.org LDAP - no. Andre Oppermann has some ldap patches for qmail. See http://www.nrg4u.com MIME - Not a qmail issue. qmail doesn't care what is in the body of the message. It will support the 8BITMIME SMTP protocol extensions. > need some more patches ? > _ Does qmail have ability avoiding Junk mail (spam) ? No mailing system does! Some can help you minimise spam but NOTHING (apart from social change and re-education) will eliminate it. That said, qmail has a number of mechanisms to help you deal with spam. You can prevent specific senders and sender domains from talking to qmail-smtpd. You can prevent unauthorised mail relaying. If you use Dan's ucspi-tcp package to control the execution of qmail-smtpd (recommended)_ then you can use the rblsmtpd program in that package to block mail from sites listed with RBL, ORBS, DUL etc. > _ Does qmail allow administrator to control the limit > of the messsages for different users ? Incoming, outgoing, mailbox storage? What limits do you have in mind? Basically, no. There are quota patches for qmail. The user quotas problem is not really the job of the MTA. There is a mechanism to limit the size of incoming mail messages but it does not work on a user level. > Thank you very much Also have a look at Dave Sill's excellent Life With Qmail page http://web.infoave.net/~dsill/lwg.html Regards Peter ---------- Peter Samuel [EMAIL PROTECTED] Technical Consultant or at present: eServ. Pty Ltd [EMAIL PROTECTED] Phone: +61 2 9206 3410 Fax: +61 2 9281 1301 "If you kill all your unhappy customers, you'll only have happy ones left"
Hi, I haven't a file where there are the pop3 log. This is the configuration in the /etc/inetd.conf file pop-3 stream tcp nowait root /var/qmail/bin/qmail-popup qmail-popup dns.protec.it /bin/checkpassword /var/qmail/bin/qmail-pop3d Maildir Any suggestion? Thanks -- - Marco
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On 31 May 00, at 10:50, Marco Benetton wrote: > Hi, > I haven't a file where there are the pop3 log. What kind of log do you need/expect? > This is the configuration in the /etc/inetd.conf file > > > pop-3 stream tcp nowait root /var/qmail/bin/qmail-popup > qmail-popup dns.protec.it /bin/checkpassword > /var/qmail/bin/qmail-pop3d Maildir > > Any suggestion? No log is getting created this way (except that if /bin/checkpassword is PAMified, it reports failed authentication attempts). -----BEGIN PGP SIGNATURE----- Version: PGP 6.0.2 -- QDPGP 2.60 Comment: http://community.wow.net/grt/qdpgp.html iQA/AwUBOTTDjVMwP8g7qbw/EQKnfgCfRs4PC3uYCt+64baMorOYTieUeZ8AniSE EbY2GCZV12QEIVeTHWfJtG9Z =A3LG -----END PGP SIGNATURE----- -- Petr Novotny, ANTEK CS [EMAIL PROTECTED] http://www.antek.cz PGP key ID: 0x3BA9BC3F -- Don't you know there ain't no devil there's just God when he's drunk. [Tom Waits]
Dear all I found in this Mailing list about many features of qmail. Can I have some questions about using qmail for making a mail server. _ Is qmail one of a complete solution for making a mail server for Internet Services Provider (Creat and Manage user account, deliver quota for each mailbox, mail relay .v.v..) or only a Mail Transport Agent (MTA) ? _ I've got qmail-1.03, do I need some more patches for the complete solution ? Thank for advance ________________________________________________________________________ Get Your Private, Free E-mail from MSN Hotmail at http://www.hotmail.com
