[prev in list] [next in list] [prev in thread] [next in thread]
List: kmail-devel
Subject: [Bug 60575] kmail deleted all my mail folders!!! (Interaction with
From: Adriaan De Groot <adridg () cs ! kun ! nl>
Date: 2003-09-18 9:52:05
[Download RAW message or body]
------- You are receiving this mail because: -------
You are the assignee for the bug, or are watching the assignee.
http://bugs.kde.org/show_bug.cgi?id=60575
------- Additional Comments From adridg@cs.kun.nl 2003-09-18 11:52 -------
What KPilot does is
if (!dcopptr->call("kmail",
"KMailIface",
"dcopAddMessage(QString,QString)",
data,
returnType,
returnValue,
true))
where data is created with
arg << kmailOutboxName << t.name();
(t is the tempfile name containing the message from the Pilot). Finally, \
KPilot determines the name of KMail's outbox folder with
QString PopMailConduit::getKMailOutbox() const
{
FUNCTIONSETUP;
// Read-only config file. This is code
// suggested by Don Sanders. It must be
// kept up-to-date with what KMail does.
//
// TODO: Completely broken since KMail disposed of this
// setting in KDE 3.0. No idea how to fix short of i18n("outbox").
KSimpleConfig c(CSL1("kmailrc"),true);
c.setGroup("General");
QString outbox = c.readEntry("outboxFolder");
if (outbox.isEmpty())
{
KConfigGroupSaver gs(fConfig,PopmailConduitFactory::group); \
outbox = fConfig->readEntry("outboxFolder");
}
return outbox;
}
and, as the comment shows, there's no way to discover the outbox name in \
KMail anymore. The immediate fix in KPilot is to disable sending through \
KMail. However, the fact remains that using an empty folder name in the \
dcopAddMessage call apparently causes damage to KMail. \
_______________________________________________ KMail Developers mailing \
list kmail@mail.kde.org
http://mail.kde.org/mailman/listinfo/kmail
[prev in list] [next in list] [prev in thread] [next in thread]
Configure |
About |
News |
Add a list |
Sponsored by KoreLogic