whats the total number of #s in:
q: some pdfs to iphones via activesync are corrupt we have two server applications (one .net/asp web app, the other a native windows app) that generate pdfs that are then emailed to our users on exchange 2010. the apps deliver the emails to the exchange server via smtp, and our iphone/ipad users receive their email via activesync.
pretty much all of the pdfs generated by the web app and many of the pdfs generated by the windows app fail to open on an iphone or ipad. tapping the attachment shows the screen that would display the pdf with the name of the file at the top but the bottom of the screen is completely grey.
one thing i have figured out is that the attachment on the ipad is uuencoded. forwarding the attachment to another email address shows the uuencoded format. heres a sample:
begin 600 unknown
m)5!$1btq+c0-)>+cs],-c8@,!o8fh\/](6s8u-b`q-#a=+tqi;f5a<fez
m960@,2]%(#dq-#8o3`q,s`q.2].(#$o3r`y+u0@,3(x-3,^/@ue;f1o8fh-

---snip---

m,c8t,`p,#`p,!n#0it<f%i;&5r#0h\/]3:7ie(#8^/@t*<w1a<g1x<f5f
.#0hq,38-b4e14]&#0h`
`
end

whereas the normal version of the file looks like a normal pdf:
%pdf-1.4
%âãïó
6 0 obj<</h[656 147]/linearized 1/e 9698/l 13571/n 1/o 9/t 13405>>

---snip---

trailer
<</size 6>>
startxref
116
%%eof

so i think the problem is that the attachment is being double uuencoded somewhere, or the iphone is failing to recognize that the attachment is uuencoded and not decoding it.
any suggestions on where to begin troubleshooting this problem?

a: it appears that iphones and ipads do not support uuencoded attachments.

user
The given text has 10 "#"s.
assistant