[qmailtoaster] Cannot send email using squiremail and MS-Outlook
I finished my Qmailtoaster installation on CentOS 5.2 x64 bit using Mr. ERIC SCHWARTZ manual on http://wiki.qmailtoaster.com/index.php/CentOS_5_QmailToaster_Install, i can login using my account but when i tried to send email using squiremail webmail i got this : ERROR : Message not set. Server Replied: . And i tried to connet to mail server using Ms-Outlook for Pop3 mail service and i got these : [ V ] Establish network connection Completed [ V ] Find outgoing mail server [SMTP] Completed [ V ] Find incoming mail server [POP3] Completed [ X ] Log onto incoming mail server [POP3] Failed [ X ] Send test email messageFailed and the error message : *Send test e-mail message : The specified was not found, but there was no reponse from the server. Please verify that the port and SSL information is correct. *Log into incoming mail server (POP3) : Outlook could not connect to the incoming POP3 mail server because the server did not accept your username or password. For your info that i already ran the qmailctl stat and i got no error and i think everything is up: autlib: up (pid 2512) 566 seconds clamd: up (pid 2505) 566 seconds imap4: up (pid 2501) 566 seconds imap4-ssl: up (pid 2509) 566 seconds pop3: up (pid 2515) 566 seconds pop3-ssl: up (pid 2516) 566 seconds send: up (pid 2514) 566 seconds smtp: up (pid 2507) 566 seconds spamd: up submission: up and so on ... Please help me.
Re: [qmailtoaster] simscan problem
daily.cld mirrors.dat MSRBL-Images.hdb-bak MSRBL-SPAM.ndb-bak main.cld MSRBL-Images.hdb MSRBL-SPAM.ndbphish.ndb.gz On Wed, 2009-03-25 at 09:16 -0400, Jake Vickers wrote: > Dan Page wrote: > > My toaster was working fine but as of lately it seems simscan is not > > running clamav or spamassassin on incoming mail. running > > /var/qmail/bin/simscanmk -g > > produces: > > LibClamAV Error: cl_cvdhead: Can't open file /usr/share/clamav/main.cvd > > LibClamAV Error: cl_cvdhead: Can't open file /usr/share/clamav/daily.cvd > > simscan versions cdb file built. /var/qmail/control/simversions.cdb > > > > What files do you have in the /usr/share/clamav directory? .cld files? > > - > Managed Qmailtoaster servers are now available >Visit http://qmailtoaster.com/QMTManaged.html to order yours today! > > Qmailtoaster is sponsored by Vickers Consulting Group > (www.vickersconsulting.com) > > Please visit qmailtoaster.com for the latest news, updates, and packages. > > > To unsubscribe, e-mail: testing-unsubscr...@qmailtoaster.com > For additional commands, e-mail: testing-h...@qmailtoaster.com > > - Managed Qmailtoaster servers are now available Visit http://qmailtoaster.com/QMTManaged.html to order yours today! Qmailtoaster is sponsored by Vickers Consulting Group (www.vickersconsulting.com) Please visit qmailtoaster.com for the latest news, updates, and packages. To unsubscribe, e-mail: testing-unsubscr...@qmailtoaster.com For additional commands, e-mail: testing-h...@qmailtoaster.com
Re: [qmailtoaster] simscan problem
Dan Page wrote: My toaster was working fine but as of lately it seems simscan is not running clamav or spamassassin on incoming mail. running /var/qmail/bin/simscanmk -g produces: LibClamAV Error: cl_cvdhead: Can't open file /usr/share/clamav/main.cvd LibClamAV Error: cl_cvdhead: Can't open file /usr/share/clamav/daily.cvd simscan versions cdb file built. /var/qmail/control/simversions.cdb What files do you have in the /usr/share/clamav directory? .cld files? - Managed Qmailtoaster servers are now available Visit http://qmailtoaster.com/QMTManaged.html to order yours today! Qmailtoaster is sponsored by Vickers Consulting Group (www.vickersconsulting.com) Please visit qmailtoaster.com for the latest news, updates, and packages. To unsubscribe, e-mail: testing-unsubscr...@qmailtoaster.com For additional commands, e-mail: testing-h...@qmailtoaster.com
Re: [qmailtoaster] simscan problem
Steve Huff wrote: this sounds a lot like the problem i saw a while back around the release of clamav-toaster-0.93. are you running freshclam to get clamav database updates? if so, you may need a patched version of simscan that knows how to read the updates in the new format. Hmm. I haven't run into this problem myself. Looking at the patch in the current version of simscan-toaster (1.3.1) the date is 1-11-2007 so I think it may be a good idea to freshen up the patch to something a little more current. I'll attempt to patch the current version this week and see if it builds correctly. I'll need a couple volunteers to test the package out though. Steve, I'll look at your simscan RPM once the new version of QMT is out (or at least in testing). At this point in time I am continuing Erik's policy on freezing development on the 1.3 branch of QMT. I do not want to add new versions/features to something that currently works as this has the potential to slow the progress on the 2.0 branch of QMT if an issue arises. Thanks. - Managed Qmailtoaster servers are now available Visit http://qmailtoaster.com/QMTManaged.html to order yours today! Qmailtoaster is sponsored by Vickers Consulting Group (www.vickersconsulting.com) Please visit qmailtoaster.com for the latest news, updates, and packages. To unsubscribe, e-mail: testing-unsubscr...@qmailtoaster.com For additional commands, e-mail: testing-h...@qmailtoaster.com
Re: [qmailtoaster] perl-Getopt-Long conflict with qtp-newmodel
Steve Huff wrote: 2) qtp-newmodel uses RPM package names (following the rpmforge naming convention) to model Perl dependencies; a better way is to use RPM's own Perl-specific dependency format, e.g. 'perl(LWP::UserAgent)' instead of 'perl-LWP-UserAgent'. this enables yum to be more flexible about dependency solving and not try to install a third-party package which will conflict with an existing core package. attached is a patch to qtp-newmodel which makes the appropriate changes; i just did a cursory test on my own system, and it seems to work OK. Jake, please consider merging it for a future release? FYI, if QmailToaster needs specific versions of Perl modules, RPM's Perl dependency syntax supports that as well, e.g. 'perl(LWP::UserAgent) >= 5.805' instead of 'perl(LWP::UserAgent)'. so, to sum up: Thomas, please configure the priorities plugin to protect your core packages from being clobbered. Jake, please modify qtp-newmodel so that it doesn't needlessly try to clobber core packages. :) Steve, please open a ticket for this on qtp.qmailtoaster.com. I do not maintain the qtp-newmodel script personally but if you open a ticket (including the patch) then it will at least be on our "work sheet" when we get ready for the next release. I try and clean up as many bugs as I'm aware of before cutting a new release so if this is not fixed by the time I cut a new release I will see it on the ticket report and will remember to do something about it if no one else does it first. Thanks. - Managed Qmailtoaster servers are now available Visit http://qmailtoaster.com/QMTManaged.html to order yours today! Qmailtoaster is sponsored by Vickers Consulting Group (www.vickersconsulting.com) Please visit qmailtoaster.com for the latest news, updates, and packages. To unsubscribe, e-mail: testing-unsubscr...@qmailtoaster.com For additional commands, e-mail: testing-h...@qmailtoaster.com
Re: [qmailtoaster] Maximum no user in Empf Policy file
Hi, I changed from 1024 to 4096 in policy.c and it is working fine for me. Thanks for your support. Regards, S.Sivakumar. On Tue, Mar 24, 2009 at 9:14 PM, A M wrote: > 2009/3/24 siva kumar : > > Hi All, > > > > i added 42 users and their policy in /var/qmail/control/policy file. it > was > > working fine without any problem. > > > > if i add one more user called test43 in policy file, no user unable to > send > > mail any one ( even local domain also). > > > > Is there is any limit is there to add policy file. > > > > > > my policy file > > > > abc.com: > LreI,test1:RE,test2:RE,test3:RE,test4:RE,test5:RE,test6:RE,test7:RE,test8:RE,test9:RE,test10:RE,test11:RE,test12:RE,test13:RE,test14:RE,test15:RE,test16:RE,test17:RE,test18:RE,test19:RE,test20:RE,test21:RE(*@ > gmail.com),test22:RE(*...@gmail.com),test23:RE(*...@gmail.com),test24:RE(*@ > gmail.com),test25:RE(*...@gmail.com),test26:RE(*...@gmail.com),test27:RE(*@ > gmail.com),test28:RE(*...@gmail.com),test29:RE(*...@gmail.com),test30:RE(*@ > gmail.com),test31:RE(*...@gmail.com),test32:RE(*...@gmail.com),test33:RE(*@ > gmail.com),test34:RE(*...@gmail.com),test35:RE(*...@gmail.com),test36:RE(*@ > gmail.com),test37:RE(*...@gmail.com),test38:RE(*...@gmail.com),test39:RE(*@ > gmail.com),test40:RE(*...@gmail.com),test41:RE(*...@gmail.com),test42:RE(*@ > gmail.com), > > > > Thanks, > > S.Sivakumar. > > > > Hi, > > As I recall the default should be 1024, as defined in policy.c > policy_load function - I think. > > This limit can be altered. I think the highest I used was about 20 > times that. To change the limit you'll have to recompile the package > after altering it in policy.c. > > In anyway you should get a "policy broken" message in the logs if your > policy line exceeds the defined limit. > > > > -- > AM > agmsoft(at)gmail.com > > > - > Managed Qmailtoaster servers are now available > Visit http://qmailtoaster.com/QMTManaged.html to order yours today! > > Qmailtoaster is sponsored by Vickers Consulting Group ( > www.vickersconsulting.com) > > Please visit qmailtoaster.com for the latest news, updates, and > packages. > > > To unsubscribe, e-mail: testing-unsubscr...@qmailtoaster.com > For additional commands, e-mail: testing-h...@qmailtoaster.com > > >
