Acrobat 9 and the API issue

Have you tested Mail Print with Acrobat 9 Professional yet? Does it work? Is the API bug that plagued earlier versions of Acrobat, and that sometimes caused trouble with Mail Print still there?

Ville,

We haven't tested Acrobat 9 yet, I'll post here when we have.

I installed Acrobat 9 and mailprint version 1.31104 does not print PDF attachments anymore. When do you plan on testing/fixing Acrobat 9?

And just to clarify, it doesn't print the PDF at all, with or without the "print PDF files using Acrobat's COM interface" checkbox checked. It's Acrobat 9 Professional. Thanks!

In our initial testing Acrobat 9 is working fine with Mail Print 2.0

I'll post here again after we have done some testing with Mail Print 1.3

Mail Print 1.3 seems to be fine as well, Dave do you get any error messages in the log window?

Hi Tony. After more testing this seems to be an issue with google apps (gmail) that I've spoke with you about previously. Mailprint thinks it has already printed the PDF for some reason so it doesn't try to print it again. Is there a way to clear out what mailprint thinks it's printed already - some type of log file somewhere? Thanks. This only happens when trying to print from files from gmail, other mailboxes work fine.

On version 1.30 if you look in the installation folder there is a file called printed.lst, if you delete this it will reprocess the messages.

Is there any indication as to whether the Acrobat API bug that caused problems for Mail Print has been fixed in Acrobat 9.0?

I think it's too early to say yet.

i have the same API Problems with Acrobat 9
is there an fix to this problem ?

Jacon,

What problem are you having with Acrobat 9?

i get an API error i mailed your support some screan dumps of the event error

Jacob,

What version of Windows are you running Mail Print on?

I am running it on an Windows Server 2008 with Admin rights

Jacob,

Can you check on the physical console to see if Distiller has popped up a message box asking you to acknowledge the license. It does this for every new user, as the service is counted as a new user it will appear on the physical machine but not through any terminal sessions.

Hey that helped, i cnahged the service logon info so it uses the admin account, and it worked