Menu
▾
▴
squirrelmail-users — SquirrelMail Users Mailing List
You can subscribe to this list here.
| 2001 |
Jan
|
Feb
|
Mar
|
Apr
|
May
|
Jun
|
Jul
|
Aug
|
Sep
|
Oct
|
Nov
|
Dec
(323) |
|---|---|---|---|---|---|---|---|---|---|---|---|---|
| 2002 |
Jan
(886) |
Feb
(712) |
Mar
(808) |
Apr
(522) |
May
(798) |
Jun
(462) |
Jul
(718) |
Aug
(765) |
Sep
(680) |
Oct
(610) |
Nov
(763) |
Dec
(805) |
| 2003 |
Jan
(907) |
Feb
(960) |
Mar
(757) |
Apr
(1072) |
May
(1084) |
Jun
(934) |
Jul
(839) |
Aug
(587) |
Sep
(644) |
Oct
(824) |
Nov
(653) |
Dec
(611) |
| 2004 |
Jan
(556) |
Feb
(405) |
Mar
(619) |
Apr
(557) |
May
(630) |
Jun
(577) |
Jul
(535) |
Aug
(460) |
Sep
(446) |
Oct
(597) |
Nov
(517) |
Dec
(471) |
| 2005 |
Jan
(474) |
Feb
(573) |
Mar
(438) |
Apr
(508) |
May
(355) |
Jun
(455) |
Jul
(389) |
Aug
(412) |
Sep
(382) |
Oct
(345) |
Nov
(448) |
Dec
(368) |
| 2006 |
Jan
(433) |
Feb
(378) |
Mar
(379) |
Apr
(356) |
May
(265) |
Jun
(334) |
Jul
(305) |
Aug
(273) |
Sep
(292) |
Oct
(192) |
Nov
(240) |
Dec
(263) |
| 2007 |
Jan
(279) |
Feb
(222) |
Mar
(185) |
Apr
(175) |
May
(313) |
Jun
(218) |
Jul
(157) |
Aug
(236) |
Sep
(277) |
Oct
(274) |
Nov
(198) |
Dec
(285) |
| 2008 |
Jan
(251) |
Feb
(188) |
Mar
(185) |
Apr
(152) |
May
(203) |
Jun
(152) |
Jul
(198) |
Aug
(135) |
Sep
(178) |
Oct
(160) |
Nov
(94) |
Dec
(175) |
| 2009 |
Jan
(101) |
Feb
(89) |
Mar
(117) |
Apr
(79) |
May
(130) |
Jun
(148) |
Jul
(157) |
Aug
(98) |
Sep
(117) |
Oct
(96) |
Nov
(112) |
Dec
(129) |
| 2010 |
Jan
(126) |
Feb
(158) |
Mar
(149) |
Apr
(60) |
May
(87) |
Jun
(149) |
Jul
(128) |
Aug
(66) |
Sep
(78) |
Oct
(42) |
Nov
(40) |
Dec
(62) |
| 2011 |
Jan
(53) |
Feb
(68) |
Mar
(39) |
Apr
(66) |
May
(25) |
Jun
(51) |
Jul
(34) |
Aug
(45) |
Sep
(39) |
Oct
(45) |
Nov
(51) |
Dec
(45) |
| 2012 |
Jan
(59) |
Feb
(38) |
Mar
(72) |
Apr
(24) |
May
(36) |
Jun
(44) |
Jul
(55) |
Aug
(48) |
Sep
(25) |
Oct
(39) |
Nov
(27) |
Dec
(21) |
| 2013 |
Jan
(16) |
Feb
(29) |
Mar
(31) |
Apr
(42) |
May
(24) |
Jun
(15) |
Jul
(31) |
Aug
(28) |
Sep
(5) |
Oct
(8) |
Nov
(15) |
Dec
(3) |
| 2014 |
Jan
(5) |
Feb
(14) |
Mar
(22) |
Apr
(32) |
May
(32) |
Jun
(11) |
Jul
(6) |
Aug
(23) |
Sep
(16) |
Oct
(4) |
Nov
(13) |
Dec
(12) |
| 2015 |
Jan
(30) |
Feb
(17) |
Mar
(24) |
Apr
(11) |
May
(3) |
Jun
(25) |
Jul
|
Aug
(8) |
Sep
(45) |
Oct
(4) |
Nov
(5) |
Dec
(8) |
| 2016 |
Jan
(22) |
Feb
(17) |
Mar
(8) |
Apr
(11) |
May
(26) |
Jun
(4) |
Jul
(18) |
Aug
(11) |
Sep
(6) |
Oct
(10) |
Nov
(17) |
Dec
(15) |
| 2017 |
Jan
(33) |
Feb
(1) |
Mar
(4) |
Apr
(2) |
May
(9) |
Jun
(9) |
Jul
(5) |
Aug
(7) |
Sep
(4) |
Oct
(7) |
Nov
|
Dec
(2) |
| 2018 |
Jan
(2) |
Feb
|
Mar
(10) |
Apr
(29) |
May
(13) |
Jun
(4) |
Jul
(3) |
Aug
|
Sep
|
Oct
(14) |
Nov
(6) |
Dec
(2) |
| 2019 |
Jan
(3) |
Feb
|
Mar
(5) |
Apr
(13) |
May
(5) |
Jun
|
Jul
(6) |
Aug
(25) |
Sep
(1) |
Oct
|
Nov
|
Dec
(6) |
| 2020 |
Jan
(10) |
Feb
(8) |
Mar
|
Apr
|
May
(4) |
Jun
(26) |
Jul
(3) |
Aug
(2) |
Sep
|
Oct
|
Nov
|
Dec
(13) |
| 2021 |
Jan
(12) |
Feb
|
Mar
(10) |
Apr
(2) |
May
(21) |
Jun
|
Jul
|
Aug
|
Sep
|
Oct
(14) |
Nov
(14) |
Dec
(6) |
| 2022 |
Jan
(20) |
Feb
(1) |
Mar
(3) |
Apr
(21) |
May
|
Jun
|
Jul
(1) |
Aug
|
Sep
(3) |
Oct
|
Nov
(13) |
Dec
(4) |
| 2023 |
Jan
(3) |
Feb
(15) |
Mar
|
Apr
(4) |
May
(5) |
Jun
|
Jul
(11) |
Aug
(6) |
Sep
(3) |
Oct
|
Nov
|
Dec
(11) |
| 2024 |
Jan
(20) |
Feb
|
Mar
(5) |
Apr
|
May
(3) |
Jun
|
Jul
(5) |
Aug
(8) |
Sep
(8) |
Oct
|
Nov
|
Dec
|
| 2025 |
Jan
|
Feb
(2) |
Mar
(1) |
Apr
(11) |
May
|
Jun
|
Jul
(3) |
Aug
|
Sep
|
Oct
|
Nov
|
Dec
|
|
From: Paul L. <pa...@sq...> - 2021-03-19 07:46:05
|
On Tue, March 16, 2021 6:58 am, Voytek Eymont via squirrelmail-users wrote: > I get certain email from a particular sender that have a header as below, > and, that display as below: (reply based on receiving the actual email itself offlist) > am I correct to say it's sender's fault as mail has HTML only contents, > and, should included text/plain part ? Yes. If you click on "View as HTML" you will see the message (requires view_as_html plugin in 1.4.x). The message text is off center in SM version 1.5.2 due to a namespace clash in the CSS (which I will fix soon), but it's still readable. It displays perfectly in SM version 1.4.23. -- Paul Lesniewski SquirrelMail Team Please support Open Source Software by donating to SquirrelMail! http://squirrelmail.org/donate_paul_lesniewski.php |
|
From: Paul L. <pa...@sq...> - 2021-03-19 06:52:03
|
On Thu, March 18, 2021 12:43 pm, James B. Byrne wrote: > > > On Thu, March 18, 2021 02:00, Paul Lesniewski wrote: >> >> >> On Wed, March 17, 2021 4:48 pm, James B. Byrne via squirrelmail-users >> wrote: >>> Is there a plugin to handle these things? I have a message >>> encapsulated >>> in this format and I cannot extract the contents. Usually I download >>> and >>> extract using the tnef utility, but this time it says that 'Seems not >>> to >>> be a TNEF file'. >> >> It's a normal email message, just a text file with message headers and >> body. If it has the right mime type assigned in the parent message, >> SquirrelMail should handle it just fine. Or download it and open it in >> a >> text editor. >> >> > > First, I was inexact in my initial description. What I have is an .eml > attachment that is a message that was forwarded to me. I do not have the > original message. This is what Squirrelmail displays: [snip] > I can make out the headers even if they are all run together. But the > message > itself is in Base64 and this is not being translated into human readable > text. The person or mailer software that sent it munged the original and that's a problem on their side. You can just plug in the message to a base64 decoder and get the contents. The part you included is the beginning of a HTML formatted message. -- Paul Lesniewski SquirrelMail Team Please support Open Source Software by donating to SquirrelMail! http://squirrelmail.org/donate_paul_lesniewski.php |
|
From: James B. B. <by...@ha...> - 2021-03-18 12:43:56
|
On Thu, March 18, 2021 02:00, Paul Lesniewski wrote: > > > On Wed, March 17, 2021 4:48 pm, James B. Byrne via squirrelmail-users wrote: >> Is there a plugin to handle these things? I have a message encapsulated >> in this format and I cannot extract the contents. Usually I download and >> extract using the tnef utility, but this time it says that 'Seems not to >> be a TNEF file'. > > It's a normal email message, just a text file with message headers and > body. If it has the right mime type assigned in the parent message, > SquirrelMail should handle it just fine. Or download it and open it in a > text editor. > > First, I was inexact in my initial description. What I have is an .eml attachment that is a message that was forwarded to me. I do not have the original message. This is what Squirrelmail displays: Return-Path: Received: from . . . -0500 (EST) DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; d=smtpcorp.com; s=a1-4; h=Feedback-ID:X-Smtpcorp-Track:Message-ID:Subject: Date:To:From:Reply-To:Sender:List-Unsubscribe; bh=C6zADkWAi+q6GmH/jHnmLYDSEpjWbcuEpIYBhmTtXbg=; b=qEvpUTyL+x+NtI6OVfYBWWZPW4 yuDZqjHRpfyxLXNgFpdIOMKfKrS+DjJF/fozujYDjW338nak70RCbbQqgWGcvs4P9fWyavqkXz8Ho L3QQqlpCEN/9ALmAbWJ3/P2plnS6oRJNYXepTCasJxFkaklO/54Y8AUFFNjvtSOm4tF0MdPK61HXu zBWaxjYEyCiuVSRofpmP9umffiw6NnVNi2fH6dRmVvf6AeOF0fjw+IB6z9tO7OVRMREQJuq0/fnbD db82swY38EVMeDEB5LHM+wWRRiA8in3O2/w+YlHKE/5jmnso8PqaoKVTZi9MQTlww+N7m8mDwm6E4 fyKLgXaw==; Received: from [10.127.0.0] (helo=SmtpCorp) by smtpcorp.com with esmtp (Exim 4.92-S2G) (envelope-from ) id 1lJjME-095Eg1-6o for pay...@ha...; Tue, 09 Mar 2021 20:53:34 +0000 Received: from [10.45.79.71] (helo=SmtpCorp) by smtpcorp.com with esmtpsa (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.92-S2G) (envelope-from ) id 1lJjEa-095Fat-3j for pay...@ha...; Tue, 09 Mar 2021 20:45:40 +0000 Received: from [10.35.168.242] (helo=na-smtp03) by smtpcorp.com with esmtp (Exim 4.92-S2G) (envelope-from ) id 1lJjEZ-DuugjF-AJ for pay...@ha...; Tue, 09 Mar 2021 20:45:39 +0000 Received: from ip-0A0A024F (ip-10-10-3-200.ec2.internal [10.10.3.200]) by na-smtp03 (Postfix) with ESMTP id 50AEBBB881 for ; Tue, 9 Mar 2021 15:55:14 -0500 (EST) Received: from ip-0A0A024F ([127.0.0.1]) by ip-0A0A024F with Microsoft SMTPSVC(8.5.9600.16384); Tue, 9 Mar 2021 15:45:38 -0500 MIME-Version: 1.0 From: "LaserAge Support" To: pay...@ha... Date: 9 Mar 2021 15:45:38 -0500 Subject: =?utf-8?B?VGlja2V0IzE0MjUxL3N0YXR1cz0+Q2xvc2VkL0hBUlRFICBM?= =?utf-8?B?WU5FIExJTUlURUQvTGV4bWFyayBUNjMyIOKAkyBTTjogOTkxRzJWUiAs?= =?utf-8?B?IFByaW50ZXIgaXMgZ2l2aW5nIGVycm9yIG1lc3NhZ2UgOTgyIFNlcnZp?= =?utf-8?B?Y2UgRW5naW5lIENPTU0=?= Content-Type: text/html; charset=utf-8 Content-Transfer-Encoding: base64 Message-ID: X-OriginalArrivalTime: 09 Mar 2021 20:45:38.0107 (UTC) FILETIME=[2944D8B0:01D71525] X-Smtpcorp-Track: 1_JMEZDIIgMFjJ.R55yQwlRPKa40 Feedback-ID: 318306m:318306aCCoxYz:318306sEzEybsorq X-Report-Abuse: Please forward a copy of this message, including all headers, to PCFET0NUWVBFIGh0bWwgUFVCTElDICItLy9XM0MvL0RURCBYSFRNTCAxLjAgVHJhbnNp dGlvbmFsLy9FTiIgImh0dHA6Ly93d3cudzMub3JnL1RSL3hodG1sMS9EVEQveGh0bWwx LXRyYW5zaXRpb25hbC5kdGQiPjxodG1sIHhtbG5zPSJodHRwOi8vd3d3LnczLm9yZy8x OTk5L3hodG1sIj48aGVhZD4gICAgPG1ldGEgaHR0cC1lcXVpdj0iQ29udGVudC1UeXBl IiBjb250ZW50PSJ0ZXh0L2h0bWw7IGNoYXJzZXQ9dXRmLTgiIC8+ICAgIDx0aXRsZT48 L3RpdGxlPiAgICA8c3R5bGU+ICAgICAgICBpbWcgeyAgICAgICAgICAgIG1heC13aWR0 aDogNTY4cHg7ICAgICAgICB9ICAgIDwvc3R5bGU+PC9oZWFkPjxib2R5IGNvbnRlbnRF ZGl0YWJsZT0iZmFsc2UiIHVuc2VsZWN0YWJsZT0idHJ1ZSI+DQogICAgPHRhYmxlIGlk PSJuZXdGb3JtYXRFbWFpbCIgc3R5bGU9ImJhY2tncm91bmQtY29sb3I6I2U2ZTZlNjtm b250LWZhbWlseTpSb2JvdG8sQXJpYWwsc2Fucy1zZXJpZiFpbXBvcnRhbnQ7Zm9udC1z aXplOjE0cHg7IiB3aWR0aD0iMTAwJSIgYm9yZGVyPSIwIiBjZWxscGFkZGluZz0iMCIg Y2VsbHNwYWNpbmc9IjAiIGNvbnRlbnRFZGl0YWJsZT0iZmFsc2UiIHVuc2VsZWN0YWJs ZT0idHJ1ZSI+DQogICAgICAgIDx0cj4NCiAgICAgICAgICAgIDx0ZCBzdHlsZT0id2lk dGg6IDEwMCU7Ij4NCiAgICAgICAgICAgICAgICA8dGFibGUgaWQ9InRlbXBsYXRlU2Vj dGlvbiIgYWxpZ249ImNlbnRlciIgc3R5bGU9ImZvbnQtc2l6ZToxNHB4O2JvcmRlcjpu b25lO2JhY2tncm91bmQtY29sb3I6I0ZGRkZGRjttYXJnaW46YXV0bztsaW5lLWhlaWdo . . . I can make out the headers even if they are all run together. But the message itself is in Base64 and this is not being translated into human readable text. -- *** e-Mail is NOT a SECURE channel *** Do NOT transmit sensitive data via e-Mail Unencrypted messages have no legal claim to privacy Do NOT open attachments nor follow links sent by e-Mail James B. Byrne mailto:By...@Ha... Harte & Lyne Limited http://www.harte-lyne.ca 9 Brockley Drive vox: +1 905 561 1241 Hamilton, Ontario fax: +1 905 561 0757 Canada L8E 3C3 |
|
From: Paul L. <pa...@sq...> - 2021-03-18 06:00:48
|
On Wed, March 17, 2021 4:48 pm, James B. Byrne via squirrelmail-users wrote: > Is there a plugin to handle these things? I have a message encapsulated > in this format and I cannot extract the contents. Usually I download and > extract using the tnef utility, but this time it says that 'Seems not to > be a TNEF file'. It's a normal email message, just a text file with message headers and body. If it has the right mime type assigned in the parent message, SquirrelMail should handle it just fine. Or download it and open it in a text editor. |
|
From: James B. B. <by...@ha...> - 2021-03-17 16:48:19
|
Is there a plugin to handle these things? I have a message encapsulated in
this format and I cannot extract the contents. Usually I download and extract
using the tnef utility, but this time it says that 'Seems not to be a TNEF
file'.
--
*** e-Mail is NOT a SECURE channel ***
Do NOT transmit sensitive data via e-Mail
Unencrypted messages have no legal claim to privacy
Do NOT open attachments nor follow links sent by e-Mail
James B. Byrne mailto:By...@Ha...
Harte & Lyne Limited http://www.harte-lyne.ca
9 Brockley Drive vox: +1 905 561 1241
Hamilton, Ontario fax: +1 905 561 0757
Canada L8E 3C3
|
|
From: Paul L. <pa...@sq...> - 2021-03-17 06:31:14
|
On Tue, March 16, 2021 6:58 am, Voytek Eymont via squirrelmail-users wrote: > I get certain email from a particular sender that have a header as below, > and, that display as below: > > am I correct to say it's sender's fault as mail has HTML only contents, > and, should included text/plain part ? It's really hard to know without seeing the unmolested message source. Try sending a sanitized version as an attachment, or feel free to send the original to me offlist (again, as an attachment please) -- Paul Lesniewski SquirrelMail Team Please support Open Source Software by donating to SquirrelMail! http://squirrelmail.org/donate_paul_lesniewski.php > thanks for any advice! > > they render OK on mobile, but, not in SM > > ------------------------------------------------- > You are using SquirrelMail version: 1.5.2 [SVN] > The administrator installed the following plugins: > none installed > > > > header is as so: > ------------------ > ..... > MIME-Version: 1.0 > From: no...@aa... > To: vo...@bb... > Date: Mon, 15 Mar 2021 23:44:04 +0000 > Subject: There is xxxxxxxxxxx. > Content-Type: multipart/related; type="text/html"; > boundary=--boundary_7285_74b538b4-7819-40b0-80ad-a51581d538b5 > Message-ID: > <010...@us...> > X-OriginalArrivalTime: 15 Mar 2021 23:43:57.0824 (UTC) > FILETIME=[11469800:01D719F5] > X-SES-Outgoing: .................................... > Feedback-ID: > 1.us-west-2.jq0LT/01ANRfFMiHXGeSiNIleC9QhAgtglVJNuOnPkM=:AmazonSES > > > displays in SM as so > --------------------------- > > /* Mobile-specific Styles */ > @media only screen and (max-width: 660px) { > table[class=w0], td[class=w0] { width: 0 !important; } > table[class=w10], td[class=w10], img[class=w10] { width:10px !important; } > table[class=w15], td[class=w15], img[class=w15] { width:10px !important; } > table[class=w30], td[class=w30], img[class=w30] { width:10px !important; } > table[class=w60], td[class=w60], img[class=w60] { width:10px !important; } > table[class=w125], td[class=w125], img[class=w125] { width:80px > !important; } > table[class=w130], td[class=w130], img[class=w130] { width:55px > !important; } > table[class=w140], td[class=w140], img[class=w140] { width:90px > !important; } > table[class=w160], td[class=w160], img[class=w160] { width:180px > !important; } > table[class=w170], td[class=w170], img[class=w170] { width:100px > !important; } > table[class=w180], td[class=w180], img[class=w180] { width:80px > !important; } > table[class=w195], td[class=w195], img[class=w195] { width:80px > !important; } > table[class=w220], td[class=w220], img[class=w220] { width:220px > !important; } > table[class=w240], td[class=w240], img[class=w240] { width:180px > !important; } > table[class=w255], td[class=w255], img[class=w255] { width:185px > !important; } > table[class=w275], td[class=w275], img[class=w275] { width:135px > !important; } > table[class=w280], td[class=w280], img[class=w280] { width:135px > !important; } > table[class=w150], td[class=w150], img[class=w150] { width:150px > !important; } > table[class=w325], td[class=w325], img[class=w325] { width:95px > !important; } > table[class=w350], td[class=w350], img[class=w350] { width:70px > !important; } > table[class=w360], td[class=w360], img[class=w360] { width:140px > !important; } > table[class=w410], td[class=w410], img[class=w410] { width:180px > !important; } > table[class=w470], td[class=w470], img[class=w470] { width:200px > !important; } > table[class=w540], td[class=w540], img[class=w540] { width:270px > !important; } > table[class=w570], td[class=w570], img[class=w570] { width:280px > !important; } > table[class=w600], td[class=w600], img[class=w600] { width:300px > !important; } > > #header td {display: block;} > table[class*=hide], td[class*=hide], img[class*=hide], p[class*=hide], > span[class*=hide] { display:none !important; } > table[class=h0], td[class=h0] { height: 0 !important; } > p[class=footer-content-left] { text-align: center !important; } > #headline p { font-size: 30px !important; } > .article-content, #left-sidebar{ -webkit-text-size-adjust: 90% !important; > -ms-text-size-adjust: 90% !important; } > .header-content, .footer-content-left {-webkit-text-size-adjust: 80% > !important; > -ms-text-size-adjust: 80% !important;} > img { height: auto; line-height: 100%;} > #footer span {display: block;} > } > /* Client-specific Styles */ > #outlook a { padding: 0; } /* Force Outlook to provide a "view in > browser" button. */ > body { width: 100% !important; } > ..... > |
|
From: Voytek E. <vo...@sb...> - 2021-03-16 07:13:26
|
I get certain email from a particular sender that have a header as below,
and, that display as below:
am I correct to say it's sender's fault as mail has HTML only contents,
and, should included text/plain part ?
thanks for any advice!
they render OK on mobile, but, not in SM
-------------------------------------------------
You are using SquirrelMail version: 1.5.2 [SVN]
The administrator installed the following plugins:
none installed
header is as so:
------------------
.....
MIME-Version: 1.0
From: no...@aa...
To: vo...@bb...
Date: Mon, 15 Mar 2021 23:44:04 +0000
Subject: There is xxxxxxxxxxx.
Content-Type: multipart/related; type="text/html";
boundary=--boundary_7285_74b538b4-7819-40b0-80ad-a51581d538b5
Message-ID:
<010...@us...>
X-OriginalArrivalTime: 15 Mar 2021 23:43:57.0824 (UTC)
FILETIME=[11469800:01D719F5]
X-SES-Outgoing: ....................................
Feedback-ID:
1.us-west-2.jq0LT/01ANRfFMiHXGeSiNIleC9QhAgtglVJNuOnPkM=:AmazonSES
displays in SM as so
---------------------------
/* Mobile-specific Styles */
@media only screen and (max-width: 660px) {
table[class=w0], td[class=w0] { width: 0 !important; }
table[class=w10], td[class=w10], img[class=w10] { width:10px !important; }
table[class=w15], td[class=w15], img[class=w15] { width:10px !important; }
table[class=w30], td[class=w30], img[class=w30] { width:10px !important; }
table[class=w60], td[class=w60], img[class=w60] { width:10px !important; }
table[class=w125], td[class=w125], img[class=w125] { width:80px !important; }
table[class=w130], td[class=w130], img[class=w130] { width:55px !important; }
table[class=w140], td[class=w140], img[class=w140] { width:90px !important; }
table[class=w160], td[class=w160], img[class=w160] { width:180px
!important; }
table[class=w170], td[class=w170], img[class=w170] { width:100px
!important; }
table[class=w180], td[class=w180], img[class=w180] { width:80px !important; }
table[class=w195], td[class=w195], img[class=w195] { width:80px !important; }
table[class=w220], td[class=w220], img[class=w220] { width:220px
!important; }
table[class=w240], td[class=w240], img[class=w240] { width:180px
!important; }
table[class=w255], td[class=w255], img[class=w255] { width:185px
!important; }
table[class=w275], td[class=w275], img[class=w275] { width:135px
!important; }
table[class=w280], td[class=w280], img[class=w280] { width:135px
!important; }
table[class=w150], td[class=w150], img[class=w150] { width:150px
!important; }
table[class=w325], td[class=w325], img[class=w325] { width:95px !important; }
table[class=w350], td[class=w350], img[class=w350] { width:70px !important; }
table[class=w360], td[class=w360], img[class=w360] { width:140px
!important; }
table[class=w410], td[class=w410], img[class=w410] { width:180px
!important; }
table[class=w470], td[class=w470], img[class=w470] { width:200px
!important; }
table[class=w540], td[class=w540], img[class=w540] { width:270px
!important; }
table[class=w570], td[class=w570], img[class=w570] { width:280px
!important; }
table[class=w600], td[class=w600], img[class=w600] { width:300px
!important; }
#header td {display: block;}
table[class*=hide], td[class*=hide], img[class*=hide], p[class*=hide],
span[class*=hide] { display:none !important; }
table[class=h0], td[class=h0] { height: 0 !important; }
p[class=footer-content-left] { text-align: center !important; }
#headline p { font-size: 30px !important; }
.article-content, #left-sidebar{ -webkit-text-size-adjust: 90% !important;
-ms-text-size-adjust: 90% !important; }
.header-content, .footer-content-left {-webkit-text-size-adjust: 80%
!important;
-ms-text-size-adjust: 80% !important;}
img { height: auto; line-height: 100%;}
#footer span {display: block;}
}
/* Client-specific Styles */
#outlook a { padding: 0; } /* Force Outlook to provide a "view in
browser" button. */
body { width: 100% !important; }
.....
|
|
From: Paul L. <pa...@sq...> - 2021-01-11 16:43:05
|
On Mon, January 11, 2021 11:45 am, David Carvalho wrote: > Hello. > So now I know that Squirrelmail does not work with starttls on port 25. In fact it does. It works on any port that the SMTP server wants to accept its connections on. That does not mean it's a good thing to set up your mail server's submission service on port 25 (it's generally not). STARTTLS was added in version 1.4.23, so maybe your version is out of date. > I’ve changed $smtpPort value to 465 and maintained $use_smtp_tls = true > and $smtp_auth_mech = ‘login’ , but a network traffic inspection shows my > web server always connecting to the smtp server using port 25. SquirrelMail does not ignore your settings. Maybe you have more than one SquirrelMail installation you are mixing up or your configuration settings were never saved. You're going to have to do more sleuthing; this is not normal behavior for SquirrelMail. -- Paul Lesniewski SquirrelMail Team Please support Open Source Software by donating to SquirrelMail! http://squirrelmail.org/donate_paul_lesniewski.php |
|
From: David C. <da...@di...> - 2021-01-11 11:46:06
|
Hello. So now I know that Squirrelmail does not work with starttls on port 25. I’ve changed $smtpPort value to 465 and maintained $use_smtp_tls = true and $smtp_auth_mech = ‘login’ , but a network traffic inspection shows my web server always connecting to the smtp server using port 25. How can I set it to use 465 so that users can authenticate to send e-mails and I can get rid of the RELAY rule on the smtp server ? Thanks and regards. Os melhores cumprimentos David Alexandre M. de Carvalho ═══════════════════ Especialista de Informática Departamento de Informática Universidade da Beira Interior |
|
From: Paul L. <pa...@sq...> - 2021-01-07 18:25:26
|
Please do not top-post. You can review the mailing list posting guidelines if you have questions about how to participate on our mailing lists. >>> >>> Hello and happy new year everyone. >>> I’ve been using Squirrelmail for a long time on 2 of my servers >>> currently >>> running Oracle Linux 6 with version 1.4.22. >> >> I advise upgrading to 1.4.23-svn >> >>> While doing some tests today, I noticed on my Sendmail server, which is >>> different from my web server where Squirrelmail is installed, that it >>> needs the following line in /etc/mail/access in order to be able to >>> send. >>> Connect:ip.squirrelmail RELAY >>> If I remove this line and regenerate access.db squirrelmail complaints >>> about not being able to run “/usr/sbin/sendmail -i -t etc, etc” >> >> That's because Sendmail on the mail server should not allow just anyone to >> relay mail freely through it. The access file is there to say that the >> server running SquirrelMail is trusted to relay mail from. >> >>> My options in config.php are the following: >>> $smtp_auth_mech = 'login'; >>> $imap_auth_mech = 'login'; >> >> This is all about your mail server setup, nothing to do with SquirrelMail. >> If you are requiring SASL login to send mail, then technically, the >> access file/permission on the mail server probably isn't needed, but in >> any case, SquirrelMail will just do what you tell it. >> >>> $smtp_sitewide_user = ''; >>> $smtp_sitewide_pass = ''; >>> $use_imap_tls = true; >>> $use_smtp_tls = true; >>> >>> One test I did was remove the RELAY entry in Sendmail access file and >>> use >>> valid user for fields $smtp_sitewide_user = ''; >>> $smtp_sitewide_pass = ''; >>> But the error is the same. >>> >>> Any ideas please? >> >> Read the logs on the mail server and review what your Sendmail relay >> and/or SASL authentication configuration (client requirements) are. After >> that, configure SquirrelMail to do whatever you choose to require on the >> Sendmail side. >> On Thu, January 7, 2021 9:41 am, David Carvalho wrote: > Hello and thanks for the reply. > I understand about the RELAY. I configured the server myself so that only > authenticated users could send through it. > All clients (windows mail, thunderbird, etc) can send when properly > authenticated. > From what I read, when the fields $smtp_sitewide_user = ''; > $smtp_sitewide_pass = ''; are null, the system should try to use the same > user/pass used in imap settings to be able to send. Yes, if you also have this: $smtp_auth_mech = 'login'; > If entering an existing valid user and password in those fields, shouldn’t > squirrelmail use them to authenticate? > Thanks and best regards. > Your logs should have the answers you need. -- Paul Lesniewski SquirrelMail Team Please support Open Source Software by donating to SquirrelMail! http://squirrelmail.org/donate_paul_lesniewski.php |
|
From: David C. <da...@di...> - 2021-01-07 09:41:29
|
Hello and thanks for the reply. I understand about the RELAY. I configured the server myself so that only authenticated users could send through it. All clients (windows mail, thunderbird, etc) can send when properly authenticated. >From what I read, when the fields $smtp_sitewide_user = ''; $smtp_sitewide_pass = ''; are null, the system should try to use the same user/pass used in imap settings to be able to send. If entering an existing valid user and password in those fields, shouldn’t squirrelmail use them to authenticate? Thanks and best regards. David Carvalho From: Paul Lesniewski Sent: 06 January 2021 18:31 To: Squirrelmail User Support Mailing List Subject: Re: [SM-USERS] RELAY needed in Sendmail for squirrelmail to be ableto send? On Wed, January 6, 2021 5:14 pm, David Carvalho wrote: > > Hello and happy new year everyone. > I’ve been using Squirrelmail for a long time on 2 of my servers currently > running Oracle Linux 6 with version 1.4.22. I advise upgrading to 1.4.23-svn > While doing some tests today, I noticed on my Sendmail server, which is > different from my web server where Squirrelmail is installed, that it > needs the following line in /etc/mail/access in order to be able to send. > Connect:ip.squirrelmail RELAY > If I remove this line and regenerate access.db squirrelmail complaints > about not being able to run “/usr/sbin/sendmail -i -t etc, etc” That's because Sendmail on the mail server should not allow just anyone to relay mail freely through it. The access file is there to say that the server running SquirrelMail is trusted to relay mail from. > My options in config.php are the following: > $smtp_auth_mech = 'login'; > $imap_auth_mech = 'login'; This is all about your mail server setup, nothing to do with SquirrelMail. If you are requiring SASL login to send mail, then technically, the access file/permission on the mail server probably isn't needed, but in any case, SquirrelMail will just do what you tell it. > $smtp_sitewide_user = ''; > $smtp_sitewide_pass = ''; > $use_imap_tls = true; > $use_smtp_tls = true; > > One test I did was remove the RELAY entry in Sendmail access file and use > valid user for fields $smtp_sitewide_user = ''; > $smtp_sitewide_pass = ''; > But the error is the same. > > Any ideas please? Read the logs on the mail server and review what your Sendmail relay and/or SASL authentication configuration (client requirements) are. After that, configure SquirrelMail to do whatever you choose to require on the Sendmail side. -- Paul Lesniewski SquirrelMail Team Please support Open Source Software by donating to SquirrelMail! http://squirrelmail.org/donate_paul_lesniewski.php ----- squirrelmail-users mailing list Posting guidelines: http://squirrelmail.org/postingguidelines List address: squ...@li... List archives: http://news.gmane.org/gmane.mail.squirrelmail.user List info (subscribe/unsubscribe/change options): https://lists.sourceforge.net/lists/listinfo/squirrelmail-users |
|
From: Andrés C. <an...@ch...> - 2021-01-06 19:48:03
|
El Mie, 6 de Enero de 2021, 20:36, Paul Lesniewski escribió: ·· ·· ·· On Wed, January 6, 2021 7:16 pm, "Andrés Chandía" wrote: ··> ··> ··> El Mie, 6 de Enero de 2021, 20:05, "Andrés Chandía" escribió: ··> ·· ··> ·· ··> ·· El Mie, 6 de Enero de 2021, 19:36, Paul Lesniewski escribió: ··> ·· ·· ··> ·· ·· ··> ·· ·· On Wed, January 6, 2021 6:01 pm, "Andrés Chandía" wrote: ··> ·· ··> ··> ·· ··> ··> ·· ··> Still finding some issues, now with the unsafe_image_rules plugin. ··> ·· ··> ··> ·· ··> If I activate ··> ·· ··> this plugin when clicking the link to "See unsafe images" the ··> entire email ··> ·· ··> body ··> ·· ··> desapears, clicking back the "hide unsafe images" shows the email ··> body ··> ·· ··> again. ··> ·· ·· ··> ·· ·· http://squirrelmail.org/docs/admin/admin-11.html#ss11.1 ··> ·· ·· ··> ·· ··> If the plugin is not activated the "see unsafe images" works ok. ··> ·· ·· ··> ·· ·· This makes no sense. If you deactivate the plugin, said feature ··> will be ··> ·· ·· gone. Maybe you have the plugin installed twice or something else ··> quite ··> ·· ·· mixed up. ··> ·· ·· ··> ·· ··> SM 1.4.23 [SVN] ··> ·· ··> Unsafe Image Rules Version 0.8 ··> ·· ·· ··> ·· ··> ·· ··> ·· ··> ·· It does make sense, I'm talking about the "View unsafe images" link ··> that comes from ··> ·· /src/read_body.php ·· ·· Indeed, a bit hasty on my part. ·· ··> ·· Error: Call to undefined function eregi() in ··> ·· /usr/share/squirrelmail/plugins/unsafe_image_rules/functions.php on ·· ·· This is why reviewing the mailing list posting guidelines and including ·· all the information requested is important. ·· ··> in line 335 of ··> /usr/share/squirrelmail/plugins/unsafe_image_rules/functions.php ··> there was: ··> ··> while (eregi('(' . $Email_RegExp_Match . ')', $str, $hits)) { ··> ··> changing it to: ··> while (preg_match('(' . $Email_RegExp_Match . ')', $str, $hits)) { ··> ··> solved the problem ·· ·· That's the right fix. ·· ·· ·· ·· Thanks again Paul , it's just that maybe I did the wrong search because I didn't find it.... anyway, if it helps anybody, I know it is not the right way to do it but in my file /src/read_body.php line 710 I added: echo $download_and_unsafe_link. " | <a href='/plugins/unsafe_image_rules/options.php'>Visualization rules for images</a> "; Thanks again. |
|
From: Paul L. <pa...@sq...> - 2021-01-06 19:37:15
|
On Wed, January 6, 2021 7:16 pm, "Andrés Chandía" wrote: > > > El Mie, 6 de Enero de 2021, 20:05, "Andrés Chandía" escribió: > ·· > ·· > ·· El Mie, 6 de Enero de 2021, 19:36, Paul Lesniewski escribió: > ·· ·· > ·· ·· > ·· ·· On Wed, January 6, 2021 6:01 pm, "Andrés Chandía" wrote: > ·· ··> > ·· ··> > ·· ··> Still finding some issues, now with the unsafe_image_rules plugin. > ·· ··> > ·· ··> If I activate > ·· ··> this plugin when clicking the link to "See unsafe images" the > entire email > ·· ··> body > ·· ··> desapears, clicking back the "hide unsafe images" shows the email > body > ·· ··> again. > ·· ·· > ·· ·· http://squirrelmail.org/docs/admin/admin-11.html#ss11.1 > ·· ·· > ·· ··> If the plugin is not activated the "see unsafe images" works ok. > ·· ·· > ·· ·· This makes no sense. If you deactivate the plugin, said feature > will be > ·· ·· gone. Maybe you have the plugin installed twice or something else > quite > ·· ·· mixed up. > ·· ·· > ·· ··> SM 1.4.23 [SVN] > ·· ··> Unsafe Image Rules Version 0.8 > ·· ·· > ·· > ·· > ·· > ·· It does make sense, I'm talking about the "View unsafe images" link > that comes from > ·· /src/read_body.php Indeed, a bit hasty on my part. > ·· Error: Call to undefined function eregi() in > ·· /usr/share/squirrelmail/plugins/unsafe_image_rules/functions.php on This is why reviewing the mailing list posting guidelines and including all the information requested is important. > in line 335 of > /usr/share/squirrelmail/plugins/unsafe_image_rules/functions.php > there was: > > while (eregi('(' . $Email_RegExp_Match . ')', $str, $hits)) { > > changing it to: > while (preg_match('(' . $Email_RegExp_Match . ')', $str, $hits)) { > > solved the problem That's the right fix. |
|
From: Andrés C. <an...@ch...> - 2021-01-06 19:16:35
|
El Mie, 6 de Enero de 2021, 20:05, "Andrés Chandía" escribió: ·· ·· ·· El Mie, 6 de Enero de 2021, 19:36, Paul Lesniewski escribió: ·· ·· ·· ·· ·· ·· On Wed, January 6, 2021 6:01 pm, "Andrés Chandía" wrote: ·· ··> ·· ··> ·· ··> Still finding some issues, now with the unsafe_image_rules plugin. ·· ··> ·· ··> If I activate ·· ··> this plugin when clicking the link to "See unsafe images" the entire email ·· ··> body ·· ··> desapears, clicking back the "hide unsafe images" shows the email body ·· ··> again. ·· ·· ·· ·· http://squirrelmail.org/docs/admin/admin-11.html#ss11.1 ·· ·· ·· ··> If the plugin is not activated the "see unsafe images" works ok. ·· ·· ·· ·· This makes no sense. If you deactivate the plugin, said feature will be ·· ·· gone. Maybe you have the plugin installed twice or something else quite ·· ·· mixed up. ·· ·· ·· ··> SM 1.4.23 [SVN] ·· ··> Unsafe Image Rules Version 0.8 ·· ·· ·· ·· ·· ·· It does make sense, I'm talking about the "View unsafe images" link that comes from ·· /src/read_body.php file, line 710: "echo $download_and_unsafe_link;" ·· ·· the link created by the previous function when clicked shows an empty body if the plugin ·· "Unsafe Image Rules" is activated ·· ·· README OF THIS PLUGIN SAYS ·· "A user may now build a list of rules that will be used to determine if unsafe ·· images will be shown in HTML messages. If a message matches any of the rules and ·· contains images that would normally be initially hidden, then they are now shown ·· by default." ·· ·· activating php error display I got this: ·· ·· Error: Call to undefined function eregi() in ·· /usr/share/squirrelmail/plugins/unsafe_image_rules/functions.php on line 335 ·· Call Stack ·· # Time Memory Function Location ·· 1 0.0070 377968 {main}( ) .../read_body.php:0 ·· 2 0.5840 1474472 formatEnvheader( ) .../read_body.php:875 ·· 3 0.5920 1544800 formatToolbar( ) .../read_body.php:517 ·· 4 0.5921 1545864 do_hook( ) .../read_body.php:713 ·· 5 0.5963 1588688 unsafe_image_rules_link( ) .../plugin.php:52 ·· 6 0.5963 1588688 unsafe_image_rules_link_do( ) .../setup.php:40 ·· 7 0.5963 1588912 unsafe_image_rules_link_array( ) .../functions.php:378 ·· 8 0.5963 1588992 unsafe_image_rules_link_string( ) .../functions.php:350 ·· ·· Thanks again Paul! ·· ·· andrés chandía in line 335 of /usr/share/squirrelmail/plugins/unsafe_image_rules/functions.php there was: while (eregi('(' . $Email_RegExp_Match . ')', $str, $hits)) { changing it to: while (preg_match('(' . $Email_RegExp_Match . ')', $str, $hits)) { solved the problem Thanks! |
|
From: Andrés C. <an...@ch...> - 2021-01-06 19:05:42
|
El Mie, 6 de Enero de 2021, 19:36, Paul Lesniewski escribió: ·· ·· ·· On Wed, January 6, 2021 6:01 pm, "Andrés Chandía" wrote: ··> ··> ··> Still finding some issues, now with the unsafe_image_rules plugin. ··> ··> If I activate ··> this plugin when clicking the link to "See unsafe images" the entire email ··> body ··> desapears, clicking back the "hide unsafe images" shows the email body ··> again. ·· ·· http://squirrelmail.org/docs/admin/admin-11.html#ss11.1 ·· ··> If the plugin is not activated the "see unsafe images" works ok. ·· ·· This makes no sense. If you deactivate the plugin, said feature will be ·· gone. Maybe you have the plugin installed twice or something else quite ·· mixed up. ·· ··> SM 1.4.23 [SVN] ··> Unsafe Image Rules Version 0.8 ·· It does make sense, I'm talking about the "View unsafe images" link that comes from /src/read_body.php file, line 710: "echo $download_and_unsafe_link;" the link created by the previous function when clicked shows an empty body if the plugin "Unsafe Image Rules" is activated README OF THIS PLUGIN SAYS "A user may now build a list of rules that will be used to determine if unsafe images will be shown in HTML messages. If a message matches any of the rules and contains images that would normally be initially hidden, then they are now shown by default." activating php error display I got this: Error: Call to undefined function eregi() in /usr/share/squirrelmail/plugins/unsafe_image_rules/functions.php on line 335 Call Stack # Time Memory Function Location 1 0.0070 377968 {main}( ) .../read_body.php:0 2 0.5840 1474472 formatEnvheader( ) .../read_body.php:875 3 0.5920 1544800 formatToolbar( ) .../read_body.php:517 4 0.5921 1545864 do_hook( ) .../read_body.php:713 5 0.5963 1588688 unsafe_image_rules_link( ) .../plugin.php:52 6 0.5963 1588688 unsafe_image_rules_link_do( ) .../setup.php:40 7 0.5963 1588912 unsafe_image_rules_link_array( ) .../functions.php:378 8 0.5963 1588992 unsafe_image_rules_link_string( ) .../functions.php:350 Thanks again Paul! andrés chandía |
|
From: Paul L. <pa...@sq...> - 2021-01-06 18:37:10
|
On Wed, January 6, 2021 6:01 pm, "Andrés Chandía" wrote: > > > Still finding some issues, now with the unsafe_image_rules plugin. > > If I activate > this plugin when clicking the link to "See unsafe images" the entire email > body > desapears, clicking back the "hide unsafe images" shows the email body > again. http://squirrelmail.org/docs/admin/admin-11.html#ss11.1 > If the plugin is not activated the "see unsafe images" works ok. This makes no sense. If you deactivate the plugin, said feature will be gone. Maybe you have the plugin installed twice or something else quite mixed up. > SM 1.4.23 [SVN] > Unsafe Image Rules Version 0.8 -- Paul Lesniewski SquirrelMail Team Please support Open Source Software by donating to SquirrelMail! http://squirrelmail.org/donate_paul_lesniewski.php |
|
From: Paul L. <pa...@sq...> - 2021-01-06 18:30:55
|
On Wed, January 6, 2021 5:14 pm, David Carvalho wrote: > > Hello and happy new year everyone. > I’ve been using Squirrelmail for a long time on 2 of my servers currently > running Oracle Linux 6 with version 1.4.22. I advise upgrading to 1.4.23-svn > While doing some tests today, I noticed on my Sendmail server, which is > different from my web server where Squirrelmail is installed, that it > needs the following line in /etc/mail/access in order to be able to send. > Connect:ip.squirrelmail RELAY > If I remove this line and regenerate access.db squirrelmail complaints > about not being able to run “/usr/sbin/sendmail -i -t etc, etc” That's because Sendmail on the mail server should not allow just anyone to relay mail freely through it. The access file is there to say that the server running SquirrelMail is trusted to relay mail from. > My options in config.php are the following: > $smtp_auth_mech = 'login'; > $imap_auth_mech = 'login'; This is all about your mail server setup, nothing to do with SquirrelMail. If you are requiring SASL login to send mail, then technically, the access file/permission on the mail server probably isn't needed, but in any case, SquirrelMail will just do what you tell it. > $smtp_sitewide_user = ''; > $smtp_sitewide_pass = ''; > $use_imap_tls = true; > $use_smtp_tls = true; > > One test I did was remove the RELAY entry in Sendmail access file and use > valid user for fields $smtp_sitewide_user = ''; > $smtp_sitewide_pass = ''; > But the error is the same. > > Any ideas please? Read the logs on the mail server and review what your Sendmail relay and/or SASL authentication configuration (client requirements) are. After that, configure SquirrelMail to do whatever you choose to require on the Sendmail side. -- Paul Lesniewski SquirrelMail Team Please support Open Source Software by donating to SquirrelMail! http://squirrelmail.org/donate_paul_lesniewski.php |
|
From: David C. <da...@di...> - 2021-01-06 18:18:44
|
Hello and happy new year everyone. I’ve been using Squirrelmail for a long time on 2 of my servers currently running Oracle Linux 6 with version 1.4.22. While doing some tests today, I noticed on my Sendmail server, which is different from my web server where Squirrelmail is installed, that it needs the following line in /etc/mail/access in order to be able to send. Connect:ip.squirrelmail RELAY If I remove this line and regenerate access.db squirrelmail complaints about not being able to run “/usr/sbin/sendmail -i -t etc, etc” My options in config.php are the following: $smtp_auth_mech = 'login'; $imap_auth_mech = 'login'; $smtp_sitewide_user = ''; $smtp_sitewide_pass = ''; $use_imap_tls = true; $use_smtp_tls = true; One test I did was remove the RELAY entry in Sendmail access file and use valid user for fields $smtp_sitewide_user = ''; $smtp_sitewide_pass = ''; But the error is the same. Any ideas please? Os melhores cumprimentos David Alexandre M. de Carvalho ═══════════════════ Especialista de Informática Departamento de Informática Universidade da Beira Interior |
|
From: Andrés C. <an...@ch...> - 2021-01-06 18:02:21
|
Still finding some issues, now with the unsafe_image_rules plugin. If I activate this plugin when clicking the link to "See unsafe images" the entire email body desapears, clicking back the "hide unsafe images" shows the email body again. If the plugin is not activated the "see unsafe images" works ok. SM 1.4.23 [SVN] Unsafe Image Rules Version 0.8 _______________________             andrés chandÃa Düngupeyem | IECMap | ISECMap | NMT | Corlexim Desarrollador de: Parles.upf | IWCH | Amind terapia | ONG Mapuche koyaktu | Nocando | IAC | CddZ | ISAC | CatCg P No imprima innecesariamente. ¡Cuide el medio ambiente! |
|
From: Andrés C. <an...@ch...> - 2020-12-31 14:09:36
|
El Mie, 30 de Diciembre de 2020, 4:50, Paul Lesniewski escribió: ··> Thanks Paul, latest svn stable version did the trick, eventhough I still ··> have two minor problems, ··> ··> 1. image buttons have desapeared, I can enable and disable the plugin but ··> icons don't show ·· ·· What image button? ·· ··> 2. If my mail composition preference is the html format, when answering a ··> txt format received ··> mail the text from the original message is not recovered, I have to change ··> the setting... ··> ··> Default Email Composition Format: Plain Text ··> ··> to get the text from the message I'm answering into the response. ··> On the contrary, this does not happen with the mails that were sent to me ··> in html format. ··> ··> Some advice? ·· ·· Maybe follow the posting guidelines? You have to post details about what ·· you installed and give us more to go on. ·· Hi there, it seems that the issue about encoding is not totally solved, for some emails I'm getting : 1.* OK [ALERT] Message 1 appears to be a Unicode message and your E-mail reader did not enable Unicode support. Please use an E-mail reader that supports IMAP with UTF-8 (see https://tools.ietf.org/html/rfc6855.html) both the subject and the body contain: aprobación <br />_______________________<br /> andrés chandía |
|
From: Andrés C. <an...@ch...> - 2020-12-30 13:02:02
|
El Mie, 30 de Diciembre de 2020, 4:50, Paul Lesniewski escribió: ··> Thanks Paul, latest svn stable version did the trick, eventhough I still ··> have two minor problems, ··> ··> 1. image buttons have desapeared, I can enable and disable the plugin but ··> icons don't show ·· ·· What image button? ·· ··> 2. If my mail composition preference is the html format, when answering a ··> txt format received ··> mail the text from the original message is not recovered, I have to change ··> the setting... ··> ··> Default Email Composition Format: Plain Text ··> ··> to get the text from the message I'm answering into the response. ··> On the contrary, this does not happen with the mails that were sent to me ··> in html format. ··> ··> Some advice? ·· ·· Maybe follow the posting guidelines? You have to post details about what ·· you installed and give us more to go on. ·· Ok, image_buttons plugin working again, I had to run the patch again and that did it... The installed SM I have is 1.4.23 [SVN] from Stable version Subversion source code repository access svn checkout https://svn.code.sf.net/p/squirrelmail/code/branches/SM-1_4-STABLE/squirrelmail Related plugins: HTML Mail plugin for SquirrelMail Ver 2.3, 2005/10/15 view_as_html 3.8 <br />_______________________<br /> andrés chandía |
|
From: Paul L. <pa...@sq...> - 2020-12-30 03:51:08
|
> Thanks Paul, latest svn stable version did the trick, eventhough I still > have two minor problems, > > 1. image buttons have desapeared, I can enable and disable the plugin but > icons don't show What image button? > 2. If my mail composition preference is the html format, when answering a > txt format received > mail the text from the original message is not recovered, I have to change > the setting... > > Default Email Composition Format: Plain Text > > to get the text from the message I'm answering into the response. > On the contrary, this does not happen with the mails that were sent to me > in html format. > > Some advice? Maybe follow the posting guidelines? You have to post details about what you installed and give us more to go on. -- Paul Lesniewski SquirrelMail Team Please support Open Source Software by donating to SquirrelMail! http://squirrelmail.org/donate_paul_lesniewski.php |
|
From: Andrés C. <an...@ch...> - 2020-12-29 20:50:03
|
El Mar, 29 de Diciembre de 2020, 18:31, Paul Lesniewski escribió: ·· ·· ·· On Tue, December 29, 2020 2:54 pm, "Andrés Chandía" wrote: ·· >> ·· > Thanks for your advice Atoth, ·· > I've found at least 4 patches in the thread you sent me, but I think you ·· > refer to this one: ·· > ·· > quoted_printable_fix-1.4.x-version_3.diff ·· > ·· > I tried to apply it, but it always got rejected, so I checked the ·· > implicated files ·· > functions/i18n.php and functions/strings.php, and I have found that they ·· > already had what the ·· > patch was applying, exept that in file functions/strings.php there was a ·· > section not included ·· > which I included manually, but there was no imporvement anyway. ·· ·· This is always a bad sign and no one can really help you when it becomes ·· that messy. ·· ·· > Actually as you can see in ·· > this mail nor even what you wrote to me is recovered in the reply. ·· ·· <snip> ·· ·· > here are the packages I have installed: ·· > ·· > squirrelmail_1.4.23~svn20120406-2ubuntu1_all.deb ·· ·· This could easily be the problem. Please start over with a svn snapshot ·· build from our downloads page instead. ·· Thanks Paul, latest svn stable version did the trick, eventhough I still have two minor problems, 1. image buttons have desapeared, I can enable and disable the plugin but icons don't show 2. If my mail composition preference is the html format, when answering a txt format received mail the text from the original message is not recovered, I have to change the setting... Default Email Composition Format: Plain Text to get the text from the message I'm answering into the response. On the contrary, this does not happen with the mails that were sent to me in html format. Some advice? Thanks again.... <br />_______________________<br /> andrés chandía |
|
From: Paul L. <pa...@sq...> - 2020-12-29 17:32:17
|
On Tue, December 29, 2020 2:54 pm, "Andrés Chandía" wrote: >> > Thanks for your advice Atoth, > I've found at least 4 patches in the thread you sent me, but I think you > refer to this one: > > quoted_printable_fix-1.4.x-version_3.diff > > I tried to apply it, but it always got rejected, so I checked the > implicated files > functions/i18n.php and functions/strings.php, and I have found that they > already had what the > patch was applying, exept that in file functions/strings.php there was a > section not included > which I included manually, but there was no imporvement anyway. This is always a bad sign and no one can really help you when it becomes that messy. > Actually as you can see in > this mail nor even what you wrote to me is recovered in the reply. <snip> > here are the packages I have installed: > > squirrelmail_1.4.23~svn20120406-2ubuntu1_all.deb This could easily be the problem. Please start over with a svn snapshot build from our downloads page instead. -- Paul Lesniewski SquirrelMail Team Please support Open Source Software by donating to SquirrelMail! http://squirrelmail.org/donate_paul_lesniewski.php > squirrelmail-compatibility_2.0.16-1_all.deb > squirrelmail-decode_1.2-1ubuntu1_all.deb > squirrelmail-locales_1.4.18-20090526-1_all.deb > squirrelmail-lockout_1.7-2_all.deb > squirrelmail-logger_2.3.1-1_all.deb > squirrelmail-quicksave_2.4.5-1_all.deb > squirrelmail-secure-login_1.4-3_all.deb > squirrelmail-sent-confirmation_1.6-2_all.deb > squirrelmail-spam-buttons_2.3.1-1_all.deb > squirrelmail-viewashtml_3.8-3_all.deb > |
|
From: Tóth A. <at...@at...> - 2020-12-29 17:11:56
|
Dear Andrés,
2020.December 29.(K) 15:54 időpontban "Andrés Chandía" ezt írta:
>>
> Thanks for your advice Atoth,
> I've found at least 4 patches in the thread you sent me, but I think you
> refer to this one:
>
> quoted_printable_fix-1.4.x-version_3.diff
>
> I tried to apply it, but it always got rejected, so I checked the
> implicated files
> functions/i18n.php and functions/strings.php, and I have found that they
> already had what the
> patch was applying, exept that in file functions/strings.php there was a
> section not included
> which I included manually, but there was no imporvement anyway. Actually
> as you can see in
> this mail nor even what you wrote to me is recovered in the reply.
You may not have the problem represented by the referenced bug.
Nevertheless, it would be beneficial, if you could reproduce your symptoms
with a recent snapshot.
BR: Dw.
--
dr Tóth Attila, Radiológus, 06-20-825-8057
Attila Toth MD, Radiologist, +36-20-825-8057
>
>
> +
> + // make sure htmlspecialchars() supports the needed encoding
> + //
> + if (!in_array(strtolower($encoding), $htmlspecialchars_charsets))
> + {
> + // use default from configuration if provided or hard-coded
> fallback
> + //
> + global $default_htmlspecialchars_encoding;
> + if (!empty($default_htmlspecialchars_encoding))
> + $encoding = $default_htmlspecialchars_encoding;
> + else
> + $encoding = 'iso-8859-1';
> + }
> +
> +
>
> here are the packages I have installed:
>
> squirrelmail_1.4.23~svn20120406-2ubuntu1_all.deb
> squirrelmail-compatibility_2.0.16-1_all.deb
> squirrelmail-decode_1.2-1ubuntu1_all.deb
> squirrelmail-locales_1.4.18-20090526-1_all.deb
> squirrelmail-lockout_1.7-2_all.deb
> squirrelmail-logger_2.3.1-1_all.deb
> squirrelmail-quicksave_2.4.5-1_all.deb
> squirrelmail-secure-login_1.4-3_all.deb
> squirrelmail-sent-confirmation_1.6-2_all.deb
> squirrelmail-spam-buttons_2.3.1-1_all.deb
> squirrelmail-viewashtml_3.8-3_all.deb
>
>
>
|
238 messages has been excluded from this view by a project administrator.
