Screenshot instructions:
Windows
Mac
Red Hat Linux
Ubuntu
Click URL instructions:
Right-click on ad, choose "Copy Link", then paste here →
(This may not be possible with some types of ads)
You can subscribe to this list here.
1999 |
Jan
|
Feb
|
Mar
|
Apr
|
May
|
Jun
|
Jul
|
Aug
|
Sep
|
Oct
|
Nov
|
Dec
(20) |
---|---|---|---|---|---|---|---|---|---|---|---|---|
2000 |
Jan
(96) |
Feb
(124) |
Mar
(196) |
Apr
(169) |
May
(63) |
Jun
(230) |
Jul
(182) |
Aug
(247) |
Sep
(143) |
Oct
(153) |
Nov
(156) |
Dec
(162) |
2001 |
Jan
(399) |
Feb
(206) |
Mar
(50) |
Apr
(115) |
May
(111) |
Jun
(139) |
Jul
(153) |
Aug
(149) |
Sep
(225) |
Oct
(263) |
Nov
(90) |
Dec
(344) |
2002 |
Jan
(475) |
Feb
(303) |
Mar
(278) |
Apr
(339) |
May
(188) |
Jun
(95) |
Jul
(145) |
Aug
(277) |
Sep
(277) |
Oct
(306) |
Nov
(190) |
Dec
(153) |
2003 |
Jan
(179) |
Feb
(213) |
Mar
(126) |
Apr
(201) |
May
(85) |
Jun
(207) |
Jul
(205) |
Aug
(175) |
Sep
(226) |
Oct
(176) |
Nov
(79) |
Dec
(115) |
2004 |
Jan
(86) |
Feb
(112) |
Mar
(129) |
Apr
(185) |
May
(153) |
Jun
(157) |
Jul
(89) |
Aug
(182) |
Sep
(98) |
Oct
(105) |
Nov
(115) |
Dec
(90) |
2005 |
Jan
(61) |
Feb
(154) |
Mar
(239) |
Apr
(265) |
May
(80) |
Jun
(96) |
Jul
(118) |
Aug
(129) |
Sep
(74) |
Oct
(81) |
Nov
(261) |
Dec
(121) |
2006 |
Jan
(137) |
Feb
(204) |
Mar
(99) |
Apr
(45) |
May
(68) |
Jun
(51) |
Jul
(109) |
Aug
(56) |
Sep
(146) |
Oct
(229) |
Nov
(93) |
Dec
(47) |
2007 |
Jan
(127) |
Feb
(102) |
Mar
(89) |
Apr
(60) |
May
(41) |
Jun
(56) |
Jul
(139) |
Aug
(51) |
Sep
(51) |
Oct
(52) |
Nov
(110) |
Dec
(57) |
2008 |
Jan
(91) |
Feb
(53) |
Mar
(80) |
Apr
(57) |
May
(69) |
Jun
(36) |
Jul
(33) |
Aug
(29) |
Sep
(15) |
Oct
(13) |
Nov
(19) |
Dec
(18) |
2009 |
Jan
(15) |
Feb
(10) |
Mar
(16) |
Apr
(3) |
May
(15) |
Jun
(29) |
Jul
(30) |
Aug
(24) |
Sep
(27) |
Oct
(8) |
Nov
(14) |
Dec
(34) |
2010 |
Jan
(31) |
Feb
(34) |
Mar
(19) |
Apr
(16) |
May
(6) |
Jun
(17) |
Jul
(2) |
Aug
|
Sep
|
Oct
(2) |
Nov
(2) |
Dec
(2) |
2011 |
Jan
(7) |
Feb
(4) |
Mar
|
Apr
(14) |
May
(1) |
Jun
(1) |
Jul
(6) |
Aug
(2) |
Sep
(8) |
Oct
(4) |
Nov
(3) |
Dec
(10) |
2012 |
Jan
(18) |
Feb
(27) |
Mar
(11) |
Apr
|
May
(2) |
Jun
|
Jul
(2) |
Aug
(21) |
Sep
(4) |
Oct
(10) |
Nov
(7) |
Dec
(2) |
2013 |
Jan
(1) |
Feb
(7) |
Mar
(4) |
Apr
(1) |
May
(3) |
Jun
(11) |
Jul
|
Aug
(1) |
Sep
|
Oct
(5) |
Nov
(2) |
Dec
(8) |
2014 |
Jan
(10) |
Feb
|
Mar
(1) |
Apr
(1) |
May
|
Jun
|
Jul
|
Aug
|
Sep
(1) |
Oct
(1) |
Nov
(1) |
Dec
|
2015 |
Jan
(2) |
Feb
(1) |
Mar
|
Apr
|
May
|
Jun
|
Jul
|
Aug
|
Sep
|
Oct
|
Nov
(1) |
Dec
(2) |
2016 |
Jan
|
Feb
|
Mar
|
Apr
(2) |
May
(3) |
Jun
(2) |
Jul
(1) |
Aug
|
Sep
|
Oct
(1) |
Nov
(1) |
Dec
(34) |
2017 |
Jan
(1) |
Feb
(2) |
Mar
(6) |
Apr
|
May
|
Jun
|
Jul
|
Aug
|
Sep
|
Oct
|
Nov
|
Dec
(2) |
S | M | T | W | T | F | S |
---|---|---|---|---|---|---|
|
1
(3) |
2
(11) |
3
(13) |
4
(8) |
5
(9) |
6
|
7
(1) |
8
(11) |
9
(3) |
10
(6) |
11
(2) |
12
(3) |
13
(1) |
14
|
15
(7) |
16
(1) |
17
|
18
(2) |
19
|
20
|
21
(1) |
22
|
23
(7) |
24
(8) |
25
(4) |
26
(4) |
27
|
28
|
29
(4) |
30
(11) |
31
(9) |
|
|
|
From: Fredrik Jervfors <sqm_admin@fi...> - 2004-03-24 23:40:43
|
>>>> First of all, the issue of the 'Bypass Trash' link in >>>> read_body.php being only a link, and easy to accidentally click. >>>> This should *definitely* be changed, though to what is a tricky >>>> question. All of the other message operators in that area are >>>> links, so having one button would be weird. >>> >>> Make it a check box. If the box is checked, and you hit delete, >>> then you remove permanently... that makes it a 2 step process >>> instead of just one. >> >> Check box does not work with GET request (links). Not sure if >> javascript popups (Compose/Reply/Forward in a new window) work with >> POST (buttons). >> >> If "[delete] {} don't store in trash" is button, it would have to be >> moved to the right in order to have UI consistency. > > I was thinking of the other "Bypass trash" option, which i noticed is > already a check box... guess it'd be helpful if we were all on the > right page (read_body instead of mailbox) ;) Another way of doing this: 1. User tries to move a mail to the trashcan. 2. If it works, goto 7. 3. Open page in right frame saying "Mail is to big to fit in trashcan. Do you want to [Delete mail] [Empty trashcan] [Cancel]?" 4. If [Delete]: mark mail for deletion, expunge. Goto 7. 5. If [Empty trashcan]: Empty trashcan, move mail. Goto 7. 6. If [Cancel]: Nothing happens. 7. Problem solved. What are the arguments for and against a solution like the above? Or did I completly misunderstand anything? Sincerly, Fredrik. |
From: Jonathan Angliss <jon@sq...> - 2004-03-24 17:11:01
|
Hello Tomas, On Wednesday, March 24, 2004, Tomas Kuliavas wrote... >>> First of all, the issue of the 'Bypass Trash' link in >>> read_body.php being only a link, and easy to accidentally click. >>> This should *definitely* be changed, though to what is a tricky >>> question. All of the other message operators in that area are >>> links, so having one button would be weird. >> Make it a check box. If the box is checked, and you hit delete, >> then you remove permanently... that makes it a 2 step process >> instead of just one. > Check box does not work with GET request (links). Not sure if > javascript popups (Compose/Reply/Forward in a new window) work with > POST (buttons). > If "[delete] {} don't store in trash" is button, it would have to be > moved to the right in order to have UI consistency. I was thinking of the other "Bypass trash" option, which i noticed is already a check box... guess it'd be helpful if we were all on the right page (read_body instead of mailbox) ;) -- Jonathan Angliss (jon@...) Posting Hints: http://article.gmane.org/gmane.mail.squirrelmail.user/16718 |
From: Tomas Kuliavas <tokul@us...> - 2004-03-24 16:42:12
|
>> First of all, the issue of the 'Bypass Trash' link in read_body.php >> being only a link, and easy to accidentally click. This should >> *definitely* be changed, though to what is a tricky question. All of >> the other message operators in that area are links, so having one >> button would be weird. > > Make it a check box. If the box is checked, and you hit delete, then > you remove permanently... that makes it a 2 step process instead of > just one. Check box does not work with GET request (links). Not sure if javascript popups (Compose/Reply/Forward in a new window) work with POST (buttons). If "[delete] {} don't store in trash" is button, it would have to be moved to the right in order to have UI consistency. -- Tomas |
From: Jonathan Angliss <jon@sq...> - 2004-03-24 16:13:24
|
Hello Joshua, On Wednesday, March 24, 2004, Joshua Jabbour wrote... > So, I think there are two issues here... >> I wouldn't make it a user preference, I'd rather it matched the UI >> of the message list. In other words, not a link, but a checkbox >> modifier for the regular Delete link. > First of all, the issue of the 'Bypass Trash' link in read_body.php > being only a link, and easy to accidentally click. This should > *definitely* be changed, though to what is a tricky question. All of > the other message operators in that area are links, so having one > button would be weird. Make it a check box. If the box is checked, and you hit delete, then you remove permanently... that makes it a 2 step process instead of just one. > Second issue, that being the ability to disable the entire feature of > 'Bypass Trash'. That should be easy. > [..] If I really need to get rid of a message, I go into the Trash > folder, and Delete the message from there. Then it's gone. True, a > two-stepped process (but a better one than the other solutions I've > heard of turning off the preference for 'Move to Trash' and then > turning it back on...). However, your two step solution doesn't work if the user is over quota, which I believe was one of the main reasons the option to bypass trash was introduced in the first place. > On another note, as I mentioned before, I have simply commented out > the 'Bypass Trash' lines as shown below. Is there any reason that > having this commented out, but still existing in the Delete > functions, would be a problem? (i.e. is just commenting the 3 lines > below fine and dandy?) No, because it just means nothing gets passed on to tell it to be permanently deleted, so the code never runs. It should be fine. -- Jonathan Angliss (jon@...) Posting Hints: http://article.gmane.org/gmane.mail.squirrelmail.user/16718 |
From: William Hooper <whooperhsd2@ea...> - 2004-03-24 15:07:00
|
Joshua Jabbour said: > If I really need to get rid of > a message, I go into the Trash folder, and Delete the message from > there. Then it's gone. True, a two-stepped process (but a better one > than the other solutions I've heard of turning off the preference for > 'Move to Trash' and then turning it back on...). IIUC the "Bypass Trash" was implemented for the issue with large mails and a quota. Since "Move" is really "Copy then delete", large messages might not be deletable (is that a word?) when using the trash. This is probably the context that you see the preference changing mentioned in. -- William Hooper |
From: Marc Groot Koerkamp <marc@sq...> - 2004-03-24 13:40:01
|
Hello, I was thinking about the way we render html mail inside read_body.php and came to the conclusion that we should embed the html mail as object. The object tag is part of the html 4 spec and is supported by: MSIE 3.0 MOZ 1.0 NN 4.0 OP 4.0 The reason for this is the existence of STYLE tags, which must be located in the header of an html document, inside html mail. Of course we can rewrite the entire html email and revert to style attributes but using th= e OBJECT tag is much cleaner and easier. This raises a few questions, namely: 1) Are there browsers around which cannot handle this. 2) If yes, does that bother us ? (SquirrelMail supports HTML 4, we do not say we support older HTML specifications) 3) Do we need browser detection and simply drop style tags if we cannot make use of object embedding because the detected browser does not suppor= t it? 4) Are there better alternatives? Regards, Marc Groot Koerkamp. |
From: Joshua Jabbour <lists@wa...> - 2004-03-24 09:06:35
|
So, I think there are two issues here... >I wouldn't make it a user preference, I'd rather it matched the UI of the >message list. In other words, not a link, but a checkbox modifier for the >regular Delete link. First of all, the issue of the 'Bypass Trash' link in read_body.php being only a link, and easy to accidentally click. This should *definitely* be changed, though to what is a tricky question. All of the other message operators in that area are links, so having one button would be weird. Second issue, that being the ability to disable the entire feature of 'Bypass Trash'. I personally don't use it, and think many other people would like to be able to get rid of it. (It may not be a problem if we can solve issue one from above, but even then is the issue of having another button there that I'd probably never use.) I like having my Deleted msgs sent to the Trash for a week to cool off; I've pulled many accidentally-deleted msgs out of there. If I really need to get rid of a message, I go into the Trash folder, and Delete the message from there. Then it's gone. True, a two-stepped process (but a better one than the other solutions I've heard of turning off the preference for 'Move to Trash' and then turning it back on...). Anyway, I like the extra confirmation of the two-step process. Many people would agree, I think. If not, then they could enable 'Bypass Trash' in the (hopefully-implemented) preference) On another note, as I mentioned before, I have simply commented out the 'Bypass Trash' lines as shown below. Is there any reason that having this commented out, but still existing in the Delete functions, would be a problem? (i.e. is just commenting the 3 lines below fine and dandy?) read_body.php // $delete_link .= ' (<a href="' . $delete_url.'&bypass_trash=1">' // ._("Bypass Trash").'</a>)'; mailbox_display.php // echo '<input type="checkbox" name="bypass_trash">' . _("Bypass Trash"); -j |
From: Gustav Foseid <gustavf-squirrel@in...> - 2004-03-24 08:00:56
|
Marc Groot Koerkamp: > What Squirrelmail always did (as far as I know) is downloading the > complete header list for a mailbox in order to achieve client side > sorting. As a vintage developer I think I can confirm that (although I never worked on that part of the code). However, it is still as inefficient as it has always been. -- Gustav Foseid, Initio IT-løsninger AS http://www.initio.no/ |