How to configure an Exchange server to allow you to send email directly from Sage 50 accounts.
WARNING:
You need to know what you are doing is to allow the Exchange server to send e-mail messages that are not authenticated. If you work for an IT support company then you will no doubt see this risk, but if you are an experienced professional in the IT support or server support, then you should consider getting the help of someone who is. This is a big security risk if you do not do this properly. If you open the Exchange server to allow anyone to do this, then you risk becoming a victim of spam abuse.
Part 1 - Configure the Exchange server
We are going to configure your Exchange server to allow e-mail messages in anonymous output, but we intend to do so for only a handful of IP addresses. This greatly reduces the risk of abuse.
The first step is to create a new custom Receive connector for Microsoft Exchange Management Console. To do this, start the Exchange Management Console and expand 'Microsoft Exchange' >> 'Transport Hub' Server Configuration '. Here, click the 'New Receive Connector' function found a link to the right side of the window. Enter a label adapted to this connector in the field 'Name'. How could you call 'Sage accounts. Inside the 'Select the intended use ...' area, choose 'custom'.
Click 'Next' and then 'Next' again to access the "Remote Network Settings" page.
on the remote network settings edit page the list of IP addresses is, only the addresses you want to allow. For example, if Sage 50 accounts configured on a terminal server then you should just have the IP address of the terminal server is entered here. If Sage 50 accounts is run locally on a PC accounts, then you'll need to make the IP address of this static PC and specify in this list.
End the development of this new connector and then change to display the properties of it. Go in the 'Permission Groups tab, and ensure that only the "Exchange server' is checked. Then, go to the 'Authentication' tab and make sure that the top item only (Transport Layer Security) and the bottom entry (Externally Secured ) are selected. Click OK and restart the 'transport service Microsoft Exchange' from within the control Panel> Administrative Tools> Services.
Now you should find that you can configure Microsoft Outlook to use the 'Exchange server LAN IP address as the outgoing mail server without having to specify any authentication. you can try this by using Outlook or Outlook Express on a specific workstation or terminal server (for example, the PC or terminal server that Sage 50 accounts installed in it).
Part 2 - configure the Wise PC / Server
Now we're going to configure Sage to send e-mail using Exchange Server the new configuration we created in step 1.
In Sage Report designer, click Tools> Options> email configuration. Configure the 'default provider' for SMTP and click the SMTP line the box 'available providers. Select 'Configure' and enter the LAN IP address of the Exchange server in the 'Server Name'. Leave the port number set to port 25 and leave SSL deselected.
Enter the email address you want the emails to be sent from (such as "accounts@yourdomain.com") and type the display name for the e-mail header (eg company name - Accounts). It is important to put something in particular in the password settings so this can be set to anything. Click OK.
So you need to make sure that any layout you want to send as e-mail is configured to use SMTP.
First, edit a document in Sage Report Designer. Click 'View' on the toolbar, and click '' Properties to show the properties of the tool bar on the right side of the screen. Under the 'Options' e-mail area, click '(e-mail Options)' box and a button called '...' it will be shown. Click this button to start the setup window email.
What the ( 'Provider') Make the upper setting is set to SMTP and that the option at the bottom of the page is set to 'the send email automatically' . Click OK at the bottom of the page.
The system configuration is now complete - You should now be able to e-mail for that layout in Sage 50 accounts.
0 Komentar