Mark Livingstone | 1 Dec 06:09 2003
Picon

Opengroupware Server


www.opengroupware.org is the site for the server that Open Office's groupware
solutions are initially being targetted towards.

Though you might be interested to have a play :-)

Dr. QA

-------------------------------------------------------
This SF.net email is sponsored by: SF.net Giveback Program.
Does SourceForge.net help you be more productive?  Does it
help you create better code?  SHARE THE LOVE, and help us help
YOU!  Click Here: http://sourceforge.net/donate/
Michael A Chase | 1 Dec 12:03 2003
Picon

Timestamp on Sent Messages

I recently sent an email that had been sitting in the Drafts folder for
a week.  The timestamp reflected when I first saved the message, not
when I sent it.

Before I spend any time trying to change that, I'd like some other
opinions.  Should the timestamp of the message ever be updated after it
is first saved?  If so, what would be appropriate events for that to
happen at?

I'm leaning toward changing the timestamp when the email is sent, but
that would cause problems if I want to have two emails refer to each
others' timestamps.

--

-- 
Mac :})
** I usually forward private questions to the appropriate mail list. **
Ask Smarter: http://www.catb.org/~esr/faqs/smart-questions.html
Give a hobbit a fish and he eats fish for a day.
Give a hobbit a ring and he eats fish for an age.

-------------------------------------------------------
This SF.net email is sponsored by: SF.net Giveback Program.
Does SourceForge.net help you be more productive?  Does it
help you create better code?  SHARE THE LOVE, and help us help
YOU!  Click Here: http://sourceforge.net/donate/
Xavier Nodet | 1 Dec 19:09 2003
Picon

Re: Timestamp on Sent Messages

On Mon, 1 Dec 2003 03:03:03 -0800 (PST) Michael A Chase <mchase <at> ix.netcom.com> wrote:

> Should the timestamp of the message ever be updated after it
> is first saved?

If you actually refer to the 'Date:' header in the sent message, then
the answer is 'Yes', as it should refer to the date when the message was
deemed 'sendable'. It would seem to me the logical behavior.

Moreover, RFC2822 has this paragraph:

  The origination date specifies the date and time at which the creator
  of the message indicated that the message was complete and ready to
  enter the mail delivery system. For instance, this might be the time
  that a user pushes the "send" or "submit" button in an application
  program. 

--

-- 
Xavier Nodet
"They that can give up essential liberty to obtain a little temporary
safety deserve neither liberty nor safety." - Benjamin Franklin, 1759.

Mark Livingstone | 2 Dec 01:09 2003
Picon

Error filtering incoming messages

While filtering messages, M froze and I found this in the gdb screen:

GNU gdb 6.0
Copyright 2003 Free Software Foundation, Inc.
GDB is free software, covered by the GNU General Public License, and you are
welcome to change it and/or distribute copies of it under certain conditions.
Type "show copying" to see the conditions.
There is absolutely no warranty for GDB.  Type "show warranty" for details.
This GDB was configured as "i686-pc-linux-gnu".
(gdb) exec-file M
(gdb) run
Starting program: /usr/local/bin/M
[New Thread 16384 (LWP 7041)]
[Debug] 09:53:16: Empty header value?
[Debug] 09:53:16: Empty header value?
[Debug] 09:53:16: Empty header value?
[Debug] 09:53:16: Empty header value?
[Debug] 09:53:16: Empty header value?
[Debug] 09:53:16: Empty header value?
[Debug] 09:53:16: Invalid RFC822 address ' ,,,,,'.

Program received signal SIGSEGV, Segmentation fault.
[Switching to Thread 16384 (LWP 7041)]
0x08220bde in ?? ()
(gdb) bt
#0  0x08220bde in ?? ()
#1  0xbfffdb70 in ?? ()
#2  0xbfffda90 in ?? ()
#3  0x405c3bd4 in wxVLogTrace(char const*, char const*, char*) (
    mask=0xbfffdb70 "\224a\b\210a\bFV <at> x)A\b\201\024\021\b0 <at> \002\226I\002",
(Continue reading)

Vadim Zeitlin | 1 Dec 23:04 2003
Picon

Re: Timestamp on Sent Messages

On Mon, 1 Dec 2003 03:03:03 -0800 (PST) Michael A Chase <mchase <at> ix.netcom.com> wrote:

MAC> I recently sent an email that had been sitting in the Drafts folder for
MAC> a week.  The timestamp reflected when I first saved the message, not
MAC> when I sent it.

 This is a bug.

MAC> Before I spend any time trying to change that, I'd like some other
MAC> opinions.  Should the timestamp of the message ever be updated after it
MAC> is first saved?

 I think the Date header shouldn't be added at all at that moment, i.e. the
code which does it in SendMessageCC::Build() should be only executed if
!forStorage. As far as I remember, this should be enough, could you please
test it (previewing the message before sending it is recommended :-)?

MAC> I'm leaning toward changing the timestamp when the email is sent, but
MAC> that would cause problems if I want to have two emails refer to each
MAC> others' timestamps.

 Do you [ever want this]?
VZ

-------------------------------------------------------
This SF.net email is sponsored by: SF.net Giveback Program.
Does SourceForge.net help you be more productive?  Does it
help you create better code?  SHARE THE LOVE, and help us help
YOU!  Click Here: http://sourceforge.net/donate/
(Continue reading)

Vadim Zeitlin | 2 Dec 13:46 2003
Picon

Re: Error filtering incoming messages

On Tue, 2 Dec 2003 10:09:03 +1000 (EST) Mark Livingstone <mlivingstone <at> iprimus.com.au> wrote:

ML> [New Thread 16384 (LWP 7041)]
ML> [Debug] 09:53:16: Empty header value?
ML> [Debug] 09:53:16: Empty header value?
ML> [Debug] 09:53:16: Empty header value?
ML> [Debug] 09:53:16: Empty header value?
ML> [Debug] 09:53:16: Empty header value?
ML> [Debug] 09:53:16: Empty header value?
ML> [Debug] 09:53:16: Invalid RFC822 address ' ,,,,,'.

 Just in case: these warnings are harmless.

ML> Program received signal SIGSEGV, Segmentation fault.
ML> [Switching to Thread 16384 (LWP 7041)]
ML> 0x08220bde in ?? ()
ML> (gdb) bt
ML> #0  0x08220bde in ?? ()
ML> #1  0xbfffdb70 in ?? ()
ML> #2  0xbfffda90 in ?? ()
ML> #3  0x405c3bd4 in wxVLogTrace(char const*, char const*, char*) (
ML>     mask=0xbfffdb70 "\224²a\b\210Óa\b¨Ûÿ¿FñV <at> x)A\bðÛÿ¿¸Ûÿ¿\201\024\021\b0´Ë <at> Ò\002\226I\002",
ML>     szFormat=0x8467718 "È 8\bÒ\002\226I\005", argptr=0x0) at ../src/common/log.cpp:251
ML> #4  0x0815d162 in ?? ()
ML> #5  0xbfffdb70 in ?? ()
ML> #6  0x08467718 in ?? ()

 This is not very helpful as the stack is obviously garbled. Can you
isolate the message causing this? Is it reproducible?

(Continue reading)

Mark Livingstone | 2 Dec 01:08 2003
Picon

Error pressing send in composer window


GNU gdb 6.0
Copyright 2003 Free Software Foundation, Inc.
GDB is free software, covered by the GNU General Public License, and you are
welcome to change it and/or distribute copies of it under certain conditions.
Type "show copying" to see the conditions.
There is absolutely no warranty for GDB.  Type "show warranty" for details.
This GDB was configured as "i686-pc-linux-gnu".
(gdb) exec-file M
(gdb) run
Starting program: /usr/local/bin/M
[New Thread 16384 (LWP 7128)]

Program received signal SIGSEGV, Segmentation fault.
[Switching to Thread 16384 (LWP 7128)]
0x40840fa5 in mallopt () from /lib/i686/libc.so.6
(gdb)

-------------------------------------------------------
This SF.net email is sponsored by: SF.net Giveback Program.
Does SourceForge.net help you be more productive?  Does it
help you create better code?  SHARE THE LOVE, and help us help
YOU!  Click Here: http://sourceforge.net/donate/
Vadim Zeitlin | 2 Dec 18:01 2003
Picon

Re: Error pressing send in composer window

On Tue, 2 Dec 2003 10:08:58 +1000 (EST) Mark Livingstone <mlivingstone <at> iprimus.com.au> wrote:

ML> GNU gdb 6.0
ML> Copyright 2003 Free Software Foundation, Inc.
ML> GDB is free software, covered by the GNU General Public License, and you are
ML> welcome to change it and/or distribute copies of it under certain conditions.
ML> Type "show copying" to see the conditions.
ML> There is absolutely no warranty for GDB.  Type "show warranty" for details.
ML> This GDB was configured as "i686-pc-linux-gnu".
ML> (gdb) exec-file M
ML> (gdb) run
ML> Starting program: /usr/local/bin/M
ML> [New Thread 16384 (LWP 7128)]
ML> 
ML> Program received signal SIGSEGV, Segmentation fault.
ML> [Switching to Thread 16384 (LWP 7128)]
ML> 0x40840fa5 in mallopt () from /lib/i686/libc.so.6
ML> (gdb)

 bt?
VZ

-------------------------------------------------------
This SF.net email is sponsored by OSDN's Audience Survey.
Help shape OSDN's sites and tell us what you think. Take this
five minute survey and you could win a $250 Gift Certificate.
http://www.wrgsurveys.com/2003/osdntech03.php?site=8
mlivingstone | 3 Dec 00:17 2003
Picon

Re: Error filtering incoming messages

> On Tue, 2 Dec 2003 10:09:03 +1000 (EST) Mark Livingstone <mlivingstone <at> iprimus.com.au> wrote:
> 
> ML> [New Thread 16384 (LWP 7041)]
> ML> [Debug] 09:53:16: Empty header value?
> ML> [Debug] 09:53:16: Empty header value?
> ML> [Debug] 09:53:16: Empty header value?
> ML> [Debug] 09:53:16: Empty header value?
> ML> [Debug] 09:53:16: Empty header value?
> ML> [Debug] 09:53:16: Empty header value?
> ML> [Debug] 09:53:16: Invalid RFC822 address ' ,,,,,'.
> 
>  Just in case: these warnings are harmless.

OK. It has happened a few times in the past and IIRC it always says something about Invalid RFC822 messsages.

> ML> Program received signal SIGSEGV, Segmentation fault.
> ML> [Switching to Thread 16384 (LWP 7041)]
> ML> 0x08220bde in ?? ()
> ML> (gdb) bt
> ML> #0  0x08220bde in ?? ()
> ML> #1  0xbfffdb70 in ?? ()
> ML> #2  0xbfffda90 in ?? ()
> ML> #3  0x405c3bd4 in wxVLogTrace(char const*, char const*, char*) (
> ML>     mask=0xbfffdb70 "\224²a\b\210Óa\b¨Û

-------------------------------------------------------
This SF.net email is sponsored by OSDN's Audience Survey.
Help shape OSDN's sites and tell us what you think. Take this
five minute survey and you could win a $250 Gift Certificate.
http://www.wrgsurveys.com/2003/osdntech03.php?site=8
(Continue reading)

mlivingstone | 3 Dec 00:19 2003
Picon

Re: Error pressing send in composer window

> On Tue, 2 Dec 2003 10:08:58 +1000 (EST) Mark Livingstone <mlivingstone <at> iprimus.com.au> wrote:
> 
> ML> GNU gdb 6.0
> ML> Copyright 2003 Free Software Foundation, Inc.
> ML> GDB is free software, covered by the GNU General Public License, and you are
> ML> welcome to change it and/or distribute copies of it under certain conditions.
> ML> Type "show copying" to see the conditions.
> ML> There is absolutely no warranty for GDB.  Type "show warranty" for details.
> ML> This GDB was configured as "i686-pc-linux-gnu".
> ML> (gdb) exec-file M
> ML> (gdb) run
> ML> Starting program: /usr/local/bin/M
> ML> [New Thread 16384 (LWP 7128)]
> ML> 
> ML> Program received signal SIGSEGV, Segmentation fault.
> ML> [Switching to Thread 16384 (LWP 7128)]
> ML> 0x40840fa5 in mallopt () from /lib/i686/libc.so.6
> ML> (gdb)
> 
>  bt?

I wish I had one but all that happens is I press Send in composer and M crashes back to the gdb shell and that was
all that was there. There is no "Do you want to stop this program" etc.

Since nothing has changed in M, I'm wondering whether one of the changes in wxWindows lately may be inducing
it? 

TIA

Dr. QA
(Continue reading)


Gmane