Re: smtproutes
I've been known as the worst typer ever... :) A type fast but with lots of bugs... ( kinda like what i do with everything ) lol so youshould have done a man qmail-control but in anycase, it is smtproutes located under /var/qmail/control/ of syntax domaintoforward:machinetoforward Peter Brezny writes: A while ago, Javier offered some help on how to forward all mail to one domain, to another. (http://www.mail-archive.com/vchkpw@inter7.com/msg03860.html) Is the correct syntax, smtproute, or smtproutes? And is it really as simple as just creating a file called smtproutes with originaldomain:domain-to-forward-to in it? If someone has some background info they could share, I would appreciate it. TIA Peter Brezny SysAdmin Services Inc.
Re: Help abot qmail and vpomail
If what you want is to send unmatched emails to a remote server, I have a patch to vpopmail to do this. http://jfns.net/qmail-stuff/drip.patch.fixed.README http://jfns.net/qmail-stuff/drip.patch.fixed.tar.gz Hope that helps... -Jav [EMAIL PROTECTED]
Re: Help abot qmail and vpomail
If what you want is to send unmatched emails to a remote server, I have a patch to vpopmail to do this. http://jfns.net/qmail-stuff/drip.patch.fixed.README http://jfns.net/qmail-stuff/drip.patch.fixed.tar.gz Hope that helps... -Jav [EMAIL PROTECTED]
Re: smtpd auth issue, FIXED, plz Read
ok, i feel like a bit of a dumb ass, my problem was not the same as the problem in the auth mailing list. see, i had been calling the patched qmail-smtpd as follows... qmail-smtpd /home/vpopmail/bin/vchkpw /usr/bin/true well, all this does is have an open relay use you used ANY auth since it thinks the domain is /home/vpopmail/bin/vchkpw and the password checker is /usr/bin/true... and of course we already know what true is going to say about every username password it's fed LOL... second, went i did call with with a domain as argument... qmail-smtpd test.com /home/vpopmail/bin/vchkpw /usr/bin/true i had just reinstalled everything ( I have a few scitpts and freebsd packages of qmail etc etc that reinstall in a few minutes ) i forgot to add the test account, so that acocunted for the missing username messages... right after my laptop committed suicide kamikaze style... well, after a quick look over , I realized my dumbness... the right way to call it with vpopmail, is , as you FAQ clearly states.. qmail-smtpd somedomain.com /home/vpopmail/bin/vchkpw /usr/bin/true the reason why i chose to call it without the domain. well, i had seen it on the mailing list. meaning, anyone that is calling it as qmail-smtpd /home/vpopmail/bin/vchkpw /usr/bin/true has got themselves an open relay. as long they input any sort of user/pass conbination. also, having it be called with a domain doesnot limit the athentication of vpopmail, youc an call qmail-smtpd with xyz.com and authenticate with blah.com. hope this helps someone, and thanks kris for a great patch :) Krzysztof Dabrowski writes: At 23:44 2001-04-25 +, you wrote: Anyone ever encountered this... using the latest version found here http://members.elysium.pl/brush/qmail-smtpd-auth/index.html and vpopmail 4.9.10 Ask on the apropriate mailing list (and check archives). this is a common problem (=misunderstanding of qmail's configuration). Kris
smtpd auth issue
Anyone ever encountered this... using the latest version found here http://members.elysium.pl/brush/qmail-smtpd-auth/index.html and vpopmail 4.9.10 and calling smtpd like this... #!/bin/sh PATH=/var/qmail/bin:/usr/local/bin:/usr/bin:/bin export PATH QMAILUID=`id -u vpopmail` NOFILESGID=`id -g vpopmail` MAXSMTPD=`cat /var/qmail/control/concurrencyincoming` exec softlimit -m 200 tcpserver -p -R -x ~vpopmail/etc/tcp.smtp.cdb -c $MAXSMTPD \ -u $QMAILUID -g $NOFILESGID 0 smtp rblsmtpd qmail-smtpd ~vpopmail/bin/vchkpw /usr/bin/true 21 smtp auth takes ANY username password combination... it still requires you to imput a password.. but it just lets anything thru anyone ever seen these? am i doing something wrong? -Jav [EMAIL PROTECTED]
Re: courier imap roaming
courier imap is supposed to pick this up automatically, but it doesn't so here's the fix, after your configure, cd courier-imap-1.3.7/authlib grep RELAY config.h make sure it says #define HAVE_OPEN_SMTP_RELAY 1 if it doesn't, well change it... :) Lu writes: Does --enable-roaming option for vpopmail covers courier imap as well ? Or do I have to use something like relay-ctrl package ? If the latter, does it interfere with the roaming functionality of vpopmail ? Thanks. Lu
Re: Domain directory deleted
yeah, it was a bug in the autoresponder code if I remember correctly. It allowed to create an autoresponder without a name, which had an adverse effect. when you tried to delete it, it would do a call do delete the autoresponder directory, which if your autoresponder name was empty.. well, the dir would be your domain dir. :( ( an autoresponder without a name is for having all mail to the domain reply with anautoresponder, which is kinda useless anywayz ) as far as i knew, this was fixed by me on .35 0.35 Aug 8 - fix autorespond problem. If you added an autoresponder with out filling in the name. Then deleted the autoresponder, it would delete the entire domain. it might have been introduced again in a dev version (althoug am not sure), but it seems fixed on .43 the lingering problem is that, although the newer versions don't allow empty autoresponder names.. they will still delete one. so if you had empty autoresponders, and upgraded to a newer version, you are still at risk. i would suggest seraching you domains for .qmail-default files with the autoresponderprogram in them, and fixing accordingly. well, hope this helps -Jav [EMAIL PROTECTED] Kris von Mach writes: At 11:03 PM 4/21/2001 -0300, you wrote: Hello there I don't know how, but one of my user has deleted his whole domain directory. I only know that this has been done with qmailadmin. It's a lie. qmailadmin doesn't do that, or ever are allowed for this. Next time try to explain better your mistake. Actually, this happened to me as well. I was running qmailadmin 0.42... I have lots of domains on my server... and about a week ago, I added some domain, I even created a custom .qmailadmin-limits file, so I know the directory was in fact there, and I did login as postmaster@domain, and tried qmailadmin to make sure it was all good... Over the night, the customer was playing with his new domain, setting up users and what else not, and welp in the morning the whole directory was deleted. I don't know what happened, this was the only time it has ever happened to me and it hasn't happened since. The only program that I can think of that would be able to delete the directories would be qmailadmin. And certainly I didn't delete it. I am still trying to find out what happened as I have no idea what did occur. And knowing this happened to someone else, at least lets me know that I am not going crazy. __ Kris.
Load Balancing questions...
When load balancing a qmail+vpopmail setup... any other directories/files
I should share across the frontend mail servers besides these:
(details: using cdb, netapp as the nfs storage, syncing with a cental time
server, running
pop3 and smtp on each front end server, and possible load balacning
qmailadmin)
/home/vpopmail/domains/
/home/vpopmail/etc/ { open-smtp, tcp.smtp, tcp.smtp.cdb }
/var/qmail/users/ { assign, cdb }
/var/qmail/control { evertyhign except me }
does this about cover it?
also, has anyone had any experience load balancing qmailadmin? any issues
with cdb
files getting corrupt ( chances of simultaneous access ? )
same question for sqwebmail... should anythign be shared for
sqwebmail/qmailadmin?
would a standard web imap client ( what am used to doing ) be better than
sqwebmail
in terms of load balancing safe?
thx for any pointers
Re: Load Balancing questions...
yes, well, what i will do is share ~vpopmail/etc/ but have wrappers on the vadd and vdel domain programs that when called, will populate ( scp over ) the pertenent files to the other mail servers... as for the access of the tcp.smtp.cdb being quite high, i will check, hopefully it woun't be too high, but as an option i could take on the future, i could use matt simmerson's hack to use mysql for the relay table Ben Beuchler writes: On Tue, Apr 17, 2001 at 10:10:17PM +, Javier Frias wrote: if local copies were kept of tcp.smtp.cdb? how were you doing smtp after pop/imap? since this file is needed for the open relay... and all front servers would be adding entries to it.. just wondering.. Ah. I am not doing smtp after pop. You will apparently need to share your tcp.smtp.cdb file and hope that NFS does good cacheing. since my domains don't change often, the control files would be easy to replicate :) I think that's good choice. Ben -- Ben Beuchler There is no spoon. [EMAIL PROTECTED]-- The Matrix
User postfix patch
i don't know how useful this patch would be for the general public... but hey, I need it, so there most be at least someone else with my odd requirements :) you can get it at http://jfns.net/qmail-stuff/postfix.domain.patch.tar.gz here's the description :-) This Patch adds the ability to have a username postfix on a specified domain. It works like this: ./configure --"options you normally use" --enable-user-postfix="postfix" \ --enable-user-postfix-domain="FQDN" then, when some one emails user "john@FQDN" he can also receive mail at "john.postfix@FQDN" and he can also authenticate as "john.postfix%FQDN". It will not affect affect any other domains besides the one specified at configure time. HOW-TO APPLY: cp postfix.domain.patch vpopmail-4.9.10/ cd vpopmail-4.9.10/ patch postfix.domain.patch -Javier Frias [EMAIL PROTECTED]
Mail Drip Patch
Hrmm, haven't roamed these ways for a while :) well, anywayz, i've been using a very useful hack that i had done a while back that allows mail to be "dripped down" to another smtp server. Think of it as a way to instead of having a default pop account, you can have a default pop server, int he spirit of the virtusertable of sendmail. instructions for compile are simple, i tested it extensively on vpopmail 4.9.8_1 but it does work on 4.9.9 basically, copy drip.patch to vpopmail source dir patch drip.patch rm configure autoconf and should see a new confiure option --enable-mail-drip=n|y Ability to make unmatched emails be routed to external mail server via qmail-remote. works by opening a .smtp-route file placed in domain home, and using first line as the external mail server., default is no so that;s all folks i have about two other internal patches that am gonna clean up and release, hopefully they will be included in base vpopmail. -Jav "Teach a man to make fire, and He'll be warm for a day. Set a man on fire, and He'll be warm for a lifetime."
Re: Mail Drip Patch
ok, as a dumb ass, i forget to include the patch hehe Javier Frias wrote: Hrmm, haven't roamed these ways for a while :) well, anywayz, i've been using a very useful hack that i had done a while back that allows mail to be "dripped down" to another smtp server. Think of it as a way to instead of having a default pop account, you can have a default pop server, int he spirit of the virtusertable of sendmail. instructions for compile are simple, i tested it extensively on vpopmail 4.9.8_1 but it does work on 4.9.9 basically, copy drip.patch to vpopmail source dir patch drip.patch rm configure autoconf and should see a new confiure option --enable-mail-drip=n|y Ability to make unmatched emails be routed to external mail server via qmail-remote. works by opening a .smtp-route file placed in domain home, and using first line as the external mail server., default is no so that;s all folks i have about two other internal patches that am gonna clean up and release, hopefully they will be included in base vpopmail. -Jav "Teach a man to make fire, and He'll be warm for a day. Set a man on fire, and He'll be warm for a lifetime." drip.patch.gz
