| Commit message (Collapse) | Author | Age | Files | Lines |
|
|
|
|
| |
Change-Id: Id59253e1d121ab0dfcdb59f7018b897f6c1df086
Reviewed-by: Robin Burchell <[email protected]>
|
|
|
|
|
|
| |
Change-Id: I7f4bee6fccf1e2a805cc7e9899ae16a6e15caa8d
Reviewed-by: Valerio Valerio <[email protected]>
Reviewed-by: Robin Burchell <[email protected]>
|
|
|
|
|
| |
Change-Id: I021570bce26529adfbfb4080b18b87df74bc2c18
Reviewed-by: Matthew Vogt <[email protected]>
|
|
|
|
|
| |
Change-Id: If27729ee3fd511226a31ae096f52e130e14d8065
Reviewed-by: Robin Burchell <[email protected]>
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
These may have made some sense back when QMF was part of Qtopia (a messaging system
customizable for each platform and offering extensible message types), but it
makes a lot less sense in the sense of a library offering email-related
functionality.
This type of functionality belongs in the clients, not in the library, so move
it there.
This has been performed through a fairly quick hatchet job. It isn't really
clean, working code yet, but it is operational.
Change-Id: Ic417a5e885034b67b645df238febb30cda88b17c
Reviewed-by: Matthew Vogt <[email protected]>
Reviewed-by: Valerio Valerio <[email protected]>
|
|
|
|
|
|
|
|
|
|
| |
I'm not totally clear how useful this thing actually is, but instead of
bastardising it across a few examples/projects, let's promote it to a module and
avoid that black magic.
Change-Id: I4d34961bc30e01455274afdd344286f4e5cfd25a
Reviewed-by: Matthew Vogt <[email protected]>
Reviewed-by: Robin Burchell <[email protected]>
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
QmfMessageServer.
This was not possible prior to now due to Qt 4 support hanging around like the
undead vampire it is, but now we purged it with fire and light, and the build
system looks a lot less like a stinky, decomposed corpse.
There's still a lot of surprises lurking: qtmail is one such surprise. I don't
quite grasp why it's so heavy on plugins, and qmfutil also needs some...
attention. But at least it's a start.
As part of this work, we rename the qcop headers to fit the private convention.
This could have been done in a prior commit, but given that I didn't have an
easy way to build prior to this commit, I opted to roll them together.
Change-Id: Ia3e288ffc3639a7751c9040ceecb54fca77a31b1
Reviewed-by: Oswald Buddenhagen <[email protected]>
Reviewed-by: Matthew Vogt <[email protected]>
Reviewed-by: Valerio Valerio <[email protected]>
|
|
|
|
|
|
|
|
|
|
|
| |
This has persisted long enough, and as far as I am aware, has no users. It is
also blocking potential build system cleanups and other good things.
Reviewed-by: Valerio Valerio <[email protected]>
Reviewed-by: Matthew Vogt <[email protected]>
Change-Id: I5e0e0549ef6ffee31b5e60ec94a9e17f27e01436
Reviewed-by: John Brooks <[email protected]>
Reviewed-by: Robin Burchell <[email protected]>
|
|
|
|
|
| |
Change-Id: I7eb742fc60884881714911e76ea6de6ef4939ca4
Reviewed-by: Robin Burchell <[email protected]>
|
|
|
|
|
|
|
|
|
|
| |
This makes build system detect if Qt libraries are built as framework or not and
add correct flags to LIBS.
Change-Id: Ifb0d2ed87f5d624966395bce39959ce53f1dee89
Reviewed-by: Valerio Valerio <[email protected]>
Reviewed-by: Tasuku Suzuki <[email protected]>
Reviewed-by: Robin Burchell <[email protected]>
|
|
|
|
|
|
|
|
|
|
|
| |
Q_GLOBAL_STATIC changed implementation. To make life easy, just make the
constructor public, and stop trying to use Q_GLOBAL_STATIC in a rather
unsupported way.
Change-Id: I7c6b13534c1a32db643574a9814b73ce0e0b22cf
Reviewed-by: Valerio Valerio <[email protected]>
Reviewed-by: John Brooks <[email protected]>
Reviewed-by: Robin Burchell <[email protected]>
|
|
|
|
|
|
|
|
| |
Signed-off-by: Valerio Valerio <[email protected]>
Change-Id: I2c03d287fc871098cf45d75d4a1262b9c6c4378d
Reviewed-by: Robin Burchell <[email protected]>
Reviewed-by: Matthew Vogt <[email protected]>
|
|
|
|
|
|
|
|
| |
Update code base to match latest release of Qt.
Signed-off-by: Valerio Valerio <[email protected]>
Change-Id: I02c2ff250ea8cd960938b81903e92b04c745ae9c
Reviewed-by: Matthew Vogt <[email protected]>
Reviewed-by: Robin Burchell <[email protected]>
|
|
|
|
|
|
|
|
| |
Symbian is not a supported platform anymore.
Change-Id: I82e618e756ae0b247e6e038fa9d8d43fb90b44ff
Reviewed-by: Valerio Valerio <[email protected]>
Reviewed-by: Matthew Vogt <[email protected]>
|
|
|
|
|
| |
Change-Id: If0f4427ee93a37de4ebd9e097defd8b3956f0fc6
Reviewed-by: Lars Knoll <[email protected]>
|
|
|
|
|
|
|
|
|
|
| |
minor, but matches the changes made in Qt 5, and reflects that Nokia is no
longer the vendor of this software.
Change-Id: I3b324b813359f53e65760f3ce7a751dbd5c970e7
Reviewed-by: Sergio Ahumada <[email protected]>
Reviewed-by: Johan Thelin <[email protected]>
Reviewed-by: Valerio Valerio <[email protected]>
|
|
|
|
|
|
|
|
|
|
|
|
| |
Handle case of IMAP server supporing GENAUTHURL and SMTP server
supporting BURL, and user defining Sent folder on server
(or autodetection), then deleting that folder on the server.
Don't try to upload message to non-existent sent folder.
Probably could still be handled better, CanTransmitFromExternal
shouldn't really be used as a message flag, but should instead
be computed on demand.
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
As qDebug shouldn't be used in release code, and may become deprecated.
There's still some uses of qDebug left, namely, some automated
tests that actually test qDebug/qMailLog functionality, some uses of
qDebug in uncompiled documentation code snippet examples, one use of
include QDebug in symbian code, and in qmailid some uses of
defining operator<<(QDebug <<, ...).
There's still about 500 uses of qWarning and qFatal left. For these
I include qmaillog.h as currently that inclues QDebug. Apart from
the one symbian case already mention.
|
|
|
|
|
|
| |
as they do nothing.
Thanks to Valerio for the patch.
|
|
|
|
|
|
| |
QMailRetrievalAction::defaultMinimum() mails.
Previously only 1 mail could be retrieved.
|
|
|
|
|
|
|
|
|
|
|
|
| |
void QMailRetrievalAction::createStandardFolders(const QMailAccountId &accountId)
Requests that the message server create the standard folders for the
account accountId. If all standard folders are already set in the storage
the service action will return success immediately, in case some standard folders are
not set, a matching attempt against a predefined list of translations will be made,
if the folders can't be matched, messageserver will try to create them in the server side
and match them if the creation is successful. In case folder creation is not allowed for
the account accountId the service action will return.
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Updated message should now be saved to drafts folder on server.
This required deleting old message, and saving a new message. Which
has some side effects. #1 On gmail deleted messages are copied to the
trash automatically. #2 In qtmail if multiple qmf accounts exist
for the same remote account then updating a drafts in one qmf
account and then viewing the other account will detect that the
original drafts message has been removed due to qtmail automatic
visible message flags updating, and the new message
will not be retrieved until a synchronization is performed.
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Specifically, as documented in src/libraries/qmfclient/CHANGES.qdoc item 52, added:
'void QMailStorageAction::deleteMessages(quint64, const QMailMessageIdList &ids)',
'void QMailStorageAction::rollBackUpdates(quint64, const QMailAccountId &mailAccountId)',
'void QMailStorageAction::moveToStandardFolder(quint64, const QMailMessageIdList& ids, QMailFolder::StandardFolder standardFolder)',
'void QMailStorageAction::moveToFolder(quint64, const QMailMessageIdList& ids, const QMailFolderId& folderId)',
'void QMailStorageAction::flagMessages(quint64, const QMailMessageIdList& ids, quint64 setMask, quint64 unsetMask)',
'void QMailStorageAction::restoreToPreviousFolder(quint64, const QMailMessageKey& key)',
'void QMailMessageServer::deleteMessages(quint64, const QMailMessageIdList &ids)',
'void QMailMessageServer::rollBackUpdates(quint64, const QMailAccountId &mailAccountId)',
'void QMailMessageServer::moveToStandardFolder(quint64, const QMailMessageIdList& ids, quint64 standardFolder)',
'void QMailMessageServer::moveToFolder(quint64, const QMailMessageIdList& ids, const QMailFolderId& folderId)',
'void QMailMessageServer::flagMessages(quint64, const QMailMessageIdList& ids, quint64 setMask, quint64 unsetMask)' and
'void QMailMessageServer::restoreToPreviousFolder(quint64, const QMailMessageKey& key)'.
Also added documentation for new functions, and made some minor documentation
updates for existing functions.
Additionally added a new set of module tests tst_qmailstorageaction. These
tests require the messageserver to be running. They are not just stubs
but do real testing.
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
to be online.
Specifically:
Renamed 'void QMailStorageAction::deleteMessages(const QMailMessageIdList &ids)' to onlineDeleteMessages,
'void QMailStorageAction::copyMessages(const QMailMessageIdList &ids, const QMailFolderId &destinationId)' to onlineCopyMessages,
'void QMailStorageAction::moveMessages(const QMailMessageIdList &ids, const QMailFolderId &destinationId)' to onlineMoveMessages,
'void QMailStorageAction::flagMessages(const QMailMessageIdList &ids, quint64 setMask, quint64 unsetMask)' to onlineFlagMessages,
'void QMailStorageAction::createFolder(const QString &name, const QMailAccountId &accountId, const QMailFolderId &parentId)' to onlineCreateFolder,
'void QMailStorageAction::renameFolder(const QMailFolderId &folderId, const QString &name)' to onlineRenameFolder,
'void QMailStorageAction::deleteFolder(const QMailFolderId &folderId)' to onlineDeleteFolder.
'void QMailMessageServer::deleteMessages(const QMailMessageIdList &ids)' to onlineDeleteMessages,
'void QMailMessageServer::copyMessages(const QMailMessageIdList &ids, const QMailFolderId &destinationId)' to onlineCopyMessages,
'void QMailMessageServer::moveMessages(const QMailMessageIdList &ids, const QMailFolderId &destinationId)' to onlineMoveMessages,
'void QMailMessageServer::flagMessages(const QMailMessageIdList &ids, quint64 setMask, quint64 unsetMask)' to onlineFlagMessages,
'void QMailMessageServer::createFolder(const QString &name, const QMailAccountId &accountId, const QMailFolderId &parentId)' to onlineCreateFolder,
'void QMailMessageServer::renameFolder(const QMailFolderId &folderId, const QString &name)' to onlineRenameFolder,
'void QMailMessageServer::deleteFolder(const QMailFolderId &folderId)' to onlineDeleteFolder.
Additionally updated the doc to fix some assorted discrepancies, and indicate which functions require the device to be online.
Have not yet regenerated the html version of the doc.
|
|
|
|
|
|
|
|
|
| |
Both QMailAccount::CanReferenceExternalData and
QMailAccount::CanTransmitViaReference should be true.
In reality not a problem in qtmail example due to additional
checks, but qtmail code is used as an example by others so
good to get it right here.
|
|
|
|
| |
Remove obsolete pre-release clause.
|
| |
|
|
|
|
| |
Due to serviceactions changes.
|
| |
|
|
|
|
|
|
|
| |
Don't lose mail if messageserver crashes or is not running
while queueing mail in outbox.
Catch failure and save to outbox using qmailstore.
|
|
|
|
|
| |
If retrieving messages flags fails, give up, rather than
endlessly retry.
|
|
|
|
|
|
| |
QApplication must be constructed before QSettings.
Patch from Juha Kurikkala
|
|
|
|
|
|
| |
Eric Springer committed c1b02c7f on May 19, 2011 14:28
Fix qtmail crash when hitting the cancel button
|
| |
|
|
|
|
|
|
| |
When sending mail.
Intent is to increase responsiveness of client.
|
| |
|
|\ |
|
| | |
|
| |\ |
|
| | | |
|
| | | |
|
| | | |
|
| | | |
|
| | |
| | |
| | |
| | | |
This reverts commit 24cb8cdd0a79cd973349d31120a541308a8f49d1.
|
| |/
|/| |
|
|/
|
|
|
|
| |
handled correctly.
Just a client (qtmail) issue.
|
| |
|
|
|
|
|
|
| |
Add a guard to QList.mid call, seems really strange that the mid function is
unstable when pos is greater than (or equal to?) count of elements in the
list, but this is not the first time I've experience this crash.
|
| |
|
|
|
|
|
|
| |
Currently it's getting casted to a null pointer, and invoking the
QString(char *) constructor which is safely handling it -- but this
isn't something we should rely on.
|