I am running AR 8.0B and AI 8.0A and 99%+ of of our invoices and 100% of statements emailed. I just got chewed out by my client because for the 3rd time the email setup account information got cleared and invoices were sent out with the WRONG "From:" and "return address" which is me who is a 3rd party service company which works like a lock box. My customer insists that his customers not see that he is using a 3rd party company for Invoicing and AR. He is right now reviewing with his owners and I may lose the account.

We have been mailing successfully for 6 months without a single glich but for the 3rd time in the past 12-14 months, part of the email setup information got cleared out namely the "Account Name" and "Password". As you can see I have done no recent Adagio updates, sorry to be behind, so I have no idea how those fields go cleared. Since we have been successful for such a long period, I had no reason to suspect that setup information had changed. There is nobody else who has access to these programs and fields except me. I have posted notes in the past complimenting Softrak on the email implementation for it's ease of use and facility. Reliability is NOT high on my list.

The implementation of "printing" with the pop-ups and information if very complete. A popup of "the email setup" would give the operator an opportunity for verification before sending hundreds of emails with the WRONG return address.

Hi Kay,

The information for Email setup (return address, account name password, etc) is stored in the Windows Registry. In addition, it is stored by Adagio User ID - this means if you log into Adagio with a different User ID, you will not get the same options.

Unless you lost something in your Windows Registry (or moved to a new workstation and didn't re-enter the information), then the email setup information should still be there. I assume you don't log into Adagio using different user ID codes.

Hi:

I can understand storing the information separately for each Adagio user. But wouldn't it be better to store the information for each user in an Adagio table rather than the Windows registry?

That way it wouldn't matter which computer the user sat down to use. The settings would be always be available.

Just reporting how it currently works, to help identify why settings might 'all of a sudden disappear'. Indeed there may be a better way of handling this.

Where does it warn the user of what can change user information? It makes no sense to store this in the registry. Where is the warning? This information should be in disk tables and refreshed at module start/update. You are right I did not move to another workstation, that was the 1st failure 14 months ago and it was only a couple of invoices. No we don't log on to different workstations.

As a programmer of over 40 years, this implementation is "fun" that a programmer figured out how to do and implemented for no good reason. I fired these kinds of programmers for playing dangerous games with my products. This is a management failure and I will probably pay the price for poor management. This feature should be implemented by user-id and follow me at whatever workstation I sit at.

I now know what happened. I replaced my system server-Windows 2000 to Windows 2003. I know that there were significant differences in the management of client workstations based on this change. I planned for these changes and suffered no loss of time or function. But NOT knowing that Adagio, a user program, is storing critical information in the registry is ludicrous and probably has cost me my largest customer.

Again, I am going to request a pop-up similar to the print pop-up showing current email controls before the actual send. It is not reasonable nor should it be allowed to allow an operator to go to the email screen review the email setup for no apparent reason every time we want to send invoices or statements except in the form of a pop-up. Operators are not supposed to be aware of, how to change, or updating things that they are just supposed to use; this update/change feature should be a security restricted function. If things are not as they should be, in a pop-up, procedures should have the operator contact the supervisor for direction. Current implementation of email is great but EXTREMELY DANGEROUS and for me it is going to be very expensive.

I apologize for venting, but this is going to be very expensive for our copmany!

You are absolutly correct. I had no reason to suspect the effect on Adagio of a server upgrade.

Hi Kay,

Are you using the MAPI or Direct method of emailing documents? Do you email documents 'now' or do you send them to the queue and email from there?

This is the first report we've had with the Email Setup information not working as expected, with any of our Adagio users, so it may be unfair to say that emailing within Adagio is unreliable.

One reason why information like this should be in the Windows Registry (ie attached to the workstation) is when using the MAPI method of sending emails, you may not have access to the correct Outlook mailbox when sitting at a different workstation.

I believe if you are using MAPI as the method for sending emails, then having the return address blank will mean the process will instead use the address from your email program doing the sending. From your comments, this is not the desired behaviour, but rather have an interrupt of some sort - either indicating the return address is blank or perhaps not send the email. When using MAPI, this behaviour may be out of the control of Adagio but we can investigate this.

When I attempt to send a Direct email using our email server, with the Return Address blank, the email doesn't get sent. If you are using Direct, then there is different behaviour than what I saw.

Perhaps we'll be able to take a great email implementation method and make it even better. Thanks for using Adagio!

Let me start from the Setup top:
- Return address: Valid email address at my client
- Request receipt checked
- Select "Direct" -- probably never will use MAPI
- Mail server: Network address of client exchange server
- Display: Name of Client company
- Server authentication not checked
- Account name: Same as return address above
- Password: valid password for the email account above.

In general, invoices are sent to the queue because I supplement the generated (invoice).pdf with additional page(s), i.e., purchase order information, billing policy, informational notices, etc. Statements are usually sent immediately because there are no supplements.

Let's clarify - Emailing works great and exactly as advertised! Absolutly a great implementation until this issue. I have requested Setup CC:, supplemental attachments when submitting either to queue or sending. The problem occurred when I changed to Windows Server 2003/X64 and the way it handles and manages the desktop and my documents (I beleive I have stated this correctly, my IT company did this upgrade for me which had absolutly nothing to do with Adagio except that the drive mapping changed and the name of the server changed).

Remember that we are a service company. After thinking through this entire episode, I absolutly believe that the email setup like printers should follow the UserId. Because now the problem I have is that for my next customer, I will need to change the email setup BY CUSTOMER on the fly unless it is tied to the UserId. I will use different userid's by customer on the same computer. I will need to verify email setup and be able to change if need be totally unrelated to the workstation but tied to the UserId.

I think that I have provided all the necessary information. If this needs more discussion, my contact information is on file and I would be more than willing to discuss. This is a great way to communicate but I am getting tired of typing.

I did a little more investigation and I now beleive that this setup is more dangerous than I previously described.

My research now shows that the "Email setup" is by user by workstation. In other words, UserId AA signs on to workstation Y1 and sets up email. He later goes to workstation Z2 and signs on as AA - the email Setup is different or not even setup.

This is extremely dangerous and I have just spent the better part of the morning verifying that all my users and workstations are setup correctly to avert another accident.

I think Softrak needs to do an immediate review of this implementation and put a correction out as a HotFix. If you think about it, nothing more than a setup by company is sufficient. You probably would never have a given company have more than one email setup. Also the same email setup should be used company wide to include AR and any other module relative to that company. To be clear, a company is any data folder of accounting data.

Sorry Kay, but you might want different "reply to" addresses for the person e-mailing invoices and the one e-mailing statements. That's the reason for the approach we took. I can see the rational for the strategy you'd like, given the business process in use at your company. Now that you've reviewed all the users/workstations at your firm, you won't be faced with any more unexpected transmissions.

The suggestion to "pop" a "printer setup" like dialog before e-mailing is a reasonable one (although might be annoying to users not requiring the confirmation you desire). Perhaps for version 9.0A - we'll see.

Thanks for posting the thread.