 |
 | Home | Contact Us | FAQ | Search & Site Map | Link to Us |
 | Sign In | Join | Other 45 Sites in Network |
| HomeDiscussionsAccessExcelInfoPathOutlookPowerPointPublisherWordDirectoryUser Groups Related Topics Outlook ExpressInternet ExplorerWindowsMS Server ProductsMore Topics ... |
MS Office Forum / Outlook / 3rd Party Utilities / June 2004Outlook 2000 and ACT! Address Book
Hello World, My ACT! user are having problem in sending attachements with their Outlook emails. This happens only when they pull an address from ACT! database using ACT! address book interface (service) from within Outlook client. Otherwise they are fine if they send the same email (with attachement) from within ACT! email client. anyone? any help? thx in advance -SN What kind of problems?  SignatureSue Mosher, Outlook MVP Author of Microsoft Outlook Programming - Jumpstart for Administrators, Power Users, and Developers http://www.outlookcode.com/jumpstart.aspx Hello World, My ACT! user are having problem in sending attachements with their Outlook emails. This happens only when they pull an address from ACT! database using ACT! address book interface (service) from within Outlook client. Otherwise they are fine if they send the same email (with attachement) from within ACT! email client. anyone? any help? thx in advance -SN The attachment does not go through rather it gets converted to Winmail.dat file. rgds -Sarwar >-----Original Message----- >What kind of problems? [quoted text clipped - 13 lines] > >. (pardon my jumping in) Have the senders use Plain Text or HTML instead of Rich Text format for their e-mail message format...does that help? > The attachment does not go through rather it gets > converted to Winmail.dat file. [quoted text clipped - 26 lines] >> >> . have tried that but no change..... in fact, the only time attachement gets converted to "winmail.dat" is when they pull the address from "ACT! Address Book". If they type the same address (instead of fetching it) then everything stays fine. thanks -SN >-----Original Message----- >(pardon my jumping in) [quoted text clipped - 34 lines] > >. They need to check the settings for the individual address and make sure it's not marked for rich-text only. If the ACT! address book marks all addresses for RTF, then the advice about switching to plain text format is the most likely solution. SignatureSue Mosher, Outlook MVP Author of Microsoft Outlook Programming - Jumpstart for Administrators, Power Users, and Developers http://www.outlookcode.com/jumpstart.aspx have tried that but no change..... in fact, the only time attachement gets converted to "winmail.dat" is when they pull the address from "ACT! Address Book". If they type the same address (instead of fetching it) then everything stays fine. thanks -SN >-----Original Message----- >(pardon my jumping in) > >Have the senders use Plain Text or HTML instead of Rich Text format for >their e-mail message format...does that help? > [quoted text clipped - 4 lines] >> rgds >> -Sarwar >>> "Sarwar N" <anonymous@discussions.microsoft.com> wrote in message >>> news:b76001c40ba2$41dbfc40$a601280a@phx.gbl... >>> Hello World, >>> >>> My ACT! user are having problem in sending attachements >>> with their Outlook emails. This happens only when they >>> pull an address from ACT! database using ACT! address book >>> interface (service) from within Outlook client. Otherwise >>> they are fine if they send the same email (with >>> attachement) from within ACT! email client. [quoted text clipped - 7 lines] > >. In ACT! email options (Edit ->Preference ->Email options) we have only Plain Text and HTML options (no RTF)we have tried both the options but it did not make any difference. Interesting thing is when we send the same email with same attachement from within ACT! email client (which infact uses Outlook 2000 interface)there is no issue. The email gets to recepient(s) with the actual attachement. rgds -Sarwar >-----Original Message----- >They need to check the settings for the individual address and make sure [quoted text clipped - 48 lines] > >. That sounds like an option for message format. I was referring to the individual address setting. Double-click the underlined address in an outgoing message. SignatureSue Mosher, Outlook MVP Author of Microsoft Outlook Programming - Jumpstart for Administrators, Power Users, and Developers http://www.outlookcode.com/jumpstart.aspx > In ACT! email options (Edit ->Preference ->Email options) > we have only Plain Text and HTML options (no RTF)we have [quoted text clipped - 15 lines] > plain text format is > >the most likely solution. > >have tried that but no change..... in fact, the only time > >attachement gets converted to "winmail.dat" is when they [quoted text clipped - 44 lines] > > > >. tried that..... in E-mail prop windows, the....."Always send to this receipient in Microsoft Outlook rich-text format"..... option is unchecked. rgds -Sarwar >-----Original Message----- >That sounds like an option for message format. I was referring to the [quoted text clipped - 70 lines] > >. Well, that's too bad. It means there's no way to set an option to correct the problem at the recipient level. You may have to create the message in plain text format to avoid the Winmail.dat attachment. SignatureSue Mosher, Outlook MVP Author of Microsoft Outlook Programming - Jumpstart for Administrators, Power Users, and Developers http://www.outlookcode.com/jumpstart.aspx > tried that..... in E-mail prop windows, the....."Always > send to this receipient in Microsoft Outlook rich-text [quoted text clipped - 9 lines] > address in an > >outgoing message. > >> In ACT! email options (Edit ->Preference ->Email > options) [quoted text clipped - 63 lines] > >> >>>> they are fine if they send the same email (with > >> >>>> attachement) from within ACT! email client. If you see my March 17 posting. We have already tried "Plain Text" format option (in fact that was the very first thing I suggested to my users) but that did not help in resolving "winmail.dat" issue. I have done some more digging within Outlook 2000 client. When you enable/attach 'ACT! Address Book' service using "Outlook->Tools->Services->Add", that's when this service starts. Outlook uses a DLL named "actab32.dll" to fetch email addresses from ACT! database. It seems there is some problem in email address translation at Outlook side where Outlook is not able to understand ACT address wrappers. Basically, this looks like an issue with "actab32.dll" that needs to be fixed....... This is my understanding of this problem. I would be glad to know if anyone else sees it differently..... btw, I have seen similar issues with Lotus Notes Mail service under Outlook which uses "nwnsp32.dll". -cheers Sarwar >-----Original Message----- >Well, that's too bad. It means there's no way to set an option to correct [quoted text clipped - 84 lines] > >. I think you've diagnosed this pretty well. It might be interesting for you to get the trial version of Office 2003 and see if it handles it better. SignatureSue Mosher, Outlook MVP Author of Microsoft Outlook Programming - Jumpstart for Administrators, Power Users, and Developers http://www.outlookcode.com/jumpstart.aspx > If you see my March 17 posting. We have already > tried "Plain Text" format option (in fact that was the [quoted text clipped - 23 lines] > create the message in > >plain text format to avoid the Winmail.dat attachment. > >> tried that..... in E-mail prop windows, the....."Always > >> send to this receipient in Microsoft Outlook rich-text [quoted text clipped - 88 lines] > > > >. Hey, Do you know what dll MYOB uses ? cause i have everythign set to plain text in outlook but when i send a email via MYOB it sends it in Rich Text! Thanks K > If you see my March 17 posting. We have already > tried "Plain Text" format option (in fact that was the [quoted text clipped - 116 lines] > > > >.
|
Reply to this Message |
 Sign In
 Join
 My Latest Posts My Monitored Threads My Blog My Photo Gallery My Profile My Homepage Start New Thread Enable EMail Alerts Rate this Thread
|
©2008 Advenet LLC Privacy Policy - Terms of Use
This website includes both content owned or controlled by Advenet as well as content owned or controlled by third parties.