Bug 150969 - KMail manual contains no instructions about back up of e-mail
Summary: KMail manual contains no instructions about back up of e-mail
Status: RESOLVED WORKSFORME
Alias: None
Product: docs.kde.org
Classification: Websites
Component: general (show other bugs)
Version: unspecified
Platform: unspecified Linux
: NOR normal
Target Milestone: ---
Assignee: Documentation Editorial Team
URL:
Keywords: investigated, triaged
Depends on:
Blocks:
 
Reported: 2007-10-18 13:57 UTC by Colin L. Carter
Modified: 2018-10-21 05:00 UTC (History)
2 users (show)

See Also:
Latest Commit:
Version Fixed In:
Sentry Crash Report:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Colin L. Carter 2007-10-18 13:57:17 UTC
Version:           3.5.1 Level "a"  (using KDE 3.5.1 Level "a" , SUSE 10.1)
Compiler:          Target: x86_64-suse-linux
OS:                Linux (x86_64) release 2.6.16.53-0.16-default

No back up instructions.

Your documentation states that my mail is in  ~/Mail   it is not.
But I found it.

When I try to copy it, the directory structure copies, but no mail.

I realise that there should be a security issue to consider,
but it would be nice if I didn't have to copy every single letter
onto my removable back up.

Thank you for any help in this regard.

PS: Why does the manual specify two contact e-mail address which 'bounce'?

Regards,
Colin
Comment 1 Burkhard Lück 2008-07-25 12:53:12 UTC
Sorry but I don't understand your report.
I suppose you mean some documentations, but which one?

>Your documentation states that my mail is in  ~/Mail   it is not.

Which documentation? The Kmail Handbook?

>PS: Why does the manual specify two contact e-mail address which 'bounce'?

Which manual has two bouncing e-mail adresses?
Could you please name these adresses?

Consider that you filed this bug report for the product "khelpenter", but this is only the application to display the help documentation.

I suppose the correct product should be "docs", so please change it.
Comment 2 Björn Ruberg 2010-01-14 01:01:17 UTC
Needs an answer. Is the problem still there?
Comment 3 Andrew Crouthamel 2018-09-20 03:17:00 UTC
Dear Bug Submitter,

This bug has been in NEEDSINFO status with no change for at least 15 days. Please provide the requested information as soon as possible and set the bug status as REPORTED. Due to regular bug tracker maintenance, if the bug is still in NEEDSINFO status with no change in 30 days, the bug will be closed as RESOLVED > WORKSFORME due to lack of needed information.

For more information about our bug triaging procedures please read the wiki located here: https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging

If you have already provided the requested information, please set the bug status as REPORTED so that the KDE team knows that the bug is ready to be confirmed.

Thank you for helping us make KDE software even better for everyone!
Comment 4 Andrew Crouthamel 2018-10-21 05:00:18 UTC
This bug has been in NEEDSINFO status with no change for at least
30 days. The bug is now closed as RESOLVED > WORKSFORME
due to lack of needed information.

For more information about our bug triaging procedures please read the
wiki located here:
https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging

Thank you for helping us make KDE software even better for everyone!