[Kde-pim] Ping/Pong Loop between Mailtransport and KMail

[Ingo Klöcker]

On Friday 16 July 2010, Kevin Krammer wrote:
> On Friday, 2010-07-16, Kevin Krammer wrote:
> > On Friday, 2010-07-16, Kevin Krammer wrote:
> > > Hi all,
> > > 
> > > while debugging Mailtransport related problems, I discovered a
> > > nice ping/pong inside KMail.
> > > 
> > > This is what happens:
> > > 
> > > 1) KMail's ETM lists a folder
> > > 2) Akonadi synchronizes the collection
> > > 3) KMKernel::instanceStatusChanged() goes "oooh, mail is being
> > > checked" 4) when "mail check" ends,
> > > KMMainWidget::slotEndCheckMail() decides to send queued messages
> > > 
> > > So far so good
> > > 
> > > 5) DispatcherInterface creates a FilterActionJob
> > > 6) FilterActionJob does and ItemFetchJob on the outbox
> > > 7) Akonadi synchronizes the outbox
> > > 8) -> (3)
> > > 
> > > Not sure where to fix this though.
> > > The most problematic part seems to be in
> > > KMKernel::instanceStatusChanged(). Any of its agents switching to
> > > state "Running" is considered a mail check in progress.
> > 
> > It is basically a side effect of progress reporting, extened by
> > Laurent in revision 1138325.
> > 
> > EnumSendOnCheck::SendOnManualChecks could probably be moved out of
> > KMMainWidget::slotEndCheckMail() and triggered by the GUI action
> > itself (would then run in parallel to the mail check)
> > 
> > EnumSendOnCheck::SendOnAllChecks could probably be removed,
> > assuming the mail dispatcher agent has some kind of interval
> > checking for queued mails. It is not exactly the same behavior,
> > e.g. happens more often if the dispatcher timeout is shorter than
> > the check timeouts.
> 
> Wrong assumption on my part, "Send later" requires sending on mail
> check.

Actually, this behavior is (and has always been) broken. Many users have 
already complained that a message which was queued with "Send later" is 
send as soon as the next message is send. I agree with this.

Queued messages should be sent in the following situations:
- On mail check (if configured this way)
- As soon as the computer is online (resp. as soon as the mail server 
can be reached)
- On explicit request (via the UI)

Queued messages should not be sent just because some other messages are 
sent directly (without queuing them).


Regards,
Ingo
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 198 bytes
Desc: This is a digitally signed message part.
URL: <http://mail.kde.org/pipermail/kde-pim/attachments/20100718/911e1646/attachment.sig>
-------------- next part --------------
_______________________________________________
KDE PIM mailing list kde-pim at kde.org
https://mail.kde.org/mailman/listinfo/kde-pim
KDE PIM home page at http://pim.kde.org/