| Commit message (Collapse) | Author | Age | Files | Lines |
| ... | |
| |
|
|
|
|
| |
Due to reregistration API change.
Small chance this may fix NB#259082 Sync never stops
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
| |
Requests that the message server updates the meta data of the existing
messages in the message store, to match each of the messages listed in
\a messages.
The messages will be updated asynchronously.
All messages must use the same content scheme.
\sa QMailStorageAction::messagesUpdated, QMailMessageData::contentScheme
void QMailStorageAction::updateMessages(const QMailMessageMetaDataList &messages)
|
| |
|
|
|
|
| |
In addMessages and updateMessages.
Also clean up error handling logic, so metadata objects aren't leaked.
|
| | |
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Related to NB#199393 'Response time to send Email message is above the target
value'
messagserver will no longer reload message data, should reduce
peak memory usage (and reduce cpu/filesystem use).
Required fixing bug in mailstore where updateMessage ignored udpated
contentIdentifier.
Required changing QMailContentManager interface to add new NoDurability option
and new ensureDurability(const QList<QString> &) function, and updating
QmfStorageManager plugin appropriately.
Required adding new limitation to addMessages and updateMessages
service actions, all messages must have same content scheme.
|
| | |
|
| |
|
|
| |
Possible, but unproven fix for NB#258677.
|
| |
|
|
| |
QCoreApplication must be constructed before QSettings.
|
| | |
|
| | |
|
| | |
|
| | |
|
| | |
|
| | |
|
| | |
|
| | |
|
| | |
|
| | |
|
| | |
|
| |
|
|
|
|
| |
support Cram-MD5 then fail loudly.
Previously would fall back to some other authentication mechanism.
|
| | |
|
| | |
|
| | |
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Taken from QMF merge request #6 by Vitaly Repin:
Current version of the QMF logging subsystem has the following issues:
1) Whenever application is linked against QMF, all the syslog messages are
prefixed with QMF regardless of the application settings.
E.g., Aug 31 00:25:16 vitnote QMF[4959]: [Critical] Test
It makes it harder to identify the application which has printed specific
message to syslog. It also overwrites the previous calls to "openlog" made by
application which is impolite
2) It is not possible to enable/disable logging through syslog in runtime
3) It is not possible to log into file and stderr
4) Output of Q_ASSERT is not logged. In fact, QWarning(), qFatal(), qDebug()
do not go to the log
5) Library installs the SIGHUP handler transparently for the application. It
is bad because application might want to install its own handler for this
signal and it could conflict with the library's logic.
The patch attached for your review fixes the issues above. It also adds the
following possibilities:
- To log into file and stderr, controllable through the configuration file in
runtime
- To create chain of loggers if needed (e.g., output to file and stderr, to
file and syslog etc). Chain of loggers is defined in run-time through
configuration file.
- Configuration file is per application. Not the only file for all the users
of the library.
|
| | |
|
| |
|
|
| |
Fixes QTSOL-77
|
| |
|
|
| |
This is done to avoid conflicts with the QPID Management Framework
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Library Renames:
libmessageserver -> libqmfmessageserver
libqtopiamail -> libqmf
Directory Changes:
src/libraries/messageserver -> src/libraries/qmfmessageserver
src/libraries/qtopiamail -> src/libraries/qmf
src/plugins/contentmanagers/qtopiamailfile -> qmfstoragemanager
src/plugins/messageservices/qtopiamailfile -> qmfsettings
Class changes:
QtopiamailfileConfigurator -> QmfConfigurator
QtopiamailfileSettings -> QmfSettings
QtopiamailfileServicePlugin -> QmfServicePlugin
QtopiamailfileManager -> QmfStorageManager
There's still a few outstanding changes in the docs / translations
that should be fixed shortly.
|
| |
|
|
| |
QMailMessage::New status flag unset.
|
| | |
|
| |
|
|
|
|
|
|
|
| |
Using QTime, when the day rolled over it would invalidate our
expiry time comparison, making actions expire prematurely.
By using unix time instead we can prolong this from daily to every ~136 years.
Unfortunately unix time ignores leap seconds (?!), meaning our expiry might
happen 1 second after it should.
|
| | |
|
| | |
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Task: NB#175678
Details:
Patch from Linc for NB#175678
Remove the QtGui dependency from both libs, all messageserver
plugins and messageserver itself.
The libqtopiamail patch changes the model to return QString instead of QIcon so
code using QMailMessageModelBase may need to be updated (see the change to
qtmail for an example).
The second patch removes message service editors via an ifdef. To enable this
patch you must run qmake with an extra argument.
eg.
qmake -r qmf.pro DEFINES+=QMF_NO_MESSAGE_SERVICE_EDITOR
|
| | |
|
| | |
|
| |
|
|
|
|
| |
If a service was cancelled and there were actions waiting (mRequests)
for that service -- they would never be dispatched. (And no other
requests would ever get through)
|
| | |
|
| | |
|
| | |
|
| |
|
|
| |
Fix issues suggested by KDE's code checking tool "Krazy"
|
| | |
|
| | |
|
| |
|
|
|
|
| |
don't try and send them.
(Even if they are also marked as being in the outbox).
|
| |
|
|
|
|
|
|
| |
are sent in the case of user cancelled action.
Task: NB#176450 kinda.
Details: Service was being removed from list too early.
|
| |
|
|
|
|
|
|
|
|
| |
internally cancelled services.
Task: NB#176450
Details: Add QMailServiceAction::Status::ErrInternalStateReset
enum value use it when appropriate, e.g. in the messageserver
when an account is modified by another process.
|
| | |
|
| |
|
|
|
| |
Task: NB#168536
Details: Small patch contributed (8 lines)
|
| | |
|
| |
|
|
|
|
|
|
|
| |
A) leave it in the outbox and continue sending other messages in the outbox.
B) emit a messagesFailedTransmitted signal.
API change QMailTransmitAction has new messagesFailedTransmitted signal.
Task: NB#177952 NB#153703
|