松鼠邮件数据副本
我在我的 Linux 服务器上安装并配置了 squirrelmail，我用它来发送和接收电子邮件。
现在我必须格式化 Linux 服务器...那么在格式化之前我如何备份我的电子邮件和配置以便它们可以再次使用？
I have an installed and configured squirrelmail in my linux server which i used to send and receive emails.
Now i have to format the linux server... then before formatting how can i backup my emails and configuration so that they can be used again ?
如果你对这篇内容有疑问，欢迎到本站社区发帖提问 参与讨论，获取更多帮助，或者扫码二维码加入 Web 技术交流群。
绑定邮箱获取回复消息
由于您还没有绑定你的真实邮箱，如果其他用户或者作者回复了您的评论，将不能在第一时间通知您！
发布评论
评论（1）
备份电子邮件不是 SquirrelMail 的问题。 SquirrelMail 是一个 IMAP 客户端，本身不存储电子邮件。您需要确定您的特定电子邮件系统使用哪种存储。如果这是一个非常简单/默认的 *nix 电子邮件设置，您可以首先在 /home/ 中查找名称表明用途的目录，例如“Mail”、“Maildir”或类似名称。您还可以查看 /var/mail 或 /var/spool/mail
这里有一些关于在服务器之间迁移电子邮件的一些方法的入门信息：http://squirrelmail.org/docs/admin/admin-11.html#ss11.2
另外，您可能需要重新思考为什么需要格式化整个系统。 *nix 系统不需要像 Windows 系统那样对待。它们通常可以重新排列、扩展、调整和以其他方式更改，而无需重新格式化。
至于 SquirrelMail 本身，您可能需要备份一些内容，其中包括 SquirrelMail 本身的任何配置文件（在其“config”目录中）以及您安装的任何插件（您通常可以复制整个插件）最典型插件的目录并以最小的麻烦将它们传输到新系统），您可能在“主题”目录中拥有的任何自定义主题，最后是所有用户首选项。用户首选项的位置取决于您的配置 - 可能在数据库中，也可能在“$data_dir”设置指向的任何位置（通过查看“config/config.php”或使用 SquirrelMail 的配置工具（“config /conf.pl")。如果您将用户首选项存储在目录中，通常只需复制整个目录即可。请注意，即使您将 SquirrelMail 配置为将用户首选项保存在数据库中，某些插件仍将使用数据目录出于某些目的而设置，因此，无论如何，建议备份该目录，
SquirrelMail 上详细介绍升级的 wiki 页面与您需要的内容相同：http://squirrelmail.org/docs/admin/admin-4.html
在服务器之间备份和迁移此类内容时，您需要非常小心文件/目录所有权/权限您的电子邮件数据以及应用程序配置和首选项数据。如果服务器之间的用户和系统帐户名称以及 UID 不同，则您需要非常小心地调整文件的所有权以适合目标服务器。
Backing up your email messages is not a SquirrelMail issue. SquirrelMail is an IMAP client and does not store email itself. You need to determine what kind of storage is used for your particular email system. If it's a very simple/default *nix email setup, you might start by looking in /home/ for a directory with a name indicative of the purpose, such as "Mail", "Maildir" or similar. You might also look in /var/mail or /var/spool/mail
There is some starter information on some ways to migrate email between servers here: http://squirrelmail.org/docs/admin/admin-11.html#ss11.2
Also, you might want to re-think why you need to format the whole system. *nix systems don't need to be treated like Windows systems do. They can usually be rearranged, expanded, tweaked and otherwise changed without the need for reformatting.
As for SquirrelMail itself, there are a couple things you may want to back up, which would be any configuration files for SquirrelMail itself (in its "config" directory) and any plugins you'd installed (you can usually just copy the entire plugin directory for most typical plugins and transport them to the new system with minimal hassle), any custom themes you may have had in the "themes" directory, and finally, all user preferences. The location of your user preferences depends on your configuration - might be in a database or might be wherever the "$data_dir" setting points to (find this by looking in "config/config.php" or by using SquirrelMail's configuration tool ("config/conf.pl"). If you have user preferences stored in a directory, you can normally just copy the whole directory. Note that even if you have SquirrelMail configured to keep user preferences in a database, some plugins will still use the data directory setting for some purposes, so it's advisable to back up that directory no matter what.
The wiki page at SquirrelMail detailing upgrades is the same thing you need: http://squirrelmail.org/docs/admin/admin-4.html
When backing up and migrating things like this between servers, you need to be very careful about file/directory ownership/permissions on both your email data and your application configuration and preferences data. If user and system account names and UIDs are not the same between the servers, you'll want to be very careful that you adjust the ownership of the files to suit the destination server.