Re: [qmailtoaster] Re: POP3 Authentication on CentOS 5.5 64Bit
Hello, Problem fixed. Probably it was/is of because vchkpw. I've downloaded and compiled the latest vpopmail from http://www.inter7.com/index.php?page=vpopmail and issue got fixed. Thank you Eric. Saturday, October 16, 2010, 10:46:40 PM, you wrote: > Hello Eric, > Saturday, October 16, 2010, 10:32:14 PM, you wrote: >> On 10/16/2010 12:20 PM, Mario wrote: >>> Hello all, >>> >>> I've POP3 authentication issues with qmail toaster on centos 5.5 . >>> The error the pop3 client receives it's: >>> >>> The response is: /home/vpopmail/bin/vchkpw: error while loading shared >>> libraries: libcrypt.so.1: failed to map segment from shared object: Cannot >>> allocate memory -ERR authorization failed >>> >>> I've tried increasing the softlimit for pop3 but error persists. >>> >>> Any clues ? >>> >>> Thanks >>> >>> >>> - >> What'd you increase it to? How much memory do you have? >> # free >> 64Bit machines definitely need more. I thought Jake had fixed this. >> Perhaps the memory increase doesn't happen on 5.5? > # more /var/qmail/supervise/pop3/run|grep soft > exec /usr/bin/softlimit -m 4000 \ > # free -m > total used free sharedbuffers cached > Mem: 5956 5743213 0229 4627 > -/+ buffers/cache:886 5070 > Swap: 7961 15 7945 > I guess it should be sufficient ram allocated. > Thanks, > Mario - 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: POP3 Authentication on CentOS 5.5 64Bit
Hello Eric, Saturday, October 16, 2010, 10:32:14 PM, you wrote: > On 10/16/2010 12:20 PM, Mario wrote: >> Hello all, >> >> I've POP3 authentication issues with qmail toaster on centos 5.5 . >> The error the pop3 client receives it's: >> >> The response is: /home/vpopmail/bin/vchkpw: error while loading shared >> libraries: libcrypt.so.1: failed to map segment from shared object: Cannot >> allocate memory -ERR authorization failed >> >> I've tried increasing the softlimit for pop3 but error persists. >> >> Any clues ? >> >> Thanks >> >> >> - > What'd you increase it to? How much memory do you have? > # free > 64Bit machines definitely need more. I thought Jake had fixed this. > Perhaps the memory increase doesn't happen on 5.5? # more /var/qmail/supervise/pop3/run|grep soft exec /usr/bin/softlimit -m 4000 \ # free -m total used free sharedbuffers cached Mem: 5956 5743213 0229 4627 -/+ buffers/cache:886 5070 Swap: 7961 15 7945 I guess it should be sufficient ram allocated. Thanks, Mario - 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] Re: POP3 Authentication on CentOS 5.5 64Bit
On 10/16/2010 12:20 PM, Mario wrote: Hello all, I've POP3 authentication issues with qmail toaster on centos 5.5 . The error the pop3 client receives it's: The response is: /home/vpopmail/bin/vchkpw: error while loading shared libraries: libcrypt.so.1: failed to map segment from shared object: Cannot allocate memory -ERR authorization failed I've tried increasing the softlimit for pop3 but error persists. Any clues ? Thanks - What'd you increase it to? How much memory do you have? # free 64Bit machines definitely need more. I thought Jake had fixed this. Perhaps the memory increase doesn't happen on 5.5? -- -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] POP3 Authentication on CentOS 5.5 64Bit
Hello all, I've POP3 authentication issues with qmail toaster on centos 5.5 . The error the pop3 client receives it's: The response is: /home/vpopmail/bin/vchkpw: error while loading shared libraries: libcrypt.so.1: failed to map segment from shared object: Cannot allocate memory -ERR authorization failed I've tried increasing the softlimit for pop3 but error persists. Any clues ? Thanks - 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] Re: SMTP problems
There is no smtp-ssl port configured on QMT. Port 465 is deprecated. TLS on port 25 or 587 is preferred. Outlook'03 can't do this however. If you need port 465, follow the directions at http://wiki.qmailtoaster.com/index.php/SSL to set this up. Port 995 for pop3-ssl should work ok. -- -Eric 'shubes' On 10/15/2010 07:19 PM, mahesh.b...@modelytics.com wrote: my Smtp-ssl and pop3-ssl has stopped functioning... i did a port scan 995 and 465 are not functional On 10/15/2010 04:57 PM, Mahesh Bhat wrote: Hi all, Since a couple of days my remote users are not able to send mails via Outlook smtp (25)….. internal users are just fine. What could be the problem /-Regards Mahesh Bhat / It would help to know what sort of error message they get, or what smtp log messages are that correspond to a failed submission. Can they send via port 587 instead of port 25? My guess is that their IP address is blacklisted. You have 2 options to fix that - either use port 587 or install spamdyke. Spamdyke is highly recommended, and it's a cinch to install with the qtp-install-spamdyke script. -- -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] Re: SMTP problems
Are they running? # qmailctl stat On 10/15/2010 07:19 PM, mahesh.b...@modelytics.com wrote: my Smtp-ssl and pop3-ssl has stopped functioning... i did a port scan 995 and 465 are not functional On 10/15/2010 04:57 PM, Mahesh Bhat wrote: Hi all, Since a couple of days my remote users are not able to send mails via Outlook smtp (25)….. internal users are just fine. What could be the problem /-Regards Mahesh Bhat / It would help to know what sort of error message they get, or what smtp log messages are that correspond to a failed submission. Can they send via port 587 instead of port 25? My guess is that their IP address is blacklisted. You have 2 options to fix that - either use port 587 or install spamdyke. Spamdyke is highly recommended, and it's a cinch to install with the qtp-install-spamdyke script. -- -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 and installations. If you need professional help with your setup, contact them today! -- -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
Re: [qmailtoaster] Issue with yahoo differing our email
Hi Anil, I sent you a couple of emails. As for now yahoo did not give an error. I also send a test message to yahoo.com domain but the issue persisted. Thank you, Sandeil - Original Message From: Anil Aliyan To: qmailtoaster-list@qmailtoaster.com Sent: Saturday, October 16, 2010 9:30:59 PM Subject: RE: [qmailtoaster] Issue with yahoo differing our email Can you send a test message on a valid yahoo email address instead of t...@yahoo.com and then check it. Send a test message on my email address anil.ali...@yahoo.co.in -Original Message- From: Sandeil Tenebro [mailto:mayukmo...@yahoo.com] Sent: 16 October 2010 18:12 To: qmailtoaster-list@qmailtoaster.com Subject: Re: [qmailtoaster] Issue with yahoo differing our email Hi Anil, Domain keys and dkim $ORIGIN mydomain.com. _domainkey TXT "t=y\; o=-\; r=t...@booom.com.ph" $ORIGIN _domainkey.mydomain.com. dkim1 TXT "k=rsa\; p=My Key" private TXT "k=rsa\; p=My Key" That is the entry for DNS its a slave DNS in this case The suggested procedure worked. Thank you This is the new header: Hi. This is the qmail-send program at erato.booom.com.ph. I'm afraid I wasn't able to deliver your message to the following addresses. This is a permanent error; I've given up. Sorry it didn't work out. : User and password not set, continuing without authentication. 66.94.236.34 failed after I sent the message. Remote host said: 554 Message not allowed - [PH01] Email not accepted for policy reasons. Please visit http://postmaster.yahoo.com/errors/postmaster-27.html [120] --- Below this line is a copy of the message. Return-Path: Received: (qmail 7558 invoked by uid 89); 16 Oct 2010 12:35:39 - Comment: DomainKeys? See http://antispam.yahoo.com/domainkeys DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=private; d=booom.com.ph; b=WjTuJw1zMG5xMPNvZ2u1G/TeGp4eqFjBhOW162fBjqAWMUk+FOq1oyb6wU6yw2Ea; Received: from unknown (HELO booom.com.ph) (127.0.0.1) by erato.booom.com.ph with SMTP; 16 Oct 2010 12:35:39 - Received: from 124.6.155.51 (proxying for 192.168.0.5) (SquirrelMail authenticated user sctene...@booom.com.ph) by booom.com.ph with HTTP; Sat, 16 Oct 2010 20:35:39 +0800 Message-ID: <93a971cd7d3814d8dff19d55d42bfed5.squir...@booom.com.ph> Date: Sat, 16 Oct 2010 20:35:39 +0800 Subject: test From: sctene...@booom.com.ph To: t...@yahoo.com User-Agent: SquirrelMail/1.4.20-1.3.17 MIME-Version: 1.0 Content-Type: text/plain;charset=iso-8859-1 Content-Transfer-Encoding: 8bit X-Priority: 3 (Normal) Importance: Normal Any idea from the group? Thanks - Original Message From: Anil Aliyan To: qmailtoaster-list@qmailtoaster.com Sent: Saturday, October 16, 2010 7:52:57 PM Subject: RE: [qmailtoaster] Issue with yahoo differing our email 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: Sandeil Tenebro [mailto:mayukmo...@yahoo.com] Sent: 16 October 2010 16:48 To: qmailtoaster-list@qmailtoaster.com Subject: Re: [qmailtoaster] Issue with yahoo differing our email Hi, Update from yahoo differed full headers. Hi. This is the qmail-send program at erato.booom.com.ph. I'm afraid I wasn't able to deliver your message to the following addresses. This is a permanent error; I've given up. Sorry
RE: [qmailtoaster] Issue with yahoo differing our email
Can you send a test message on a valid yahoo email address instead of t...@yahoo.com and then check it. Send a test message on my email address anil.ali...@yahoo.co.in -Original Message- From: Sandeil Tenebro [mailto:mayukmo...@yahoo.com] Sent: 16 October 2010 18:12 To: qmailtoaster-list@qmailtoaster.com Subject: Re: [qmailtoaster] Issue with yahoo differing our email Hi Anil, Domain keys and dkim $ORIGIN mydomain.com. _domainkey TXT "t=y\; o=-\; r=t...@booom.com.ph" $ORIGIN _domainkey.mydomain.com. dkim1 TXT "k=rsa\; p=My Key" private TXT "k=rsa\; p=My Key" That is the entry for DNS its a slave DNS in this case The suggested procedure worked. Thank you This is the new header: Hi. This is the qmail-send program at erato.booom.com.ph. I'm afraid I wasn't able to deliver your message to the following addresses. This is a permanent error; I've given up. Sorry it didn't work out. : User and password not set, continuing without authentication. 66.94.236.34 failed after I sent the message. Remote host said: 554 Message not allowed - [PH01] Email not accepted for policy reasons. Please visit http://postmaster.yahoo.com/errors/postmaster-27.html [120] --- Below this line is a copy of the message. Return-Path: Received: (qmail 7558 invoked by uid 89); 16 Oct 2010 12:35:39 - Comment: DomainKeys? See http://antispam.yahoo.com/domainkeys DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=private; d=booom.com.ph; b=WjTuJw1zMG5xMPNvZ2u1G/TeGp4eqFjBhOW162fBjqAWMUk+FOq1oyb6wU6yw2Ea; Received: from unknown (HELO booom.com.ph) (127.0.0.1) by erato.booom.com.ph with SMTP; 16 Oct 2010 12:35:39 - Received: from 124.6.155.51 (proxying for 192.168.0.5) (SquirrelMail authenticated user sctene...@booom.com.ph) by booom.com.ph with HTTP; Sat, 16 Oct 2010 20:35:39 +0800 Message-ID: <93a971cd7d3814d8dff19d55d42bfed5.squir...@booom.com.ph> Date: Sat, 16 Oct 2010 20:35:39 +0800 Subject: test From: sctene...@booom.com.ph To: t...@yahoo.com User-Agent: SquirrelMail/1.4.20-1.3.17 MIME-Version: 1.0 Content-Type: text/plain;charset=iso-8859-1 Content-Transfer-Encoding: 8bit X-Priority: 3 (Normal) Importance: Normal Any idea from the group? Thanks - Original Message From: Anil Aliyan To: qmailtoaster-list@qmailtoaster.com Sent: Saturday, October 16, 2010 7:52:57 PM Subject: RE: [qmailtoaster] Issue with yahoo differing our email 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: Sandeil Tenebro [mailto:mayukmo...@yahoo.com] Sent: 16 October 2010 16:48 To: qmailtoaster-list@qmailtoaster.com Subject: Re: [qmailtoaster] Issue with yahoo differing our email Hi, Update from yahoo differed full headers. Hi. This is the qmail-send program at erato.booom.com.ph. I'm afraid I wasn't able to deliver your message to the following addresses. This is a permanent error; I've given up. Sorry it didn't work out. : ould not find ParserDetails.ini in /usr/lib/perl5/vendor_perl/5.8.8/XML/SAX rUser and password not set, continuing without authentication. 74.6.136.65 failed after I sent the message. Remote host said: 554 Message not allowed - [PH01] Email not accepted for policy reasons. Please visit http://postmaster.yahoo.com/errors/postmaster-27.html [120]
Re: [qmailtoaster] Issue with yahoo differing our email
Hi Anil, Domain keys and dkim $ORIGIN mydomain.com. _domainkey TXT "t=y\; o=-\; r=t...@booom.com.ph" $ORIGIN _domainkey.mydomain.com. dkim1 TXT "k=rsa\; p=My Key" private TXT "k=rsa\; p=My Key" That is the entry for DNS its a slave DNS in this case The suggested procedure worked. Thank you This is the new header: Hi. This is the qmail-send program at erato.booom.com.ph. I'm afraid I wasn't able to deliver your message to the following addresses. This is a permanent error; I've given up. Sorry it didn't work out. : User and password not set, continuing without authentication. 66.94.236.34 failed after I sent the message. Remote host said: 554 Message not allowed - [PH01] Email not accepted for policy reasons. Please visit http://postmaster.yahoo.com/errors/postmaster-27.html [120] --- Below this line is a copy of the message. Return-Path: Received: (qmail 7558 invoked by uid 89); 16 Oct 2010 12:35:39 - Comment: DomainKeys? See http://antispam.yahoo.com/domainkeys DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=private; d=booom.com.ph; b=WjTuJw1zMG5xMPNvZ2u1G/TeGp4eqFjBhOW162fBjqAWMUk+FOq1oyb6wU6yw2Ea; Received: from unknown (HELO booom.com.ph) (127.0.0.1) by erato.booom.com.ph with SMTP; 16 Oct 2010 12:35:39 - Received: from 124.6.155.51 (proxying for 192.168.0.5) (SquirrelMail authenticated user sctene...@booom.com.ph) by booom.com.ph with HTTP; Sat, 16 Oct 2010 20:35:39 +0800 Message-ID: <93a971cd7d3814d8dff19d55d42bfed5.squir...@booom.com.ph> Date: Sat, 16 Oct 2010 20:35:39 +0800 Subject: test From: sctene...@booom.com.ph To: t...@yahoo.com User-Agent: SquirrelMail/1.4.20-1.3.17 MIME-Version: 1.0 Content-Type: text/plain;charset=iso-8859-1 Content-Transfer-Encoding: 8bit X-Priority: 3 (Normal) Importance: Normal Any idea from the group? Thanks - Original Message From: Anil Aliyan To: qmailtoaster-list@qmailtoaster.com Sent: Saturday, October 16, 2010 7:52:57 PM Subject: RE: [qmailtoaster] Issue with yahoo differing our email 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: Sandeil Tenebro [mailto:mayukmo...@yahoo.com] Sent: 16 October 2010 16:48 To: qmailtoaster-list@qmailtoaster.com Subject: Re: [qmailtoaster] Issue with yahoo differing our email Hi, Update from yahoo differed full headers. Hi. This is the qmail-send program at erato.booom.com.ph. I'm afraid I wasn't able to deliver your message to the following addresses. This is a permanent error; I've given up. Sorry it didn't work out. : ould not find ParserDetails.ini in /usr/lib/perl5/vendor_perl/5.8.8/XML/SAX rUser and password not set, continuing without authentication. 74.6.136.65 failed after I sent the message. Remote host said: 554 Message not allowed - [PH01] Email not accepted for policy reasons. Please visit http://postmaster.yahoo.com/errors/postmaster-27.html [120] --- Below this line is a copy of the message. Return-Path: Received: (qmail 11368 invoked by uid 89); 16 Oct 2010 11:13:06 - Comment: DomainKeys? See http://antispam.yahoo.com/domainkeys DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=private; d=booom.com.ph; b=rutsd3WrxguNgCgfu7JnbQdZL0Rpv3Xm7IqLzOr+5AaKB8/Fppr8zoEm+VKh0Cys; Received: from unknown (HELO bo
RE: [qmailtoaster] Issue with yahoo differing our email
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: Sandeil Tenebro [mailto:mayukmo...@yahoo.com] Sent: 16 October 2010 16:48 To: qmailtoaster-list@qmailtoaster.com Subject: Re: [qmailtoaster] Issue with yahoo differing our email Hi, Update from yahoo differed full headers. Hi. This is the qmail-send program at erato.booom.com.ph. I'm afraid I wasn't able to deliver your message to the following addresses. This is a permanent error; I've given up. Sorry it didn't work out. : ould not find ParserDetails.ini in /usr/lib/perl5/vendor_perl/5.8.8/XML/SAX rUser and password not set, continuing without authentication. 74.6.136.65 failed after I sent the message. Remote host said: 554 Message not allowed - [PH01] Email not accepted for policy reasons. Please visit http://postmaster.yahoo.com/errors/postmaster-27.html [120] --- Below this line is a copy of the message. Return-Path: Received: (qmail 11368 invoked by uid 89); 16 Oct 2010 11:13:06 - Comment: DomainKeys? See http://antispam.yahoo.com/domainkeys DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=private; d=booom.com.ph; b=rutsd3WrxguNgCgfu7JnbQdZL0Rpv3Xm7IqLzOr+5AaKB8/Fppr8zoEm+VKh0Cys; Received: from unknown (HELO booom.com.ph) (127.0.0.1) by erato.booom.com.ph with SMTP; 16 Oct 2010 11:13:06 - Received: from 124.6.155.51 (proxying for 192.168.0.5) (SquirrelMail authenticated user sctene...@booom.com.ph) by booom.com.ph with HTTP; Sat, 16 Oct 2010 19:13:06 +0800 Message-ID: Date: Sat, 16 Oct 2010 19:13:06 +0800 Subject: test From: sctene...@booom.com.ph To: t...@yahoo.com User-Agent: SquirrelMail/1.4.20-1.3.17 MIME-Version: 1.0 Content-Type: text/plain;charset=iso-8859-1 Content-Transfer-Encoding: 8bit X-Priority: 3 (Normal) Importance: Normal I also tried to add dkim but with no avail. its now DKIM + domain keys. If this is no good please let me know which is the standard and how to remove 1. Please advice. Thank you, Sandeil - Original Message From: Sandeil Tenebro To: qmailtoaster mailing list Sent: Saturday, October 16, 2010 6:46:09 PM Subject: [qmailtoaster] Issue with yahoo differing our email Hi List, Just migrated to a new server. We can properly send emails to other public domains but we have an issue with yahoo. The are differing our email. Domain key is configured but with no avail. Full message from yahoo: Hi. This is the qmail-send program at erato.booom.com.ph. I'm afraid I wasn't able to deliver your message to the following addresses. This is a permanent error; I've given up. Sorry it didn't work out. : User and password not set, continuing without authentication. 98.139.54.60 failed after I sent the message. Remote host said: 554 Message not allowed - [PH01] Email not accepted for policy reasons. Please visit http://postmaster.yahoo.com/errors/postmaster-27.html [120] --- Below this line is a copy of the message. Return-Path: Received: (qmail 9522 invoked by uid 89); 16 Oct 2010 10:42:31 - Comment: DomainKeys? See http://antispam.yahoo.com/domainkeys DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=private; d=booom.com.ph; b=TE7CUoKQUNn55fHcF7j9Oup+PXV3dF8YJBHkEgXD5bYc5SK8FMFOWHJW9/LP9zpS; Received: from unknown (HELO booom.com.ph) (127.0.0.1) by erato.booom.com.p
RE: [qmailtoaster] Issue with yahoo differing our email
Can you tell us when you updated your DNS records for Domain Keys??? -Original Message- From: Sandeil Tenebro [mailto:mayukmo...@yahoo.com] Sent: 16 October 2010 16:48 To: qmailtoaster-list@qmailtoaster.com Subject: Re: [qmailtoaster] Issue with yahoo differing our email Hi, Update from yahoo differed full headers. Hi. This is the qmail-send program at erato.booom.com.ph. I'm afraid I wasn't able to deliver your message to the following addresses. This is a permanent error; I've given up. Sorry it didn't work out. : ould not find ParserDetails.ini in /usr/lib/perl5/vendor_perl/5.8.8/XML/SAX rUser and password not set, continuing without authentication. 74.6.136.65 failed after I sent the message. Remote host said: 554 Message not allowed - [PH01] Email not accepted for policy reasons. Please visit http://postmaster.yahoo.com/errors/postmaster-27.html [120] --- Below this line is a copy of the message. Return-Path: Received: (qmail 11368 invoked by uid 89); 16 Oct 2010 11:13:06 - Comment: DomainKeys? See http://antispam.yahoo.com/domainkeys DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=private; d=booom.com.ph; b=rutsd3WrxguNgCgfu7JnbQdZL0Rpv3Xm7IqLzOr+5AaKB8/Fppr8zoEm+VKh0Cys; Received: from unknown (HELO booom.com.ph) (127.0.0.1) by erato.booom.com.ph with SMTP; 16 Oct 2010 11:13:06 - Received: from 124.6.155.51 (proxying for 192.168.0.5) (SquirrelMail authenticated user sctene...@booom.com.ph) by booom.com.ph with HTTP; Sat, 16 Oct 2010 19:13:06 +0800 Message-ID: Date: Sat, 16 Oct 2010 19:13:06 +0800 Subject: test From: sctene...@booom.com.ph To: t...@yahoo.com User-Agent: SquirrelMail/1.4.20-1.3.17 MIME-Version: 1.0 Content-Type: text/plain;charset=iso-8859-1 Content-Transfer-Encoding: 8bit X-Priority: 3 (Normal) Importance: Normal I also tried to add dkim but with no avail. its now DKIM + domain keys. If this is no good please let me know which is the standard and how to remove 1. Please advice. Thank you, Sandeil - Original Message From: Sandeil Tenebro To: qmailtoaster mailing list Sent: Saturday, October 16, 2010 6:46:09 PM Subject: [qmailtoaster] Issue with yahoo differing our email Hi List, Just migrated to a new server. We can properly send emails to other public domains but we have an issue with yahoo. The are differing our email. Domain key is configured but with no avail. Full message from yahoo: Hi. This is the qmail-send program at erato.booom.com.ph. I'm afraid I wasn't able to deliver your message to the following addresses. This is a permanent error; I've given up. Sorry it didn't work out. : User and password not set, continuing without authentication. 98.139.54.60 failed after I sent the message. Remote host said: 554 Message not allowed - [PH01] Email not accepted for policy reasons. Please visit http://postmaster.yahoo.com/errors/postmaster-27.html [120] --- Below this line is a copy of the message. Return-Path: Received: (qmail 9522 invoked by uid 89); 16 Oct 2010 10:42:31 - Comment: DomainKeys? See http://antispam.yahoo.com/domainkeys DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=private; d=booom.com.ph; b=TE7CUoKQUNn55fHcF7j9Oup+PXV3dF8YJBHkEgXD5bYc5SK8FMFOWHJW9/LP9zpS; Received: from unknown (HELO booom.com.ph) (127.0.0.1) by erato.booom.com.ph with SMTP; 16 Oct 2010 10:42:31 - Received: from 124.6.155.51 (proxying for 192.168.0.5) (SquirrelMail authenticated user sctene...@booom.com.ph) by booom.com.ph with HTTP; Sat, 16 Oct 2010 18:42:31 +0800 Message-ID: Date: Sat, 16 Oct 2010 18:42:31 +0800 Subject: test From: sctene...@booom.com.ph To: t...@yahoo.com User-Agent: SquirrelMail/1.4.20-1.3.17 MIME-Version: 1.0 Content-Type: text/plain;charset=iso-8859-1 Content-Transfer-Encoding: 8bit X-Priority: 3 (Normal) Importance: Normal Full header from google: Delivered-To: t...@gmail.com Received: by 10.216.52.66 with SMTP id d44cs397493wec; Sat, 16 Oct 2010 03:23:25 -0700 (PDT) Received: by 10.142.211.20 with SMTP id j20mr1526362wfg.408.1287224601655; Sat, 16 Oct 2010 03:23:21 -0700 (PDT) Return-Path: Received: from erato.booom.com.ph (ns2.booom.com.ph [203.177.60.42]) by mx.google.com with ESMTP id l40si30124712wfa.106.2010.10.16.03.23.19; Sat, 16 Oct 2010 03:23:20 -0700 (PDT) Received-SPF: pass (google.com: domain of sctene...@booom.com.ph designates 203.177.60.42 as permitted sender) client-ip=203.177.60.42; DomainKey-Status: good Authentication-Results: mx.google.com; spf=pass (google.com: domain of sctene...@booom.com.ph designates 203.177.60.42 as permitted sender) smtp.mail=sctene...@booom.com.ph; domainkeys=pass header.from=sctene...@booom.com.ph Received: (qmail 8545 invoked by uid 89); 16 Oct 2010 10:23:18 - Comment: DomainKeys? See http://antispam.yahoo.com/domainkeys DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=private; d=booom.c
Re: [qmailtoaster] Issue with yahoo differing our email
Hi, Update from yahoo differed full headers. Hi. This is the qmail-send program at erato.booom.com.ph. I'm afraid I wasn't able to deliver your message to the following addresses. This is a permanent error; I've given up. Sorry it didn't work out. : ould not find ParserDetails.ini in /usr/lib/perl5/vendor_perl/5.8.8/XML/SAX rUser and password not set, continuing without authentication. 74.6.136.65 failed after I sent the message. Remote host said: 554 Message not allowed - [PH01] Email not accepted for policy reasons. Please visit http://postmaster.yahoo.com/errors/postmaster-27.html [120] --- Below this line is a copy of the message. Return-Path: Received: (qmail 11368 invoked by uid 89); 16 Oct 2010 11:13:06 - Comment: DomainKeys? See http://antispam.yahoo.com/domainkeys DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=private; d=booom.com.ph; b=rutsd3WrxguNgCgfu7JnbQdZL0Rpv3Xm7IqLzOr+5AaKB8/Fppr8zoEm+VKh0Cys; Received: from unknown (HELO booom.com.ph) (127.0.0.1) by erato.booom.com.ph with SMTP; 16 Oct 2010 11:13:06 - Received: from 124.6.155.51 (proxying for 192.168.0.5) (SquirrelMail authenticated user sctene...@booom.com.ph) by booom.com.ph with HTTP; Sat, 16 Oct 2010 19:13:06 +0800 Message-ID: Date: Sat, 16 Oct 2010 19:13:06 +0800 Subject: test From: sctene...@booom.com.ph To: t...@yahoo.com User-Agent: SquirrelMail/1.4.20-1.3.17 MIME-Version: 1.0 Content-Type: text/plain;charset=iso-8859-1 Content-Transfer-Encoding: 8bit X-Priority: 3 (Normal) Importance: Normal I also tried to add dkim but with no avail. its now DKIM + domain keys. If this is no good please let me know which is the standard and how to remove 1. Please advice. Thank you, Sandeil - Original Message From: Sandeil Tenebro To: qmailtoaster mailing list Sent: Saturday, October 16, 2010 6:46:09 PM Subject: [qmailtoaster] Issue with yahoo differing our email Hi List, Just migrated to a new server. We can properly send emails to other public domains but we have an issue with yahoo. The are differing our email. Domain key is configured but with no avail. Full message from yahoo: Hi. This is the qmail-send program at erato.booom.com.ph. I'm afraid I wasn't able to deliver your message to the following addresses. This is a permanent error; I've given up. Sorry it didn't work out. : User and password not set, continuing without authentication. 98.139.54.60 failed after I sent the message. Remote host said: 554 Message not allowed - [PH01] Email not accepted for policy reasons. Please visit http://postmaster.yahoo.com/errors/postmaster-27.html [120] --- Below this line is a copy of the message. Return-Path: Received: (qmail 9522 invoked by uid 89); 16 Oct 2010 10:42:31 - Comment: DomainKeys? See http://antispam.yahoo.com/domainkeys DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=private; d=booom.com.ph; b=TE7CUoKQUNn55fHcF7j9Oup+PXV3dF8YJBHkEgXD5bYc5SK8FMFOWHJW9/LP9zpS; Received: from unknown (HELO booom.com.ph) (127.0.0.1) by erato.booom.com.ph with SMTP; 16 Oct 2010 10:42:31 - Received: from 124.6.155.51 (proxying for 192.168.0.5) (SquirrelMail authenticated user sctene...@booom.com.ph) by booom.com.ph with HTTP; Sat, 16 Oct 2010 18:42:31 +0800 Message-ID: Date: Sat, 16 Oct 2010 18:42:31 +0800 Subject: test From: sctene...@booom.com.ph To: t...@yahoo.com User-Agent: SquirrelMail/1.4.20-1.3.17 MIME-Version: 1.0 Content-Type: text/plain;charset=iso-8859-1 Content-Transfer-Encoding: 8bit X-Priority: 3 (Normal) Importance: Normal Full header from google: Delivered-To: t...@gmail.com Received: by 10.216.52.66 with SMTP id d44cs397493wec; Sat, 16 Oct 2010 03:23:25 -0700 (PDT) Received: by 10.142.211.20 with SMTP id j20mr1526362wfg.408.1287224601655; Sat, 16 Oct 2010 03:23:21 -0700 (PDT) Return-Path: Received: from erato.booom.com.ph (ns2.booom.com.ph [203.177.60.42]) by mx.google.com with ESMTP id l40si30124712wfa.106.2010.10.16.03.23.19; Sat, 16 Oct 2010 03:23:20 -0700 (PDT) Received-SPF: pass (google.com: domain of sctene...@booom.com.ph designates 203.177.60.42 as permitted sender) client-ip=203.177.60.42; DomainKey-Status: good Authentication-Results: mx.google.com; spf=pass (google.com: domain of sctene...@booom.com.ph designates 203.177.60.42 as permitted sender) smtp.mail=sctene...@booom.com.ph; domainkeys=pass header.from=sctene...@booom.com.ph Received: (qmail 8545 invoked by uid 89); 16 Oct 2010 10:23:18 - Comment: DomainKeys? See http://antispam.yahoo.com/domainkeys DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=private; d=booom.com.ph; b=Mxx90ZN7M0M724/9fXcMQ6iWjJ2rNGpvKVcE9QLLp2lJnVPbGRwug4SaWBg/0iOv; Received: from unknown (HELO booom.com.ph) (127.0.0.1) by erato.booom.com.ph with SMTP; 16 Oct 2010 10:23:18 - Received: from 124.6.155.51 (proxying for 192.168.0.5) (SquirrelMail auth
[qmailtoaster] Issue with yahoo differing our email
Hi List, Just migrated to a new server. We can properly send emails to other public domains but we have an issue with yahoo. The are differing our email. Domain key is configured but with no avail. Full message from yahoo: Hi. This is the qmail-send program at erato.booom.com.ph. I'm afraid I wasn't able to deliver your message to the following addresses. This is a permanent error; I've given up. Sorry it didn't work out. : User and password not set, continuing without authentication. 98.139.54.60 failed after I sent the message. Remote host said: 554 Message not allowed - [PH01] Email not accepted for policy reasons. Please visit http://postmaster.yahoo.com/errors/postmaster-27.html [120] --- Below this line is a copy of the message. Return-Path: Received: (qmail 9522 invoked by uid 89); 16 Oct 2010 10:42:31 - Comment: DomainKeys? See http://antispam.yahoo.com/domainkeys DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=private; d=booom.com.ph; b=TE7CUoKQUNn55fHcF7j9Oup+PXV3dF8YJBHkEgXD5bYc5SK8FMFOWHJW9/LP9zpS; Received: from unknown (HELO booom.com.ph) (127.0.0.1) by erato.booom.com.ph with SMTP; 16 Oct 2010 10:42:31 - Received: from 124.6.155.51 (proxying for 192.168.0.5) (SquirrelMail authenticated user sctene...@booom.com.ph) by booom.com.ph with HTTP; Sat, 16 Oct 2010 18:42:31 +0800 Message-ID: Date: Sat, 16 Oct 2010 18:42:31 +0800 Subject: test From: sctene...@booom.com.ph To: t...@yahoo.com User-Agent: SquirrelMail/1.4.20-1.3.17 MIME-Version: 1.0 Content-Type: text/plain;charset=iso-8859-1 Content-Transfer-Encoding: 8bit X-Priority: 3 (Normal) Importance: Normal Full header from google: Delivered-To: t...@gmail.com Received: by 10.216.52.66 with SMTP id d44cs397493wec; Sat, 16 Oct 2010 03:23:25 -0700 (PDT) Received: by 10.142.211.20 with SMTP id j20mr1526362wfg.408.1287224601655; Sat, 16 Oct 2010 03:23:21 -0700 (PDT) Return-Path: Received: from erato.booom.com.ph (ns2.booom.com.ph [203.177.60.42]) by mx.google.com with ESMTP id l40si30124712wfa.106.2010.10.16.03.23.19; Sat, 16 Oct 2010 03:23:20 -0700 (PDT) Received-SPF: pass (google.com: domain of sctene...@booom.com.ph designates 203.177.60.42 as permitted sender) client-ip=203.177.60.42; DomainKey-Status: good Authentication-Results: mx.google.com; spf=pass (google.com: domain of sctene...@booom.com.ph designates 203.177.60.42 as permitted sender) smtp.mail=sctene...@booom.com.ph; domainkeys=pass header.from=sctene...@booom.com.ph Received: (qmail 8545 invoked by uid 89); 16 Oct 2010 10:23:18 - Comment: DomainKeys? See http://antispam.yahoo.com/domainkeys DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=private; d=booom.com.ph; b=Mxx90ZN7M0M724/9fXcMQ6iWjJ2rNGpvKVcE9QLLp2lJnVPbGRwug4SaWBg/0iOv; Received: from unknown (HELO booom.com.ph) (127.0.0.1) by erato.booom.com.ph with SMTP; 16 Oct 2010 10:23:18 - Received: from 124.6.155.51 (proxying for 192.168.0.5) (SquirrelMail authenticated user sctene...@booom.com.ph) by booom.com.ph with HTTP; Sat, 16 Oct 2010 18:23:18 +0800 Message-ID: Date: Sat, 16 Oct 2010 18:23:18 +0800 Subject: test From: sctene...@booom.com.ph To: t...@gmail.com User-Agent: SquirrelMail/1.4.20-1.3.17 MIME-Version: 1.0 Content-Type: text/plain;charset=iso-8859-1 Content-Transfer-Encoding: 8bit X-Priority: 3 (Normal) Importance: Normal Appreciate your help. Thank you, Sandeil - 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: After backup restoration web based email sending went slow
Hi List, We manage to find a work around on our issue. These are the steps that we undergo: - Install the toaster to the new server [destination server] - Create the important account from source server to destination server - From source server we just tar those users directory - To destination server we untar it This solved our issue but now we are getting differed by yahoo but not on gmail. Domain key was configured but yahoo seems to differ it. Here is the full header. I guess I have to open a nw thread for this. Delivered-To: t...@gmail.com Received: by 10.216.52.66 with SMTP id d44cs397493wec; Sat, 16 Oct 2010 03:23:25 -0700 (PDT) Received: by 10.142.211.20 with SMTP id j20mr1526362wfg.408.1287224601655; Sat, 16 Oct 2010 03:23:21 -0700 (PDT) Return-Path: Received: from erato.booom.com.ph (ns2.booom.com.ph [203.177.60.42]) by mx.google.com with ESMTP id l40si30124712wfa.106.2010.10.16.03.23.19; Sat, 16 Oct 2010 03:23:20 -0700 (PDT) Received-SPF: pass (google.com: domain of sctene...@booom.com.ph designates 203.177.60.42 as permitted sender) client-ip=203.177.60.42; DomainKey-Status: good Authentication-Results: mx.google.com; spf=pass (google.com: domain of sctene...@booom.com.ph designates 203.177.60.42 as permitted sender) smtp.mail=sctene...@booom.com.ph; domainkeys=pass header.from=sctene...@booom.com.ph Received: (qmail 8545 invoked by uid 89); 16 Oct 2010 10:23:18 - Comment: DomainKeys? See http://antispam.yahoo.com/domainkeys DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=private; d=booom.com.ph; b=Mxx90ZN7M0M724/9fXcMQ6iWjJ2rNGpvKVcE9QLLp2lJnVPbGRwug4SaWBg/0iOv; Received: from unknown (HELO booom.com.ph) (127.0.0.1) by erato.booom.com.ph with SMTP; 16 Oct 2010 10:23:18 - Received: from 124.6.155.51 (proxying for 192.168.0.5) (SquirrelMail authenticated user sctene...@booom.com.ph) by booom.com.ph with HTTP; Sat, 16 Oct 2010 18:23:18 +0800 Message-ID: Date: Sat, 16 Oct 2010 18:23:18 +0800 Subject: test From: sctene...@booom.com.ph To: t...@gmail.com User-Agent: SquirrelMail/1.4.20-1.3.17 MIME-Version: 1.0 Content-Type: text/plain;charset=iso-8859-1 Content-Transfer-Encoding: 8bit X-Priority: 3 (Normal) Importance: Normal Thank you for all the help - 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
