squirrelmail-devel — SquirrelMail Development Mailing List

Re: [SM-DEVEL] Squirrelmail under IE 10 auto-refreshes the right frame along with the folder list

[Paul L. <pa...@sq...>]

On Thu, Dec 12, 2013 at 2:16 AM, ansgarat <ans...@gm...> wrote:
> Hi,
> I noticed that when using IE on Windows 8 with metro, when SquirrelMail
> auto-refreshes the folder list (the left frame), the right frame also gets
> refreshed. (Tested on SM 1.4.22 and 1.4.23). So when you're composing a
> message, you lose what you have written because the right frame gets
> reloaded and you find yourself on the mail list page.

Per the mailing list posting guidelines, please list the plugins you
have running.  I suspect you are using the Folder Sync plugin.  If
not, then I don't know why this would happen.  If you are using that
plugin, it would be helpful (if you understand JavaScript) if you
could see why it is trying to refresh the compose screen.  On all
other browsers I know of, this does not happen.  The JavaScript is
reasonably simple - nothing fancy (for best compatibility), therefore
I wouldn't expect IE to break... although if anyone's going to
break.....

> Is there any fix for that? Thanks!

Maybe you can tell us - give us a hand!  Thanks!

PS - if this is a Folder Sync issue, this thread belongs on the
plugins mailing list

-- 
Paul Lesniewski
SquirrelMail Team
Please support Open Source Software by donating to SquirrelMail!
http://squirrelmail.org/donate_paul_lesniewski.php

[SM-DEVEL] Squirrelmail under IE 10 auto-refreshes the right frame along with the folder list

[ansgarat <ans...@gm...>]

Hi,
I noticed that when using IE on Windows 8 with metro, when SquirrelMail
auto-refreshes the folder list (the left frame), the right frame also gets
refreshed. (Tested on SM 1.4.22 and 1.4.23). So when you're composing a
message, you lose what you have written because the right frame gets
reloaded and you find yourself on the mail list page.

Is there any fix for that? Thanks!



--
View this message in context: http://squirrelmail.5843.n7.nabble.com/Squirrelmail-under-IE-10-auto-refreshes-the-right-frame-along-with-the-folder-list-tp25698.html
Sent from the squirrelmail-devel mailing list archive at Nabble.com.

[SM-DEVEL] CA validation

[<ma...@ne...>]

Squirrelmail has TLS support, but it lacks the ability to enforce server
certificate validation. This leaves no defense against MiM attacks using
a self-signed certificate.

Here is how it could be fixed, for SMTP side. Connexion is established
in class/deliver/Deliver_SMTP.class.php:

$stream = 
    @fsockopen('tls://' . $host, $port, $errorNumber, $errorString);

The stream_socket_client() function is an alternative to fsockopen()
that appeared in PHP 5. It allows the caller to specify a context with
various options:

if (function_exists('stream_socket_client') {
  $remote = sprintf("ssl://%s:%d", $host, port);
  $opts = array(
    'ssl' => array(
      'verify_peer' => TRUE,
      'verify_depth' => 5,
      'cafile' => '/path/to/ca_file',
    ),
  );
  $ctx = stream_context_create($opts);
  $timeout = ini_get("default_socket_timeout");
  $stream = 
    @stream_socket_client($remote, $errorNumber, $errorString,  
     $timeout, STREAM_CLIENT_CONNECT, $ctx);
} else {
  $stream = 
    @fsockopen('ssl://' . $host, $port, $errorNumber, $errorString);
}

Of course '/path/to/ca_file' needs to be configurable, I can work on
this if the idea is accepted.

Also note that I changed tls:// to ssl://. Inside the bowels of PHP,
tls:// causes OpenSSL's TLSv1_client_method() to be used. As its name
suggests, this metho can only negociate TLSv1.

ssl:// causes SSLv23_client_method() to be used. As its named does not
suggests, it is able to negociate the highest protocol version
avaialble, up to TLSv1.2 if the installed OpenSSL supports it. This
causes much stronger ciphers to be used.

For now Squirrelmail's usage of tls:// can be worked around by
specifying a ssl:// prefixed $smtpServerAddress with $use_smtp_tls =
false, but switching the code to ssl:// would immediatly improve
everyone setup.

I did not look at the IMAP side since I use imapproxy, and therefore
Squirrelmail is not incharge of IMAP TLS, but the idea is the same.

-- 
Emmanuel Dreyfus
http://hcpnet.free.fr/pubz
ma...@ne...

[SM-DEVEL] The real reason for failure to login to IMAP

[Alain W. <ad...@ph...>]

This is a summary of feature request #581 and patch #486 that provides the feature.

See:

    https://sourceforge.net/p/squirrelmail/feature-requests/581/



The purpose of the patches is to display the *reason* for an IMAP login failure.
Prior to this patch squirrelmail just displays the message:

    Unknown user or password incorrect.



It can be useful to a user to know the reason that login is refused, eg there might
be an administrative lock or their password may have expired.

For this to work the following configuration variable must be set true:

    $display_imap_login_error

Also enclosed is a patch to config/conf.pl to set this variable.


This is predicated on IMAP returning a meaningful reason, this is beyond the scope
of this patch and is why it is configurable.


There are two patch files:

  config-conf.pl.patch  for config/conf.pl

  functions-imap_general.php.patch  for functions/imap_general.php


These patches are released under the same license as the rest of SquirrelMail: GPLv2 (or later)


-- 
Alain Williams
Linux/GNU Consultant - Mail systems, Web sites, Networking, Programmer, IT Lecturer.
+44 (0) 787 668 0256  http://www.phcomp.co.uk/
Parliament Hill Computers Ltd. Registration Information: http://www.phcomp.co.uk/contact.php
#include <std_disclaimer.h>

Re: [SM-DEVEL] Process $body with decodeHeader()?

[Takahiro K. <ta...@ba...>]

In message <CAHog114WmSVjpuTw+2+pR2hLV=YEU...@ma...>
	on Thu, 24 Oct 2013 16:45:32 -0700,
	Paul Lesniewski <pa...@sq...> wrote:
> 神部さん、おひさしぶりです。
お久しぶりです。

>> In src/compose.php, body of a message is passed to decodeHeader().
>> Why $body is passed to decodeHeader()?
> 
> I'm not certain.  Marc introduced it long, long ago:
> 
> http://sourceforge.net/p/squirrelmail/code/4565/
Thanks for your pointer.

> If you look at the code around there, a few things that aren't headers
> (such as $signature) are being passed to decodeHeader() so it may have
> been a safety mechanism to catch values of many different strings that
> were possibly encoded.
First, I guessed it was intended to handle forward (text in body) or
cited message when replying.  But I noticed later, the codes handle
saved signature using MIME encoded format.

>> 1. Accidently (or intentionally) body text contains encoded MIME
>>    header string such as "=?iso-2022-jp?B ...".
> 
> I see.  Although a quick test replying to a text/plain message in
> quoted-printable encoding seems to show that the message is already
> decoded by the time it gets here (thus it seems this decodeHeader()
> call isn't needed to convert the QP blocks/entities), I'm hesitant to
> touch this since there was presumably good reason for the change.  If
> you want to remove all the calls to decodeHeader($body...) (I see at
> least three of them) and test for a while, your feedback would be
> welcomed.
I already tested a few case by removing decodeHeader() for body and it
works fine.  But we should consider what character encoding (or
encoded string) are used in each part of codes...

-- 
Takahiro Kambe / 神戸 隆博 <ta...@ba...>

Re: [SM-DEVEL] Process $body with decodeHeader()?

[Paul L. <pa...@sq...>]

神部さん、おひさしぶりです。

On Thu, Oct 24, 2013 at 4:26 AM, Takahiro Kambe <ta...@ba...> wrote:
> Hi,
>
> This isn't a bug report but a simple question.
>
> In src/compose.php, body of a message is passed to decodeHeader().
> Why $body is passed to decodeHeader()?

I'm not certain.  Marc introduced it long, long ago:

http://sourceforge.net/p/squirrelmail/code/4565/

If you look at the code around there, a few things that aren't headers
(such as $signature) are being passed to decodeHeader() so it may have
been a safety mechanism to catch values of many different strings that
were possibly encoded.

> SM-1_4-STABLE: about line 1316 of src/compose.php:
>     echo sm_encode_html_special_chars(decodeHeader($body,false,false,true));
>
> trunk: about line 1398 of src/compose.php:
>
>     $body_str = sm_encode_html_special_chars(decodeHeader($body,false,false));
>
> There was a bad scenario.
>
> 1. Accidently (or intentionally) body text contains encoded MIME
>    header string such as "=?iso-2022-jp?B ...".

I see.  Although a quick test replying to a text/plain message in
quoted-printable encoding seems to show that the message is already
decoded by the time it gets here (thus it seems this decodeHeader()
call isn't needed to convert the QP blocks/entities), I'm hesitant to
touch this since there was presumably good reason for the change.  If
you want to remove all the calls to decodeHeader($body...) (I see at
least three of them) and test for a while, your feedback would be
welcomed.

> 2. decodeHeader() decodes such ""=?iso-2022-jp?B ..." string into
>    iso-2022-jp (or other none UTF-8 string) encoded string.
>
> 3. Body is expected to UTF-8 or EUC-JP and really contain such string
>    in the encoding.
>
> 4. As a result, multiple text encopding are miexed and it cause
>    strange garbled characters.
>
> I hope $body should be already properly encoded and no need to decode
> header any more at that time.

-- 
Paul Lesniewski
SquirrelMail Team
Please support Open Source Software by donating to SquirrelMail!
http://squirrelmail.org/donate_paul_lesniewski.php

[SM-DEVEL] Process $body with decodeHeader()?

[Takahiro K. <ta...@ba...>]

Hi,

This isn't a bug report but a simple question.

In src/compose.php, body of a message is passed to decodeHeader().
Why $body is passed to decodeHeader()?

SM-1_4-STABLE: about line 1316 of src/compose.php:

    echo sm_encode_html_special_chars(decodeHeader($body,false,false,true));

trunk: about line 1398 of src/compose.php:

    $body_str = sm_encode_html_special_chars(decodeHeader($body,false,false));

There was a bad scenario.

1. Accidently (or intentionally) body text contains encoded MIME
   header string such as "=?iso-2022-jp?B ...".

2. decodeHeader() decodes such ""=?iso-2022-jp?B ..." string into
   iso-2022-jp (or other none UTF-8 string) encoded string.

3. Body is expected to UTF-8 or EUC-JP and really contain such string
   in the encoding.

4. As a result, multiple text encopding are miexed and it cause
   strange garbled characters.

I hope $body should be already properly encoded and no need to decode
header any more at that time.

Best regards.

-- 
Takahiro Kambe <ta...@ba...>

Re: [SM-DEVEL] FreeBSD now using an SVN snapshot

[Paul L. <pa...@sq...>]

Hi Adam,

On Sun, Oct 20, 2013 at 6:16 PM, Adam Weinberger <ad...@ad...> wrote:
> Hello! I wanted to let you know that I've switched the FreeBSD port to
> use an SVN snapshot rather than 1.4.22. PHP 5.4 and 5.5 compatibility
> has been an oft-requested feature, and I figured that rather than
> backporting just those patches, I'd bring in all the other hard work
> you've done since June 2011!
>
> FreeBSD requires that distfiles have known checksums, which means that I
> cannot point the port at the latest daily snapshot. As a result, I've
> mirrored the 2013/10/20 SVN snapshot onto the ftp.*.freebsd.org servers,
> and I intend to cherry-pick future SVN snapshots for the same. I'm
> pretty confident that I am not violating the letter or spirit of the GPL
> in doing this but I felt like letting you know about this was the right
> thing to do.
>
> Thanks for all of the hard work you've done! I'm pleased to now share
> more of it with the FreeBSD community!

Thanks for letting us know.  Hopefully 1.4.23 will be getting an
official release in the near future.  Thanks for your patience.

-- 
Paul Lesniewski
SquirrelMail Team
Please support Open Source Software by donating to SquirrelMail!
http://squirrelmail.org/donate_paul_lesniewski.php

[SM-DEVEL] FreeBSD now using an SVN snapshot

[Adam W. <ad...@ad...>]

Hello! I wanted to let you know that I've switched the FreeBSD port to
use an SVN snapshot rather than 1.4.22. PHP 5.4 and 5.5 compatibility
has been an oft-requested feature, and I figured that rather than
backporting just those patches, I'd bring in all the other hard work
you've done since June 2011!

FreeBSD requires that distfiles have known checksums, which means that I
cannot point the port at the latest daily snapshot. As a result, I've
mirrored the 2013/10/20 SVN snapshot onto the ftp.*.freebsd.org servers,
and I intend to cherry-pick future SVN snapshots for the same. I'm
pretty confident that I am not violating the letter or spirit of the GPL
in doing this but I felt like letting you know about this was the right
thing to do.

Thanks for all of the hard work you've done! I'm pleased to now share
more of it with the FreeBSD community!

# Adam


--
Adam Weinberger
ad...@ad... / ad...@Fr...
http://www.adamw.org

[SM-DEVEL] [PATCH] use prctl(PRCTL_SET_NO_NEW_PRIVS, 1) for added security

[Shawn L. <sh...@ch...>]

---
 include/imapproxy.h |  3 +++
 src/becomenonroot.c | 16 +++++++++++++++-
 2 files changed, 18 insertions(+), 1 deletion(-)

diff --git a/include/imapproxy.h b/include/imapproxy.h
index ce0b13b..aa090c4 100644
--- a/include/imapproxy.h
+++ b/include/imapproxy.h
@@ -152,6 +152,9 @@
 #include <limits.h>
 #endif
 
+#ifndef PR_SET_NO_NEW_PRIVS
+#define PR_SET_NO_NEW_PRIVS	38
+#endif
 
 /* 
  * Common definitions 
diff --git a/src/becomenonroot.c b/src/becomenonroot.c
index f19a9fb..59dfb37 100644
--- a/src/becomenonroot.c
+++ b/src/becomenonroot.c
@@ -57,6 +57,9 @@
 #if HAVE_UNISTD_H
 #include <unistd.h>
 #endif
+#ifdef __linux__
+#include <sys/prctl.h>
+#endif
 
 #include "imapproxy.h"
 
@@ -185,7 +188,18 @@ extern int BecomeNonRoot( void )
 	       newuid, strerror(errno));
 	return(-1);
     }
-    
+
+#ifdef __linux__
+    if ( prctl(PR_SET_NO_NEW_PRIVS, 1, 0, 0, 0) < 0)
+    {
+        syslog( LOG_WARNING, "%s: prctl(PR_SET_NO_NEW_PRIVS, 1) failed: %s",  fn,
+               strerror(errno));
+        if ( errno == EINVAL )
+            syslog( LOG_INFO, "%s: Perhaps kernel too old", fn);
+    } else
+        syslog( LOG_INFO, "%s: prctl(PR_SET_NO_NEW_PRIVS, 1) succeeded",  fn)
+#endif
+
     return(0);
 }
 
-- 
1.8.4.rc3

Re: [SM-DEVEL] send mail

[Fredrik J. <jer...@sq...>]

Hi Giovanni.

> Good morning using squirrel mail, we point out that coirca two months,
> responses to e-mails I receive, are not delivered to mitente the message,
> but only to the writer.

There's a difference between the SquirrelMail software and a mail system.
Delivery of mail is handled by the MTA (not by SquirrelMail), so you need
to contact the system administrator.

http://squirrelmail.org/support/enduser.php

Sincerely,
Fredrik

--
Fredrik Jervfors <http://fredrik.jervfors.se/>
The SquirrelMail Project
Please support Open Source Software by donating to SquirrelMail!
http://squirrelmail.org/donations.php

[SM-DEVEL] send mail

[Tuttiaprua S. B. <tut...@ho...>]

Tuttiaprua Sail


Good morning using squirrel mail, we point out that coirca two months, responses to e-mails I receive,
are not delivered to mitente the message, but only to the writer.

I hope I have contributed to a better service

Thank you
Giovanni




 TUTTIAPRUA
 Sede e Uff Amministrativo:
 Fiumicino (Rm) Italy
 
 Base Nautica:
 Porto di Roma 
 Lung.re Duca degli Abruzzi 84 - Ostia
   
 Contatti    
   +39 333.2227074
   +39 338.6714833
   
 Bordo +39 338.6462392
 Skype: TUTTIAPRUA S/y DelfiRena
 Facebook: Tuttiaprua Sail
 		 	   		  

Re: [SM-DEVEL] No Subject = No Ability To Read?

[Per H. <ha...@ya...>]

Thank you ST66!
I tried your fix in Squirrelmail v1.4.23 SVN 2013-05-30
It works great with PHP 5.4.16, it even fixed display errors in mails where
not the full mail would be shown.
And also when replying to such mails the full mail would not be appended
below...

There still exists some issues where some mails with Swedish characters
"åäö" display as questionmarks.
But this has been a such long-standing issue and was there before the
upgrade to PHP v5.4 aswell...

Here is one example of a mail sender not shown correctly even with your fix:
From:  	=?utf-8?Q?Kundtj=C3=A4nst Uppercut.se?=

And here the body of another mail:
Det '?'r v'?'ll maskulin vs feminim ben'?'mning?

I've tried to change the "Default Charset" from iso-8859-1 to utf-8 but it
makes no difference for these mails.
I've also tried enabling "lossy encoding" but likewise saw no change...




--
View this message in context: http://squirrelmail.5843.n7.nabble.com/No-Subject-No-Ability-To-Read-tp25132p25499.html
Sent from the squirrelmail-devel mailing list archive at Nabble.com.

Re: [SM-DEVEL] No Subject = No Ability To Read?

[Paul L. <pa...@sq...>]

On Tue, Jun 11, 2013 at 2:23 AM, ST66 <ts...@sw...> wrote:
> I have same problem here.
>
> A month ago I upgrade my server to Debian Stable 7, and since then trouble
> with encoding in emails.
> php5 (5.4.4-14)
> squirrelmail (2:1.4.23~svn20120406-2)
>
> My settings for language in squirrelmail
> 1.  Default Language       : en_US
> 2.  Default Charset        : UTF-8
> 3.  Enable lossy encoding  : true
>
> In Display Preferences I select Language=Default.
> All outgoing emails are now encoding as UTF-8, all fine.
>
> But now all incoming messages with a subject including f.ex. Danish letters
> (æ ø
> å) encoded with ISO-8859-1 show up with blank subject, and impossible to
> read them.
> Example:
> *Subject:* =?ISO-8859-1?B?VGVzdCDm+OUgxtjF?=
>
> If I then in Display Preferences instead select Language=Danish, subject is
> displayed fine, but then outgoing emails are encoded ISO-8859-1.

Please see our tracker where this is being discussed in more detail.

https://sourceforge.net/tracker/?func=detail&atid=100311&aid=3609402&group_id=311

-- 
Paul Lesniewski
SquirrelMail Team
Please support Open Source Software by donating to SquirrelMail!
http://squirrelmail.org/donate_paul_lesniewski.php

Re: [SM-DEVEL] No Subject = No Ability To Read?

[ST66 <ts...@sw...>]

I found reason for this error and have a fix.

http://php.net/manual/en/function.htmlspecialchars.php
have different default values from PHP 5.4.0 and  forward, before PHP 5.4.0
default encoding was ISO-8859-1, now it is UTF-8.

SquirrelMail does not pass incoming charset to this function, instead it
uses default.
So in a setup where you with SquirrelMail use UTF-8, incoming email encoded
ISO-8859-1 will be translated wrong.

To get it working correct I have change 1 line in
/usr/share/squirrelmail/functions/i18n.php
In "function charset_decode" change
   if (! $save_html) $string = sm_encode_html_special_chars ($string);
to
   if (! $save_html) $string = sm_encode_html_special_chars
($string,ENT_COMPAT | ENT_HTML401,$charset,true);





--
View this message in context: http://squirrelmail.5843.n7.nabble.com/No-Subject-No-Ability-To-Read-tp25132p25495.html
Sent from the squirrelmail-devel mailing list archive at Nabble.com.

Re: [SM-DEVEL] No Subject = No Ability To Read?

[ST66 <ts...@sw...>]

I have same problem here.

A month ago I upgrade my server to Debian Stable 7, and since then trouble
with encoding in emails.
php5 (5.4.4-14) 
squirrelmail (2:1.4.23~svn20120406-2)

My settings for language in squirrelmail
1.  Default Language       : en_US
2.  Default Charset        : UTF-8
3.  Enable lossy encoding  : true

In Display Preferences I select Language=Default.
All outgoing emails are now encoding as UTF-8, all fine.

But now all incoming messages with a subject including f.ex. Danish letters
(æ ø
å) encoded with ISO-8859-1 show up with blank subject, and impossible to
read them.
Example:
*Subject:* =?ISO-8859-1?B?VGVzdCDm+OUgxtjF?=

If I then in Display Preferences instead select Language=Danish, subject is
displayed fine, but then outgoing emails are encoded ISO-8859-1.

Brgds
Torben
 




--
View this message in context: http://squirrelmail.5843.n7.nabble.com/No-Subject-No-Ability-To-Read-tp25132p25494.html
Sent from the squirrelmail-devel mailing list archive at Nabble.com.

Re: [SM-DEVEL] Multiple sessions from the same browser

[Paul L. <pa...@sq...>]

Please read the mailing list posting guidelines to learn why you
should not top post.

>>> Hi to all,
>>>
>>> I had a problem: when the same user logged in (at the same time) from
>>> the same browser but with a different browser tab, doesn't work.
>>>
>>> I would like to know if there is a solution (a plugin or similar whith
>>> new session mechanisms ??) instead of saying users that they have to use
>>> 2 different browsers for login with 2 different accounts concurrently...
>> This is a long-standing issue; you should search before posting.  The
>> solution is to use the Login Check plugin.
>
> Two notes:
> - I had installed (or tried, I am followed the INSTALL intructions) this
> plugin, but nothing happens...I had tried with the three methods of the
> plugin, but the result was the same: no changes.
> - The documentation tell us that it is a solution about the
> contamination with the sessions, but not that allow two sessions at the
> same time from the same browser.

This is the same thing.  You *cannot* have multiple sessions in the
same browser, since sessions are cookie-based.  The plugin makes sure
you don't accidentally log in to the same SM using the same browser.

-- 
Paul Lesniewski
SquirrelMail Team
Please support Open Source Software by donating to SquirrelMail!
http://squirrelmail.org/donate_paul_lesniewski.php

Re: [SM-DEVEL] Multiple sessions from the same browser

[Sistemas <sis...@uv...>]

Hi,

Two notes:
- I had installed (or tried, I am followed the INSTALL intructions) this 
plugin, but nothing happens...I had tried with the three methods of the 
plugin, but the result was the same: no changes.
- The documentation tell us that it is a solution about the 
contamination with the sessions, but not that allow two sessions at the 
same time from the same browser. The three methods:
[login_check_method]
1 = Further logins not allowed until the original user is signed out
2 = Only display a warning on the login page
3 = Redirect to show the original user's mailbox

neither match with the functionality that we look at.

If I am wrong in something, please tell me...

Thanks a lot.
Regards,

Systems Area
Univeristy of Valladolid



El 04/06/13 18:29, Paul Lesniewski escribió:
> On Tue, Jun 4, 2013 at 6:26 AM, Sistemas <sis...@uv...> wrote:
>> Hi to all,
>>
>> I had a problem: when the same user logged in (at the same time) from
>> the same browser but with a different browser tab, doesn't work.
>>
>> I would like to know if there is a solution (a plugin or similar whith
>> new session mechanisms ??) instead of saying users that they have to use
>> 2 different browsers for login with 2 different accounts concurrently...
> This is a long-standing issue; you should search before posting.  The
> solution is to use the Login Check plugin.
>

Re: [SM-DEVEL] Multiple sessions from the same browser

[Paul L. <pa...@sq...>]

On Tue, Jun 4, 2013 at 6:26 AM, Sistemas <sis...@uv...> wrote:
> Hi to all,
>
> I had a problem: when the same user logged in (at the same time) from
> the same browser but with a different browser tab, doesn't work.
>
> I would like to know if there is a solution (a plugin or similar whith
> new session mechanisms ??) instead of saying users that they have to use
> 2 different browsers for login with 2 different accounts concurrently...

This is a long-standing issue; you should search before posting.  The
solution is to use the Login Check plugin.

-- 
Paul Lesniewski
SquirrelMail Team
Please support Open Source Software by donating to SquirrelMail!
http://squirrelmail.org/donate_paul_lesniewski.php

[SM-DEVEL] Multiple sessions from the same browser

[Sistemas <sis...@uv...>]

Hi to all,

I had a problem: when the same user logged in (at the same time) from 
the same browser but with a different browser tab, doesn't work.

I would like to know if there is a solution (a plugin or similar whith 
new session mechanisms ??) instead of saying users that they have to use 
2 different browsers for login with 2 different accounts concurrently...

Thanks in avance..


System Area of University of Valladolid

Re: [SM-DEVEL] No Subject = No Ability To Read?

[jlehtira <jo...@le...>]

Hi! I have a problem quite much like this. But in addition to some senders
and subjects being missing, also parts of my messages are blanked. This
problem appeared when I updated my server to the newest Slackware, that
comes with php 5.4.13. This seems to be about weird special characters -
international messages in english seem to be fine, but local ones are not.

I observed the error first on SquirrelMail 1.4.22, then on the
20130603_0200-SVN.stable, and on a version I downloaded using svn today,
20130603.

This is an example of a message that fails!!:



Return-Path: <hi...@ho...>
X-Original-To: hi...@hi...
Delivered-To: hi...@hi...
Received: from blu0-omc1-s31.blu0.hotmail.com
(blu0-omc1-s31.blu0.hotmail.com [65.55.116.42])
        by mail.lehtiranta.net (Postfix) with ESMTP id DB4F76005B
        for <hi...@hi...>; Mon,  3 Jun 2013 09:13:46 +0300 (EEST)
Received: from BLU0-SMTP143 ([65.55.116.9]) by
blu0-omc1-s31.blu0.hotmail.com with Microsoft SMTPSVC(6.0.3790.4675);
         Sun, 2 Jun 2013 23:13:47 -0700
X-EIP: [zGr9HD1vR2AtzjQJptB/Ba+xVE5qlnniAXWyWUysoo0=]
X-Originating-Email: [hi...@ho...]
Message-ID: <BLU...@ph...l>
Received: from cashew-MacBook-Pro.local ([109.204.181.124]) by
BLU0-SMTP143.phx.gbl over TLS secured channel with Microsoft
SMTPSVC(6.0.3790.4675);
         Sun, 2 Jun 2013 23:13:44 -0700
Date: Mon, 3 Jun 2013 09:13:41 +0300
From: M M <hi...@ho...>
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.7; rv:17.0)
Gecko/20130509 Thunderbird/17.0.6
MIME-Version: 1.0
To: P S <hi...@gm...>
CC: H V <hi...@gm...>, hi...@hi..., 
 R T <hi...@aa...>
Subject: Re: Lofootit
References: <FDB...@ki...>
<CAFctW=2f1...@ma...>
<CAL...@ma...>
In-Reply-To:
<CAL...@ma...>
X-Enigmail-Version: 1.5.1
Content-Type: text/plain; charset="ISO-8859-1"
Content-Transfer-Encoding: quoted-printable
X-OriginalArrivalTime: 03 Jun 2013 06:13:44.0683 (UTC)
FILETIME=[8086D3B0:01CE6021]

Moikka=2C

Menen omia kyytej=E4ni ja aikojani sinne. Majoitusvaihtoehtoja en ole
viel=E4 miettinyt=2C tiet=E4=E4k=F6 joku leirint=E4alueen (onko niit=E4kin =
useampi?)
hinnoista? M=F6kkikin periaatteessa kiinnostaa..

M M




--
View this message in context: http://squirrelmail.5843.n7.nabble.com/No-Subject-No-Ability-To-Read-tp25132p25467.html
Sent from the squirrelmail-devel mailing list archive at Nabble.com.

[SM-DEVEL] I have a doubt about using Squirrelmail,

[Ranieri Q. <qra...@gm...>]

Hello,

I have a doubt about using Squirrelmail, scenery Squirrelmail for internal
accounting and exchanges to speak with an outside world.

create an account distribution in exchange and include the accounts of the
internal Squirrelmail this is possible? what procedure?

thank you

ranieri

Re: [SM-DEVEL] Support for more flags

[Paul L. <pa...@sq...>]

On Tue, May 7, 2013 at 8:34 AM, Pander <pa...@us...> wrote:
> Hi all,
>
> At the moment Squirrelmail 1.4.22 and the development version supports the
> flagged flag by either giving the email entry in the overview pane a red
> font or providing it with a red flag.

The flag icons are from the Message Flags & Icons plugin.

> This flag can also be toggled via Thunderbird by pressing '1' when that
> particular message is selected. By default Thunderbird offers five
> different flags, see
> http://forums.mozillazine.org/viewtopic.php?p=6090655#p6090655
>
> Could SquirelMail also support the four additional flags please?

For displaying the flags (change text and icon color), this is
possible (patches welcome, or at least someone can provide appropriate
colors).

For adding those flags from SquirrelMail without using JavaScript,
this becomes difficult due to UI space constraints.  The extra
flagging could be a JavaScript-only feature, for which, again,
interface suggestions are welcome.

-- 
Paul Lesniewski
SquirrelMail Team
Please support Open Source Software by donating to SquirrelMail!
http://squirrelmail.org/donate_paul_lesniewski.php

[SM-DEVEL] Support for more flags

[Pander <pa...@us...>]

Hi all,

At the moment Squirrelmail 1.4.22 and the development version supports the
flagged flag by either giving the email entry in the overview pane a red
font or providing it with a red flag.

This flag can also be toggled via Thunderbird by pressing '1' when that
particular message is selected. By default Thunderbird offers five
different flags, see
http://forums.mozillazine.org/viewtopic.php?p=6090655#p6090655

Could SquirelMail also support the four additional flags please?

Implementing this will improve using flags among different kind of email
applications. A similar request is also pending at K-9 email client for
Android.

Regards,

Pander

[SM-DEVEL] DAViCal CardDAV export to SquirrelMail address books

[Pander <pa...@us...>]

Hi all,

I am developing a Python script which will export contacts from DAViCal
CardDAV to SquirrelMail address books.

If you are interested in this for testing and helping out completing the
development, please have a look here:

http://sourceforge.net/mailarchive/forum.php?thread_name=517EB665.90909%40users.sourceforge.net&forum_name=davical-general
and:
  https://github.com/PanderMusubi/davical2abook/blob/master/test.py

Please continue discussion via GitHub and/or DAViCal mailing list.

Regards,

Pander