| Commit message (Collapse) | Author | Age | Files | Lines |
| |
|
| |
|
| |
|
|
|
|
|
|
|
|
| |
void QMailMessageServer::transmitMessage(quint64 action, const QMailMessageId &messageId)
Requests that the MessageServer application transmit the message
identified by 'messageId' that are currently in the Outbox folder.
The request has the identifier 'action'.
|
|
|
|
|
|
| |
Dynamic libraries don't need -pie, it just increases their size unnecessarily.
-fPIC should be added only for boosted normal executables, qmake adds it
by default to dynamic loaded libraries.
|
| |
|
|
|
|
| |
Fix for NB#296686 Problems configuring and accessing “.eim” & “emirates.net.ae” mail accounts
|
|
|
|
|
|
|
|
|
|
| |
Code is from MeeGo:
fix_plugins_installation.patch
fix_docs_installation.patch
Docs patch not yet fully applied.
Also update plugin path documentation in messaging.qdoc.
|
| |
|
| |
|
|
|
|
|
|
| |
Except those in messagenavigator and messageviewer examples
which are not actually included, or at least accessible in
the generated doc output.
|
| |
|
|\ |
|
| |
| |
| |
| |
| | |
Ported from MeeGo QMF
Fixes messsgerserver crash when account is removed while sync is on-going.
|
| |
| |
| |
| |
| |
| |
| |
| | |
Ported from MeeGo QMF.
Set custom fields, fix caching, set msg id in QMailServiceAction::Status
when TX fails.
Ensure that messageserver does not crash when sending email with invalid
smtp server address or invalid smtp commands, proper error will be reported.
|
| | |
|
|/
|
|
|
|
|
|
|
| |
Remove messagenavigator and messageviewer examples from qmf.qdocconf
files, but the doc for these examples in the doc/src/examples directory
is still being parsed.
Add QT_BEGIN_NAMESPACE and QT_END_NAMESPACE to Cpp.ignoredirectives.
Unfortunately they still aren't correctly ignored by qdoc in all cases.
|
|
|
|
|
| |
Hide most of the ELF symbols which would have previously (and unnecessarily)
been public. http://gcc.gnu.org/wiki/Visibility
|
|\ |
|
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
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.
|
| | |
|
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
Would cause deleted messages to not be deleted from server.
Only occurs in rare situations.
Only occurs for ImapUpdateMessagesFlagsStrategy and
ImapSynchronizeAllStrategy strategies. So will not
occur in any known products using QMF, except qtmail.
Probably will not occur in qtmail either, but I need
to fix this for edit mail in drafts.
Fix a bug whereby all message removal records where deleted instead of none
|
|/
|
|
|
|
| |
Port from QMF MeeGo.
Don't encode the attachment filename if it's ascii.
Add new public method "addAttachment".
|
|
|
|
|
| |
Port from MeeGo QMF.
Prefer the Content-Disposition/Size to the body size.
|
|
|
|
|
| |
Ported from MeeGo QMF.
Makes disabled accounts detection more robust.
|
| |
|
|
|
|
| |
Update version in CHANGES to 201202_2
|
|
|
|
| |
Fixes NB#291875 also update CHANGES file to correct previous tag name.
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
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.
|
|
|
|
| |
Patch from Stefano Pironato.
|
| |
|
|
|
|
|
| |
* Use QNetworkProxy::applicationProxy() requires qt 4.8
* Revert removal emission of IPC notification
|
|
|
|
|
|
|
|
|
| |
Patch by: Radakovic Bojan <[email protected]>
If application is not setting proxy by itself, use proxy
setings from the system.
Unix support only introduced in Qt 4.8, see:
https://bugreports.qt.nokia.com/browse/QTBUG-14623
|
|
|
|
|
|
| |
If we don't emit notifications when messages change and automatic flag
updating for visible messages is turned off, for some use cases the UI
is not correctly updated after a full sync(using qtmail example app).
|
|
|
|
|
|
|
|
|
|
|
| |
Follow up fix for NB#294947.
Make unit tests more robust by making content-type header field
parameter testing case insensitive.
Also lower case "utf-8" in input text, as an expedient measure
to ensure unit tests pass. It's only use for content-type charset
parameter and that specific text is case insensitive.
|
|
|
|
|
|
|
|
|
|
|
| |
Follow up fix for NB#294947.
Required to make unit tests pass, otherwise Content-Type header
field output by QMailMessage::toRfc2822 has a spurious empty
charset parameter e.g.
Content-Type: text/plain; charset=
Instead of
Content-Type: text/plain;
|
|
|
|
|
| |
Fix duplicate signal emission of addMessages and updateMessagesMetaData.
Add UTs to verify that the signals are emitted only once per message added.
|
| |
|
|
|
|
| |
Update previous entry.
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Patch from Edit Siket-Szasz.
QMailMessageMetaData::recipients only contained to recipients,
whereas it should also contain cc and bcc recipients, and should
do so after this commit is made.
This change will appropriately update the data stored in the
recipients row of the mailmessages table in the qmailstore.db
database for new mails, but no retroactive changes will be made.
Hence the behavior of the QMailMessageKey::recipients functions
will be modified, and should now be correct.
The following API changes have been made as documented in the
qmfclient library CHANGES file.
49. Added QList<QMailAddress> QMailMessage::to() const
virtual QList<QMailAddress> QMailMessageMetaData::recipients() const
protected:
virtual void QMailMessageMetaData::setRecipients(const QList<QMailAddress>& s);
virtual void QMailMessageMetaData::setRecipients(const QMailAddress& s);
Removed QList<QMailAddress> QMailMessageMetaData::to() const
void QMailMessageMetaData::setTo(const QList<QMailAddress>& s);
void QMailMessageMetaData::setTo(const QMailAddress& s);
This change is BIC (a binary incompatible change).
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
New function static QByteArray QMailCodec::bestCompatibleCharset(const QByteArray& charset, bool translateAscii);
commit 227635e77381bf98158b6d373a40760877d47e9b
Author: Javier Fernandez <[email protected]>
Date: Fri Nov 4 11:20:19 2011 +0100
Fixes: NB#289443 - Mail; Hong Kong special characters are displayed as garbage text.
commit d7bce4800db29006c5e0da1b5a34598a5f44f911
Author: Javier Fernandez <[email protected]>
Date: Fri Oct 28 11:06:10 2011 +0200
Fixes: NB#286730 - Thai texts cannot be read in gmail.
NB#294947 - Mail; Preview in Hong Kong special Chinese characters (Big5) displays as garbage after downloading the attachment.
Apply the bestCompatibleCharset function to the ensureCharsetExists
when the preview is generated it checks if the body is encoded or not. If not
encoded, it does not call to the codecForName, which actually replaces the
charset (GB2312 --> GB18030) to one more appropriated or general.
In that case, the charset coming into the body is used, so I think it's a good
idea to do it inside the ensureCharsetExists, as it's called every time the
body is built in memory.
We could just solve the problem by calling the new method inside the
QMailMessageBodyPrivate::toStream(QTextStream& out) const method, used to
generate the preview form a plain text body. However, there are additional
places where the charset is used without checking for a proper replacement, so
calling it inside the ensureCharsetExists method seems a better approach.
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
| |
Decode the metadata headerfield using the charset of the plain text or
html body part if one is found, and the libicu analysis fails to find a
charset with a high confidence, and the mail doesn't contain a charset
parameter in the content type headerfield.
The plain text or html body part may not be found in some situations,
e.g. depending on user settings, only headers may be downloaded, and
for IMAP only IMAPSTRUCTURE envelope may be downloaded, or two passes
may occur and only envelope may be downloaded in first past.
|
|
|
|
|
|
| |
This reverts commit c931c8085cf1f7c43ef36a391fc771ab0d3dce72.
Better fix incoming.
|
|
|
|
| |
Fix for NB#295637.
|
| |
|
|
|
|
|
| |
In qmailcodec handle microsoft "unicode-1-1-utf-7" charset as if
it is "ISO-8859-1" charset.
|
|
|
|
|
|
|
| |
delivery status failure notification mail
When finding plain or html body part treat multipart mime parts of unknown subtype
as if they are multipart/mixed parts, as specified in rfc2046 section 5.1.7
|
| |
|