#148 Feature regression - Dont display file date in list views


Im having problems with the displayed date of emails - in the list view the file date was displayed whereas in detail view the correct date was displayed - I did some testing today with SM 1.4. and SM 1.5. and I found out that this is a problem of 1.5. (I downloaded the squirrelmail-20090428_0000-SVN.devel file) - in 1.4 the date is displayed correctly whereas in 1.5. the file date is displayed

I already reported that in the IRC chat:

<andreas_> is this issue already known or is there a workaround available?
<TruckStuff> andreas_: that might be a change in behavior between 1.4 and 1.5, but it is still up to your IMAP server to report the date recieved correctly
<andreas_> ok - but for the end-user (me :-) ) it seems that this is a feature regression - so perhaps the behavior from 1.4 could also be implemented in 1.5?
<TruckStuff> perhaps, but end users differ in their opinion as to which date should be displayed there
<TruckStuff> either way, the core of your problem is still the timestamps on the files in your Maildirs
<andreas_> ok - perhaps this could be implemented and selectable as option in the option menu?
<TruckStuff> sure


  • Paul Lesniewski

    Paul Lesniewski - 2009-04-29

    You didn't include any details that can help narrow down the problem. For starters, we need to know the details of your IMAP server. Then, you need to send the full message source of an offending message (and which dates are shown in each version). You can use the message details plugin to get the full message source or just include the file itself if you know where to find it.

  • Paul Lesniewski

    Paul Lesniewski - 2009-04-29
    • status: open --> pending
  • andreas_rth

    andreas_rth - 2009-04-29

    I'm using courier-imapd-ssl (4.3.0. 200810271-ubuntu1).

    In SM 1.4. the correct date ( Feb 3, 2009 ) is displayed in SM 1.5 the file date (Apr 12, 2009) is displayed - this is the source of the mail (but all other mails are effected as well):

    Message-ID: <4988A8F9.8070507@24speed.at>
    Date: Tue, 03 Feb 2009 21:28:41 +0100
    From: x@y.z
    Reply-To: x@y.z
    User-Agent: Thunderbird (X11/20090105)
    MIME-Version: 1.0
    To: x@y.z
    Subject: as
    Content-Type: text/plain; charset=ISO-8859-15; format=flowed
    Content-Transfer-Encoding: 7bit


  • andreas_rth

    andreas_rth - 2009-04-29
    • status: pending --> open
  • Paul Lesniewski

    Paul Lesniewski - 2009-04-29
    • status: open --> closed-rejected
  • Paul Lesniewski

    Paul Lesniewski - 2009-04-29

    SquirrelMail 1.5 displays and sorts mail using the INTERNALDATE given by the IMAP server, which is exactly the file date under most circumstances. This is because caching headers for large mailboxes is much, much faster when just stat'ing files compared to opening each file and parsing out the Date header. The only reason that date would be wrong would be if you manually altered the file for some message - otherwise the file's date should correspond to its date of delivery ("Received Date").

  • andreas_rth

    andreas_rth - 2009-04-29

    I can understand that but I have 2 comments:

    1. The file date was changed since I was forced to move my mail server and had to copy all the files (what changed the file date)

    2. My suggestion was to make the behavior configurable (for example via the options menu) in order to allow the user to decide if to use the "old" SM 1.4 behavior or the "new" SM 1.5. behavior.

    From my point of view this behavior will prevent me from upgrading to SM 1.5. as I will not be able to get the correct date when the mail was received.

  • Jonathan Angliss

    If I remember correct, 1.5 uses a slightly different method. Go to Options | Index Order, and make sure the "Date" field is added, and not the "Received Date". Also, the default sort will be by INTERNALDATE (or as you call it file date). If you want to change it, simply click the [] next to the "Date" field.

  • andreas_rth

    andreas_rth - 2009-04-30

    @jangliss: Thanks a lot for the hint! That solved my problem!


Log in to post a comment.

Get latest updates about Open Source Projects, Conferences and News.

Sign up for the SourceForge newsletter:

No, thanks