Re: [SM-USERS] smtp and tls issue
iClou wrote: > > On Fri, 2010-09-03 at 14:50 -0700, Tomas Kuliavas wrote: >> >> iClou wrote: >> > >> > Hi >> > I run squirrelmail on ubuntu 9.04 successfully. >> > When I switch to a different smtp server which requires tls then I get >> the >> > following error message. (the server runs on port 25) >> > >> > "0 Can't open SMTP stream" >> > >> > I tried to connect from other clients to the same smtp server and it >> works >> > fine. >> > Any idea how to resolve this? >> > >> Don't confuse TLS with StartTLS extension. >> >> Stable SquirrelMail versions support plain text SMTP and SMTP-over-SSL. >> If >> you set SquirrelMail to use TLS, you set it to connect to SMTP-over-SSL >> service. >> >> Service on 25 port can be only plain text SMTP with optional StartTLS >> extension. >> >> StartTLS is supported only in SquirrelMail 1.5.x and limited number of >> PHP >> versions. > I upgraded to version 1.5.x; now I can connect to the server -thanks! > But the email get the content-transfer-encoding: 8bit, see this extract > from the email: > > Content-Transfer-Encoding: 8bit > > Such emails will not be delivered through the Internet. > > How does this come and how can I resolve this? What kind of error you get? Which SquirrelMail version are you using? Which SMTP server are you using? Can you show EHLO response of SMTP server? telnet your-smtp-server 25 > server's greeting ehlo your-hostname > some response that I want to see quit There is nothing wrong in this header. Emails with "Content-Transfer-Encoding: 8bit" can be delivered. SquirrelMail 1.4.x uses same header. Are you from China? Some countries filter internet traffic. Not sure how it is done in your country. I don't think that traffic filters block "Content-Transfer-Encoding: 8bit" iClou wrote: > > Is it possible to specify different user/passw for different email > addresses? > SquirrelMail can use same username/password as specified in webmail login or one username/password for all users. -- View this message in context: http://old.nabble.com/smtp-and-tls-issue-tp29618208p29620417.html Sent from the squirrelmail-users mailing list archive at Nabble.com. -- This SF.net Dev2Dev email is sponsored by: Show off your parallel programming skills. Enter the Intel(R) Threading Challenge 2010. http://p.sf.net/sfu/intel-thread-sfd - squirrelmail-users mailing list Posting guidelines: http://squirrelmail.org/postingguidelines List address: squirrelmail-users@lists.sourceforge.net List archives: http://news.gmane.org/gmane.mail.squirrelmail.user List info (subscribe/unsubscribe/change options): https://lists.sourceforge.net/lists/listinfo/squirrelmail-users
Re: [SM-USERS] smtp and tls issue
On Sat, 2010-09-04 at 01:03 -0700, Tomas Kuliavas wrote: > > iClou wrote: > > > > On Fri, 2010-09-03 at 14:50 -0700, Tomas Kuliavas wrote: > >> > >> iClou wrote: > >> > > >> > Hi > >> > I run squirrelmail on ubuntu 9.04 successfully. > >> > When I switch to a different smtp server which requires tls then I get > >> the > >> > following error message. (the server runs on port 25) > >> > > >> > "0 Can't open SMTP stream" > >> > > >> > I tried to connect from other clients to the same smtp server and it > >> works > >> > fine. > >> > Any idea how to resolve this? > >> > > >> Don't confuse TLS with StartTLS extension. > >> > >> Stable SquirrelMail versions support plain text SMTP and SMTP-over-SSL. > >> If > >> you set SquirrelMail to use TLS, you set it to connect to SMTP-over-SSL > >> service. > >> > >> Service on 25 port can be only plain text SMTP with optional StartTLS > >> extension. > >> > >> StartTLS is supported only in SquirrelMail 1.5.x and limited number of > >> PHP > >> versions. > > I upgraded to version 1.5.x; now I can connect to the server -thanks! > > But the email get the content-transfer-encoding: 8bit, see this extract > > from the email: > > > > Content-Transfer-Encoding: 8bit > > > > Such emails will not be delivered through the Internet. > > > > How does this come and how can I resolve this? > What kind of error you get? Which SquirrelMail version are you using? Which > SMTP server are you using? Can you show EHLO response of SMTP server? > > telnet your-smtp-server 25 > > server's greeting > ehlo your-hostname > > some response that I want to see > quit > > There is nothing wrong in this header. Emails with > "Content-Transfer-Encoding: 8bit" can be delivered. SquirrelMail 1.4.x uses > same header. Are you from China? Some countries filter internet traffic. Not > sure how it is done in your country. I don't think that traffic filters > block "Content-Transfer-Encoding: 8bit" I found the root cause of it - I send out the emails throught a custom perl script. mail::gpg has a default option of use_strict_7bit_encoding - When I change this then it runs fine. -- Thanks for your support on this! Best, Mike -- This SF.net Dev2Dev email is sponsored by: Show off your parallel programming skills. Enter the Intel(R) Threading Challenge 2010. http://p.sf.net/sfu/intel-thread-sfd - squirrelmail-users mailing list Posting guidelines: http://squirrelmail.org/postingguidelines List address: squirrelmail-users@lists.sourceforge.net List archives: http://news.gmane.org/gmane.mail.squirrelmail.user List info (subscribe/unsubscribe/change options): https://lists.sourceforge.net/lists/listinfo/squirrelmail-users
[SM-USERS] change_passwd-4.3beta7-1.2.8.tar.gz -- has stopped working.
OS: FreeBSD 7.3 SM: 1.4.21 Plugins Installed Plugins: (up to date) 1. filters 2. password_forget 3. cookie_warning 4. quicksave 5. login_check 6. timeout_user 7. change_passwd -- using the default settings in config.php 8. qotd_login Change_passwd worked one (1) time then stopped. The error message only tells the logged in user to contact the 'admin'. - Changed the following in config.php in hopes of gaining a clue: // If you want see the output of the chpasswd program (usually^M // only useful for debugging purposes, set this to 1^M //^M $seeOutput = 1;^M ^M ^M ^M // For debugging only, set this variable to 1. WARNING: this will ^M // echo any password information you enter in clear text! Please ^M // use this setting with care!^M //^M $debug = 1;^M --- The results after the changes above: permission of chpasswd executable are: 104750 To test the chpasswd utility from the commandline, do this: change_passwd/chpasswd 'userID' 'old_pass' 'new_pass' 2>&1 THE RESULT: ELF binary type "0" not known. We try and use: $pathToPw ='/full/path/' RESULT: In red; "Your password was changed successfully" left-click on the INBOX, it logs/signs the user 'out'. While attempting to log back in SM will not use the new password, it continues to use the 'old_password'. -- Any thoughts? -- This SF.net Dev2Dev email is sponsored by: Show off your parallel programming skills. Enter the Intel(R) Threading Challenge 2010. http://p.sf.net/sfu/intel-thread-sfd - squirrelmail-users mailing list Posting guidelines: http://squirrelmail.org/postingguidelines List address: squirrelmail-users@lists.sourceforge.net List archives: http://news.gmane.org/gmane.mail.squirrelmail.user List info (subscribe/unsubscribe/change options): https://lists.sourceforge.net/lists/listinfo/squirrelmail-users
