Re: [qmailtoaster] Re: Error while sending mail
not trying to hijack a thread - but in regards to: ...Outlook is riddled with other problems I'd rather not get into I would be interested in knowing more regarding outlook and problems.. love to know more - just curious - thanks! Eric Shubert wrote: Amit, There's a difference between an immediate error and a bounce. I think what you have here is a failure to submit (immediate error), not a bounce. A bounce would be a message that has been successfully submitted, but failed to be delivered within a certain time period. This is an interesting dilemma. The first thought that came to my mind was that if they used MS Outlook, they wouldn't have this problem, since Outlook has its own mail queue. That's not really a good thing imo, and don't recommend it as a solution. Outlook is riddled with other problems I'd rather not get into. Your real problem here is internet availability. Solve that, and this problem goes away with it. You should have a caching nameserver (resolver) on your QMT. If you don't, install the caching-nameserver package (CentOS) and set your resolv.conf file accordingly (nameserver 127.0.0.1). This will cache domain names, so if someone sends to a domain that was looked up recently, they wouldn't get this error. I expect this might help a little, but not entirely. Unfortunately, there doesn't appear to be a way to disable this check in the tcp.smtp file. Hey Tonino (the chkuser author sometimes lurks here), am I right on this? Do you have a suggestion? I was thinking that perhaps chkuser shouldn't return an error on 4xx conditions, only 5xx conditions. What yo you think? If Tonino doesn't see this, you might want to contact him on the vpopmail users list.
Re: [qmailtoaster] Re: Error while sending mail
Hi Jim, This will help you up. http://wiki.qmailtoaster.com/index.php/Outlook_problems_and_possible_solutions Regards, Amit At Monday, 28-06-2010 on 19:12 Jim Shupert wrote: not trying to hijack a thread - but in regards to: ...Outlook is riddled with other problems I'd rather not get into I would be interested in knowing more regarding outlook and problems.. love to know more - just curious - thanks! Eric Shubert wrote: Amit, There's a difference between an immediate error and a bounce. I think what you have here is a failure to submit (immediate error), not a bounce. A bounce would be a message that has been successfully submitted, but failed to be delivered within a certain time period. This is an interesting dilemma. The first thought that came to my mind was that if they used MS Outlook, they wouldn't have this problem, since Outlook has its own mail queue. That's not really a good thing imo, and don't recommend it as a solution. Outlook is riddled with other problems I'd rather not get into. Your real problem here is internet availability. Solve that, and this problem goes away with it. You should have a caching nameserver (resolver) on your QMT. If you don't, install the caching-nameserver package (CentOS) and set your resolv.conf file accordingly (nameserver 127.0.0.1). This will cache domain names, so if someone sends to a domain that was looked up recently, they wouldn't get this error. I expect this might help a little, but not entirely. Unfortunately, there doesn't appear to be a way to disable this check in the tcp.smtp file. Hey Tonino (the chkuser author sometimes lurks here), am I right on this? Do you have a suggestion? I was thinking that perhaps chkuser shouldn't return an error on 4xx conditions, only 5xx conditions. What yo you think? If Tonino doesn't see this, you might want to contact him on the vpopmail users list.
Re: [qmailtoaster] Re: Error while sending mail
I don't know how large your network is so adding an entry in the hosts file may not be an option, but if it's not too much trouble that is certainly a partial solution if domain/ip's that are being accessed don't change that frequently. It has some limitations, but if it's all local intranet it won't be an issue. On 06/25/2010 09:49 AM, Eric Shubert wrote: Amit, There's a difference between an immediate error and a bounce. I think what you have here is a failure to submit (immediate error), not a bounce. A bounce would be a message that has been successfully submitted, but failed to be delivered within a certain time period. This is an interesting dilemma. The first thought that came to my mind was that if they used MS Outlook, they wouldn't have this problem, since Outlook has its own mail queue. That's not really a good thing imo, and don't recommend it as a solution. Outlook is riddled with other problems I'd rather not get into. Your real problem here is internet availability. Solve that, and this problem goes away with it. You should have a caching nameserver (resolver) on your QMT. If you don't, install the caching-nameserver package (CentOS) and set your resolv.conf file accordingly (nameserver 127.0.0.1). This will cache domain names, so if someone sends to a domain that was looked up recently, they wouldn't get this error. I expect this might help a little, but not entirely. Unfortunately, there doesn't appear to be a way to disable this check in the tcp.smtp file. Hey Tonino (the chkuser author sometimes lurks here), am I right on this? Do you have a suggestion? I was thinking that perhaps chkuser shouldn't return an error on 4xx conditions, only 5xx conditions. What yo you think? If Tonino doesn't see this, you might want to contact him on the vpopmail users list. -- Cecil Yother, Jr. cj cj's 2318 Clement Ave Alameda, CA 94501 tel 510.865.2787 | fax 510.864.7300 http://yother.com - Qmailtoaster is sponsored by Vickers Consulting Group (www.vickersconsulting.com) Vickers Consulting Group offers Qmailtoaster support and installations. If you need professional help with your setup, contact them today! - Please visit qmailtoaster.com for the latest news, updates, and packages. To unsubscribe, e-mail: qmailtoaster-list-unsubscr...@qmailtoaster.com For additional commands, e-mail: qmailtoaster-list-h...@qmailtoaster.com
Re: [qmailtoaster] Re: Error while sending mail
Of course the caching-nameserver is the best way, but under certain circumstances I have used the host file successfully for testing. This however was for web not mail services. On 06/25/2010 10:49 AM, Eric Shubert wrote: I don't believe the hosts file will be of any help. There are 2 different ways of resolving names. I don't recall the details, but IIRC one includes the hosts file and the other doesn't. I expect that chkuser uses the one that doesn't include hosts, and even if chkuser used the method that includes the hosts file, it would fail obtaining the MX record for the domain. I'm curious to know, Amit, do you have a caching-nameserver on your host, and do you have nameserver 127.0.0.1 listed first in your resolv.conf file? -- Cecil Yother, Jr. cj cj's 2318 Clement Ave Alameda, CA 94501 tel 510.865.2787 | fax 510.864.7300 http://yother.com - Qmailtoaster is sponsored by Vickers Consulting Group (www.vickersconsulting.com) Vickers Consulting Group offers Qmailtoaster support and installations. If you need professional help with your setup, contact them today! - Please visit qmailtoaster.com for the latest news, updates, and packages. To unsubscribe, e-mail: qmailtoaster-list-unsubscr...@qmailtoaster.com For additional commands, e-mail: qmailtoaster-list-h...@qmailtoaster.com
Re: [qmailtoaster] Re: Error in Sending Mail
Could this have something to do with RPM not recognizing something installed via Perl? Did you use Perl to install something? It may be better to use the RPMforge. I may be way off track See response above; Eric Shubert wrote: I don't see any problem with the --lint diag output. I also don't understand how perl-XML-SAX comes into play. What do you get when you try to remove it? # rpm -e perl-XML-SAX I expect that if it's not there then, as Steve said, some other XML parser will be used if/when necessary. -- -Eric 'shubes' Amit Dalia wrote: Hi Eric, If you see error below ould not find ParserDetails.ini in /usr/lib/perl5/vendor_perl/5.8.8/XML/SAX ZSorry, I wasn't able to establish an SMTP connection. (#4.4.1) I'm unable to understand how perl-XML-SAX is related to SMTP connection. Is this somewhere related to SMARTHOST? Regards, Amit At Wednesday, 28-04-2010 on 10:33 Amit Dalia wrote: Hi Eric, Please find output of the command you mentioned below: [r...@mail ~]# sudo -u vpopmail -H spamassassin -D --lint 21 | grep diag: [18621] dbg: diag: perl platform: 5.008008 linux [18621] dbg: diag: module installed: Digest::SHA1, version 2.12 [18621] dbg: diag: module installed: HTML::Parser, version 3.64 [18621] dbg: diag: module installed: Net::DNS, version 0.66 [18621] dbg: diag: module installed: MIME::Base64, version 3.07 [18621] dbg: diag: module installed: DB_File, version 1.814 [18621] dbg: diag: module installed: Net::SMTP, version 2.31 [18621] dbg: diag: module installed: Mail::SPF, version v2.006 [18621] dbg: diag: module installed: Mail::SPF::Query, version 1.999001 [18621] dbg: diag: module installed: IP::Country::Fast, version 604.001 [18621] dbg: diag: module installed: Razor2::Client::Agent, version 2.84 [18621] dbg: diag: module installed: Net::Ident, version 1.20 [18621] dbg: diag: module installed: IO::Socket::INET6, version 2.57 [18621] dbg: diag: module installed: IO::Socket::SSL, version 1.31 [18621] dbg: diag: module installed: Compress::Zlib, version 2.024 [18621] dbg: diag: module installed: Time::HiRes, version 1.9717 [18621] dbg: diag: module installed: Mail::DomainKeys, version 1.0 [18621] dbg: diag: module installed: Mail::DKIM, version 0.37 [18621] dbg: diag: module installed: DBI, version 1.609 [18621] dbg: diag: module installed: Getopt::Long, version 2.35 [18621] dbg: diag: module installed: LWP::UserAgent, version 2.033 [18621] dbg: diag: module installed: HTTP::Date, version 1.47 [18621] dbg: diag: module installed: Archive::Tar, version 1.56 [18621] dbg: diag: module installed: IO::Zlib, version 1.10 [18621] dbg: diag: module installed: Encode::Detect, version 1.01 Regards, Amit At Wednesday, 28-04-2010 on 10:03 Eric Shubert wrote: Hey Amit, I'm particularly interested in the --lint output which lists diag:, so I guess you could do: # sudo -u vpopmail -H spamassassin -D --lint 21 | grep diag: That will show if modules that are used, and if any are missing. From what Steve said though, I'm not sure it will show what all is missing with XML/SAX. The stock QMT does not use LDAP of any kind (that I'm aware of, and I'm pretty sure about that). FWIW, I hope to introduce an LDAP option (in place of MySQL) once vpopmail 5.5 is fully available. I don't know of an estimated target date for that, but I expect it will be at least several months from now. I'll be happy if we see it by the end of this year. -- -Eric 'shubes' Amit Dalia wrote: Dear Eric/Steve, Sorry I agree I should google first. Eric: Please find output of command sudo -u vpopmail -H spamassassin -D --lint below: [14326] dbg: rules: compiled meta tests [14326] dbg: check: running tests for priority: 1000 [14326] dbg: rules: running head tests; score so far=4.205 [14326] dbg: rules: compiled head tests [14326] dbg: rules: running body tests; score so far=4.205 [14326] dbg: rules: compiled body tests [14326] dbg: rules: running uri tests; score so far=4.205 [14326] dbg: rules: compiled uri tests [14326] dbg: rules: running rawbody tests; score so far=4.205 [14326] dbg: rules: compiled rawbody tests [14326] dbg: rules: running full tests; score so far=4.205 [14326] dbg: rules: compiled full tests [14326] dbg: rules: running meta tests; score so far=4.205 [14326] dbg: rules: compiled meta tests [14326] dbg: check: is spam? score=4.205 required=5 [14326] dbg: check:
Re: [qmailtoaster] Re: Error in Sending Mail
Hi Eric/ Kent, Kent: I had installed this module from RPMforge only. Eric: Please find output of command below: [r...@mail ~]# rpm -e perl-XML-SAX error: Failed dependencies: perl(XML::SAX::Base) is needed by (installed) perl-LDAP-0.33-3.fc6.noarch Regards, Amit At Wednesday, 28-04-2010 on 21:32 Kent Busbee wrote: Could this have something to do with RPM not recognizing something installed via Perl? Did you use Perl to install something? It may be better to use the RPMforge. I may be way off track See response above; Eric Shubert wrote: I don't see any problem with the --lint diag output. I also don't understand how perl-XML-SAX comes into play. What do you get when you try to remove it? # rpm -e perl-XML-SAX I expect that if it's not there then, as Steve said, some other XML parser will be used if/when necessary. -- -Eric 'shubes' Amit Dalia wrote: Hi Eric, If you see error below ould not find ParserDetails.ini in /usr/lib/perl5/vendor_perl/5.8.8/XML/SAX ZSorry, I wasn't able to establish an SMTP connection. (#4.4.1) I'm unable to understand how perl-XML-SAX is related to SMTP connection. Is this somewhere related to SMARTHOST? Regards, Amit At Wednesday, 28-04-2010 on 10:33 Amit Dalia wrote: Hi Eric, Please find output of the command you mentioned below: [r...@mail ~]# sudo -u vpopmail -H spamassassin -D --lint 21 | grep diag: [18621] dbg: diag: perl platform: 5.008008 linux [18621] dbg: diag: module installed: Digest::SHA1, version 2.12 [18621] dbg: diag: module installed: HTML::Parser, version 3.64 [18621] dbg: diag: module installed: Net::DNS, version 0.66 [18621] dbg: diag: module installed: MIME::Base64, version 3.07 [18621] dbg: diag: module installed: DB_File, version 1.814 [18621] dbg: diag: module installed: Net::SMTP, version 2.31 [18621] dbg: diag: module installed: Mail::SPF, version v2.006 [18621] dbg: diag: module installed: Mail::SPF::Query, version 1.999001 [18621] dbg: diag: module installed: IP::Country::Fast, version 604.001 [18621] dbg: diag: module installed: Razor2::Client::Agent, version 2.84 [18621] dbg: diag: module installed: Net::Ident, version 1.20 [18621] dbg: diag: module installed: IO::Socket::INET6, version 2.57 [18621] dbg: diag: module installed: IO::Socket::SSL, version 1.31 [18621] dbg: diag: module installed: Compress::Zlib, version 2.024 [18621] dbg: diag: module installed: Time::HiRes, version 1.9717 [18621] dbg: diag: module installed: Mail::DomainKeys, version 1.0 [18621] dbg: diag: module installed: Mail::DKIM, version 0.37 [18621] dbg: diag: module installed: DBI, version 1.609 [18621] dbg: diag: module installed: Getopt::Long, version 2.35 [18621] dbg: diag: module installed: LWP::UserAgent, version 2.033 [18621] dbg: diag: module installed: HTTP::Date, version 1.47 [18621] dbg: diag: module installed: Archive::Tar, version 1.56 [18621] dbg: diag: module installed: IO::Zlib, version 1.10 [18621] dbg: diag: module installed: Encode::Detect, version 1.01 Regards, Amit At Wednesday, 28-04-2010 on 10:03 Eric Shubert wrote: Hey Amit, I'm particularly interested in the --lint output which lists diag:, so I guess you could do: # sudo -u vpopmail -H spamassassin -D --lint 21 | grep diag: That will show if modules that are used, and if any are missing. From what Steve said though, I'm not sure it will show what all is missing with XML/SAX. The stock QMT does not use LDAP of any kind (that I'm aware of, and I'm pretty sure about that). FWIW, I hope to introduce an LDAP option (in place of MySQL) once vpopmail 5.5 is fully available. I don't know of an estimated target date for that, but I expect it will be at least several months from now. I'll be happy if we see it by the end of this year. -- -Eric 'shubes' Amit Dalia wrote: Dear Eric/Steve, Sorry I agree I should google first. Eric: Please find output of command sudo -u vpopmail -H spamassassin -D --lint below: [14326] dbg: rules: compiled meta tests [14326] dbg: check: running tests for priority: 1000 [14326] dbg: rules: running head tests; score so far=4.205 [14326] dbg: rules: compiled head tests [14326] dbg: rules: running body tests; score so far=4.205 [14326] dbg: rules: compiled body tests [14326] dbg: rules: running uri tests; score so far=4.205 [14326] dbg: rules: compiled uri tests [14326] dbg: rules: running rawbody tests; score so far=4.205 [14326] dbg: rules: compiled rawbody tests [14326] dbg: rules: running full tests; score so far=4.205 [14326] dbg: rules: compiled full tests [14326] dbg: rules: running meta tests; score so far=4.205 [14326] dbg: rules: compiled meta tests [14326] dbg: check: is spam? score=4.205 required=5 [14326] dbg: check: tests=MISSING_DATE,MISSING_HEADERS,MISSING_SUBJECT,NO_RECEIVED,NO_RELAYS [14326] dbg: check:
Re: [qmailtoaster] Re: Error in Sending Mail
On Apr 27, 2010, at 12:41 PM, Eric Shubert wrote: I've no idea why you would need XML/SAX/. Is there a rule that uses it that's not part of the stock QMT? How are you installing XML/SAX? I would use the rpmforge repo instead of CPAN, but that doesn't really explain why you would need it to begin with. the error Amit is encountering is so common that it is an entry in the Perl-XML FAQ: http://perl-xml.sourceforge.net/faq/#parserdetails.ini there are tons of Perl programs that want to use XML::SAX; i would hesitate to conjecture which one is involved here. -steve -- If this were played upon a stage now, I could condemn it as an improbable fiction. - Fabian, Twelfth Night, III,v http://five.sentenc.es PGP.sig Description: This is a digitally signed message part
Re: [qmailtoaster] Re: Error in Sending Mail
On Apr 27, 2010, at 2:18 PM, Eric Shubert wrote: Perhaps there's another XML parser that is used if XML::SAX doesn't exist? I can only speculate. I expect that there are others on the list that know better than I do about this. it's the other way around; that error message indicates that XML::SAX is falling back to its built-in pure-Perl parser, and the fix is to install a better one (or to take action that indicates to XML::SAX that yes, you really do want it to use the pure-Perl parser). it's all in the FAQ. -shuff -- If this were played upon a stage now, I could condemn it as an improbable fiction. - Fabian, Twelfth Night, III,v http://five.sentenc.es PGP.sig Description: This is a digitally signed message part
RE: [qmailtoaster] Re: Error in Sending Mail
Hi Amit/Eric This is true that the spamassassin uses perl but why It needs ParserDetails.ini is not known, may just to make sure that all XML Parser modules are install and upto-date. When we do rpm install of XML-SAX this ParserDetails.ini file doesn’t gets created as it requires manual compilation and installation of the SAX and XML Parser modules, that’s what I have read few days back when I was updating my server and I faced the similar problem with qmail send. So I simply downloaded an ParserDetails.ini and placed in the perl SAX folder and every thing works fine now. Please find the ParserDetails.ini file attached with this mail. Place it in the /usr/lib/perl5/vendor_perl/5.8.8/XML/SAX And everything should work now. Regards, Anil Aliyan -Original Message- From: Eric Shubert [mailto:e...@shubes.net] Sent: Wednesday, April 28, 2010 10:03 AM To: qmailtoaster-list@qmailtoaster.com Subject: [qmailtoaster] Re: Error in Sending Mail Hey Amit, I'm particularly interested in the --lint output which lists diag:, so I guess you could do: # sudo -u vpopmail -H spamassassin -D --lint 21 | grep diag: That will show if modules that are used, and if any are missing. From what Steve said though, I'm not sure it will show what all is missing with XML/SAX. The stock QMT does not use LDAP of any kind (that I'm aware of, and I'm pretty sure about that). FWIW, I hope to introduce an LDAP option (in place of MySQL) once vpopmail 5.5 is fully available. I don't know of an estimated target date for that, but I expect it will be at least several months from now. I'll be happy if we see it by the end of this year. -- -Eric 'shubes' Amit Dalia wrote: Dear Eric/Steve, Sorry I agree I should google first. Eric: Please find output of command sudo -u vpopmail -H spamassassin -D --lint below: [14326] dbg: rules: compiled meta tests [14326] dbg: check: running tests for priority: 1000 [14326] dbg: rules: running head tests; score so far=4.205 [14326] dbg: rules: compiled head tests [14326] dbg: rules: running body tests; score so far=4.205 [14326] dbg: rules: compiled body tests [14326] dbg: rules: running uri tests; score so far=4.205 [14326] dbg: rules: compiled uri tests [14326] dbg: rules: running rawbody tests; score so far=4.205 [14326] dbg: rules: compiled rawbody tests [14326] dbg: rules: running full tests; score so far=4.205 [14326] dbg: rules: compiled full tests [14326] dbg: rules: running meta tests; score so far=4.205 [14326] dbg: rules: compiled meta tests [14326] dbg: check: is spam? score=4.205 required=5 [14326] dbg: check: tests=MISSING_DATE,MISSING_HEADERS,MISSING_SUBJECT,NO_RECEIVED,NO_RELAYS [14326] dbg: check: subtests=__HAS_MSGID,__MISSING_REF,__MSGID_OK_DIGITS,__MSGID_OK_HOST,__MSOE_MID_WRONG_CASE,__NONEMPTY_BODY,__SANE_MSGID,__SARE_WHITELIST_FLAG,__TVD_BODY,__UNUSABLE_MSGID There was lot more but I thought to post last few line, if require will post complete output. Also I found that perl-LDAP module depands on perl-XML-SAX. Does QMT perl-LDAP module(I don't think so)? Regards, Amit At Wednesday, 28-04-2010 on 0:21 Eric Shubert wrote: Steve Huff wrote: On Apr 27, 2010, at 2:18 PM, Eric Shubert wrote: Perhaps there's another XML parser that is used if XML::SAX doesn't exist? I can only speculate. I expect that there are others on the list that know better than I do about this. it's the other way around; that error message indicates that XML::SAX is falling back to its built-in pure-Perl parser, and the fix is to install a better one (or to take action that indicates to XML::SAX that yes, you really do want it to use the pure-Perl parser). it's all in the FAQ. -shuff -- Ah, I see. That makes sense. I read the FAQ but that wasn't clear to me. I still wonder though which package Amit could be missing. Amit, can you post the result of: # sudo -u vpopmail -H spamassassin -D --lint -- -Eric 'shubes' - Qmailtoaster is sponsored by Vickers Consulting Group (www.vickersconsulting.com) Vickers Consulting Group offers Qmailtoaster support and installations. If you need professional help with your setup, contact them today! - Please visit qmailtoaster.com for the latest news, updates, and packages. To unsubscribe, e-mail: qmailtoaster-list-unsubscr...@qmailtoaster.com For additional commands, e-mail: qmailtoaster-list-h...@qmailtoaster.com - Qmailtoaster is sponsored by Vickers Consulting Group (www.vickersconsulting.com) Vickers Consulting Group offers Qmailtoaster support
RE: [qmailtoaster] Re: Error in Sending Mail -- ParserDetails ini not found error
http://perl-xml.sourceforge.net/faq/#parserdetails.ini 3.18. could not find ParserDetails.ini A number of people have reported encountering the error could not find ParserDetails.ini in ... when installing or attempting to use XML::SAX. ParserDetails.ini is used by XML::SAX::ParserFactory to determine which SAX parser modules are installed. It should be created by the XML::SAX installation script and should be updated automatically by the install script for each SAX parser module. If you are installing XML::SAX manually you must run Makefile.PL. Unpacking the tarball and copying the files into your Perl lib directory will not work. During the initial installation, if you are asked whether ParserDetails.ini should be updated, always say yes. If you say no, the file will not be created. If you are using ActivePerl, the following command should resolve the problem: ppm install http://theoryx5.uwinnipeg.ca/ppms/XML-SAX.ppd Once you have successfully installed XML::SAX, you should consider installing a module such as XML::SAX::Expat or XML::LibXML to replace the slower pure-Perl parser bundled with SAX. If you are packaging XML::SAX in an alternative distribution format (such as RPM), your post-install script should check if ParserDetails.ini exists and if it doesn't, run this command: perl -MXML::SAX -e XML::SAX-add_parser(q(XML::SAX::PurePerl))-save_parsers() Don't unconditionally run this command, or users who re-install XML::SAX may find that any fast SAX parser they have installed will be replaced as the default by the pure-Perl parser. I hope this will help many of us who are facing this problem. Regards, Anil Aliyan -Original Message- From: Eric Shubert [mailto:e...@shubes.net] Sent: Wednesday, April 28, 2010 10:03 AM To: qmailtoaster-list@qmailtoaster.com Subject: [qmailtoaster] Re: Error in Sending Mail Hey Amit, I'm particularly interested in the --lint output which lists diag:, so I guess you could do: # sudo -u vpopmail -H spamassassin -D --lint 21 | grep diag: That will show if modules that are used, and if any are missing. From what Steve said though, I'm not sure it will show what all is missing with XML/SAX. The stock QMT does not use LDAP of any kind (that I'm aware of, and I'm pretty sure about that). FWIW, I hope to introduce an LDAP option (in place of MySQL) once vpopmail 5.5 is fully available. I don't know of an estimated target date for that, but I expect it will be at least several months from now. I'll be happy if we see it by the end of this year. -- -Eric 'shubes' Amit Dalia wrote: Dear Eric/Steve, Sorry I agree I should google first. Eric: Please find output of command sudo -u vpopmail -H spamassassin -D --lint below: [14326] dbg: rules: compiled meta tests [14326] dbg: check: running tests for priority: 1000 [14326] dbg: rules: running head tests; score so far=4.205 [14326] dbg: rules: compiled head tests [14326] dbg: rules: running body tests; score so far=4.205 [14326] dbg: rules: compiled body tests [14326] dbg: rules: running uri tests; score so far=4.205 [14326] dbg: rules: compiled uri tests [14326] dbg: rules: running rawbody tests; score so far=4.205 [14326] dbg: rules: compiled rawbody tests [14326] dbg: rules: running full tests; score so far=4.205 [14326] dbg: rules: compiled full tests [14326] dbg: rules: running meta tests; score so far=4.205 [14326] dbg: rules: compiled meta tests [14326] dbg: check: is spam? score=4.205 required=5 [14326] dbg: check: tests=MISSING_DATE,MISSING_HEADERS,MISSING_SUBJECT,NO_RECEIVED,NO_RELAYS [14326] dbg: check: subtests=__HAS_MSGID,__MISSING_REF,__MSGID_OK_DIGITS,__MSGID_OK_HOST,__MSOE_ MID_WRONG_CASE,__NONEMPTY_BODY,__SANE_MSGID,__SARE_WHITELIST_FLAG,__TVD_BODY ,__UNUSABLE_MSGID There was lot more but I thought to post last few line, if require will post complete output. Also I found that perl-LDAP module depands on perl-XML-SAX. Does QMT perl-LDAP module(I don't think so)? Regards, Amit At Wednesday, 28-04-2010 on 0:21 Eric Shubert wrote: Steve Huff wrote: On Apr 27, 2010, at 2:18 PM, Eric Shubert wrote: Perhaps there's another XML parser that is used if XML::SAX doesn't exist? I can only speculate. I expect that there are others on the list that know better than I do about this. it's the other way around; that error message indicates that XML::SAX is falling back to its built-in pure-Perl parser, and the fix is to install a better one (or to take action that indicates to XML::SAX that yes, you really do want it to use the pure-Perl parser). it's all in the FAQ. -shuff -- Ah, I see. That makes sense. I read the FAQ but that wasn't clear to me. I still wonder though which package Amit
