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

[Thomas McGuire]

Hi,

On Friday 16 July 2010 17:35:22 Kevin Krammer wrote:
> 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.

Err, this reply is a bit late, but anyway:
A simple solution would be to consider only manual mail checks for sending 
queued messages, i.e. only when the user manually activated the KAction(s).
I don't think that sending when the _automatic_ mail check kicks in is much of 
a usecase. Otherwise, I agree completely with what Ingo said.

Regards,
Thomas
-------------- 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/20100729/caa0c6c2/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/