Solved

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

Posted on 2011-09-16
5
1,219 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 24

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 24

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

The curse of the end user strikes again      

You’ve updated all your end user’s email signatures. Hooray! But guess what? They’re playing around with the HTML, adding stupid taglines and ruining the imagery. Find out how you can save your signatures from end users today.

Join & Write a Comment

We are happy to announce a brand new addition to our line of acclaimed email signature management products – CodeTwo Email Signatures for Office 365.
Not sure what the best email signature size is? Are you worried about email signature image size? Follow this best practice guide.
In this video we show how to create a User Mailbox in Exchange 2013. We show this process by using the Exchange Admin Center. Log into Exchange Admin Center.: First we need to log into the Exchange Admin Center. Navigate to the Recipients >> Mailb…
The video tutorial explains the basics of the Exchange server Database Availability groups. The components of this video include: 1. Automatic Failover 2. Failover Clustering 3. Active Manager

759 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

Need Help in Real-Time?

Connect with top rated Experts

25 Experts available now in Live!

Get 1:1 Help Now