| Summary: | mails started from a template have wrong date | ||
|---|---|---|---|
| Product: | [Unmaintained] kmail | Reporter: | cobaco |
| Component: | general | Assignee: | kdepim bugs <pim-bugs-null> |
| Status: | RESOLVED FIXED | ||
| Severity: | normal | CC: | Heinrich20, ulrich.heinen |
| Priority: | NOR | ||
| Version First Reported In: | 1.9.7 | ||
| Target Milestone: | --- | ||
| Platform: | unspecified | ||
| OS: | Linux | ||
| Latest Commit: | Version Fixed/Implemented In: | ||
| Sentry Crash Report: | |||
|
Description
cobaco
2007-06-08 12:29:48 UTC
I can see this, too in 3.5.7 SVN commit 674569 by marten:
Remove date and message-id from template message, so that new message
will be assigned new up-to-date ones.
CCBUG:146534
M +4 -0 kmcommands.cpp
--- branches/KDE/3.5/kdepim/kmail/kmcommands.cpp #674568:674569
@@ -699,6 +699,10 @@
KMMessage *newMsg = new KMMessage( new DwMessage( *msg->asDwMessage() ) );
newMsg->setComplete( msg->isComplete() );
+ // these fields need to be regenerated for the new message
+ newMsg->removeHeaderField("Date");
+ newMsg->removeHeaderField("Message-ID");
+
KMail::Composer *win = KMail::makeComposer();
newMsg->setTransferInProgress( false ); // From here on on, the composer owns the message.
win->setMsg( newMsg, FALSE, TRUE );
SVN commit 674571 by marten:
Forward port of 674569 from 3.5 branch:
Remove date and message-id from template message, so that new message
will be assigned new up-to-date ones.
BUG:146534
M +4 -0 kmcommands.cpp
--- trunk/KDE/kdepim/kmail/kmcommands.cpp #674570:674571
@@ -706,6 +706,10 @@
KMMessage *newMsg = new KMMessage( new DwMessage( *msg->asDwMessage() ) );
newMsg->setComplete( msg->isComplete() );
+ // these fields need to be regenerated for the new message
+ newMsg->removeHeaderField("Date");
+ newMsg->removeHeaderField("Message-ID");
+
KMail::Composer *win = KMail::makeComposer();
newMsg->setTransferInProgress( false ); // From here on on, the composer owns the message.
win->setMsg( newMsg, false, true );
*** Bug 146704 has been marked as a duplicate of this bug. *** *** Bug 147452 has been marked as a duplicate of this bug. *** |