Skip to main content.
home | support | download

Back to List Archive

RE: Re: swish-e hypermail and date_ranges

From: Jackson Craig <c.jackson(at)>
Date: Tue Aug 23 2005 - 12:44:16 GMT
Well, I have found an ugly fix which works for my needs. 
I have changed the following in hypermail :
In print.c, change line 1352 from   getdatestr(email->date)    to
This 'forces' the body of the page to contain a human readable date, and
ignores the dateformat setting
In printfile.c, change line 331 from  secs_to_iso_meta(date)    to
This makes the Date meta tag in the header conform to whatever  you set
dateformat to in hypermail.rc.  I can now set it to %s and this gives me a
UNIX timestamp in the meta tag - which is what I need in order to make it a
property in my index.
I know it is ugly, and I'm sure with a little more thought I could make it
cleaner (like add another config option for the format of the date in the
body) but it will do !


From: Jackson Craig [] 
Sent: 23 August 2005 10:07
To: (
Subject: Re: swish-e hypermail and date_ranges

Hi Bill,
Thanks alot for your reply. Sadly, I do not know how to get the script to do
this conversion. If you were feeling generous, maybe you could help me with
that .....  ;-)
Thanks again,

On Mon, Aug 22, 2005 at 02:43:31AM -0700, Jackson Craig wrote: 
> I have been able to search by date in the past, but now because
> is using swishlastmodified, I am unable to effectively search mail sent
> prior to the date I recreated the archive !! - since all this mail has its
> swishlastmodified date set to the date I recreated the archive :-(

I see that the script does pull out a received date. Maybe you could use

> I understand that swish-e cannot parse dates, and so I was going to get
> hypermail to use UNIX timestamps, but then I lose a human readable date in
> the archived message which I don't want to do.

So have the script convert the dates. 


Bill Moseley

Unsubscribe from or help with the swish-e list:

Help with Swish-e:
This email and any attachments are confidential to the intended recipient
and may also be privileged.  If you are not the intended recipient, please
delete it from your system and notify the sender.  You should not copy it 
or use it for any purpose nor disclose or distribute its contents to any
other person.

Due to deletion of content types excluded from this list by policy,
this multipart message was reduced to a single part, and from there
to a plain text message.
Received on Tue Aug 23 05:44:21 2005