unsubscribe qmail
Port 25
With some help from Jerry, I was able to narrow down a problem I am having with receiving mail from outside servers through Qmail. It's apparent that my port 25 is closed off to outside connections. I don't know how or why it's closed off.. TCPwrappers? Why would port 25 be closed off anyway. Perhaps there is a security feature in Mandrake 7.02 that closes this port? I was able to receive mail through sendmail before I installed qmail, so I am guessing qmail somehow closed port 25. How do I open that port? james
Share queue between servers and other questions.
I _need_ to be able able to do following, else I'll probibly end up in a sendmail solution: Share queue between servers: It is _not_ acceptable that if one of the servers dies (as in start burnin etc.. ie: a non-recoverble error) the mail that was in that queue is gone forever. We _must_ be able to put the queue on a NAS/SAN storage where several servers (atleast 4 servers) on different sites can process the queue. We also need to be able to split a domain over serveral servers. Example: User John Doe's ([EMAIL PROTECTED]) email is handeled on server 1 (as it is physicaly closer to him) and GI Jane's ([EMAIL PROTECTED]) email is stored on server 4, as it is closer to her. Why we need this is that company.com is spread all over the world, and the connection to the HQ is not always acceptible when it comes to speed and quality (not becasue HQ is in a bad place, but that the braches don't have that high-speed and good lines to the 'net). We need to be able to put our users in either LDAP or SQL database (well, this part is already solved for qmail+vpopmail). We are currently running on qmail 1.03 (with some patches for antivirus etc - a fairly normal setup I guess) and vpopmail 3.4.11-2 on Linux. Please help me with a solution to this problem else I'll end up installing sendmail sometime next week. Best regards Michael Boman -- W I Z O F F I C E . C O M L T D - Your Online Office Wizard 16 Tannery Lane, Crystal Time Building, #04-00, Singapore 347778 Voice : (+65) 844 3228 [extension 118] Fax : (+65) 842 7228 Pager : (+65) 92 93 29 49 ICQ : 5566009 Mobile: (+65) 97 87 39 14 eMail : mailto:[EMAIL PROTECTED]URL : http://www.wizoffice.com
Re: pop before SMTP recomendations
On Fri, May 12, 2000 at 12:15:22AM -0500, Peter Janett wrote: > I am looking for recomendations for pop before smpt add ons to qmail. > I've looked at a couple that are listed on the qmail.org site, but wanted to > see if any of you had recomendations. the relay-ctrl from Bruce G. is just great, and very easy to setup. Regards, Olivier
Re: Share queue between servers and other questions.
On Fri, May 12, 2000 at 03:43:39PM +0800, Michael Boman wrote: > Share queue between servers: It is _not_ acceptable that if one of the servers > dies (as in start burnin etc.. ie: a non-recoverble error) the mail that was in > that queue is gone forever. We _must_ be able to put the queue on a NAS/SAN > storage where several servers (atleast 4 servers) on different sites can process > the queue. You hint at the failure mode that you're trying to protect against, but it would be more helpful if you stated it explicitly: What is it that you want to protect against failing? Direct answer: Can't be done with stock qmail. I know of no attempts to patch qmail to do this. Alternate solution: Put the queue on an external RAID. Still need to connect to it by SCSI, but failure of the server hardware won't result in loss of the queue. Just hook up the backup server to the RAID, reboot, and fix the queue. Again, what it is that you're trying to protect against? Moving the queue to NAS implies that you want to continue operations independant of server hardware. Is that correct? Or is there some other failure mode that you're trying to protect against? John
qmail-smtpd appears to work but doesn't
I've followed the steps in the "Life as Qmail" document. The install seems to have gone without a hitch--- qmail, ucspi-tcp, daemontools. All the test along the way seem to work. TEST.deliver works fine. TEST.receive fails on the first test. I've tried to telnet to both 127.0.0.1 25 and direct to the domain the dialog, helo dude, mail, rcpt and data all give the correct results back. Looking in the /var/log/qmail/smtpd/current looks ok to me: @4000391ba61d07d823fc tcpserver: status: 1/40 @4000391ba61d07dc0bfc tcpserver: pid 8855 from 127.0.0.1 @4000391ba61d08b3f954 tcpserver: ok 8855 localhost:127.0.0.1:25 :127.0.0.1:root:1063 @4000391ba64910b5b3cc tcpserver: end 8855 status 0 @4000391ba64910b5fe04 tcpserver: status: 0/40 @4000391ba6bb0f0bbcec tcpserver: status: 1/40 @4000391ba6bb0f0fc814 tcpserver: pid 12466 from 209.81.49.16 @4000391ba6bc08c1a93c tcpserver: ok 12466 main.send2u.com:209.81.49.35:25 ceres.wallis.com:\ 209.81.49.16:mwallis:3795 @4000391ba6bc08ecc84c tcpserver: end 12466 status 0 @4000391ba6bc08ed87b4 tcpserver: status: 0/40 @4000391ba6c21d542014 tcpserver: status: 1/40 @4000391ba6c21db5107c tcpserver: pid 12641 from 209.81.49.35 @4000391ba6c21e560784 tcpserver: ok 12641 main.send2u.com:209.81.49.35:25 main.send2u.com:2\ 09.81.49.35:root:1067 @4000391ba6df32cf2de4 tcpserver: end 12641 status 0 @4000391ba6df32cf7fec tcpserver: status: 0/40 @4000391ba81e1bace854 tcpserver: status: 1/40 @4000391ba81e1bb0e3dc tcpserver: pid 20600 from 209.81.49.16 @4000391ba81f0e0bd14c tcpserver: ok 20600 main.send2u.com:209.81.49.35:25 ceres.wallis.com:\ 209.81.49.16:mwallis:3921 @4000391ba81f0ef834ec tcpserver: end 20600 status 0 @4000391ba81f0ef8f454 tcpserver: status: 0/40 @4000391bac810fe720fc tcpserver: status: 0/40 @4000391bada21a6f99dc tcpserver: status: 1/40 @4000391bada21a73ef3c tcpserver: pid 10219 from 209.81.49.16 @4000391bada3188cbc94 tcpserver: ok 10219 main.send2u.com:209.81.49.35:25 ceres.wallis.com:\ 209.81.49.16:mwallis:4431 @4000391bada31adede3c tcpserver: end 10219 status 0 @4000391bada31adfa95c tcpserver: status: 0/40 BUT nothing ever shows up in the Mailbox file. This seems strange to me since the TEST.deliver seemed to work fine. I got rid of the daemontools and the tcpserver and tried using inetd and the rc script directly. This also fails in exactly the same way. Is there a tool to trace where it's getting lost? I even did a find on the system by time to see if the data is just getting written in the wrong place. This is strange because it appears to accept the connection and says it was successful but nothing gets written to disk. Any ideas would be appreciated. Bob Brown
Re: qmail-smtpd appears to work but doesn't
On Fri, May 12, 2000 at 01:17:19AM -0700, Bob Brown wrote: > Is there a tool to trace where it's getting lost? There should be. You're looking at the smtpd logs, which show that an smtp connection existed. That's a start. How are you doing your logging. do you have a /var/log/qmail/ or something which doesn't log smtpd? John
Re: QMail Performance Question & Miscellaneous Issues
On Fri, May 12, 2000 at 12:40:28AM -0600, Neil Schemenauer wrote: > On Thu, May 11, 2000 at 10:54:37PM -0700, John White wrote: > > If you're looking for queue speed, you want RAID 1+0 with a > > NVRAM cache to accellerate the small block writes. > > zeroseek would be even cooler. Don't use zeroseek! Any writes made to vaporware are automatically lost!!! :) John
What is initd.conf?
I have been doing a search to find out how to open my port 25 for listening, and I've come across a suggestion that I should edit my initd.conf file to insure that port 25 is listening. I am using Mandrake 7.02 and I can't find initd.conf anywhere. It's not in /etc/ or /etc/rc.d/init.d or anywhere. Is this the file I need to edit to allow qmail to listen to port 25? Thanks. James
Re: What is initd.conf?
James wrote: > > I have been doing a search to find out how to open my port 25 for > listening, and I've come across a suggestion that I should edit my > initd.conf file to insure that port 25 is listening. I am using Mandrake > 7.02 and I can't find initd.conf anywhere. It's not in /etc/ or > /etc/rc.d/init.d or anywhere. > > Is this the file I need to edit to allow qmail to listen to port 25? > > Thanks. > > James he meant inetd.conf ^ -- "Parler pour ne rien dire et ne rien dire pour parler sont les deux principes majeurs et rigoureux de tous ceux qui feraient mieux de la fermer avant de l'ouvrir." -- Pierre Dac
Re: What is wrong, then?
Thanks to all of you who personally mailed me that it's inetd.conf, which I knew of already.. I just figured there was a new file called initd.conf. Ok, so I've opened the inetd.conf and found this at the bottom: smtp stream tcp nowait qmaild /var/qmail/bin/tcp-env tcp-env/var/qmail/bin/qmail-smtpd All of that line is on one line. Is this how it should be for Qmail? And if so.. how come I still can't telnet to port 25? Or send mail to my qmail server. I can send mail OUT from the server, as well as WITHIN the server to other users.. but I can't get mail from the outside. James
Qestion about qmail
Hi, I have read the installation procedure from life with qmail, I wonder what is the usage for postmaster , mailer-daemon, and root?? Which one is used for bouncing the messages.?? Thank you Mark
Re: Qestion about qmail
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On 12 May 00, at 17:07, Mark Lo wrote: > I have read the installation procedure from life with qmail, I > wonder what is the usage for postmaster , mailer-daemon, and root?? > Which one is used for bouncing the messages.?? Normally, the bounces come "from" mailer-daemon (controllable by /var/qmail/control/bouncefrom); some users might choose to reply to this message, therefore you create the alias. By RFC requirements, each host _must_ have a "postmaster" mailbox. Therefore you create the alias. Also, double bounces usually go to postmaster (controllable by /var/qmail/control/doublebounceto). It's wise to have an alias for root: First, lots of mail (like cron error reports) is sent to root. Second, qmail doesn't deliver to root (read: doesn't deliver under uid=0) - it delivers to root's alias. It's possible to let root, postmaster and mailer-daemon deliver to alias's mailbox; usually, you want to edit the files to forward mail to some real user (preferably the user who knows root's password). -BEGIN PGP SIGNATURE- Version: PGP 6.0.2 -- QDPGP 2.60 Comment: http://community.wow.net/grt/qdpgp.html iQA/AwUBORu9ClMwP8g7qbw/EQI9tQCfdIO1D+D/0zTZ1PmpojHp7kG4I6IAoLy4 fJVb1fvnP284k0/H9jOnvRCc =fYeY -END PGP SIGNATURE- -- Petr Novotny, ANTEK CS [EMAIL PROTECTED] http://www.antek.cz PGP key ID: 0x3BA9BC3F -- Don't you know there ain't no devil there's just God when he's drunk. [Tom Waits]
Re: Qestion about qmail
Hi, Thank you for your reply, what is double bounce?? And in my /var/qmail/control, I only have defaultdomain, me, locals, rcpthosts, virtualdomains, ...for those doesn't automatically appear at that directory, do i just create the appropriate file by myself.?? Or did i do something wrong in the installation process..so that It doesn't show up automatically.?? Thank You mark Petr Novotny wrote: > -BEGIN PGP SIGNED MESSAGE- > Hash: SHA1 > > On 12 May 00, at 17:07, Mark Lo wrote: > > > I have read the installation procedure from life with qmail, I > > wonder what is the usage for postmaster , mailer-daemon, and root?? > > Which one is used for bouncing the messages.?? > > Normally, the bounces come "from" mailer-daemon (controllable by > /var/qmail/control/bouncefrom); some users might choose to reply > to this message, therefore you create the alias. > > By RFC requirements, each host _must_ have a "postmaster" > mailbox. Therefore you create the alias. Also, double bounces > usually go to postmaster (controllable by > /var/qmail/control/doublebounceto). > > It's wise to have an alias for root: First, lots of mail (like cron error > reports) is sent to root. Second, qmail doesn't deliver to root (read: > doesn't deliver under uid=0) - it delivers to root's alias. > > It's possible to let root, postmaster and mailer-daemon deliver to > alias's mailbox; usually, you want to edit the files to forward mail to > some real user (preferably the user who knows root's password). > > -BEGIN PGP SIGNATURE- > Version: PGP 6.0.2 -- QDPGP 2.60 > Comment: http://community.wow.net/grt/qdpgp.html > > iQA/AwUBORu9ClMwP8g7qbw/EQI9tQCfdIO1D+D/0zTZ1PmpojHp7kG4I6IAoLy4 > fJVb1fvnP284k0/H9jOnvRCc > =fYeY > -END PGP SIGNATURE- > -- > Petr Novotny, ANTEK CS > [EMAIL PROTECTED] > http://www.antek.cz > PGP key ID: 0x3BA9BC3F > -- Don't you know there ain't no devil there's just God when he's drunk. > [Tom Waits]
Re: Qestion about qmail
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On 12 May 00, at 17:32, Mark Lo wrote: > Hi, > Thank you for your reply, what is double bounce?? You wanted to bounce the message, and the bounce bounced. Like mail from [EMAIL PROTECTED] to [EMAIL PROTECTED] > And in my > /var/qmail/control, I only have defaultdomain, me, locals, rcpthosts, > virtualdomains, ...for those doesn't automatically appear at that directory, > do i just create the appropriate file by myself.?? Most of the configuration files have sane defaults. man qmail-control explains them. > Or did i do something > wrong in the installation process..so that It doesn't show up > automatically.?? Oh no - your installation is perfectly fine. By saying "something is configurable" I do not infer "you must configure it". -BEGIN PGP SIGNATURE- Version: PGP 6.0.2 -- QDPGP 2.60 Comment: http://community.wow.net/grt/qdpgp.html iQA/AwUBORvB+1MwP8g7qbw/EQLaOgCgt2h9kl+lVwoJVWplQXco3EvQHAMAnAgH nGPiqK0gu/K4RpY+s1bQJwUi =+i4L -END PGP SIGNATURE- -- Petr Novotny, ANTEK CS [EMAIL PROTECTED] http://www.antek.cz PGP key ID: 0x3BA9BC3F -- Don't you know there ain't no devil there's just God when he's drunk. [Tom Waits]
Re: What is initd.conf?
It is not initd.conf but inetd.conf The inetd daemon sits and listens to the ports specified in inetd.conf, and when a request comes in it transfers it to the program specified in the conf file. It also does other things but that is about it. The downside is that inetd does not tend to handle high loads very well so qmail tends to be run from tcpserver, which does effectively the same thing but only listens on one port, as well as a few extras such as ensuring the request is coming from an appropriate IP address. This is all covered in the faqs and man pages, although I acknowledge they can be cryptic at times. Edmund James wrote: > I have been doing a search to find out how to open my port 25 for > listening, and I've come across a suggestion that I should edit my > initd.conf file to insure that port 25 is listening. I am using Mandrake > 7.02 and I can't find initd.conf anywhere. It's not in /etc/ or > /etc/rc.d/init.d or anywhere. > > Is this the file I need to edit to allow qmail to listen to port 25? > > Thanks. > > James
Usage for Maildrop or Promcmail
Hi, I would like to know the usage of Maildrop?? Why do i need it ?? Can I run my qmail without Maildrop ?? Thank you Mark
qmail Digest 12 May 2000 10:00:01 -0000 Issue 999
qmail Digest 12 May 2000 10:00:01 - Issue 999 Topics (messages 41542 through 41600): qmail-smtp problem 41542 by: kapil sharma 41544 by: Petr Novotny 41545 by: .rth Unix_Loveletter 41543 by: Dewald Strauss 41558 by: Jon Rust AntiSpam police. 41546 by: lopera.eprinsa.es 41547 by: Will Harris Re: Still can't get mail from outside server 41548 by: Ralf Günthner 41549 by: Dave Kitabjian Re: QMail Performance Question & Miscellaneous Issues 41550 by: Steve Craft 41581 by: John White 41583 by: Neil Schemenauer 41591 by: John White Re: What does this mean? "unable to parse" 41551 by: Dave Sill 41555 by: Greg Owen to see distribution list or the other users 41552 by: R.Ilker Gokhan Re: Virtual Domain Error 41553 by: Dave Sill 41556 by: Mark Lo preline getting hung 41554 by: Narvekar, Ashish REAL method for bringing up qmail... 41557 by: Marcelo J. Iturbe [follow -up] REAL method for bringing up qmail... 41559 by: Marcelo J. Iturbe Still Having 822field Troubles 41560 by: Kai MacTane 41565 by: Kai MacTane qmail-smtpd-auth patch seems to have no effect and I can no longer receive mail. 41561 by: Steve Peace tcpserver error message in /var/log/qmail/smtpd/current 41562 by: Eric Fletcher Re: qmail-smtpd problem 41563 by: Eric Cox Re: Manage QMail Queue manually 41564 by: Eric Cox spool vs individual files 41566 by: Michael Smith tcprules 41567 by: Andrés 41569 by: Kai MacTane 41571 by: Jason Haar qmail-queue problem 41568 by: Ricardo D. Albano Re: qmail+procmail+maildir 41570 by: bobski.netnet.net MailDrop or Procamail 41572 by: Mark Lo Re: location of Unsent messages 41573 by: Eric Cox Virtual domain bounce 41574 by: Juan E Suris 41575 by: Peter van Dijk 41576 by: Juan E Suris 41577 by: Peter van Dijk qmail script. 41578 by: Ricardo D. Albano 41579 by: Eric Cox fastforward wierdness 41580 by: Peter Samuel pop before SMTP recomendations 41582 by: Peter Janett 41587 by: Olivier M. unsubscribe qmail 41584 by: zhangmin Port 25 41585 by: James Share queue between servers and other questions. 41586 by: Michael Boman 41588 by: John White qmail-smtpd appears to work but doesn't 41589 by: Bob Brown 41590 by: John White What is initd.conf? 41592 by: James 41593 by: Fabrice Scemama 41599 by: Edmund von der Burg Re: What is wrong, then? 41594 by: James Qestion about qmail 41595 by: Mark Lo 41596 by: Petr Novotny 41597 by: Mark Lo 41598 by: Petr Novotny Usage for Maildrop or Promcmail 41600 by: Mark Lo 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] -- I am running redhat6.1, qmail1.03. I am unable to telnet to 25 port. When I try to telnet to 25 port I am getting the following error: - smtpd: 958034910.901821 tcpserver: warning: dropping connection, unable to read /etc/tcprules.d/qmail-smtpd: input/output error -- I am starting my smtpd as follows: tcpserver -v -c 400 -x/etc/tcprules.d/qmail-smtpd -u 81 -g 80 0 smtp /var/qmail/bin/qmail-smtpd \ 2>&1 | /var/qmail/bin/splogger smtpd 3 & My contents of /etc/tcprules.d/qmail-smtpd are : 127.0.0.1:allow,RELAYCLIENT="" 211.33.44.5:allow,RELAYCLIENT="" 211.33.44.6:allow,RELAYCLIENT="" :allow Please help. -- Kapil Sharma Acube-software [EMAIL PROTECTED] http://www.acubesoftware.com -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On 11 May 00, at 15:33, kapil sharma wrote: > I am running redhat6.1, qmail1.03. I am unable to telnet to 25 port. > When I try to telnet to 25 port I am getting the following error: > > - > smtpd: 958034910.901821 tcpserver: warning: dropping > connection, unable to read /etc/tcprules.d/qmail-smtpd: input/output > error > -- > I am starting my smtpd as follows: > tcpserver -v -c 400 -x/etc/tcprules.d/qmail-smtpd -u 81 -g 80 0 smtp > /var/qmail/bin/qmail-smtpd \ > 2>&1 | /var/qmail/bin/splogger smtpd 3 & Make that "/etc/tcprules.d/qmail-smtpd.cdb" or such. > My contents of /etc/tcprules.d/qmail-smtpd are : > 127.0.0.1:allow,RELAYCLIENT="" > 211.33.44.5:allow,RELAYCLIENT="" > 211.33.44.6:allow,RELAYCLIENT="" > :allow The cleartext tcp rules
Re: Virtual domain bounce
Peter van Dijk writes: > On Fri, May 12, 2000 at 01:44:53AM +, Juan E Suris wrote: > > > > Peter van Dijk writes: > > > > > On Fri, May 12, 2000 at 01:36:28AM +, Juan E Suris wrote: > > > > > > > > Hi All, > > > > > > > > I know that when a bounce is generated, qmail will use control/me as the > > > > bouncehost. is there a way to overide this? > > > > > > > > I would like bounces from a virtual domain to have itself as the bouncehost > > > > and not control/me. Can this be done? > > > > > > No. As far as I know, ther are no patches to do so. > > > > Thanks. > > > > > > > > > Well, I was thinking of just having another qmail installation to handle > > bounces and set control/me to the virtual domain, but that seemed a little > > bit of an overkill. Any suggestions? > > That would involve one qmail installation per qmail domain, which would be > overkill indeed. > True in the case of many domains, but I will just have 2, the local domain plus 1 virtual domain. So, only two instalations would be needed. Still, I hope there is a better solution. JES
qmail: can't create subfolder
Hi, I'm using courier IMAP (don't know if there's a mailing list) and am having problems allowing users to create subfolders from Netscape 4.x or Outlook It will create subfolders in Netscape however if you specify Inbox as the folder to create in and specify the new folder name as subfolder.newsubfolder Anyone seen this behaviour? Have I missed something? p.s. I'm using vchkpw for auth. Cheers, Del.
Ezmlm web front
Does any one know anyway to create a web front for ezmlm administration e.g. to subscribe & un-subscribe etc..
RE: Share queue between servers and other questions.
> I _need_ What is need, compared to the path? > Share queue between ... > several servers (atleast 4 servers) on > different sites can process the queue. I'm heavily editing here, but are you REALLY saying you want a queue shared between different sites which: > spread all over the world, and the connection to the HQ is not > always acceptible when it comes to speed and quality (not becasue HQ > is in a bad place, but that the braches don't have that high-speed > and good lines to the 'net). So your sites are: 1) seperated by great distance, which rules out any SAN or NAS 2) Connected by questionable data links, which may suffer from low performance or occassional downtime. So, because of the distance, you'll need to use a networked filesystem like NFS, AFS, etc. But networked filesystems are designed for LAN environments where performance is reasonable and link downtime is rare. If you attempt to share your queue (or your mail store) like this, you are guaranteeing that performance and reliability will suffer. > Please help me with a solution to this problem else I'll end > up installing sendmail sometime next week. You don't want a solution to your problem, you want an implementation for your solution. But your proposed solution is suboptimal to say the least. Why don't you state the problem instead? -- gowen -- Greg Owen -- [EMAIL PROTECTED]
RE: qmail: can't create subfolder
read the README.imap for hints on configuring IMAP clients This is normal behavior. http://www.inter7.com/courierimap/ -Original Message- From: Derek Smith [mailto:[EMAIL PROTECTED]] Sent: Friday, May 12, 2000 8:56 AM To: qmail Mailing List Subject: qmail: can't create subfolder Hi, I'm using courier IMAP (don't know if there's a mailing list) and am having problems allowing users to create subfolders from Netscape 4.x or Outlook It will create subfolders in Netscape however if you specify Inbox as the folder to create in and specify the new folder name as subfolder.newsubfolder Anyone seen this behaviour? Have I missed something? p.s. I'm using vchkpw for auth. Cheers, Del.
Re: Ezmlm web front
On Fri, May 12, 2000 at 02:23:47PM +0100, Rodney Edwards wrote: ezweb > Does any one know anyway to create a web front for ezmlm administration > e.g. to subscribe & un-subscribe etc.. > -- Now, it's quite simple to defend yourself against a man armed with a banana. First of all you force him to drop the banana; then, second, you eat the banana, thus disarming him. You have now rendered him helpless. - Monty Python
usage of maildrop
Hi, I would like to know the usage of maildrop? I already installed the rblstmp prgram, do i still need maildrop? Thanks Mark
Re: Usage for Maildrop or Promcmail
[EMAIL PROTECTED] wrote: > I would like to know the usage of Maildrop?? It's a Message Delivery Agent (MDA) that takes a message from the Message Transfer Agent (MTA), qmail in our case, and delivers it according to the user's instructions. Maildrop, like procmail, has powerful tools for looking for certain patterns in various parts of the message and delivering the message to various mailboxes or programs depending on the existence or absence of those patterns. This is known as "filtering". >Why do i need it ?? You don't. You might *want* it, but you can get by without it. >Can I run my qmail without Maildrop ?? Yes. qmail contains its own MDA: qmail-local. -Dave
Subject: SMTP & POP ports are non responding
Dear all , All of a sudden my POP3 & SMTP ports are hanged.Even after restarting the essential POP3d & SMTPd services the response is very poor. The server configuration is 256MB RAM,Pentium III processor 450 MHZ, with 20 GB harddisk space. Any guess?any help will be appreciated. Rgds, RAVI.V.R
SMTP & POP ports are non responding
Dear all , All of a sudden my POP3 & SMTP ports are hanged.Even after restarting the essential POP3d & SMTPd services the response is very poor. The server configuration is 256MB RAM,Pentium III processor 450 MHZ, with 20 GB harddisk space. Any guess?any help will be appreciated. Rgds, RAVI.V.R
Re: What is wrong, then?
James <[EMAIL PROTECTED]> wrote: >Ok, so I've opened the inetd.conf and found this at the bottom: > >smtp stream tcp nowait qmaild /var/qmail/bin/tcp-env >tcp-env/var/qmail/bin/qmail-smtpd > >All of that line is on one line. Is this how it should be for Qmail? No, you need a space after the last tcp-env. -Dave
Re: MailDrop or Procamail
[EMAIL PROTECTED] wrote: >I would like to know whether i should use procmail or maildrop for >qmail, actuallly, which one comes with more support and documentation. >and most importantly, easier to use. Ease of use and quantity of documentation are comparable, but procmail is far more popular. I use procmail because I've been using it for years and I didn't see anything in maildrop to justify learning a new tool. If I was starting from scratch, I'd give maildrop a try since procmail is kind of baroque. -Dave
bypassing relaydomains (reverse DNS issues)
I am using qmail under tcpserver. We have users that are coming in from IPs that have no reverse DNS resolution. As a result, it takes forever for them to send email via smtp connections. I want to disable reverse lookups using the -HR flag on tcpserver, but appear to run into a problem with /var/qmail/control/relaydomains, i.e. users that are listed in relaydomains are now disallowed since I disabled reverse lookups. Is there an easy way to temporarily disable relaydomains, and control relaying purely based on relayclients. I do realize that tcpserver itself provides an IP based relaying mechanism, but I currently cannot update qmail due to some other issues (since I already have patched qmail with relayclient/domains patch). Again, how can I modify tcpserver or qmail or relaydomains in order to ignore domain based relay checks. Thanks for your help! __ Do You Yahoo!? Send instant messages & get email alerts with Yahoo! Messenger. http://im.yahoo.com/
Re: qmail: can't create subfolder
Hi, Got Netscape working (by forcing a subscribe on the INBOX (wasn't set!)), but I still can't get Outlook (v5) or Outlook Express working. If anyone has instructions on setting up these clients, or possible causes, can the point me to them or post them to the group. Cheers, Del. Tim Hunter wrote: > read the README.imap for hints on configuring IMAP clients > This is normal behavior. > > http://www.inter7.com/courierimap/ > > -Original Message- > From: Derek Smith [mailto:[EMAIL PROTECTED]] > Sent: Friday, May 12, 2000 8:56 AM > To: qmail Mailing List > Subject: qmail: can't create subfolder > > Hi, > > I'm using courier IMAP (don't know if there's a mailing list) and am > having problems allowing users to create subfolders from Netscape 4.x or > Outlook > > It will create subfolders in Netscape however if you specify Inbox as > the folder to create in and specify the new folder name as > subfolder.newsubfolder > > Anyone seen this behaviour? Have I missed something? > > p.s. I'm using vchkpw for auth. > > Cheers, > > Del.
Re: spool vs individual files
"Michael Smith" <[EMAIL PROTECTED]> wrote: >We're currently looking at mail solutions for our online email >system, and we've hit against an interesting conundrum. We were >wondering what the advantages are to listing mail messages as >individual files over a spool file? The choice is file-per-mailbox (a la mbox) or file-per-message (a la maildir). They each have their pros and cons, of course. Adding a new message to either is pretty cheap, but in the case of mbox, locking is required to ensure that multiple simultaneous updates don't conflict. Deleting a message from an mbox requires reading the entire file and writing it all back out, except for the deleted message. Deleting a message from a maildir only requires unlinking the file containing the message. Again, updating the mbox requires locking. Indexing an mbox mailbox requires reading the entire mailbox and parsing the messages--parsing is undesirable. Indexing a maildir mailbox requires opening each file and reading the header--that means lots of directory accesses and open() system calls. Large mbox mailboxes are huge, unwieldy files. Large maildir mailboxes are huge, unwieldy directories--most filesystems don't handle them efficiently after they grow to a few thousand files. >We're looking for a system which will scale to several tens of thousands of >users on each machine. How will mailboxes be served? POP? IMAP? Which daemon? Which mailbox format(s) does it support well? Where will they be stored? If the storage is network attached (which is good for redundancy), does the storage system provide a satisfactory locking mechanism? -Dave
Auto Resolve sender's domain
Hi, Will qmail automatically resolve sender's domain for valid DNS?? Thanks Mark
Re: tcpserver error message in /var/log/qmail/smtpd/current
Eric Fletcher <[EMAIL PROTECTED]> wrote: >I get the following error message repeated every minute. > >I've checked and rechecked my D. Sill bible and all "seems" to be correct. > >I can send and receive email fine. Allow relay for remote hosts works >properly also. > >tcpserver: fatal: unable to figure out port number for /var/qmail/bin/qmail-smtp > >Ideas ??? Your /var/qmail/supervise/qmail-smtpd/run file should look like: #!/bin/sh QMAILDUID=`id -u qmaild` NOFILESGID=`id -g qmaild` exec /usr/local/bin/softlimit -m 200 \ /usr/local/bin/tcpserver -v -p -x /etc/tcp.smtp.cdb \ -u $QMAILDUID -g $NOFILESGID 0 smtp /var/qmail/bin/qmail-smtpd 2>&1 It sounds like QMAILDUID and/or NOFILESGID aren't getting set. You don't say what platform you're on, but it's possible that "id" isn't in the path when the script is run, or doesn't support the -u and -g options. Try running: id -u qmaild If that fails, do "man id". See if your system has an "id" that will work. Solaris, for example, has one in /usr/xpg4/bin/id. Change the run script to specify the location of the correct "id" command, e.g.: QMAILDUID=`/usr/xpg4/bin/id -u qmaild` NOFILESGID=`/usr/xpg4/bin/id -g qmaild` Talk about gratutious incompatibility... -Dave
Re: Auto Resolve sender's domain
Mark Lo <[EMAIL PROTECTED]> wrote: >Will qmail automatically resolve sender's domain for valid DNS?? You mean reject mail if the sender's domain doesn't resolve? No, but I think there's a patch to do that. -Dave
Improving queue performance using the noatime mount option in Solaris?
I would like to boost the queue IO performance on our mail servers running qmail 1.03. Both mail servers are SUN boxes running Solaris 7. According to Solaris documentation, starting from Solaris 7, the mount has the noatime option available. Quoted: Suppresses access time updates on files, except when they coincide with updates to the ctime or mtime. See stat(2). This option reduces disk activity on file systems where access times are unimportant (for example, a Usenet news spool). The default is normal access time (atime) recording. I did some reading of the qmail source. It seems to me that turning on this option wouldn't hurt. However, I prefer not to try on our production mail servers. So, I would be very appreciative for a confirmation from anyone who has used this option with good results. While I am at it, how about the logging option too? Regards, Chin Fang [EMAIL PROTECTED]
Re: spool vs individual files
Dave Sill <[EMAIL PROTECTED]> wrote on Fri, 12 May 2000: > Deleting a message from an mbox requires reading the entire file and > writing it all back out, except for the deleted message. Deleting a > message from a maildir only requires unlinking the file containing the > message. Again, updating the mbox requires locking. Actually, to be specific, if the client is smart only the part from the deleted email onwards need to be written out. If you delete the last message from an mbox folder, the file only needs to be truncated. Mikko -- // Mikko Hänninen, aka. Wizzu // [EMAIL PROTECTED] // http://www.iki.fi/wiz/ // The Corrs list maintainer // net.freak // DALnet IRC operator / // Interests: roleplaying, Linux, the Net, fantasy & scifi, the Corrs / Gravity brings me down
Re: Improving queue performance using the noatime mount option in Solaris?
You might want to grep the sources and see if atime is referenced. I think you'll find it is, in important programs too. Regards. On Fri, May 12, 2000 at 08:40:26AM -0700, Chin Fang wrote: > I would like to boost the queue IO performance on our mail servers > running qmail 1.03. Both mail servers are SUN boxes running > Solaris 7. > > According to Solaris documentation, starting from Solaris 7, the mount > has the noatime option available. > > Quoted: > >Suppresses access time updates on files, except when >they coincide with updates to the ctime or mtime. >See stat(2). This option reduces disk activity on file >systems where access times are unimportant (for >example, a Usenet news spool). The default is normal >access time (atime) recording. > > I did some reading of the qmail source. It seems to me that turning > on this option wouldn't hurt. However, I prefer not to try on our > production mail servers. So, I would be very appreciative for a > confirmation from anyone who has used this option with good results. > While I am at it, how about the logging option too? > > Regards, > > Chin Fang > [EMAIL PROTECTED]
Re: Improving queue performance using the noatime mount option in Solaris?
I know that atime is referenced. The source of my unsureness is "except when they coincide with updates to the ctime or mtime." Actually, after looking at for instance, maildir.c further, I am not sure tunning on the noatime would really buy any gain. Regards, Chin Fang [EMAIL PROTECTED] > You might want to grep the sources and see if atime is referenced. > > I think you'll find it is, in important programs too. > > > Regards. [...]
Re: spool vs individual files
Dave Sill wrote: > > Large mbox mailboxes are huge, unwieldy files. Large maildir mailboxes > are huge, unwieldy directories--most filesystems don't handle them > efficiently after they grow to a few thousand files. DEC/Compaq ADVFS handles huge directories without trouble, using a hashed directory table that grows as needed. For linux, reiserfs supposedly doesn't care about directory size as it blurs the directory_entry / file_data distinction. I should have qmail running over reiserfs any day now, and will give a report when I do -- David Nicol 816.235.1187 [EMAIL PROTECTED] You discover uranium: collect $240,000
Re: spool vs individual files
> DEC/Compaq ADVFS handles huge directories without trouble, using > a hashed directory table that grows as needed. Sun Solaris 8 uses a similar strategy too. That's a main reason I am upgrading our mail servers to Solaris 8. Chin Fang [EMAIL PROTECTED]
Re: running qmail smtpd at a different port
Hi, I am trying to run qmail smtpd at a different port. I have used the setup method specified in Dave Sill (Live with Qmail). And I am not sure how to tell qmail-smtpd to listen to a different port... Any help is greatly appreciated. Thanks in advance. chester
Re: running qmail smtpd at a different port
"Chester Chee" <[EMAIL PROTECTED]> wrote: >I am trying to run qmail smtpd at a different port. I have used the >setup method specified in Dave Sill (Live with Qmail). And I am not >sure how to tell qmail-smtpd to listen to a different port... Any >help is greatly appreciated. Thanks in advance. In /var/qmail/supervise/qmail-smtpd/run, change the "smtp" to the desired port number, or it's name as specified in /etc/services. -Dave
Re: Hanging smtpd processes - Again w/more info
As best I can determine, it's a bug in Solaris 2.6, as a truss will show that qmail-smtpd is sitting on a select and never comes off of it (if memory serves me correctly). The only solution I know is to go to 2.7 or maybe 2.8... Sorry. On Thu, May 11, 2000 at 04:48:29PM +0800, [EMAIL PROTECTED] wrote: > Hi there, > > I made a post the other day to ask about hanging > qmail-smtpd processes problem I'm encountering. I'm still having > the problem here but just found some more 'facts' about > it, so am re-posting this problem with the new info and hope > someone out there happens to know how to explain this. > > I'm running qmail1.03 w/tcpserver and vpopmail on a Solaris2.6 > box. I found that some of the qmail-smtpd processes get hung > and all these smtpd processes got corresponding qmail-queue > processes. All the hanging smtpd and queue show 'sleeping' when > I use truss to see them and the queue process always finaly went become > a Zombie process after 24hrs. I also tried to check if the messages > have ever been queued and as expected found nothing that could be > the message from the hanging smtp connection in the queue. > > It looks like something went wrong between the establishment of > smtp connection and the queue-in process, but it doesn't happen > in every delivery. I also tried to find out in what circumstance > will it occur but failed to figure it out. > > Some suggested that just kill the processes and > this is how I am dealing with it but am still wondering if anyone > out there could explain why this is happening and eventually know > some more 'cleaner' method to solve this problem. Also since > the queue-in process is not finished, could I say that no message > is lost due to this problem. ( I mean that from the viewpoint of > the end user who is making a smtp connection to my server, will > something like the user thinks that her/his message was sent > but the message was actually even never queued ?) > > > Any idea will be appreciated. > > Thanks in advance, > > - > Wang-hua Li
Re: running qmail smtpd at a different port
Thanks, Dave - Original Message - From: "Dave Sill" <[EMAIL PROTECTED]> To: <[EMAIL PROTECTED]> Sent: Friday, May 12, 2000 2:19 PM Subject: Re: running qmail smtpd at a different port > "Chester Chee" <[EMAIL PROTECTED]> wrote: > > >I am trying to run qmail smtpd at a different port. I have used the > >setup method specified in Dave Sill (Live with Qmail). And I am not > >sure how to tell qmail-smtpd to listen to a different port... Any > >help is greatly appreciated. Thanks in advance. > > In /var/qmail/supervise/qmail-smtpd/run, change the "smtp" to the > desired port number, or it's name as specified in /etc/services. > > -Dave >
tcpserver error message in /var/log/qmail/smtpd/current
Let this be a lesson to everbody. I followed Dave's LWQ to the letter OR ! I thought I did. That was the problem. There were 2 letters (characters) missing at various points. God knows how many times I checked and others checked and we kept missing the letter d in smtpd at one point and an upper case S in NOFILESGID at another. Read carefully. Qmail works and works well if you do as Dave says. Get it going then make any changes. Thanks Dave... The time you spend makes all our lives a lot easier. Eric Eric Fletcher <[EMAIL PROTECTED]> wrote: >I get the following error message repeated every minute. > >I've checked and rechecked my D. Sill bible and all "seems" to be correct. > >I can send and receive email fine. Allow relay for remote hosts works >properly also. > >tcpserver: fatal: unable to figure out port number for /var/qmail/bin/qmail-smtp > >Ideas ??? Your /var/qmail/supervise/qmail-smtpd/run file should look like: #!/bin/sh QMAILDUID=`id -u qmaild` NOFILESGID=`id -g qmaild` exec /usr/local/bin/softlimit -m 200 \ /usr/local/bin/tcpserver -v -p -x /etc/tcp.smtp.cdb \ -u $QMAILDUID -g $NOFILESGID 0 smtp /var/qmail/bin/qmail-smtpd 2>&1 It sounds like QMAILDUID and/or NOFILESGID aren't getting set. You don't say what platform you're on, but it's possible that "id" isn't in the path when the script is run, or doesn't support the -u and -g options. Try running: id -u qmaild If that fails, do "man id". See if your system has an "id" that will work. Solaris, for example, has one in /usr/xpg4/bin/id. Change the run script to specify the location of the correct "id" command, e.g.: QMAILDUID=`/usr/xpg4/bin/id -u qmaild` NOFILESGID=`/usr/xpg4/bin/id -g qmaild` Talk about gratutious incompatibility... -Dave -- Eric Fletcher - Data Center Support Dialtone Internet - Extremely Fast Web Systems (954) 581-0097 - Voice (954) 581-7629 - Fax [EMAIL PROTECTED] - Email http://www.dialtoneinternet.net
Re: Port 25
James wrote: > > With some help from Jerry, I was able to narrow down a problem I am having > with receiving mail from outside servers through Qmail. It's apparent > that my port 25 is closed off to outside connections. I don't know how or > why it's closed off.. TCPwrappers? Why would port 25 be closed off > anyway. Perhaps there is a security feature in Mandrake 7.02 that closes > this port? > > I was able to receive mail through sendmail before I installed qmail, so I > am guessing qmail somehow closed port 25. How do I open that port? Have you set up qmail-smtpd in your /etc/inetd.conf ? (qmail-smtpd is not a standalone daemon, it needs to be called by inetd) Eric -- NEEDHAM'S ELECTRONICS Device Programmers (916) 924-8037 (Voice) http://www.needhams.com
fastforward?- new to qmail
I am new to qmail. I have a qmail server running on domain, "a.com". I don't want any local accounts if I don't have to. I just want to use /etc/aliases to send stuff going to say, [EMAIL PROTECTED] to go to [EMAIL PROTECTED] I can send stuff directly to [EMAIL PROTECTED] and it works. That is a valid account on the mail server in b.com domain. This is what my /etc/aliases file looks like: [EMAIL PROTECTED]: [EMAIL PROTECTED] Again. My qmail server is not on b.com domain. It is on a.com. I have put in the fastforward entry in /var/qmail/alias/.qmail-default. What am I doing wrong? Thanks for any help.
Looking for pointers with qmail delivery problems (additional info provided with original message)
Hi, Here is some more info with the qmail delivery problems we are having (original message appended at the bottom). The additional info I have here is the output from qmail-qread and qmail-qstat. Is there any other place I can look since the qmail log files don't show any errors? Thanks. Please scroll down for original message. --- [root@dev-mx-001 bin]# ./qmail-qread 12 May 2000 14:22:05 GMT #201558 748 <[EMAIL PROTECTED]> local [EMAIL PROTECTED] 12 May 2000 14:23:11 GMT #201606 776 <[EMAIL PROTECTED]> local [EMAIL PROTECTED] [root@dev-mx-001 bin]# ./qmail-qstat messages in queue: 2 messages in queue but not yet preprocessed: 0 -- Ashish P. Narvekar email: [EMAIL PROTECTED] My original message follows: We have been seeing a strange problem where mail stops getting delivered to the mailbox. We have qmail (release 1.03) running on a linux box. Mail is delivered to Cyrus (IMAP v1.5.14) using the following command |preline -f /usr/cyrus/bin/deliver -a sb -e sb Messages will get delivered fine for a day or two. Then, suddenly, messages will stop getting delivered. A process dump will show a number of preline commands just waiting there (I have included the process dump output). I have also attached the qmail log (the last few pages of it). Note in the qmail log that delivery 484 and 485 were not successful. However, there is no indication of any error. Please ignore delivery 486. That is the system admin emailing me the log files. Does anybody know what might be going on here? Any pointers would be greatly appreciated. Thanks. -- Ashish P. Narvekar email: [EMAIL PROTECTED] -- PROCESS DUMP OUTPUT: (Scroll down for qmail log output) 000 0 436 433 5 0 1088 72 do_sel S? 0:00 \_ qmail-lspawn |preline procmail PATH=/var/qmail/bin:/sbin:/usr/sbin:/bin:/usr/bin:/usr/X11R6/bin 100 1020 11099 436 0 0 1096 340 wait4 S? 0:00 | \_ bin/qmail-local -- alias /var/qmail/alias synchrony_test4 - synchrony_test4 dev-mx-001.synchrony.net [EMAIL PROTECTED] |preline procmail PATH=/var/qmail/bin:/sbin:/usr/sbin:/bin:/usr/bin:/usr/X11R6/bin 000 1020 11101 11099 0 0 1088 316 wait4 S? 0:00 | | \_ preline -f /usr/cyrus/bin/deliver -a synch -e synch EXT2= EXT3= EXT4= RPLINE=Return-Path: <[EMAIL PROTECTED]>? LOCAL=synchrony_test4 [EMAIL PROTECTED] TERM=dumb HOSTTYPE=i386 PATH=/var/qmail/bin:/sbin:/usr/sbin:/bin:/usr/bin:/usr/X11R6/bin EXT=synchrony_test4 HOME=/var/qmail/alias SHELL=/bin/bash HOST2=dev-mx-001.synchrony HOST3=dev-mx-001 HOST4=dev-mx-001 [EMAIL PROTECTED] USER=alias DTLINE=Delivered-To: [EMAIL PROTECTED]? [EMAIL PROTECTED] HOST=dev-mx-001.synchrony.net OSTYPE=Linux UFLINE=From [EMAIL PROTECTED] Wed May 10 20:39:25 2000? SHLVL=1 _=/var/qmail/bin/preline 000 100 11102 11101 0 0 2008 860 flock_ S? 0:00 | | \_ /usr/cyrus/bin/deliver -a synch -e synch EXT2= EXT3= EXT4= RPLINE=Return-Path: <[EMAIL PROTECTED]>? LOCAL=synchrony_test4 [EMAIL PROTECTED] TERM=dumb HOSTTYPE=i386 PATH=/var/qmail/bin:/sbin:/usr/sbin:/bin:/usr/bin:/usr/X11R6/bin EXT=synchrony_test4 HOME=/var/qmail/alias SHELL=/bin/bash HOST2=dev-mx-001.synchrony HOST3=dev-mx-001 HOST4=dev-mx-001 [EMAIL PROTECTED] USER=alias DTLINE=Delivered-To: [EMAIL PROTECTED]? [EMAIL PROTECTED] HOST=dev-mx-001.synchrony.net OSTYPE=Linux UFLINE=From [EMAIL PROTECTED] Wed May 10 20:39:25 2000? SHLVL=1 _=/var/qmail/bin/preline 100 1020 1 436 0 0 1096 340 wait4 S? 0:00 | \_ bin/qmail-local -- alias /var/qmail/alias synchrony_test4 - synchrony_test4 dev-mx-001.synchrony.net [EMAIL PROTECTED] |preline procmail PATH=/var/qmail/bin:/sbin:/usr/sbin:/bin:/usr/bin:/usr/X11R6/bin 000 1020 3 1 0 0 1088 316 wait4 S? 0:00 | \_ preline -f /usr/cyrus/bin/deliver -a synch -e synch EXT2= EXT3= EXT4= RPLINE=Return-Path: <[EMAIL PROTECTED]>? LOCAL=synchrony_test4 [EMAIL PROTECTED] TERM=dumb HOSTTYPE=i386 PATH=/var/qmail/bin:/sbin:/usr/sbin:/bin:/usr/bin:/usr/X11R6/bin EXT=synchrony_test4 HOME=/var/qmail/alias SHELL=/bin/bash HOST2=dev-mx-001.synchrony HOST3=dev-mx-001 HOST4=dev-mx-001 [EMAIL PROTECTED] USER=alias DTLINE=Delivered-To: [EMAIL PROTECTED]? [EMAIL PROTECTED] HOST=dev-mx-001.synchrony.net OSTYPE=Linux UFLINE=From [EMAIL PROTECTED] Wed May 10 20:40:35 2000? SHLVL=1 _=/var/qmail/bin/preline 000 100 4 3 0 0 2008 860 flock_ S? 0:00 | \_ /usr/cyrus/bin/deliver -a synch -e synch EXT2= EXT3= EXT4= RPLINE=Return-Path: <[EMAIL PROTECTED]>? LOCAL=synchrony_test4 [EMAIL PROTECTED] TERM=dumb HOSTTYPE=i386 PATH=/var/qmail/bin:/sbin:/usr/sbin:/bin:/u
dnscache, multilog
i wonder: does anybody use the dnscache-package instaed of the numerous BIND implementations like named(8)? and if so: do you also use multilog? the only source of wisdom concerning multilog seems to be the source, but it doesn't tell me why the selection-mechanism in multilog scripts seems not to work intuitively: #!/bin/sh exec setuidgid root multilog t s2 n2 -\*cached\* ./main this script does not weed out "@ cached ..." lines from the log, and i would like to get in touch with people with multilog-experience. -- clemens [EMAIL PROTECTED]
Re: Ezmlm web front
On Fri, May 12, 2000 at 02:23:47PM +0100, Rodney Edwards wrote: > Does any one know anyway to create a web front for ezmlm administration > e.g. to subscribe & un-subscribe etc.. Try ezmlm-web... http://rucus.ru.ac.za/~guy/ezmlm/#ezmlm-web HTH, Steffan -- http://therookie.dyndns.org
Need help with Novell/GW SMTP and QMail
Client with Novell's SMTP Gateway or GroupWise ver 5.5 is having problem connecting to our QMail 1.03 SMTP server. Email can send to their SMTP server, but reverse doesn't work. Nothing shows in our logs that a connection was even established Has anybody had similar problem with solution? Jose de Leon System Administrator InVision Telecommunications (209) 549-8800 FAST Internet Access and no bull. InVision DSL, www.invisiondsl.com
Help me understand "allowed rcpthosts"
I've been mulling through various how-to's and qmail help pages.. but I still don't quite understand what rcpthosts is about. If I am wrong, correct me. rcpthosts is where you place the domain addresses of the people you want to allow relaying. If this is correct, then I understand that part. But.. what controls the ability for anyone to send me an email at [EMAIL PROTECTED]? How does joe-blow send me an email?? How does relaying and receiving mail relate to each other? All I want is to get mail from anyone, but not have anyone use my server as a relay. If anyone is sending me an email, I get this error: "reason: 553 sorry, that domain isn't in my list of allowed rcpthosts (#5.7.1)" Of course, I have read up on the FAQ's and all this tells me is that I am not allowing that domain ([EMAIL PROTECTED]) to use my server as a relay, right? But I don't care, at this point, that he can't use my server as a relay.. all I want is to get his mail. I don't want him to use my server as a relay, but I do want to get his mail in my Mailbox. How come I can't get his mail? James
Re: Help me understand "allowed rcpthosts"
At 5/12/2000 01:43 PM -0700, James wrote or quoted: >If I am wrong, correct me. rcpthosts is where you place the domain >addresses of the people you want to allow relaying. If this is correct, >then I understand that part. No, rcpthosts is where you place the list of hosts and domain names that *you want to receive mail for*. If your rcpthosts contains: .foobar.com whangdoodle.net wombat.mammal.org then you can receive mail for any address in the entire foobar com domain ([EMAIL PROTECTED] *and* [EMAIL PROTECTED], for example). You can also receive mail for any address @whangdoodle.net, and any address @wombat.mammal.org, but mail for, say, [EMAIL PROTECTED], or [EMAIL PROTECTED], will be rejected. >But.. what controls the ability for anyone to send me an email at >[EMAIL PROTECTED]? The rcpthosts file. >All I want is to get mail from anyone, but not have anyone use my server >as a relay. A good thing to desire. If you have the domains red.com and green.org, you just put the following in rcpthosts: red.com green.org .red.com .green.org The last two lines are only necessary if you're using subhost names, such as mail.red.com or smtp.green.org. Then, you can receive mail for any address in those domains, but nobody can send mail out through your server, except by using MUAs that are *on that server* (such as Elm, Mutt and Pine). If you need to allow remote users (say, using Windows mail clients) to send mail from your server, look at the stuff on selective relaying in Dave Sill's Life With Qmail, at http://Web.InfoAve.Net/~dsill/lwq.html#relaying . You might also want to see Dave's link to Chris Johnson's selective relaying guide, at http://www.palomine.net/qmail/relaying.html . - Kai MacTane System Administrator Online Partners.com, Inc. - From the Jargon File: (v4.0.0, 25 Jul 1996) finger trouble /n./ Mistyping, typos, or generalized keyboard incompetence (this is surprisingly common among hackers, given the amount of time they spend at keyboards). "I keep putting colons at the end of statements instead of semicolons", "Finger trouble again, eh?".
Re: Help me understand "allowed rcpthosts"
Ok.. now I understand that "rcpthosts" contains "domains that we accept mail for"Huh? Domains that we accept mail for? So, if I want to accept mail for [EMAIL PROTECTED] I have to have that specifically in my rcpthosts? That's absurd. I know I must be confused about this. So how do I get mail from any user in the world? All I want is to be able to get mail from anyone, but not allow them to use my server as a relay (at this point) james
Re: Help me understand "allowed rcpthosts"
Kai wrote: :f you have the domains red.com and green.org, you just put the following :in rcpthosts: :red.com :green.org :.red.com :.green.org :The last two lines are only necessary if you're using subhost names, such :as mail.red.com or smtp.green.org. Ok, I might be getting a little closer. I have placed mydomain.com in my rcpthosts long ago. I've rebooted the system since. When [EMAIL PROTECTED] sends me an email, I still get the "that domain isn't in my list of allowed rcpthosts" error. I'm not sure what else to set. james
Re: Help me understand "allowed rcpthosts"
James wrote: > > I've been mulling through various how-to's and qmail help pages.. but I > still don't quite understand what rcpthosts is about. > > If I am wrong, correct me. rcpthosts is where you place the domain > addresses of the people you want to allow relaying. If this is correct, > then I understand that part. > > But.. what controls the ability for anyone to send me an email at > [EMAIL PROTECTED]? How does joe-blow send me an email?? How does relaying > and receiving mail relate to each other? All I want is to get mail from > anyone, but not have anyone use my server as a relay. If anyone is > sending me an email, I get this error: > > "reason: 553 sorry, that domain isn't in my list of allowed rcpthosts > (#5.7.1)" If you get this error when somene sends mail to a _local_ user, then qmail is confused about which domains are the local ones, and thinks that the recipent's domain is a remote one. It's saying to the SMTP client "hmm...the domain to which you are trying to send mail isn't in my control/locals file, so you must be asking me to relay a message to a remote host for you. Hold on, I'll check my control/rcpthosts file for permission to do that.Hey! That domain isn't in my control/rcpthosts file either! Get outa here you damn spammer!!!" > Of course, I have read up on the FAQ's and all this tells me is that I am > not allowing that domain ([EMAIL PROTECTED]) to use my server as a > relay, right? Nope, when someone tries to send mail to a local user, that's not relaying. I suspect the problem is that you do not have your local domain setup properly in control/locals, so qmail believes your local domain is really a remote one. Eric
RE: Help me understand "allowed rcpthosts"
It really looks like a configuration/communication problem What we really need if you cannot figgure out the problem is a snippet from your log of an example error, the exact contents of your rcpthosts file. Please do not edit these at all if you wish to get a good answer. thanks, Tim -Original Message- From: Eric Cox [mailto:[EMAIL PROTECTED]] Sent: Friday, May 12, 2000 5:04 PM To: [EMAIL PROTECTED] Subject: Re: Help me understand "allowed rcpthosts" James wrote: > > I've been mulling through various how-to's and qmail help pages.. but I > still don't quite understand what rcpthosts is about. > > If I am wrong, correct me. rcpthosts is where you place the domain > addresses of the people you want to allow relaying. If this is correct, > then I understand that part. > > But.. what controls the ability for anyone to send me an email at > [EMAIL PROTECTED]? How does joe-blow send me an email?? How does relaying > and receiving mail relate to each other? All I want is to get mail from > anyone, but not have anyone use my server as a relay. If anyone is > sending me an email, I get this error: > > "reason: 553 sorry, that domain isn't in my list of allowed rcpthosts > (#5.7.1)" If you get this error when somene sends mail to a _local_ user, then qmail is confused about which domains are the local ones, and thinks that the recipent's domain is a remote one. It's saying to the SMTP client "hmm...the domain to which you are trying to send mail isn't in my control/locals file, so you must be asking me to relay a message to a remote host for you. Hold on, I'll check my control/rcpthosts file for permission to do that.Hey! That domain isn't in my control/rcpthosts file either! Get outa here you damn spammer!!!" > Of course, I have read up on the FAQ's and all this tells me is that I am > not allowing that domain ([EMAIL PROTECTED]) to use my server as a > relay, right? Nope, when someone tries to send mail to a local user, that's not relaying. I suspect the problem is that you do not have your local domain setup properly in control/locals, so qmail believes your local domain is really a remote one. Eric
Re: Help me understand "allowed rcpthosts"
On Fri, 12 May 2000, James wrote: > Ok.. now I understand that "rcpthosts" contains "domains that we accept > mail for"Huh? Domains that we accept mail for? So, if I want to yes - your domains(s) (somedomain.com). > accept mail for [EMAIL PROTECTED] I have to have that specifically > in my rcpthosts? That's absurd. I know I must be confused about this. > So how do I get mail from any user in the world? > well if your email is [EMAIL PROTECTED], then you will want to accept mail for email addresses to somedomain.com (RCPT To:). thus it goes into rcpthosts. if you want to allow relaying from your local network, or anywhere else then you need to follow the FAQ in /var/qmail/doc/FAQ. this will tell u that u need to setup the tcp wrappers to set an environment variable (RELAYCLIENT) from ceratin hosts that will allow qmail to be used as a relay from these hosts. > All I want is to be able to get mail from anyone, but not allow them to > use my server as a relay (at this point) > > james > >
RE: Help me understand "allowed rcpthosts"
Tim Hunter wrote: :What we really need if you cannot figgure out the problem is a snippet :from your log of an example error, the exact contents of your rcpthosts :file. Which log? I've looked at /var/log/messages, /var/log/maillog, /var/log/qmail and none of those contain any errors pertaining to my allowed rcpthosts problem. The only message I get is from my returned mail which is this (the only thing I've changed here is my domain name): ___ ... while talking to www.mydomain.com.: >>> RCPT To:<[EMAIL PROTECTED]> <<< 553 sorry, that domain isn't in my list of allowed rcpthosts (#5.7.1) 550 5.1.1 <[EMAIL PROTECTED]>... User unknown --- I see the "User unknown" part.. but if I send a local mail (using inject) from root to james, it reaches james. Thanks for any help. James
Re: Help me understand "allowed rcpthosts"
On Fri, May 12, 2000 at 02:02:38PM -0700, James wrote: > Ok, I might be getting a little closer. I have placed mydomain.com in my > rcpthosts long ago. I've rebooted the system since. When > [EMAIL PROTECTED] sends me an email, I still get the "that domain isn't > in my list of allowed rcpthosts" error. I'm not sure what else to set. That error can only be the result of a remote host saying: RCPT TO:<[EMAIL PROTECTED]> during the SMTP conversation and "mydomain.com" not being in control/rcpthosts. It's that simple. So if you're getting that error, you don't have mydomain.com in control/rcpthosts. Look for spelling errors, stray characters, whatever. Chris
Re: Ezmlm web front
Doesn't qmailadmin also support mailing list administration using ezmlm??? What is the different between this package and qmailadmin? - Original Message - From: "Steffan Hoeke" <[EMAIL PROTECTED]> To: "qmail" <[EMAIL PROTECTED]> Sent: Friday, May 12, 2000 3:59 PM Subject: Re: Ezmlm web front > On Fri, May 12, 2000 at 02:23:47PM +0100, Rodney Edwards wrote: > > Does any one know anyway to create a web front for ezmlm administration > > e.g. to subscribe & un-subscribe etc.. > Try ezmlm-web... http://rucus.ru.ac.za/~guy/ezmlm/#ezmlm-web > > HTH, > Steffan > -- > http://therookie.dyndns.org > >
Re: Help me understand "allowed rcpthosts"
Chris Johnson wrote: :So if you're getting that error, you don't have mydomain.com in :control/rcpthosts. Look for spelling errors, stray characters, whatever. I've set up every way I can think of setting in my rcpthosts.. here is what it contains (with the domain name changed): __ localhost ns.my-domain.com www.my-domain.com [EMAIL PROTECTED] my-domain.com -- Will it mess things up to have multiple listings like this? How about the - ? Will having a domain name with - in it mess things up? James
Re: Ezmlm web front
On Fri, May 12, 2000 at 05:29:39PM -0400, Chester Chee wrote: > Doesn't qmailadmin also support mailing list administration using ezmlm??? Yes it does, but that's for the 'integrated' mailing list management options in qmail > What is the different between this package and qmailadmin? Ezmlm-Web is specifically designed for ezmlm management, while AFAIK qmailadmin uses the 'internal' mailing list possebilitys that qmail has. Since you asked for a web front for ezmlm i wouldn't use qmailadmin (probably wouldn't work anyway ) HTH, Steffan > - Original Message - > > On Fri, May 12, 2000 at 02:23:47PM +0100, Rodney Edwards wrote: > > > Does any one know anyway to create a web front for ezmlm administration > > > e.g. to subscribe & un-subscribe etc.. > > Try ezmlm-web... http://rucus.ru.ac.za/~guy/ezmlm/#ezmlm-web > > > > HTH, > > Steffan > > -- > > http://therookie.dyndns.org > > > > > -- http://therookie.dyndns.org
RE: Help me understand "allowed rcpthosts"
If you setup mail by following "Life with qmail" the smtpd logs are in /var/log/qmail/smtp if you are using tcpserver and following "life with qmail" it will show up there. It would still be helpful if you do not log smtp connections to show us an UNEDITED header of a mail that bounces and the contents of your rcpthosts file. If you have not read "life with qmail" I would suggest it as it is pretty good reading and will give you an incredible understanding of how qmail works along with a seamless install. -- Tim -Original Message- From: James [mailto:[EMAIL PROTECTED]] Sent: Friday, May 12, 2000 5:27 PM To: [EMAIL PROTECTED] Subject: RE: Help me understand "allowed rcpthosts" Tim Hunter wrote: :What we really need if you cannot figgure out the problem is a snippet :from your log of an example error, the exact contents of your rcpthosts :file. Which log? I've looked at /var/log/messages, /var/log/maillog, /var/log/qmail and none of those contain any errors pertaining to my allowed rcpthosts problem. The only message I get is from my returned mail which is this (the only thing I've changed here is my domain name): ___ ... while talking to www.mydomain.com.: >>> RCPT To:<[EMAIL PROTECTED]> <<< 553 sorry, that domain isn't in my list of allowed rcpthosts (#5.7.1) 550 5.1.1 <[EMAIL PROTECTED]>... User unknown --- I see the "User unknown" part.. but if I send a local mail (using inject) from root to james, it reaches james. Thanks for any help. James
"What is wrong then" FIXED
Thanks to Dave Sill, it was pointed out to me that a simple syntax error was my problem. In inetd.conf I had the line: smtp stream tcp nowait qmaild /var/qmail/bin/tcp-env tcp-env/var/qmail/bin/qmail-smtpd Dave pointed out that there should be a space after the second tcp-env. Days of pulling my hair out due to one simple thing. ugh. Problem solved. Thanks Dave! James
Re: Help me understand "allowed rcpthosts"
On Fri, May 12, 2000 at 02:35:11PM -0700, James wrote: > Chris Johnson wrote: > :So if you're getting that error, you don't have mydomain.com in > :control/rcpthosts. Look for spelling errors, stray characters, whatever. > > I've set up every way I can think of setting in my rcpthosts.. here > is what it contains (with the domain name changed): > __ > localhost > ns.my-domain.com > www.my-domain.com > [EMAIL PROTECTED] > my-domain.com > -- > > Will it mess things up to have multiple listings like this? How about the > - ? Will having a domain name with - in it mess things up? What's the output of: /var/qmail/bin/qmail-showctl | grep '^SMTP clients may' And why disguise the domain? If you want to receive mail at this domain, it can't be that big a secret. Chris
Re: Help me understand "allowed rcpthosts"
Chris Johnson wrote: :What's the output of: :/var/qmail/bin/qmail-showctl | grep '^SMTP clients may' The output is this: SMTP clients may send messages to recipeints at localhost. SMTP clients may send messages to recipeints at ns.vivid-eye.com. SMTP clients may send messages to recipeints at www.vivid-eye.com. SMTP clients may send messages to recipeints at [EMAIL PROTECTED] SMTP clients may send messages to recipeints at vivid-eye.com. :And why disguise the domain? If you want to receive mail at this domain, :it can't be that big a secret. I've always been warned not to give out information on a static domain address (especially when requesting help on mail-lists) since this opens the door for possible attacks on my system by unscrupulous lurkers of any given mail-list. Do you "really" need the domain name? Ok, if so, you've noticed it's vivid-eye.com. Is my problem possibly located in the DNS setup? I've not had any problems with receiving email before, when I used sendmail. James
Re: Help me understand "allowed rcpthosts"
On Fri, May 12, 2000 at 02:51:12PM -0700, James wrote: > Chris Johnson wrote: > :What's the output of: > :/var/qmail/bin/qmail-showctl | grep '^SMTP clients may' > > The output is this: > SMTP clients may send messages to recipeints at localhost. > SMTP clients may send messages to recipeints at ns.vivid-eye.com. > SMTP clients may send messages to recipeints at www.vivid-eye.com. > SMTP clients may send messages to recipeints at [EMAIL PROTECTED] > SMTP clients may send messages to recipeints at vivid-eye.com. > > :And why disguise the domain? If you want to receive mail at this domain, > :it can't be that big a secret. > > I've always been warned not to give out information on a static domain > address (especially when requesting help on mail-lists) since this opens > the door for possible attacks on my system by unscrupulous lurkers of any > given mail-list. > > Do you "really" need the domain name? Ok, if so, you've noticed it's > vivid-eye.com. If you'd provided it in the first place it would have shortened this thread considerably: [cjohnson@shemp cjohnson]$ telnet www.vivid-eye.com 25 Trying 63.224.195.57... Connected to ns.vivid-eye.com. Escape character is '^]'. helo mail 220 ns.vivid-eye.com ESMTP 250 ns.vivid-eye.com mail from:<> 250 ok rcpt to:<[EMAIL PROTECTED]> 250 ok quit 221 ns.vivid-eye.com Connection closed by foreign host. So your host certainly appears to be willing to receive mail for this domain. Are you sure you're talking to 63.224.195.57 (which is what's listed as the MX for vivd-eye.com) when you do this test? Chris
Re: Port 25
James wrote: > With some help from Jerry, I was able to narrow down a problem I am having > with receiving mail from outside servers through Qmail. It's apparent > that my port 25 is closed off to outside connections. I don't know how or > why it's closed off.. TCPwrappers? Why would port 25 be closed off > anyway. Perhaps there is a security feature in Mandrake 7.02 that closes > this port? > > I was able to receive mail through sendmail before I installed qmail, so I > am guessing qmail somehow closed port 25. How do I open that port? > > james What commands are you using to startup the smtp service and in what file are they in? Dale
Re: qmail-smtpd appears to work but doesn't
Bob Brown wrote: > I've followed the steps in the "Life as Qmail" document. > The install seems to have gone without a hitch--- qmail, > ucspi-tcp, daemontools. All the test along the way seem > to work. TEST.deliver works fine. TEST.receive fails > on the first test. > > I've tried to telnet to both 127.0.0.1 25 and direct to > the domain the dialog, helo dude, mail, rcpt and data > all give the correct results back. > > Looking in the /var/log/qmail/smtpd/current looks ok to me: > > @4000391ba61d07d823fc tcpserver: status: 1/40 > @4000391ba61d07dc0bfc tcpserver: pid 8855 from 127.0.0.1 > @4000391ba61d08b3f954 tcpserver: ok 8855 localhost:127.0.0.1:25 > :127.0.0.1:root:1063 > @4000391ba64910b5b3cc tcpserver: end 8855 status 0 > @4000391ba64910b5fe04 tcpserver: status: 0/40 > @4000391ba6bb0f0bbcec tcpserver: status: 1/40 > @4000391ba6bb0f0fc814 tcpserver: pid 12466 from 209.81.49.16 > @4000391ba6bc08c1a93c tcpserver: ok 12466 > main.send2u.com:209.81.49.35:25 ceres.wallis.com:\ > 209.81.49.16:mwallis:3795 > @4000391ba6bc08ecc84c tcpserver: end 12466 status 0 > @4000391ba6bc08ed87b4 tcpserver: status: 0/40 > @4000391ba6c21d542014 tcpserver: status: 1/40 > @4000391ba6c21db5107c tcpserver: pid 12641 from 209.81.49.35 > @4000391ba6c21e560784 tcpserver: ok 12641 > main.send2u.com:209.81.49.35:25 main.send2u.com:2\ > 09.81.49.35:root:1067 > @4000391ba6df32cf2de4 tcpserver: end 12641 status 0 > @4000391ba6df32cf7fec tcpserver: status: 0/40 > @4000391ba81e1bace854 tcpserver: status: 1/40 > @4000391ba81e1bb0e3dc tcpserver: pid 20600 from 209.81.49.16 > @4000391ba81f0e0bd14c tcpserver: ok 20600 > main.send2u.com:209.81.49.35:25 ceres.wallis.com:\ > 209.81.49.16:mwallis:3921 > @4000391ba81f0ef834ec tcpserver: end 20600 status 0 > @4000391ba81f0ef8f454 tcpserver: status: 0/40 > @4000391bac810fe720fc tcpserver: status: 0/40 > @4000391bada21a6f99dc tcpserver: status: 1/40 > @4000391bada21a73ef3c tcpserver: pid 10219 from 209.81.49.16 > @4000391bada3188cbc94 tcpserver: ok 10219 > main.send2u.com:209.81.49.35:25 ceres.wallis.com:\ > 209.81.49.16:mwallis:4431 > @4000391bada31adede3c tcpserver: end 10219 status 0 > @4000391bada31adfa95c tcpserver: status: 0/40 > > BUT nothing ever shows up in the Mailbox file. This seems strange to > me since the TEST.deliver seemed to work fine. > > I got rid of the daemontools and the tcpserver and tried using inetd > and the rc script directly. This also fails in exactly the same way. > > Is there a tool to trace where it's getting lost? I even did a find on > the system by time to see if the data is just getting written in the > wrong place. This is strange because it appears to accept the connection > and says it was successful but nothing gets written to disk. > > Any ideas would be appreciated. > > Bob Brown If you are trying to send mail the root account qmail will not let you, it sends it to a mail folder in the /var/qmail tree. Try sending an e-mail to another user account. You can setup qmail to deliver root mail to another user by using the .qmail-root file and putting your e-mail address in it. If you want to see if the root mail was at least delivered to the alias mail folder, cd /var/qmail/alias and you should have amongst other files a Mailbox or Maildir file (depending on which method you are using). You should be able to view the Mailbox or Maildir with a text editor or with the more or less pager less filename.ext or more filename.ext . Take Care, Dale
qmail@list.cr.yp.to
Chris Johnson wrote: :So your host certainly appears to be willing to receive mail for this :domain. Are you sure you're talking to 63.224.195.57 (which is what's :listed as the MX for vivd-eye.com) when you do this test? What do you mean am I sure? I'm not being caustic.. just trying to understand your question. When I send email from an outside server, I believe it is going to that ip address.. how would I know? I simply send email to [EMAIL PROTECTED] .. from there I have no idea how to check if it's going to that ip address. How would I check? I'm just guessing that since vivid-eye.com is a functioning domain, that the email is going to it's correct destination. James
Re: qmail-smtpd appears to work but doesn't
Sorry about that last "subject" screw-up. james
Filtering
Hello ! I'm rather a beginner not only with QMAIL but with unix as a whole. I just wanted to ask if anyone can help - something I didn't find anywhere. I want to filter some incoming messages - both local and remote. However, I want to filter them as they are coming, not when they have come and have been placed in the queue. The whole idea is to prohibit big attachments and to deny any mail with huge attachments before it has arrived - for the sake of saving bandwidth, so I want to reject as it comes before its being delivered already. I hope this makes sense. Thank you very much, Peter
RE: How do you do it?
> -Original Message- > From: John Gonzalez/netMDC admin [mailto:[EMAIL PROTECTED]] > Sent: Tuesday, May 09, 2000 1:17 PM > To: Len Budney > Cc: [EMAIL PROTECTED] > Subject: Re: How do you do it? > > > On Tue, 9 May 2000, Len Budney wrote: > > >At FORE systems we had a phone support person who would shout those > >things, so loud that everybody in building one could hear it. He was > >astoundingly imaginative and colorful, and many of his > remarks are not > >printable. > > > >Eventually, somebody spied on his work, and noticed that he > was deftly > >using the mute button on his phone. He could interject these > >incredible outbursts, while speaking levelly and courteously at all > >times to the customer. Amazing. > > > >Len. > > That would work great, until your finger slipped off the mute > button on > accident, or it failed to work one time :) Hrm. This is vaguely reminiscent of a time that I was on the phone to Local TelCo, and got annoyed. I hit "mute" and screamed "You STUPID woman!" at the top of my lungs before releasing the button. She said to me icily "We all make mistakes, you know." It was only later that I found out that the mut button didn't actually cut the microphone out, rather it just turned the volume down very low. Unfortunately I screamed so loudly that she heard it. Oops. Aled. PS. Can you delimit your .sig properly please? Thanks. > ___ _ __ _ > __ /___ ___ /__ John Gonzalez/Net.Tech > __ __ \ __ \ __/_ __ `__ \/ __ /_ ___/ MDC Computers/netMDC! > _ / / / `__/ /_ / / / / / / /_/ / / /__ (505)437-7600/fax-437-3052 > /_/ /_/\___/\__/ /_/ /_/ /_/\__,_/ \___/ http://www.netmdc.com > [-[system > info]---] > 12:15pm up 105 days, 19:12, 6 users, load average: 0.05, > 0.28, 0.32 >
Re: Filtering
on 5/12/00 3:34 PM, [EMAIL PROTECTED] had the thought: > Hello ! > I'm rather a beginner not only with QMAIL but with unix as a whole. I > just wanted to ask if anyone can help - something I didn't find > anywhere. > I want to filter some incoming messages - both local and remote. > However, I want to filter them as they are coming, not when they have > come and have been placed in the queue. The whole idea is to prohibit > big attachments and to deny any mail with huge attachments before it > has arrived - for the sake of saving bandwidth, so I want to reject as > it comes before its being delivered already. I hope this makes sense. > > Thank you very much, > Peter > > > Try using /var/qmail/control/databytes This will allow you to control the size of the messages... http://Web.InfoAve.Net/~dsill/lwq.html#config-files Pat -- Freestyle Interactive | http://www.freestyleinteractive.com | 415.778.0610
Re: Filtering
thank you for this one. However, my problem is not only the size of the message but as well as its contents. I want to deny also any messages that contain .EXE files to avoid virus spread. So actually I have to filter the message in two ways - the size and its content. >> >> Hello ! >> I'm rather a beginner not only with QMAIL but with unix as a whole. I >> just wanted to ask if anyone can help - something I didn't find >> anywhere. >> I want to filter some incoming messages - both local and remote. >> However, I want to filter them as they are coming, not when they have >> come and have been placed in the queue. The whole idea is to prohibit >> big attachments and to deny any mail with huge attachments before it >> has arrived - for the sake of saving bandwidth, so I want to reject as >> it comes before its being delivered already. I hope this makes sense. >> >> Thank you very much, >> Peter > >put your size limit in /var/qmail/control/databytes, like this: > >su >echo 32700 > /var/qmail/control/databytes > >This will cause excessive messages to get bounced. > >I don't know if qmail-smtpd looks at that file or not, if not you >could patch it to look at that file, or patch it to abruptly drop >the connection once it has received that much data. Abruptly dropping >connections would cause retries and so forth, though, while bounce messages >will retrain the people sending the attachments to do something else so >their messages can get through. > > > >-- > David Nicol 816.235.1187 [EMAIL PROTECTED] >You discover uranium! collect $240,000 >
Re: Filtering
On Sat, 13 May 2000 [EMAIL PROTECTED] wrote: > I want to filter some incoming messages - both local and remote. > However, I want to filter them as they are coming, not when they have > come and have been placed in the queue. The whole idea is to prohibit > big attachments and to deny any mail with huge attachments before it > has arrived - for the sake of saving bandwidth, so I want to reject as > it comes before its being delivered already. I hope this makes sense. >From man qmail-smtpd: CONTROL FILES [...] databytes Maximum number of bytes allowed in a message, or 0 for no limit. Default: 0. If a message exceeds this limit, qmail-smtpd returns a permanent error code to the client; in contrast, if the disk is full or qmail- smtpd hits a resource limit, qmail-smtpd returns a temporary error code. databytes counts bytes as stored on disk, not as transmitted through the network. It does not count the qmail-smtpd Received line, the qmail-queue Received line, or the envelope. If the environment variable DATABYTES is set, it overrides databytes. Notice the last paragraph! this can make it possible to have selective rules for different IP-ranges. -- Thorkild
Re: Filtering
QMAILQUEUE and qmail-qfilter should do the trick. They're both listed on the qmail.org web page. jon At 2:08 AM +0300 5/13/00, [EMAIL PROTECTED] wrote: >thank you for this one. However, my problem is not only the size of >the message but as well as its contents. I want to deny also any >messages that contain .EXE files to avoid virus spread. So actually I >have to filter the message in two ways - the size and its content. > >>> >>> Hello ! >>> I'm rather a beginner not only with QMAIL but with unix as a whole. I >>> just wanted to ask if anyone can help - something I didn't find >>> anywhere. >>> I want to filter some incoming messages - both local and remote. >>> However, I want to filter them as they are coming, not when they have >>> come and have been placed in the queue. The whole idea is to prohibit >>> big attachments and to deny any mail with huge attachments before it >>> has arrived - for the sake of saving bandwidth, so I want to reject as >>> it comes before its being delivered already. I hope this makes sense. >>> >>> Thank you very much, >>> Peter >> >>put your size limit in /var/qmail/control/databytes, like this: >> >>su >>echo 32700 > /var/qmail/control/databytes >> >>This will cause excessive messages to get bounced. >> >>I don't know if qmail-smtpd looks at that file or not, if not you >>could patch it to look at that file, or patch it to abruptly drop >>the connection once it has received that much data. Abruptly dropping >>connections would cause retries and so forth, though, while bounce messages >>will retrain the people sending the attachments to do something else so >>their messages can get through. >> >> >> >>-- >> David Nicol 816.235.1187 [EMAIL PROTECTED] >> You discover uranium! collect $240,000 >>
Re: Ezmlm web front
also sprach chee: > Doesn't qmailadmin also support mailing list administration using ezmlm??? > What is the different between this package and qmailadmin? Some differences have already been mentioned. Another important one is that qmailadmin currently doesn't support ezmlm with the idx patch. ezmlm-web (and ezweb) does. /pg -- Peter Green Gospel Communications Network, SysAdmin [EMAIL PROTECTED]
Re: Filtering
[EMAIL PROTECTED] wrote: > thank you for this one. However, my problem is not only the size of > the message but as well as its contents. I want to deny also any > messages that contain .EXE files to avoid virus spread. So actually I > have to filter the message in two ways - the size and its content. What you want is Scan4Virus http://www.geocities.com/jhaar/scan4virus/ There is a text filter solution where you can filter on ex. attachement of .EXE files not allowed when over ex. 5MB, etc.. This is the emergency solution when stopping brand new viruses not detected by the scanners. Scan4Virus supports Trend/Mcaffee/Sophos/H+BEDV and also very soon AVP from Kaspersky Lab. Take a look and I guess you will be impressed. I was and still am. -- IDG New Media Einar Bordewich Technical Manager Phone: +47 2336 1420 E-Mail: [EMAIL PROTECTED]
Re: Wrong subject line
That last message I sent had the wrong subject line after "FIXED".. God my brain is fried tonight. It should have said: Problem FIXED (was Help me understand "allowed rcpthosts") Sorry about that.. I'm not sure if Bob Brown fixed his problem or not. James
Problem FIXED (was qmail-smtp appears to work but doesn't)
I don't know why, but when I sent a few email tests to my server at around 4:30 this afternoon (about 6 hours ago), it kept coming back rejected. When I got home and did another test, the mail went through fine. I did nothing since my last test (I had to leave). I don't really care why it started working, I'm just happy it is now. Thanks for all the help and suggestions. James
Re: Vertify the e-mail address;
> But, as I know, in > order to receive e-mail from any domain to [EMAIL PROTECTED], I need > both to and from 's domain in my rcpthosts file, that would result in a complete inability to receive mail. QMail will recieve mail from any domain, *as long* as it's to a domain listed in the locals file. steve
qfilelog...
... won't go away!
Hi Bruce,
I'm trying to use your qlogtools, qfilelog specifically because I want
to use logrotate & qmail-analog.
http://em.ca/~bruceg/qlogtools/
My problem is that qfilelog won't go away when I issue "qmail.init stop"
it's "Process State Code" get changed to "R" (runnable (on run queue))
and it just sits there.
I'm using the scripts that come with the memphis RPM's for qmail v1.03.
They come setup by default for cyclog. Here's the pertinent part of the
script:
As distributed:
===
supervise $DIR qmail-start "$DEFAULT_DELIVERY" accustamp qmail \
| setuser $LOGUSER cyclog $FILESIZE $FILENO $LOGDIR &
===
With my modifications for use of qfilelog:
===
supervise $DIR qmail-start "$DEFAULT_DELIVERY" accustamp qmail \
| setuser $LOGUSER qfilelog $LOGFILE &
===
The commands run fine, no errors reported. I can do a "ps -auxww | grep
qmai" and all is well. The log gets created, etc. The only problem is
when stopping the service.
I can add "killall -TERM qfilelog" to the "stop" portion of the script
and it'll die just fine but that doesn't help if I want to run qfilelog
on the other logs like the ones for qmail-smtpd & pop3... (Which I do!)
I thank you for writing the tools and for posting to the list (I found
your posts with eGroups when I searched for logrotate in the archive.)
Any help you can provide would be greatly appreciated. I've atttached
the whole qmail.init script in case you're not familiar with it.
Any caveats with using qmail-mrtg on qfilelog-produced logfiles? That's
my next task re: qmail...
Thanks for your time,
~Jason
Jason Ingham
System Administrator
WebEasy, Inc.
T: (310) 576-0770
F: (310) 576-2011
[EMAIL PROTECTED]
http://www.webeasy.com
#! /bin/sh -
# $INITDIR/qmail.init
# INITDIR is defined below
# Sun Dec 14 1997 XZ <[EMAIL PROTECTED]> v2.3
#
# chkconfig: 345 80 45
# description: Start, stop, restart, reload, and otherwise signal qmail \
# Makes heavy use of parts of DJB's daemontools package \
# It also relies upon daemontools.functions for 91.04982% \
# of the grunt work.
# Do not remove the next line, RH will not function w/o
# killproc action daemon
# customize
QMAILHOME=/var/qmail # ~qmail
PROG=qmail# what program?
DIR=/var/lock/$PROG # a directory for supervise to use
LOGDIR=/var/log/$PROG # directory for logs
archiveOGFILE=/var/log/qmail/qm.log
LOGFILE=/var/log/$PROG/qm.log
LOGUSER=qmaill# user to own logs
LOGCONFDIR=/etc/cyclog# config dir for cyclog
DEFAULT_DELIVERY="`egrep -v "(^#|^ *$)" $QMAILHOME/defaultdelivery/rc`" # where to
deliver mail
USESUBSYS="y" # use /var/lock/subsys/$PROG, y/n
INITDIR=/etc/rc.d/init.d # location of initscripts
# Grab the daemontools init functions
. $INITDIR/daemontools.functions
FILESIZE=${FILESIZE="-s 100"} # for compatibility, use /etc/cyclog instead;
FILENO=${FILENO="-n 10"} # see daemontools.functions for more
export PATH=$QMAILHOME/bin:$PATH
start() {
if check; then
echo "$PROG is already running"
else
echo -n "Starting $PROG..."
supervise $DIR qmail-start "$DEFAULT_DELIVERY" accustamp qmail \
| setuser $LOGUSER qfilelog $LOGFILE &
if [ "$USESUBSYS" = "y" ]; then
touch /var/lock/subsys/$PROG
fi
echo "done"
fi
}
case "$1" in
start)
start
;;
stop)
stop
##killall -TERM qfilelog
;;
restart)
restart
;;
status)
status
;;
help)
help
;;
*)
signal $1
;;
esac
Re: bypassing relaydomains (reverse DNS issues)
> Dinesh Punjabi (Fri 12.0500-08:16): > Again, how can I modify tcpserver or qmail or > relaydomains in order to ignore domain based > relay checks. did you think of opening up the server temporarily to relieve your customers until you are set? while open-relaying you should give tcpserver the -x flag and set up the "noconnects" database according to rbl standards. i think there are dns implementations that do the neccessary lookups (dns implemetation of [EMAIL PROTECTED]?). -- clemens [EMAIL PROTECTED]
Re: spool vs individual files
> Dave Sill (Fri 12.0500-11:24): > "Michael Smith" <[EMAIL PROTECTED]> wrote: > > >We're currently looking at mail solutions for our online email > >system, and we've hit against an interesting conundrum. We were > >wondering what the advantages are to listing mail messages as > >individual files over a spool file? > > The choice is file-per-mailbox (a la mbox) or file-per-message (a la > maildir). > > They each have their pros and cons, of course. you should also consider the pros for maildir in a nfs environment, where filelocking might not work correctly. -- clemens [EMAIL PROTECTED]
Vertify the e-mail address;
Hi, I am using PHP's mail function and qmail to send out a on-line inquiry form to my company e-mail address. I won't be able to figure out the relaying problem and the validate of the sender's e-mail address. For the relaying problem, if my company's e-mail address is [EMAIL PROTECTED], so I just need to put netvigator.com in my /var/qmail/control/rcpthosts and /var/qmail/control/locals, so that my server will receive any e-mail for netvigator.com. But, as I know, in order to receive e-mail from any domain to [EMAIL PROTECTED], I need both to and from 's domain in my rcpthosts file, but how can i know every domains that will send mail to my company. any suggestions are helpful . For the php mail(), there are a from field and to field in mail function, will qmail use the to field to vertify this domain is accpeted for relaying. And how can I vertify that the from field's e-mail address is valid. Any suggestions !! Thank you so much. Thank you so much, Mark
Re: qmail@list.cr.yp.to
You _should_ be getting mail from the outside... - $ host -t mx vivid-eye.com vivid-eye.com mail is handled (pri=10) by www.vivid-eye.com $ telnet www.vivid-eye.com 25 Trying 63.224.195.57... Connected to ns.vivid-eye.com. Escape character is '^]'. 220 ns.vivid-eye.com ESMTP HELO dude 250 ns.vivid-eye.com MAIL FROM: [EMAIL PROTECTED] 250 ok RCPT TO: [EMAIL PROTECTED] 250 ok RCPT TO: [EMAIL PROTECTED] 553 sorry, that domain isn't in my list of allowed rcpthosts (#5.7.1) - Everything looks OK. The MX accepts mail for that domain, and rejects relaying otherwise. Where exactly are you testing from? RC On Fri, May 12, 2000 at 03:16:37PM -0700, James wrote: > Chris Johnson wrote: > :So your host certainly appears to be willing to receive mail for this > :domain. Are you sure you're talking to 63.224.195.57 (which is what's > :listed as the MX for vivd-eye.com) when you do this test? > > What do you mean am I sure? I'm not being caustic.. just trying to > understand your question. When I send email from an outside server, I > believe it is going to that ip address.. how would I know? I simply send > email to [EMAIL PROTECTED] .. from there I have no idea how to check if > it's going to that ip address. How would I check? I'm just guessing that > since vivid-eye.com is a functioning domain, that the email is going to > it's correct destination. > > James > -- +--- | Ricardo Cerqueira | PGP Key fingerprint - B7 05 13 CE 48 0A BF 1E 87 21 83 DB 28 DE 03 42 | Novis - Engenharia ISP / Rede Técnica | Pç. Duque Saldanha, 1, 7º E / 1050-094 Lisboa / Portugal | Tel: +351 21 3166730/00 (24h/dia) - Fax: +351 21 3166701
automatically resolve dns
Hi, I would like to know whether qmail will perform a automatic DNS lookup in order to prove the sender's address that has a valid DNS record before receiving messages.?? Thank You Mark
Re: automatically resolve dns
On Sat, May 13, 2000 at 10:03:13AM +0800, Mark Lo wrote: > I would like to know whether qmail will perform a automatic DNS > lookup in order to prove the sender's address that has a valid DNS > record before receiving messages.?? The answer is, as it was when Dave Sill answered the same question asked by you earlier today, still "no." Chris
Re: automatically resolve dns
Hi, Oh, I have missed some of the messages from qmail mailing list, I don't know why. Sorry for asking the same question again. So How to enable a DNS lookup ?? And Should I do it?? There is a patch in qmail Anti-Spam HowTo for enabling a DNS lookup, but there has not any installation procedure, and I am not able to understand a thing from the patch. What should I do ?? www.summersault.com/chris/techno/qmail/qmail-antispam.html Thank you Mark Chris Johnson wrote: > On Sat, May 13, 2000 at 10:03:13AM +0800, Mark Lo wrote: > > I would like to know whether qmail will perform a automatic DNS > > lookup in order to prove the sender's address that has a valid DNS > > record before receiving messages.?? > > The answer is, as it was when Dave Sill answered the same question asked by you > earlier today, still "no." > > Chris
Re: qmail-smtpd appears to work but doesn't
At 06:13 PM 05/12/2000 -0400, Dale Miracle wrote:
Bob Brown wrote:
> I've followed the steps in the "Life as Qmail"
document.
> The install seems to have gone without a hitch--- qmail,
> ucspi-tcp, daemontools. All the test along the way seem
> to work. TEST.deliver works fine. TEST.receive fails
> on the first test.
..
>
> Any ideas would be appreciated.
>
> Bob Brown
If you are trying to send mail the root account qmail will not let you,
it
sends it to a mail folder in the /var/qmail tree. Try sending an e-mail
to
another user account. You can setup qmail to deliver root mail to
another
user by using the .qmail-root file and putting your e-mail address in
it.
If you want to see if the root mail was at least delivered to the
alias
mail folder, cd /var/qmail/alias and you should have amongst other files
a
Mailbox or Maildir file (depending on which method you are using).
You
should be able to view the Mailbox or Maildir with a text editor or
with
the more or less pager less filename.ext or more
filename.ext .
Take Care,
Dale
Hi Dale,
I ran the telnet 127.0.0.1 25 from another account as you
suggested.
reb is an existing account. The telnet session acted correctly but
nothing shows up in the Mailbox file. Here's the session:
main: {2} telnet 127.0.0.1 25
Trying 127.0.0.1...
Connected to 127.0.0.1.
Escape character is '^]'.
220 main.send2u.com ESMTP
helo dude
250 main.send2u.com
mail [EMAIL PROTECTED]
250 ok
rcpt [EMAIL PROTECTED]
250 ok
data
354 go ahead
Subject: Testing Mail again
testing mail again
.
250 ok 958192006 qp 13854
quit
221 main.send2u.com
Connection closed by foreign host.
main: {3}
The /var/log/qmail/current file shows:
@4000391cd9901536c364 new msg 1064988
@4000391cd990153709b4 info msg 1064988: bytes 231 from <> qp
13854 uid 6004
@4000391cd9901559d00c starting delivery 84: msg 1064988 to local
@main.send2u.com
@4000391cd990155a2dcc status: local 1/10 remote 0/20
@4000391cd9901562ad94 delivery 84: success:
@4000391cd9901562dc74 status: local 0/10 remote 0/20
@4000391cd99015630b54 end msg 1064988
The /var/log/qmail/smtpd/current file shows:
@4000391cd97304426e64 tcpserver: status: 1/40
@4000391cd97304461fb4 tcpserver: pid 13407 from 127.0.0.1
@4000391cd973053b0704 tcpserver: ok 13407 localhost:127.0.0.1:25
:127.0.0.1:majordomo:1516
@4000391cd9950936a674 tcpserver: end 13407 status 0
@4000391cd9950936f494 tcpserver: status: 0/40
Bob
