Anyone have file structure documentation for Windows Live Mail contacts.edb file? - email

Does anyone have any documentation or info on the file structure of the contacts.edb file as it is used in Windows Live Mail? I can't seem to find any way to import file back into WLM (I'm told it HAS no way, and must be "backed up" via manual exports to CSV files).
Given the apparent lack of means to reimport a backed up EDB file, I figured that perhaps I could just write a program to read all the contacts out into vcards or something, and then import those. (I'm actually looking ultimately to get them into Outlook, and ditch WLM for this user, cuz I don't feel like dealing with these maintenance headaches).
Problem is that I cannot find anywhere any information on the file format/structure for WLM's EDB files.
Thanks in advance, any help GREATLY appreciated!

To anyone finding this in the future, THIS CAN BE DONE, without needing to code anything! Use this program - EseDbViewer - to export the file to a CSV file, and then you can import that where ever you want.
Note that you pretty much need the whole file structure containing the edb, not just the edb file.
Hat-tip to #MicrosoftHelps on twitter.

Related

Powershell import encoded module

I am writing a script with a lot of modules but I don't really want the user to see my source code so I figured to encode everything in base64 since the user won't be able to decode it even if it is that basic.
I tried to somehow add an encoded module but no luck.
So my question is -
Is it possible to import a base64 encoded module to the main script file?
If you have any better solutions to hide source code please share, I would be more than happy to try them out.
P.S. I tried to find some info on making a .dll files but found out I would have to rewrite the script in C#. (if I didn't missed anything)
Also I tried to put all modules into one encoded file, but then the file gets too big and Powershell is not able to process it anymore.
You've got two options, which can be combined if you would like to be extremely sure that no one will be able to access your code, making your code into an exe was already mentioned, there are several projects to do this but This one is nice as it is wholly contained within PS. The other, imo better, method is to use an obfuscator, which will take your code and replace variable names with nonsense strings and make other changes to make your code very difficult to read, it's still possible to work out your code but generally not worth the effort, you can find a working one Here. But I do have to add that obfuscating your code really goes against the powershell ethos and I recommend against doing it unless you have some sort of requirement too being passed down from management. And please note that this NOT an acceptable method of obscuring code that includes passwords, api keys, or any other information that needs to be secured as all of those are quite easy to extract from code that has been obfuscated this way.
You could change your ps1 to an exe file by using
https://ps2exe.codeplex.com/
You'd still be able to get at the code if you tried, but it would prevent a casual look.
Why do you want to hide the modules?

Powershell Help, the code i have sends a email out to people, need to save a the data of the code but not as a text file

I am new to powershell and need some help. I have a code which runs everyday and sends an email out to people regarding the server status and other details. What i need to do is save that file as maybe an output file or something so if the customer wants can go in to powershell type in the script command and it comes up with the information thats on the email
Is there a way to do this. This cant be a text file. Has to be something u can type and the data comes up?
please help, thanks in advance
Os
Without code the only definite answer I can give you is using the Out-File command. I do not see why it can't be a txt file (because it's just an email)since data can come up and be typed. You can always Out-File to excel or csv, it really all depends on what you're trying to ask.

tiki-wiki: How to batch import categorized articles from a CSV file

Importing categories as a CSV file is OK in tiki-wiki, But how to import categorized articles to the system. Tiki supports media wiki and word press importing, While my data base has another format.
Is there any module for CSV upload/import?
Is there any flexible migration-like script to import articles?
In case that both of answers are NO, would you please give me a clue to write down the proper code to import articles directly to data base.
I went through understanding database, But I think accessing to database directly should be my last choice!
For custom import jobs, you can use Tiki's profiles. The profiles are a YAML-based format. While it is not the primary use for them, it might be the easiest way to perform what you want to do.
Normally, you need to place the profile in a repository to execute it, but there is a developer option to load content from a textarea. You can simply prepare your YAML definition and paste it in there.
Categorizing elements through the database could be harder than it seems as many tables are involved.

perl excel to pdf

I'm using perl with an excel template to try to make creating invoices for clients somewhat automated. My only issue is that I'd really like to be able to convert this excel file to a PDF when I'm done, but I can't seem to find any perl modules that do anything of the sort. Anyone ever heard of something like this being done? I know it can be done somehow, since word and open office manage to do it!
Simply shell out to unoconv.
There are also Perl bindings to UNO, but last time I looked, they didn't work.
You may have to convert/flatten the Excel file first, and then figure out a way to pipe it in, but this may get you headed in the right direction http://metacpan.org/pod/PDF::Create

What/where are the "quote site" options for z/OS FTP server?

I'm writing a script using Perl and Net::FTP, which is trying to upload a rather large file to the mainframe and I can't seem to get the primary/secondary allocations right.
I try to change them but it appears that, because the data sets are SMS-managed, they go to a different volume each time.
So I went looking the the quote site option which would (hopefully) lock the upload to a specific volume.
The current options I have are:
$ftp->site ("bl=10204 lr=170 rec=vb cy pri=100 sec=100")
and space is pretty tight on most volumes. However, I've located a volume with the required space but don't know how to specify that in the FTP options.
Is there a document somewhere detailing them? I couldn't find anything in the CommServer stuff nor did a Google search for ftp zos quote site turn up anything useful.
Alternatively, does anyone know the option to specify a fixed volume? Obviously I'd prefer the former since there may be other useful things in there but, at this point, I'd take the latter gratefully - I've darn near pulled out all my hair :-)
Log onto your mainframe's FTP using an interactive FTP program (e.g. FTP). Then type "quote help site" and you should get a good list of the options.
Just a little explanation... "site" is a command for the mainframe's FTP server. Typing "help" in front of it gets you help on the function. However, just typing "help site" will look for help on your FTP client (which probably never heard of the site command), so you have to pump the command to the server, which is what the "quote" command does.
BTW, your site command is asking for 100 primary and 100 secondary cylinders. That's a hefty chunk of DASD. Do you really need all that?
Good luck... let me know if you have any questions. I practically live on FTP on the mainframe and have written dozens (maybe hundreds) of Perl scripts to make things easier.
As a general FTP reference for z/os try Z/OS V1R7.0 Comm Svr: IP User's Guide and Commands.
Site commands can be found here.
Why not let SMS find the appropriate volume by using a DataClass appropriate for the file size?
How much hair did you start out with? Some can't afford to pull too much!