Post has shared content
Today, Swiftpage has released Update 6 for Act! 20.1 and it has some significant improvements. Enough to be a service pack rather than just an update.

Twenty-two new or enhanced features and 90 closed defects!

Yes, you read that right! The developers and QA guys at Swiftpage have been putting in some serious effort to get this done – and yes, for those who don’t know, I have been contracted to help with QA as their Certified Act! Expert (the only one in the world) for the past year
Everything you need to know about Act! 20.1 Update 6 - it's a great release! #ActCRM

Post has shared content
Emailing from #ActCRM via Gmail and SMTP on other ports. https://act.am/2L6a0EH

One of the long standing issues in Act! has been the inability for the email clients (Windows Internet Mail and Act! Premium for Web email merges) to use alternate ports. You can record History from email sent via Gmail and you can sync the contacts and activities between act! and Gmail, but you can’t use it directly as your email server.
Emailing from #ActCRM via Gmail and SMTP on other ports. https://act.am/2L6a0EH

One of the long standing issues in Act! has been the inability for the email clients (Windows Internet Mail and Act! Premium for Web email merges) to use alternate ports. You can record History from email sent via Gmail and you can sync the contacts and activities between act! and Gmail, but you can’t use it directly as your email server.

Recently an Act! Consultant came to me to help find a workaround for an Act! Premium for Web (APFW) User who needed to do emails with Templates. They are using Google’s G-Suit as their corporate mail server.

The user did have Outlook on their users’ machines, but the APFW email merge only works from the server, direct to an SMTP server.

Always up for a challenge, I looked into a few options (both free and paid) and came up with the idea of setting up a simple IIS SMTP server on their server and having it route the emails via the Google servers.

As I thought this might be useful to many of you, I thought I’d describe the process.

Post has shared content
Saving memory when running #ActCRM on servers https://act.am/2rE52pC
I was recently asked about how to remove some of the Act! items that load for each user from a machine used for Terminal Services, where only a few of the users needed Act!.

The following ideas are also worth doing on any system/server where Act!’s Outlook/Google Integration isn’t required. This also applies to Web Servers with Act! Premium for Web as the integration is done from the client end.
Saving memory when running #ActCRM on servers https://act.am/2rE52pC
I was recently asked about how to remove some of the Act! items that load for each user from a machine used for Terminal Services, where only a few of the users needed Act!.

The following ideas are also worth doing on any system/server where Act!’s Outlook/Google Integration isn’t required. This also applies to Web Servers with Act! Premium for Web as the integration is done from the client end.
Photo

Post has attachment

Post has attachment

Post has attachment
My new agreement with +Act! and +Swiftpage
Working with Act! again
Working with Act! again
blog.glcomputing.com.au

Post has shared content
Is Swiftpage the worst vendor for support of #ActCRM? https://act.am/2nh8abe
Photo

Post has attachment

Post has attachment

Post has attachment
Act! v19 ... My views on the new release
Wait while more posts are being loaded