W
wkarraker
Version: 2008
Operating System: Mac OS X 10.5 (Leopard)
Processor: Intel
Email Client: Exchange
This problem has been stated before but I was curious if a fix would be made in a future patch. The problem is a VCF card that is sent directly by Entourage inserts a space after the 76th character (typically the e-mail address itself). If the VCF card is moved to the Desktop first, compressed to a zip file by the Finder and then forwarded, the file decompresses without error on the recipients end. Unless you manually deselect the auto zip function in the attachments pop-up you end up with a file called '[Original Name].vcf.zip.zip'. Not a very professional looking file if sending it to a client.
The VCF file is in perfect condition prior to sending, I have reviewed multiple VCF files before and after sending and it consistently has problems if a line has more than 76 characters and is not zipped before sending. If the file is compressed in other formats (BinHex for one) it still develops the same problem.
Operating System: Mac OS X 10.5 (Leopard)
Processor: Intel
Email Client: Exchange
This problem has been stated before but I was curious if a fix would be made in a future patch. The problem is a VCF card that is sent directly by Entourage inserts a space after the 76th character (typically the e-mail address itself). If the VCF card is moved to the Desktop first, compressed to a zip file by the Finder and then forwarded, the file decompresses without error on the recipients end. Unless you manually deselect the auto zip function in the attachments pop-up you end up with a file called '[Original Name].vcf.zip.zip'. Not a very professional looking file if sending it to a client.
The VCF file is in perfect condition prior to sending, I have reviewed multiple VCF files before and after sending and it consistently has problems if a line has more than 76 characters and is not zipped before sending. If the file is compressed in other formats (BinHex for one) it still develops the same problem.