From: <tri...@te...> - 2006-04-20 14:38:19
|
>>>>>>>> I just install Squirrelmail on Fedora Core 5 and I'm getting the >>>>>>>> following >>>>>>>> erorrs when I try to send a message: >>>>>>>> >>>>>>>> Notice: Undefined property: Deliver_SMTP::$dlv_msg in >>>>>>>> /var/www/html/webmail/src/compose.php on line 1577 >>>>>>>> >>>>>>>> Notice: Undefined property: Deliver_SMTP::$dlv_server_msg in >>>>>>>> /var/www/html/webmail/src/compose.php on line 1579 >>>>>>>> >>>>>>>> Anyone seen this error before? >>>>>>> >>>>>>> Could you make sure that you are using SquirrelMail 1.4.6 or 1.5.1? >>>>>>> >>>>>>> If you use SquirrelMail 1.4.6 - show SMTP server settings in >>>>>>> SquirrelMail >>>>>>> configuration. conf.pl -> 2. Server settings -> B. Update SMTP -> >>>>>>> settings >>>>>>> from 4 to 8. >>>>>>> >>>>>>> -- >>>>>>> Tomas >>>>>> >>>>>> >>>>>> I'm using 1.4.6 >>>>> >>>>> Are you sure? Your email headers show different version. >>>>> >>>>>> Here are my settings: >>>>>> >>>>>> 4. SMTP Server : localhost >>>>>> 5. SMTP Port : 25 >>>>>> 6. POP before SMTP : false >>>>>> 7. SMTP Authentication : login >>>>>> 8. Secure SMTP (TLS) : false >>>>> >>>>> Are you sure that SMTP AUTH is supported and works on your email >>>>> server >>>>> without STARTTLS or Secure SMTP requirement? >>>>> >>>>> -- >>>>> Tomas >>>>> >>>> >>>> >>>> I have setup the mail server using QmailRocks install. I believe it >>>> is >>>> setup to use starttls. I have it setup up on some FC2 boxes and SM >>>> works >>>> just fine. Is it something with FC5? Do I need to use 1.5.1? >>> >>> 1. SquirrelMail SMTP delivery has two places that process smtp >>> connection >>> errors. first place checks connection itself. It can cause undefined >>> dlv_server_msg property error in 1.4.5. if you can see this error, then >>> you should see fsockopen function errors too. It is fixed in 1.4.6. >>> Other >>> error checks use one function and this function sets all three error >>> properties. So you should not see undefined dlv_msg property errors in >>> standard SquirrelMail 1.4.6. >>> >>> SquirrelMail 1.5.1 has more fixes in sendmail delivery functions, but >>> you >>> are not using sendmail delivery. >>> >>> If you do get undefined property errors in standard unmodified >>> SquirrelMail 1.4.6 install, I would like to understand how you managed >>> to >>> do that. Could you show md5sums and id tags of your SquirrelMail >>> class/deliver/*.php and src/compose.php files? Id tags are listed in >>> file >>> headers. $Id: something $. md5sums are generated with md5sum utility. >>> Could you also check if you are using some php cache or optimizer or >>> other >>> zend extension? >>> >>> 2. Fedora Core 3 and later enables SELinux by default. Default policy >>> does >>> not allow making network connections from httpd. Don't know if you have >>> tried setting selinux to permissive mode. See >>> http://www.squirrelmail.org/wiki/FedoraSELinux >>> >>> 3. Are you sure that SMTP AUTH is working correctly in your qmail >>> setup? >>> Qmail SMTP AUTH does not work without patches and requires some >>> tweaking >>> in vchkpw permissions and tcpserver startup files. Could you set 7. >>> SMTP >>> Authentication to none and see if it helps. >>> >>> -- >>> Tomas >>> If you do get undefined property errors in standard unmodified >>> SquirrelMail 1.4.6 install, I would like to understand how you managed >>> to >>> do that. Could you show md5sums and id tags of your SquirrelMail >>> class/deliver/*.php and src/compose.php files? Id tags are listed in >>> file >>> headers. $Id: something $. md5sums are generated with md5sum utility. >> >> [root@testserv220 deliver]# md5sum * >> e3836e1a90c4570e27f53c8bc8e4c9ac Deliver.class.php >> f30eb85fc249614f00c2a9959b453508 Deliver_IMAP.class.php >> e04fa2acb03be66b50cab17879061c2f Deliver_SendMail.class.php >> 71ffcdd31c55656af3a04dc1e2876504 Deliver_SMTP.class.php >> 76941c2395aacc26ac64c8a98ff1c746 index.php >> >> [root@testserv220 src]# md5sum compose.php >> 134fb28b5d9bb9d7e8ee308a772cc4ce compose.php >> >>> Could you also check if you are using some php cache or optimizer or >>> other zend extension? >> >> Not that I'm aware of, not sure how to check it if I am. > > See http://www.squirrelmail.org/wiki/TestPHPSettings or check your php.ini > files. Zend Optimizer, Tursk MMCache, PHP Accelerator, EAccelerator, PHP > APC, PHP APD are zend extensions or do php script caching. They can change > normal php script execution and sometimes caching breaks SquirrelMail > scripts. > >>> 2. Fedora Core 3 and later enables SELinux by default. Default policy >>> does >>> not allow making network connections from httpd. Don't know if you have >>> tried setting selinux to permissive mode. See >>> http://www.squirrelmail.org/wiki/FedoraSELinux >> >> /etc/selinux/config >> >> # This file controls the state of SELinux on the system. >> # SELINUX= can take one of these three values: >> # enforcing - SELinux security policy is enforced. >> # permissive - SELinux prints warnings instead of enforcing. >> # disabled - SELinux is fully disabled. >> #SELINUX=enforcing tbr >> SELINUX=disabled >> # SELINUXTYPE= type of policy in use. Possible values are: >> # targeted - Only targeted network daemons are protected. >> # strict - Full SELinux protection. >> SELINUXTYPE=targeted >> >> # SETLOCALDEFS= Check local definition changes >> SETLOCALDEFS=0 >> >>> 3. Are you sure that SMTP AUTH is working correctly in your qmail >>> setup? >>> Qmail SMTP AUTH does not work without patches and requires some >>> tweaking >>> in vchkpw permissions and tcpserver startup files. Could you set 7. >>> SMTP >>> Authentication to none and see if it helps. >> >> Following the QMAILROCKS install it seems to be working correctly. >> >> [root@testserv220 src]# telnet localhost 25 >> Trying 127.0.0.1... >> Connected to localhost.localdomain (127.0.0.1). >> Escape character is '^]'. >> 220 test.techovations.com ESMTP >> ehlo localhost >> 250-test.techovations.com >> 250-AUTH LOGIN CRAM-MD5 PLAIN >> 250-AUTH=LOGIN CRAM-MD5 PLAIN >> 250-STARTTLS >> 250-PIPELINING >> 250 8BITMIME >> starttls >> 220 ready for tls >> quit >> quit > > that's not smtp auth test. > > try sending email with some other email program. > > some qmail smtp setup errors are visible only after you try sending > message. > >>> Could you set 7. SMTP >>> Authentication to none and see if it helps. >> >> When I set the SMTP Auth to none this is the error I get. >> >> Requested action aborted: error in processing >> Server replied: 451 qq temporary problem (#4.3.0) > > You have problems with smtp setup. errors should be visible in > /var/qmail/supervise/qmail-smtpd/log/main/current or any other place that > logs smtp server errors. > > if you have installed content scanner (qmail-scanner or simscan), disable > it. > > if you don't have content scanner, check what you have in > /var/qmail/supervise/qmail-smtpd/run. Qmail patched with smtp auth > requires three extra arguments after qmail-smtpd > > > -- > Tomas > > > ------------------------------------------------------- > This SF.Net email is sponsored by xPML, a groundbreaking scripting > language > that extends applications into web and mobile media. Attend the live > webcast > and join the prime developer group breaking into this new coding > territory! > http://sel.as-us.falkag.net/sel?cmd=lnk&kid=110944&bid=241720&dat=121642 > -- > squirrelmail-users mailing list > Posting Guidelines: > http://www.squirrelmail.org/wiki/MailingListPostingGuidelines > List Address: squ...@li... > List Archives: > http://news.gmane.org/thread.php?group=gmane.mail.squirrelmail.user > List Archives: http://sourceforge.net/mailarchive/forum.php?forum_id=2995 > List Info: https://lists.sourceforge.net/lists/listinfo/squirrelmail-users > Thomas, > if you have installed content scanner (qmail-scanner or simscan), disable > it. I do have qmail-scanner installed. I removed the line QMAILQUEUE="/var/qmail/bin/qmail-scanner-queue" ; export QMAILQUEUE That looks like the problem. After I removed it the error message was gone. Does this mean there is a problemw ith qmail-scanner? Do I need to reinstall qmail-scanner? Thanks Troy |