Solved

Cannot Send Email to Outside Address with Filemaker SMTP Exchange 2010 script step

Posted on 2011-09-16
5
1,230 Views
Last Modified: 2012-05-12
We just migrated from SBS and Exchange 2003 to Standard 2008 and Exchange 2010, and we have Filemaker 11 Advanced Server.  The migration seemed to go fine, but our SMTP email script steps in Filemaker will not go through if 1) an outside email address exists or 2) if a duplicate email address exists.   And, the email script step DOES work if it is send to internal email addresses ony with no duplicates in them.  Also, you CAN send to an external email or send if a duplicate email exists from the Admin console (see 1st screen print) (See 2nd screenprint for SMTP script step settings set from one's workstation.).

Other than the new exchange server address, the only other change has been that we were set up with an open relay and so no longer use the Plain authentication method.  Any suggestions.  We've run out of options.  Is this an Exchange or a Filemaker issue.
-AdminConsole.JPG
-ScriptSMTPsettings.JPG
0
Comment
Question by:rvfowler2
  • 3
  • 2
5 Comments
 
LVL 25

Expert Comment

by:Will Loving
ID: 36550353
Randy - I have no direct experience using FM with an Exchange server but it sounds to me like 1) The script is working because you are able to send internal emails, and 2) something in Exchange is objecting to the external addresses. Are you able to send to external addresses using a regular mail client rather the scripted FM method?
0
 
LVL 2

Author Comment

by:rvfowler2
ID: 36550368
Yes, not only can we send to external mails via my Outlook client, but even from the Filemaker Admin console, I can click on the "Test SMTP Settings," put in an outside email address and it goes through just fine.  Thus, the Exchange Server is at least wroking when sent from the FM admin console!
0
 
LVL 25

Expert Comment

by:Will Loving
ID: 36550447
Sorry - I don't have any other ideas. Perhaps someone else can chime in...
0
 
LVL 2

Accepted Solution

by:
rvfowler2 earned 0 total points
ID: 36561633
Turns out that our consultants set up Exchange 2010 assuming that any scripts run from a workstation first bounce off Filemaker server and then to Exchange, however, they don't.  The message goes directly to Exchange.  They just had to set up a relay that would allow each workstation to communicate with Exchange, but do so with authentication in order to protect against outside abuse.
0
 
LVL 2

Author Closing Comment

by:rvfowler2
ID: 36591672
Crediting my last answer as our Exchange consultant discovered the issue.
0

Featured Post

PRTG Network Monitor: Intuitive Network Monitoring

Network Monitoring is essential to ensure that computer systems and network devices are running. Use PRTG to monitor LANs, servers, websites, applications and devices, bandwidth, virtual environments, remote systems, IoT, and many more. PRTG is easy to set up & use.

Question has a verified solution.

If you are experiencing a similar issue, please ask a related question

Scam emails are a huge burden for many businesses. Spotting one is not always easy. Follow our tips to identify if an email you receive is a scam.
This article aims to explain the working of CircularLogArchiver. This tool was designed to solve the buildup of log file in cases where systems do not support circular logging or where circular logging is not enabled
The basic steps you have just learned will be implemented in this video. The basic steps are shown to configure an Exchange DAG in a live working Exchange Server Environment and manage the same (Exchange Server 2010 Software is used in a Windows Ser…
This video discusses moving either the default database or any database to a new volume.

809 members asked questions and received personalized solutions in the past 7 days.

Join the community of 500,000 technology professionals and ask your questions.

Join & Ask a Question