I opened a new account on an American Web-host and I didn't take into account that his server will not support Hebrew chars(on his file system):
Any way, after coping the gibberish path :
<pic src="..\_images\gallery\smallPictures\2010-08-02 âìøéä àåâåñè 2010\" width="150" height="120"></pic>
to my XML file and saving it with UTF-8 encoding it worked.
is there a way to generate this Gibberish in c#?
Is there a way to fix the encoding of the folders (to be in a certain encoding)?
Related
I have Encrypted PDF File and i have convert encypted PDF file To Base64 string. I want Base64 string convert into PDF File (Means PDF file will write without password). PDF File should open.
Encrypted Base64 string is perfectly convert into pdf file but when i am trying to open the pdf file it is asking password.
I want when file is convert into Encryted base64 to PDF File then it should open without password .File is saving on my folder.
How i can do it. with asp.net with c#.
Can’t be done.
Otherwise the mere act of emailing a password protected PDF removes the protection and I’m pretty sure the payslips I get are protected.
While importing A comma-separated values (CSV) file on company server error showing invalid file format But when I have tried locally or from testing server the same file is importing
Check default Windows CodePage both on server and local computer.
We use the LumiSoft.NET MIME library to create EML files. These EML files are constructed by database values. The body of the email can be plain text, RTF, or HTML. We know when the body is HTML so, when that occurs, our EML file's content-type is set with this line:
Content-Type: text/html; charset="utf-8"
When the body is plain text or RTF (because we don't know which it is), we set the content-type to RTF like so
Content-Type: text/rtf; charset="utf-8".
The HTML EML files show up just fine across different products... but the RTF EML files seem to be interpreted differently by different products. This worked for years and our resulting EML files were QA'd against Outlook Express and they appeared normally. But recently we had some customers report issues with these emails showing up with the message bodies as attachments. In Outlook 2007 SP2 and Outlook 2010, the email bodies do indeed show up as TXT files that are attached to the email... and the bodies inside the email itself are empty. Furthermore, we use a product called dtSearch and when it converts these EML files to HTML, it does a similar translation where the body of the EML file is shown in the content of an attachment named Attachment0.DAT. Futhermore, we also process these EML files through Outlook Redemption and, just like Outlook 2010, the message bodies are in a TXT file attachment. So weird behavior across the board... here's some screenshot of it in action.
Outlook Express:
Outlook 2010:
Here's the actual EML file.
Are we doing something wrong here by using RTF for the content type? It seems to have worked in the past and works with Outlook Express. It's been recommended to switch to the MSG format using Redemption instead of EML format to alleviate this but I believe that puts a prerequisite requirement on the user machine of either Outlook or the MAPI library.... but if the EML format isn't parsed the same by different products, then maybe the MSG format is the way to go.
The content of the email does not look like a valid rtf (No magic number "{\rtf").
It's plain text with quoted printable transfer encoding.
You should use content-type: text/plain.
I have files with filename containing # in it (eg: #qwerty.txt, file#1.exe).
I want to upload these files to WebDAV Server, running on Linux.
In ASP.Net, I use HttpUtility.UrlEncode() Method for encoding URL.
But, this removes # from the file-names, to be uploaded and thus uploading fails.
Please reply.
Thanks.
UrlEncode does not remove pound/hash characters but replaces them by %23.
Thus #qwerty.txt becomes %23qwerty.txt. If you use that resulting filename to reference the local file for uploading it will fail to find it.
If you want a more definitive answer you might want to update your question with the code you are using to upload the file.
Hell guys,
I'm coding in csharp to send an email which contains a .zip file (has htmls and css inside). When I check the mail recieved, In fact, instead of the .zip file, the attachment becomes a txt file and has:
FILE QUARANTINED
The original contents of this file have been replaced with
this message because of its characteristics.
File name: 'xxxxxxx_Result.zip'
Virus name: 'Large uncompressed size'
The exchange server has blocked the zip file..I'm using CDO to create and send the email.
I tried using the code to send a mail with a zip file generated by WINZIP, there was no problem, then I tried using outlook to send a mail with the zip file generated by my code(I use sharpziplib library), the problem occured...
How can I do to send the attachment correctly? Many thanks in advance!
Allen
I encounter similar problems sending email on our network. I've found that using an alternate compression format, such as 7-zip (.7z), is adequate to get my content through the filters. This could resolve the issue if the block is not due strictly to size.
Looks like your mail server or spam service have removed your attachement and replaced it with the txt file, it sounds like your code is fine and you need to speak to an admin regarding the mail filters and send size quotas!
For anyone facing this problem, here is a solution. You have to explicitly set the file size for the zipentry.
ZipEntry newEntry = new ZipEntry(fileName);
newEntry.DateTime = DateTime.Now;
newEntry.Size = fileData.Length; // setting data size