https://bugs.kde.org/show_bug.cgi?id=286793


Graeme Hewson <ghew...@wormhole.me.uk> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |ghew...@wormhole.me.uk




--- Comment #5 from Graeme Hewson <ghewson wormhole me uk>  2012-01-11 12:29:02 
---
Adding some more details to the report:

Add new Mbox account specifying Filename /var/mail/$user
    (on Kubuntu, /var/spool/mail is link to /var/mail)
Optionally change Display Name (default is $user)
Leave other settings as default, in particular:
    Enable file monitoring
    Compact every 50 messages
    Lock method None

Use mailx to send message to $user
Get several occurrences of these messages in Notifications:

    $user: The MBox file was changed by another program. A copy of the
    new file was made and pending changes are appended to that copy.
    To prevent this from happening use locking and make sure that all
    prog...

    $user: The file 'file:///var/mail/$user' was changed on disk while
    there were still pending changes in Akonadi. To avoid data loss, a
    backup of the internal changes has been created at
    'file:///home/$user/...

[Is it possible to see the complete text of a popup message in Notifications?]

Delete message (move to wastebin)
Use mailx to send another message to $user
Get notifications as above
Both messages appear in Kmail folder (the first message was deleted, but has
re-appeared).

It's possible to stop deleted messages from re-appearing by changing the
"compact every" setting to 1 message.

It's not possible to stop the error messages from appearing when mail is sent
to $user. Kmail1 has FCNTL locking, but Kmail2 doesn't. None of the other lock
methods in Kmail2 (Procmail or Mutt) are applicable.

Also, Kmail1 has a Destination Folder setting for an account, but this isn't
available in Kmail2.

-- 
Configure bugmail: https://bugs.kde.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug.
_______________________________________________
Kdepim-bugs mailing list
Kdepim-bugs@kde.org
https://mail.kde.org/mailman/listinfo/kdepim-bugs

Reply via email to