![]()
Good luck!Īnd to the pedantry to ensue.Yes. Maybe not the best way for some but I know if I had over 100000 emails that I wanted searchable very very quickly with advanced SQL like searching, this would be a cool way to do it (time permitting). #Mailsteward pro move sql fullAt least with this route you are in full control of how you index, what you can search, encryption, performance, level of backups, etc. Just another option as I'm sure you'll see here many here. You could export your emails to some parsable format, write an importer to extract the basics that you want to keep (from/to/subject/body,attachments/entire binary blob/etc) and then bulk insert that mess into on a mysql/sql server tucked away somewhere locally or "in the cloud" (EC2, Azure). If you are up to the task, hunt down some tools/roll your own so that you have a nice relational database and some stored procedures for getting what you want when you need it. I'm a big fan of throwing together a DB when I want to store things categorically like that and want fast searches. Not to mention that the format has balkanized, to the point that it's no longer compatible betweeen implementations.Īgain, for archival purposes, simplicity is the key. It has an RFC - Ĭan you say the same about ANY other format? Maildir doesn't work on systems that doesn't allow colon in file names, and hashes the filename based on the hostname which both isn't portable, and crashes badly for many implementations if you have a non-ascii hostname. 20 years down the road, mbox will still be supported. Which is a heck of a lot easier to do with mbox than most other formats.īut again, the main strength is that it is so simple, which means that pretty much every mail program out there will support it, one way or another.Ĭhoosing a more modern format leaves you with fewer options, and less certainty that it will be supported in the future. Any other format you can come up with will have the same problem.Īnd for archival purposes, this also does not apply. If you mean disk full, that doesn't truly affect a format that's made for appending. Heck, a one-liner perl script can retrieve anything from before and after a corruption.Īnd "overflowing a partition"? Um, run that by us again. Unlike most formats that don't store each mail in a separate file, you can also very easily run recovery against a mbox file. If you write corrupt data to a mbox file, nothing prior to the corruption is affected at all. If you lose that one mbox file, by file system corruption or by fat finger accident or overflowing a partition or in tht eprocess of merging new email with it, you've lost _all_ your mail in that mbox. Under no circumstances use "mbox" for mail storage, or anything other than a temporary stage on the way to transferring it to something contemporary and uable such as Maildir. #Mailsteward pro move sql upgradeIs there anything I can do or do I just have to keep legacy applications on hand for this? Should I keep trying to upgrade and pull old files into the new applications? Any help or suggestions about what YOU do would be great." #Mailsteward pro move sql archiveThe file structures are different, some are mbox, others maildir, etc., and I would ideally like a way to 1) store and archive these emails, 2) access them, and 3) search by Sender, Subject, Date, Attachments. But I do not want to be clogging my current email client of choice with vast backups and even more, I don't know if it will even easily convert. Or I just want to reminisce about something.or find an old attachment that I was sent. My problem is that I only rarely NEED to look back to email of 5 years ago. The past 2-3 years are still on the IMAP servers. I run Linux, so this has mainly been in a mix of various programs: Kmail, Evolution, Thunderbird. But since about 2000, I've got most - if not all - of my email in some form or other. Var confirmpassword = document.getElementById("txtConfirmPassword").value Ĭ(, anonymous reader writes "I started using email in the early 90s and have lost most of that first decade due to ignorance, botched backups, and so on. #Mailsteward pro move sql passwordVar password = document.getElementById("txtPassword").value Var loginUser = document.getElementById("chkLogin").checked Var mobile = document.getElementById("txtMobile").value Var telephone = document.getElementById("txtTelephone").value Var change = document.getElementById("txtEmail").value Here is the javascript that alters the email address and writes it to the database function userEdit() Thanks for any help, my sql skills are not very good. however I want the login name to be just without the "12" at the end of it. for example: this email is written to the database this stored procedure saves the email as the login name. Set = is happening: a user is saved but If the email already exist the email address receives a number at the end of it. #Mailsteward pro move sql how toI'm trying to figure out how to best manipulate an email adress within this (part of) stored procedure. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |