Re: [toaster] bounce from: whence comes this address ???
Michael D Schleif wrote: I have a toaster on czar.platinumaire.net. Bounces show a different system: From: [EMAIL PROTECTED] This is one of three (3) retired toasters that are now consolidated/migrated to czar. Where does this bounce-from: come from? Why is it the wrong system? What do you think? Look in /var/qmail/control/me Don't forget to restart/reload qmail-send after you change it. (qmailctl restart or qmailctl reload) Rick
[toaster] Thanks from pmailadmin
Bill: I just finished running the pmailadmin daemon test suite against the vpopmaild installed with your toaster. It ran perfectly the first time with no changes. THANKS!! Rick
Re: [toaster] Thanks from pmailadmin
Bill Shupp wrote: Rick Widmer wrote: Bill: I just finished running the pmailadmin daemon test suite against the vpopmaild installed with your toaster. It ran perfectly the first time with no changes. Excellent! Do you plan to upload pmailadmin into CVS? It doesn't appear to be there. Yes. I'm cleaning it up now. It certainly won't handle mailing lists yet, and until I hear what Tom wants to do with 5.4.15 it will only work with your toaster. I hope to have it up within the week. Rick
Re: [toaster] Greylisting
Nitchi DaMon wrote: dumb question... what are most everyone here running for the OS? I've been using redhat for years now and migrated into the Fedora Core. But I'm open to suggestions. SuSE Rick
Re: [toaster] CHKUSER Problem
Sam Laffere wrote: cat .qmail-default | /home/vpopmail/bin/vdelivermail '' bounce-no-mailbox If no mailbox for addressee, bounce #| /usr/local/bin/maildrop /home/vpopmail/domains/midkan.com/mailfilter If no mailbox for addressee, send to mailfilter #| /home/vpopmail/bin/vdelivermail '' /home/vpopmail/domains/midkan.com/postmaster If no mailbox for addressee, send to postmaster Either of the last two block chkuser from working because they direct ALL mail to non-existant mailboxes to a specific location. That means there are no non-existant mailboxes when those choices are selected.
Re: [toaster] suspending and account
Jeff Koch wrote: Hi Tom: I found the vmoduser command can operate on an entire domain to turn off pop3 access. vmoduser -p domain_name --- turns of pop3 access for all users vmoduser -x domain_name --- clears the blocking flag for all users Note to self: Find out how these work. Do they set a domain level flag, or the flag for all users. If it affects the flag on all users doing this will turn off blocking on any users that had it before. Rick
Re: [toaster] Greylisting
Nitchi DaMon wrote: I can download and recompile MySQL and that is where I am leaning at the moment, but I'm still holding out hope that there is a solution out there. That may very well be the best. You have installed the server, client AND development RPMs for MySQL, right? Server _may_ include client, but you need development to be able to compile the library into new things. (like vpopmail)
[toaster] [Fwd: rblsmtpd using maps.vix.com by default]
Bill: I just spotted this on the qmail list. If you aren't already adding Charles' fix to your toaster patches, it might be a good idea... Rick Original Message Recently, Paul Vixie, owner of vix.com, has realized that one possible reason for an unexpected amount of traffic on the decommissioned-since-1999 maps.vix.com is because of ucspi-tcp-0.88's rblsmtpd program. see http://www.merit.edu/mail.archives/nanog/msg04513.html I suggest everyone who's running rblsmtpd from ucspi-tcp-0.88 with no -r flag reinstall ucspi-tcp with Charles Cazabon's fix, available at http://pyropus.ca/software/misc/rblsmtpd-nodefaultrbl.patch. I realize there's a short blurb about this on lifewithqmail.org -- i'll be emailing dave shortly in an effort to emphasize the patch's importance. -- Jeremy Kister http://jeremy.kister.net./
Re: [toaster] Require AUTH on port 587 (was Re: [toaster] AOL port 587)
Bill Shupp wrote: Thanks for the reminder Tom. I have not integrated it, nor have I integrated tonino's chkuser 2.0.9. But I did quit a busy client recently, so I have more time these days, and will be getting through a backlog of suggestions soon. Cool. Let me know when its ready... I need to rebuild my mail server fairly soon. Rick
Re: [toaster] QmailAdmin and Qmail behind proxy
SKT/MIS/ROZI wrote: Can i install the qmailadmin on different server? No. Qmailadmin needs direct access to files and must reside on the mail server. Is it have a way to let them communicate? Vpopmaild can be configured to allow access from another machine, but currently there isn't a user interface to let users manage their mail accounts available for it. Bill has mentioned that he is working on one, but it isn't released yet. Rick
Re: [toaster] vpopmaild problem in toaster 0.9.0
Alessio Cecchi wrote: Alle 11:53, venerdì 30 marzo 2007, Alessio Cecchi ha scritto: add_alias [EMAIL PROTECTED] [EMAIL PROTECTED] -ERR 0901 not authorized Where is the problem? Oh no! Only if a set with vmoduser -S ( grant system administrator privileges - access all domains ) to [EMAIL PROTECTED] i can add/remove alias, but for all domains. There is a way to ability the postmaster to add/remove alias only for his domain? Grand a user within the desired domain this privilege: -a ( grand qmailadmin administrator privileges) Rick
Re: [toaster] vpopmaild problem in toaster 0.9.0
Rick Widmer wrote: Alessio Cecchi wrote: Alle 11:53, venerdì 30 marzo 2007, Alessio Cecchi ha scritto: add_alias [EMAIL PROTECTED] [EMAIL PROTECTED] -ERR 0901 not authorized Where is the problem? Oh no! Only if a set with vmoduser -S ( grant system administrator privileges - access all domains ) to [EMAIL PROTECTED] i can add/remove alias, but for all domains. There is a way to ability the postmaster to add/remove alias only for his domain? Grand a user within the desired domain this privilege: -a ( grand qmailadmin administrator privileges) grant not grand... Rick
Re: [toaster] Transfer mail accounts from one server to another
Some thoughts... Unless you have a massive multi server mail installation, or need to manage mail accounts from a custom program, don't mess with a database. CDB is more efficient on a single machine. Even if you are writing a custom program, look at vpopmaild to manage your mail accounts. If you want to move from one machine to another the UID, GID, permissions, ownership, and paths for all files used by qmail, vpopmail and apache must be identical. I suggest you copy and paste the /etc/passwd and /etc/group lines rather than trying to type them. Many of these values are compiled into qmail, vpopmail and qmailadmin. You will need at least /var/qmail/alias, /var/qmail/control, /var/qmail/users and the entire ~vpopmail directory. If you are updating the vpopmail code, do make install after copying the ~vpopmail directory. Be sure all ownership and permissions are preserved. Rick
Re: [toaster] qmailctl restart
Qmail List wrote: Dear List, I did a qmailctl restart and notice that qmail-smtpd is been restart but qmail-send did not. Did you wait long enough to make sure all the child processes had time to finish, or kill them, before you restarted? Is there a log whereby i can check why qmail-send is not restarted? /var/log/qmail/current
Re: [toaster] qmailctl restart
Is there a log whereby i can check why qmail-send is not restarted? /var/log/qmail/current What should i take note ok? There are too many info there. If it is not restarting properly, look at the last lines. I often move the existing file away, then attempt to restart again. Anything in the file would be related to the most recent attempt to start. my /var/log/qmail/current has lines like: new msg starting delivery status: end msg delivery 123456: success: info msg Anything else is worth checking into. Also look in ps for readproctitle service errors: If there is anything after this line, it is errors detected by daemontools. It happened after one of the junoir adminstrators deleted /var/log/qmail/current, /var/log/qmail/smtpd/current and /var/log/qmail/pop3d/current files. That could be bad news. I'm not sure how the logging process will handle having the file deleted out from under it. It might be good to shut down qmail-send, and make sure its logging process dies too. At this point you might also want to try commenting out the svscanboot line in /etc/inittab then restart init (kill -1 1). ps and make sure all the daemontools / qmail processes are shut down, then removing the comment and killing it again to restart. Or if it doesn't hurt too much, do a full reboot. (clear out the log files first.) Rick
Re: [toaster] Bill Shupps Qmailtoaster + Domainkeys installation howto with TSL 3.05
Jaroslav wrote: Hello. Whell the webpage is offline at the moment. Hope not for a long time. I can see it... Rick
Re: [toaster] Applying John Simpsons validrcptto patch
Tom Collins wrote: On Nov 1, 2007, at 4:50 PM, Bill Shupp wrote: What does this patch do that chkuser doesn't already do? Validrcptto uses ONCHANGE to monitor actions that add or delete accounts on the mail server. The valid address list is stored in a .cdb file that is easy to copy to other servers in a cluster. Earlier versions used cron to scan the user list periodically. Chkuser links to vchkpw and valias_ to determine if an address is valid. This should be much faster, but only works on the local machine. Maybe there could be a version that works with vpopmaild, but still I think validrcptto is a better choice for clusters. One big thing that I like is that it can have custom reject messages for each address. So, if I have to kill an address that's overwhelmed with spam, I can have a custom reject like "that address is no longer in use, try fred at smith.com instead". That way a human sending email to my old address could (possibly) see the reject and know to try the new address. That might be a good use for passing the first line of a .qmail file to chkuser: #blackhole That address is no longer in use, try fred at smith.com Antonio Nati (tonix) has asked for a few bits from gid_flags, and I have agreed to assign them. He hasn't given me the list of what they are yet. Also, I don't know if he is aware of it, but he has a pointer to the first line of an alias that matches the address being tested, so any .qmail- file could have a comment in its first line that chkuser can use. I want to use the first word after the '#' if the first line is a comment, but everything after that is available. I would also like to be able to produce a list of first word values to accept mail, and another list to reject. For example, #Alias, #Mini-List, #Mail-List would all be accepted by chkuser, and #blackhole would be rejected, passing the rest of the line, if any, as the error message. When he has time to work on it, I'll try to have a discussion of the possibilities on the vpopmail list.
Re: [toaster] qmail in public domain
Sasa Ebach wrote: That is really awesome. I am wondering if this will make a lot of toaster scripts obsolete. We can now precompile qmail and distribute it in binary form. May we not? Looking at this toaster, I don't see it making that much difference. Bill can now pre-package qmail + netqmail_patches + his patches. That only saves a few steps. It doesn't change vpopmail, autorespond, qmailadmin, squirrelmail or courier-imap. They are all separate projects with separate release dates the toaster author must integrate. Rick
Re: [toaster] qmail in public domain
Lampa wrote: Of course but it can be implement in "normal" locations (not /var/qmail), binary can becked in many distributions and not need patches Which will break every program that manages qmail, including vpopmail. I believe the fact that all qmail installations are the same is one of its greatest strengths. In the document that releases qmail to the public Dr. Bernstein specifically asks people not to do that. "This does not mean that modifications are encouraged! Please take time to ensure that your distribution of qmail supports exactly the same interface as everyone else's. In particular, if you move files, please set up symbolic links from the original locations, so that you don't frivolously break scripts that work everywhere else."
Re: [toaster] qmail in public domain
Boris Pavlov wrote: /var/qmail is not the very-right place for binaries. the prohibition of the binary form effectively left qmail out of many distributions. the distributions will change these paths, so, why do not put them configurable at ./configure? There is hope. The netqmail team has mentioned something about lsb compatibility. My current plan is to see what they come up with. Actually my plan is just to continue using this toaster how ever it turns out, and spend my spare time on vpopmail. Rick
Re: [toaster] ToasterAdmin
Bill Shupp wrote: On Apr 13, 2008, at 1:54 AM, Lampa wrote: How much is vpopmail 5.4.26 stable to use in real server. Any changes which are not in touch with vpopmaild ? Thank you. See the ChangeLog. The changes are not significant, but required by ToasterAdmin. I'm pretty sure 5.4.26 will work fine with cdb, and it will have problems with mysql quotas. It seems all the major contributors prefer cdb, and mysql has fallen behind. If someone can provide a patch for mysql quotas I'll roll out a new release the next weekend. Yes, as noted many times before. :) I can't do it until vpopmaild > supports it. Last time I check with Rick Widmer, he was planning to > add the ezmlm support to vpopmaild. But I'm not sure if that's still > the case. It'll get added eventually. Other than bug fixes, that is the top of my list, and I've got about half of the functions working. I've been at a new job since December, and I had 2 paid projects on the table when I started the job. One of the projects is nearly complete, and the other is getting close. Once I get the first done, I'll have time to spend on vpopmail again. Sorry for the delay, but I could not turn down the job offer! Rick
Re: [toaster] wiki
Lampa wrote: Hello, is this wiki http://www.qmailwiki.org/Vpopmaild relevant for vpopmaild in current version (5.4.26d) ? README.vpopmaild from the version you are using is probably best.
Re: [toaster] ToasterAdmin 0.0.2
Bill Shupp wrote: If you're developing in PHP, you can view the API docs for Net_Vpopmaild: http://pear.php.net/package/Net_Vpopmaild/docs/0.2.1/ Let me re-phrase that... If you are developing in PHP you should be using Net_Vpopmaild. Rick
Re: [toaster] binding IP
Qmail List wrote: Hi, I have 2 IPs for the web and mail server which is on the same box. I would like apache to attach to the 1st IP and qmail on the 2nd. How can I make qmail to bind to the 2nd IP? Here is my run file for qmail-smtpd. Notice the term 'mail.developersdesk.com' in the parameters for tcpserver. The value in a normal installation is 0 which says all ip addresses the server listens to. If you prefer, you can also use the IP address here. Rick #!/bin/sh QMAILDUID=`id -u vpopmail` NOFILESGID=`id -g vpopmail` MAXSMTPD=`cat /var/qmail/control/concurrencyincoming` exec /usr/local/bin/softlimit -m 1000 \ /usr/local/bin/tcpserver -v -H -R -l 0 \ -x /mail/etc/tcp.smtp.cdb -c "$MAXSMTPD" \ -u "$QMAILDUID" -g "$NOFILESGID" mail.developersdesk.com smtp \ /usr/local/bin/rblsmtpd \ -r safe.dnsbl.sorbs.net \ -r bl.spamcop.net \ /var/qmail/bin/qmail-smtpd \ /mail/bin/vchkpw /bin/true 2>&1 ~
[toaster] Toaster update
Bill: I've been doing an installation of the toaster on a 64 bit OpenSuSE system, and I've been updating a copy of the toaster as I go. You can see the work in progress here: http://www.rickwidmer.com/toaster/ The changes so far include: ChangeLog 0.9.3 - 10/07/2008 -- Rick Widmer * Replace courier imap with Dovecot * Upgrade to squirrelmail 1.4.16 * Added SuSE notes * Added option to use BSD standard UID and GID values * Separate qmail manpath instructions for Debian, SuSE and other * Added symlink for rcqmail from qmailctl for SuSE users * Separated stunnel runfiles into separate sections for easier use * Added an extra tag in each code block so there is a \n on the last line when you copy/paste them. * I've added a few more variables similar to you allowing them to set the source directory. These are the values I use for my server: $SourceDir = '/var/src'; $HomeDir = '/mail'; $SystemEmail = '[EMAIL PROTECTED]'; $DocRoot = '/srv/www/htdocs'; $CGIDir = '/srv/www/cgi-bin'; $WebUser = 'wwwrun'; $WebGroup= 'www'; $DataDir = '/srv/www/squirrelmail-data'; I am also considering a dropdown list for target operating system that would hide unrelated notes, and possibly set default values for the other variables. If you are willing, please send me a copy of the PHP source code and any required files, and I'll merge in my updates and send it back to you to review. thanks, Rick p.s. I did try sending this private a couple days ago, but haven't heard anything from you yet. It would be nice to get this soon, as building the server and documenting it is part of my day job, and I get to bill them for the time.
Re: [toaster] OpenSuse 11, x86_64, and SMTP Failures
-Original Message- From: John Harmon [mailto:[EMAIL PROTECTED] Sent: Monday, November 17, 2008 6:27 PM To: toaster@shupp.org Subject: Re: [toaster] OpenSuse 11, x86_64, and SMTP Failures Tren, Thank you, that did the trick. Was wondering if you could explain one thing to me. I have 8GB of memory in the box, my run file originally had a soft limit of 800 (which I assume was 8GB, but I could be wrong). I doubled it originally thinking that might be the issue, but 1600 didn't cut it either. I doubled that to 3200 and that seems to be working now. Do you have any details to help me understand why I had to bump this so high, and what it means? I just built a toaster on OpenSuSE 11.0 and x86_64. Had to use 2000. (20MB) I'll be installing on 11.0 and a 32 bit processor soon, but for now I'm betting it's the x86_64 that bumps up the memory usage. Wish I knew for sure... Rick
[toaster] Question about qmailctl cdb
Bill: Looking at the qmailctl file in toaster_scripts I see that the cdb option has the following logic: if ! 'POP_AUTH_OPEN_RELAY 1' is in ~vpopmail/include/config.h then update the tcprules file for qmail-smtpd else run clearopensmtp fi Personally I wish smtp after pop would fade away, but since it hasn't it seems to me these should not be mutually exclusive. Just because you are running with --enable-roaming-users doesn't eliminate the need to update your tcp.smtp.cdb file. seems to me it would be better as: update the tcprules file for qmail-smtpd if 'POP_AUTH_OPEN_RELAY 1' is in ~vpopmail/include/config.h run clearopensmtp fi It would be even better as two separate commands, but then I would have to come up with a good name for it, so it probably won't happen this way. What do you think? Anyone... Rick p.s. My project is coming along well... here is my current versions.xml file: 0.9.4 1.06 <- 0.9.2 0.69 0.76 0.88 5.4.27 <- 0.9.2 1.1.11 <- 0.59.1 4.1.2 1.4.17 <- 1.3.1-1.2.7 2.0.4 0.53 0.443 1.2.12 1.0.8 4.2 0.94.2 <- 1.4.0.9 1.4.0<- 4 1.1.11 0.16.3 A couple more weekends and it should be ready.
Re: [toaster] adding pop3ds to an existing qmail rollout
Shane Chrisp wrote: One of the regulars on the list did do some work towards updating the toaster and posted some of his work. Maybe he will chime in and make his work available again. http://admin.haileypubliclibrary.org/toaster/ This is a temporary link, it can't stay on this server very long. If you use it, please send me a copy of the configuration page you use. If you get the configuration right the rest of the install is almost all copy/paste. I've installed it on SuSE 11.0 and 11.1, and Debian Etch. If you are updating a server, make sure all the UID/GID values match the existing ones. If you have any notes you would like added to the toaster for your favorite distribution, I'll take those too. You probably want to print, or otherwise save your configuration page settings. There has also been discussion by many of us quite some time back about Dovecot and how much lighter it is on resources and also so much fast at sorting and threading that Courier ever was. I think most of those who frequent this list have converted to Dovecot and are extremely happy with its performance. I agree. This version of the toaster is almost up to date with dovecot. I think I am one release behind now. It is probably worth downloading the latest and compiling it instead. The last few releases only caused warnings from patch that the line numbers had changed in the configuration file. Rick
