hi i think this gets created when you run rpm -Uvh qmail-toaster*.src.rpm
i download all the files using the old download script http://wiki.qmailtoaster.com/index.php/CentOS_5_QmailToaster_Install go to Download the QmailToaster Packages after installation the scripts deletes the packages by default but i keep them. rajesh > Actually, I just double checked my notes from when I setup the servers > and saw that while I did use cnt50-deps.sh and cnt50-svcs.sh, those are > for dependencies and services. > After I ran those, I ran `qtp-newmodel` which downloaded all of the > latest packages for me and set them up for me. > It seemed really nice at the time, didn't know I would need to manually > edit one of the files by hand to get what I needed. > > Did you download all of your packages directly from the QMT website or > did you go about it the same way I did? > With the way I did it, there was no qmail-toaster.spec and none of the > source files exist. I do have all of the RPMs though in > /usr/src/qtp-upgrade/RPMS. > > On 12/25/2012 2:45 PM, Josh Bowling wrote: >> Rajesh, >> >> Wow, thanks a lot! I'll try this out on my own local VM first and see >> how it goes. >> I guess you didn't use shell scripts that automatically download the >> latest version of QMT and install it since you have the RPMs >> themselves in qtms-install. >> I used the cnt50-deps.sh and cnt50-svcs.sh scripts, but I guess I >> guess my setup would be the same as yours if I had downloaded the RPMs >> manually. >> >> Thanks again! >> >> Josh >> >> On 12/25/2012 2:35 PM, Rajesh M wrote: >>> hi >>> >>> i was also nervous when i did it first -- >>> >>> but it is so easy that i have done atleast 10 - 12 times now and i am a >>> windows man with very less knowledge of linux. >>> >>> here are the exact steps for CENTOS -- please do this on your local >>> machine before you do it on your live server. >>> >>> THE BASIC IDEA BEHIND this >>> chkuser is turned on compulsorily by default which i dont like. the >>> option >>> to turn on or off chkuser and also the various checks in it should be >>> in >>> my hands. >>> >>> the main checks which create issues for my customers who authenticate >>> and >>> send out emails are listed below >>> >>> CHKUSER_ALWAYS_ON - enabled compulsorily in stock qmail toaster >>> CHKUSER_RCPT_MX >>> CHKUSER_RCPT_FORMAT >>> CHKUSER_SENDER_FORMAT >>> CHKUSER_SENDER_MX >>> >>> ################################################# >>> >>> before you start >>> >>> keep a copy of smtp/run file. if you use spamdyke then the spamdyke >>> configuration details will be in this file. after your follow the >>> procedure below the smtp/run file is over-written. >>> >>> To tailor your chkuser settings, use the following procedure >>> >>> OPEN TWO WINDOWS OF VIA SSH CLIENT TO YOR MACHINE >>> >>> cd /usr/src/qtms-install >>> >>> # rpm -Uvh qmail-toaster*.src.rpm >>> >>> # cd /usr/src/redhat/SPECS >>> >>> edit qmail-toaster.spec. find 'sleep 5'. Change 5 to >>> 300 (5 seconds to 300 seconds). save. >>> >>> # rpmbuild -bb --with cnt50 qmail-toaster.spec >>> >>> (use the appropriate --with value for your distro) >>> >>> THE PROCESS WILL PAUSE >>> >>> When the build process pauses, go to the other terminal window and edit >>> /usr/src/redhat/BUILD/qmail-1.03/chkuser_settings.h to your liking. >>> You have >>> 5 minutes (or whatever you changed the sleep parameter to). Save your >>> changes and wait for the 300 seconds to expire and watch it build. >>> >>> Search for the items below and change / COMMENT THEM >>> >>> CHKUSER_ALWAYS_ON >>> CHKUSER_RCPT_MX >>> CHKUSER_RCPT_FORMAT >>> CHKUSER_SENDER_FORMAT >>> CHKUSER_SENDER_MX >>> >>> >>> After Change : >>> >>> /* #define CHKUSER_RCPT_MX */ >>> /* #define CHKUSER_ALWAYS_ON */ >>> /* #define CHKUSER_RCPT_FORMAT */ >>> /* #define CHKUSER_SENDER_FORMAT */ >>> /* #define CHKUSER_SENDER_MX */ >>> >>> Then save the file and let the rpm rebuild AFTER 300 SECONDS ARE >>> COMPLETED >>> >>> # cd ../RPMS/i386/ >>> >>> >>> STOP QMAIL NOW >>> >>> # qmailctl stop >>> >>> # rpm -Uvh --replacefiles --replacepkgs qmail-*.rpm >>> >>> open the smtp/run file and chk it. modify it correctly with the >>> original >>> settings. >>> >>> # qmailctl start >>> >>> test that your email services are working correctly by sending >>> receiving >>> to external hotmail / gmail accounts. >>> >>> ######################################################### >>> >>> rajesh >>> >>> >>>> Rajesh, >>>> >>>> I actually have been following that thread a bit as it did seemed to >>>> relate to my problem. I am using the stock QmailToaster, but I guess >>>> I >>>> could modify the qmail-toaster rpm and reinstall? >>>> >>>> I come from a Debian background and am pretty to new RPM package >>>> management. If I was to reinstall the qmail-toaster RPM after >>>> modifying >>>> it, would I just run it with `rpm -Uvh --replacefiles --replacepkgs >>>> qmail-toaster.rpm`? I think I just need to comment out #define >>>> CHKUSER_RCPT_MX and rebuild, but rebuilding and reinstalling >>>> QmailToaster makes me nervous. >>>> >>>> Am I going in the right direction? Any guides for this? >>>> >>>> Thanks again, >>>> >>>> Josh >>>> >>>> On 12/25/2012 11:32 AM, Josh Bowling wrote: >>>>> Rajesh, >>>>> >>>>> We are using 587 for SMTP. Only authenticated users can send as well >>>>> (don't want to become a SPAM server). Does the port number have >>>>> something to do with it? Not sure what the connection is? >>>>> >>>>> Thanks, >>>>> >>>>> Josh >>>>> >>>>> On 12/25/2012 11:28 AM, Rajesh M wrote: >>>>>> josh >>>>>> >>>>>> we faced similar issues and were able to solve the same. our >>>>>> customers >>>>>> used port 587 ie submission port for sending out emails. >>>>>> >>>>>> are your users are using submission port ie port 587 for sending out >>>>>> emails ? >>>>>> >>>>>> rajesh >>>>>> >>>>>> >>>>>> >>>>>>> I recently switched out my companies FreeBSD + Qmail/Vpopmail setup >>>>>>> with >>>>>>> a CentOS + QmailToaster setup and it has worked as expected except >>>>>>> for a >>>>>>> single problem that keeps coming up: invalid rcpt MX domain. When >>>>>>> I do >>>>>>> a manual MX dig command on these domains they in fact do not have >>>>>>> proper >>>>>>> MX records setup, but our customers have always been able to send >>>>>>> to >>>>>>> these domains in the past when we were using vanilla >>>>>>> Qmail/Vpopmail on >>>>>>> FreeBSD. Is there any workaround or fix so our servers will >>>>>>> attempt to >>>>>>> send an email even if the domain doesn't have MX records? >>>>>>> >>>>>>> Thanks in advance. >>>>>>> >>>>>>> --------------------------------------------------------------------- >>>>>>> >>>>>>> To unsubscribe, e-mail: >>>>>>> [email protected] >>>>>>> For additional commands, e-mail: >>>>>>> [email protected] >>>>>>> >>>>>>> >>>>>> >>>>>> >>>>>> >>>>>> >>>>>> --------------------------------------------------------------------- >>>>>> To unsubscribe, e-mail: >>>>>> [email protected] >>>>>> For additional commands, e-mail: >>>>>> [email protected] >>>>>> >>>>> >>>>> --------------------------------------------------------------------- >>>>> To unsubscribe, e-mail: >>>>> [email protected] >>>>> For additional commands, e-mail: >>>>> [email protected] >>>>> >>>> >>>> --------------------------------------------------------------------- >>>> To unsubscribe, e-mail: [email protected] >>>> For additional commands, e-mail: >>>> [email protected] >>>> >>>> >>> >>> >>> >>> >>> >>> --------------------------------------------------------------------- >>> To unsubscribe, e-mail: [email protected] >>> For additional commands, e-mail: >>> [email protected] >>> >> >> >> --------------------------------------------------------------------- >> To unsubscribe, e-mail: [email protected] >> For additional commands, e-mail: [email protected] >> > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [email protected] > For additional commands, e-mail: [email protected] > > --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
