Configuring IIS to use a Gmail SMTP relay server

Configuring IIS to use a Gmail SMTP relay server

Starting here make sure the IP address is set to “All Unassigned” port 25.

Under “Access” > “Authentication” check Anonymous, leave basic and windows unchecked.

“Access” > “Connection” check “All except the list below” leave it blank.

“Access” > “Relay Restrictions” same, check “Only the list below” and also check “Allow all computers which successfully authenticate to relay, regardless of list above.”

Match message size limits/etc. to below image (or adjust per environment.)

Also match Delivery settings to below (or adjust per environment.)

For “Outbound Security” select Basic Auth + TLS encryption. Account must be provided by customer.

Set “Outbound Connections” to the listed settings or adjust per environment as necessary.

Lastly be sure the fully-qualified domain name is used. If using an IP address here things can get dicey. Set smart host to smtp.gmail.com andUNCHECK the “Attempt direct delivery before sending to smart host.”

Troubleshoot SMTP Relays

To better understand how to guide a customer or partner in their troubleshooting of a SMTP Relay issue outside of ShoreTel, here are the basic routing steps of a SMTP Relay using a smart host from Director to email server:

1.     In Shoreware Director under Sites, the SMTP Relay should be set to the IP address or server name of the Windows Server you want to be the SMTP Relay. Typically, this can be the HQ server as shown in the following example:

 

2.     On the HQ Server, Open IIS 6.0 Manager.

a. Right-click the SMTP Virtual Server and click on Properties.

b. NOTE: First, look at the Messages tab to verify various messaging limits placed on the SMTP messages. This will be important when moving voice mailboxes between ST VM servers. Mailboxes are packaged up into a single SMTP message and sent via the SMTP Relay to the destination VM server. Messages larger than the set limits may result in a portion of the VM messages being lost.

Move users in groups whose total VM box used capacity is smaller than the message size limit set in the SMTP Relay or change the message limits as appropriate, aligning with the Exchange Server message limits.
 

 

c. Next, look at the Delivery tab >Advanced button, to verify the Smart host destination. Depending on the customer’s email infrastructure, this could be the name of the Exchange Server (as shown below), IP address of the Exchange Server, a specific IP address associated with a Receive Connector on the Exchange Server, or internal DNS alias which could route “round robin” to redundant perimeter mail filters that is in turn handed off to the Exchange Server.

On the same Delivery tab > Outbound Security button, (not shown here) only Anonymous Access is selected as well as the Access tab > Access Control > Authentication button, Anonymous Access is also checked.
 

 

3.     On the Exchange Server (e.g. Exch 2007) that the Smart host is pointed to above, open Exchange Management Console > Server Configuration > Hub Transport, and look at the Receive Connectors tab for the appropriate Receive Connector which matches the criteria of the HQ server or where the SMTP Relay is located via IP address or IP address range.
The HQ in this example is in the subnet 172.17.2.0/24.

 

4.     Under the same properties window, verify that the Permission Groups tab has Anonymous users checked at the very least.

 

5.     If any changes were made, the SMTP service will likely need to be restarted on the Windows Server where the changes occurred. Use services.msc instead of the services plug-in in the IIS GUI to ensure it restarts properly.

6.     When testing the SMTP Relay, use the following folder locations as reference to monitor

the progress or issues related to any test messages.

• C:\Windows\System32\Logfiles\SMTPSVCI\ [SMTP Logs on the SMTP Relay]

• C:\Inetpub\Mailroot\Queue\ [Outgoing Mail Queue on SMTP Relay]

• C:\ShoreLine Data\VMS\Message\ [System Storage location for VM messages]

• C:\Inetpub\Mailroot\Badmail\ [Unsuccessful Send Mail Folder on SMTP Relay]

7.     To Enable SMTP logging for IIS 6.0 or 7.0 for testing the SMTP Relay:
• Right-click the SMTP Virtual Server and click on Properties in IIS

• On the General tab, check Enable logging and click on the Properties button

• Go to the Advanced Tab

• Under Extended logging options, check all options except the last 3 check boxes (i.e. User Agent, Cookie, and Referer).

• When testing is complete, uncheck Enable logging and click OK.

Saving WAV files in CCITT U-Law format for Shoretel File based audio using Audacity

Core content below modified from Snafder's Hood.

• Audacity can be used to create .WAV files in the CCITT U-Law 8-bit format required for VOIP audio requirements.
• Audacity is FREE for commercial use. Excerpt taken from Audacity’s website:

• “Is Audacity really free? Why?
  Yes, Audacity is completely free, open source software. You are free to use this program for any personal, commercial, or educational purposes, including installing it on as many different computers as you wish.”

• Record the audio however you see fit, Audacity can be used directly; however you can record in any application and open the file in Audacity later.
• Once you have the file loaded in Audacity (or recorded), do the following:

• In Audacity, set the 'Project Rate (Hz)' in the bottom left hand corner to ‘8000’.

• 

• It is also important that you have it set to MONO (one channel only).
  This can be achieved by clicking on the drop down arrow of the track and selecting ‘Split Stereo to Mono’ and then clicking the ‘x’ on one of the now separated tracks.
• 

• Now it’s time to export the file…
• Select 'File'.
• Select 'Export'.

• Change the 'Save as type' to 'Other uncompressed files' (yes, it’s a bit misleading as it will make a file that is a lot smaller than the 44000 Hz WAV equivalent - but it isn't actually compressed, simply less samples a second and therefore a smaller file size).
• Click the 'Options' button (bottom right).
• 

• Select 'WAV (Microsoft)' for 'Header'.
• Select 'U-Law' for 'Encoding'.

• 

• Click 'OK'.

• Choose a name and enter it into 'File name' field (no need to enter the extension .WAV – it will automatically add it).

• Click 'Save'.
• Click 'OK' to the 'Edit Metadata' screen (don't enter ANY metadata).
• 

Remember, if you don’t set 'Project Rate (Hz)' in the bottom left hand corner to ‘8000’ and don’t make it mono, choosing ‘WAV (Microsoft)’ and ‘U-Law’ won’t be enough!