sandpilot
Level 1 (0 points)

Q: Problems sending out emails

Hello All,

 

First off I have to admit, I'm a complete newbie to FCS.  I was "asked" by my boss to take over the setup of the FCS in our company.  I do have many years of experience as a OSX and Solaris admin, so I'm not totally in the dark.

 

So I have the server up and running and I'm trying to setup a workflow for our folks here.  I was trying to get the "ready for review" emails to be sent out and I get several responses in the log of the FCS administration window.  Here is what I see....

 

Log Message 1

updated metadata for Media Asset (DTV) Global Hawk 872 1st Dropsonde Chase

updated metadata for Media Asset (DTV) Global Hawk 872 1st Dropsonde Chase Library   -  OK this looks good to me.

 

Log Message 2

response Email reviewers for Ready assets email triggered by Subscription Assets Ready for Review [Email] failed

response failed to send email to john.doe@somewhere.com with subject Asset Review: Global Hawk 872 1st Dropsonde Chase

ERROR: E_PROTOCOL

Unknown response : 501    -    Here is where things go sideways.

 

Log Message 3

response Email reviewers for Ready assets email triggered by Subscription Assets Ready for Review [Email] failed

response failed to send email to john.doe@somewhere.com with subject Asset Review: Global Hawk 872 1st Dropsonde Chase

ERROR: E_TIMEOUT

unexpected control connection shutdown   -   Still don't get it.

 

Then I get this response.........

 

Log Message 4

response Email reviewers for Ready assets email triggered by Subscription Assets Ready for Review [Email] complete

response complete, sent email to john.doe@somewhere.com with subject Asset Review: Global Hawk 872 1st Dropsonde Chase   -   This one says it was sent!

 

I never get any emails sent to my email.  I can go to the command line and send out a email that way just fine, so I know the OS is working at sending out emails, so I guess it is my lack of knowledge of FCS.  I will learn more as I go on, but now I can't find much useful documentation on this problem.

 

Thanks for any help.

John

Posted on Apr 18, 2011 4:03 PM

by Michael Guncheon,Solvedanswer
Michael Guncheon Michael Guncheon
Level 1 (35 points)
A:

I think it just pulls it from the user setup on the server computer. We figured this out prior to Final Cut Server when we were trying to get Compressor email notifications working. Finally had to trace through our email server logs to figure out what was going on.

 

You can put a metadata field in there. We do this. We have system where creators upload files and keyworders verify and and metadata. When the keyworder notices a problem they change a status field to "problem". That will then trigger an email response. Here is what the email screen looks like:

 

*To: [Created By]@mydomain.com

Sender: [Keyworded By]@mydomain.com

Subject: FILE PROBLEM: "[Title]" has a problem

 

Message:

 

File "[Title]" has some issues

 

It was uploaded by [Created By].

 

According to [Keyworded By]: "[Description]".

Posted on Apr 20, 2011 3:20 PM

Close
sandpilot

Q: Problems sending out emails

  • All replies
  • Helpful answers

  • by Michael Guncheon,Helpful

    Michael Guncheon Michael Guncheon Apr 20, 2011 9:36 AM in response to sandpilot
    Level 1 (35 points)
    Apr 20, 2011 9:36 AM in response to sandpilot

    I'm not savvy to your command line test, but FCSrvr doesn't support SMTP authentication.

    So you'll need to check on that.

     

    I also leave the sender field blank and let FCSvr put in the from email address.

  • by A. Richards,Helpful

    A. Richards A. Richards Apr 20, 2011 9:57 AM in response to sandpilot
    Level 3 (625 points)
    Apr 20, 2011 9:57 AM in response to sandpilot

    If you need to authenticate for SMTP, and you are hosting on OS X Server, you can use the SMTP forwarding in OS X Server (limited to 127.0.0.1) to authenticate to your main SMTP server.  Then you set localhost as your mail server for FCSvr and let the Mail services of OS X Server handle the authentication.  If you are familiar with Postfix, that is what is running under the hood on OS X Server's sendmail services.

  • by sandpilot,

    sandpilot sandpilot Apr 20, 2011 11:32 AM in response to sandpilot
    Level 1 (0 points)
    Apr 20, 2011 11:32 AM in response to sandpilot

    Hey Guys,

     

    Thanks for the replies.  This is running on OSX client, not server and no authentication is required.

     

    I did figure out a way to make it work late yesterday.  I'm not sure if this is the "right way" or not, but it seems to do the trick.

     

    In the automations tab in the system prefs panel of FCS, I went to "Assets Ready for Review [email]" and clicked through to the Responses screen.  Here the "From" field was left blank.  I put in a dummy email, and it worked just as advertised!

     

    Michael, is this where you said to leave it blank and let FCS fill in the address?  If so, where does it pull the address from?  Can I have it pull from a metadata field and put the person that was working on the projects email in there, so the reviewer can respond to that real email instead of the dummy one that I used?

     

    Just a thought....

     

    Thanks again.

    John

  • by Michael Guncheon,Solvedanswer

    Michael Guncheon Michael Guncheon Apr 20, 2011 3:20 PM in response to sandpilot
    Level 1 (35 points)
    Apr 20, 2011 3:20 PM in response to sandpilot

    I think it just pulls it from the user setup on the server computer. We figured this out prior to Final Cut Server when we were trying to get Compressor email notifications working. Finally had to trace through our email server logs to figure out what was going on.

     

    You can put a metadata field in there. We do this. We have system where creators upload files and keyworders verify and and metadata. When the keyworder notices a problem they change a status field to "problem". That will then trigger an email response. Here is what the email screen looks like:

     

    *To: [Created By]@mydomain.com

    Sender: [Keyworded By]@mydomain.com

    Subject: FILE PROBLEM: "[Title]" has a problem

     

    Message:

     

    File "[Title]" has some issues

     

    It was uploaded by [Created By].

     

    According to [Keyworded By]: "[Description]".

  • by sandpilot,

    sandpilot sandpilot Apr 20, 2011 4:50 PM in response to sandpilot
    Level 1 (0 points)
    Apr 20, 2011 4:50 PM in response to sandpilot

    Michael,

     

    That is a interesting way of doing it!  I think I will give it a try and see if I can do that.

     

    I'm really struggling with the permissions right now, so it will have to wait until I get that issue ironed out.

     

    Thanks for your help.

     

    John

  • by RicM,

    RicM RicM Apr 21, 2011 8:54 AM in response to A. Richards
    Level 1 (10 points)
    Apr 21, 2011 8:54 AM in response to A. Richards

    I am having a problem setting this up as well...my e-mail is all done through outside services like Register.com (for our domain name e-mail) or my Apple #$%@Mac.com address. There's no provision for entering the password, so how could FCSrvr connect?

  • by A. Richards,

    A. Richards A. Richards Apr 21, 2011 9:05 AM in response to RicM
    Level 3 (625 points)
    Apr 21, 2011 9:05 AM in response to RicM

    FCSvr does not have built-in support for authenticated SMTP.  This means that SMTP services from Gmail or Yahoo or MobileMe will not be able to send mail for FCSvr directly.  The workaround as I noted above is to use a relay SMTP server that can serve as the authenticator for your main SMTP server (ideally you'd limit the hosts that are permitted to use the relay to your FCSvr host's IP, otherwise your relay could be turned into a spambot).  If you are running FCSvr on Mac OS X Server, this is easy to set up in Server Admin in the Mail service Settings tab.  If you need SSL support (like with Gmail SMTP), you'll also need to modify the Postfix config files on the command line.  If you are not using OS X Server to host FCSvr, Postfix can still probably do it, but everything would need to be configured on the command line by hand.

  • by Michael Guncheon,

    Michael Guncheon Michael Guncheon Apr 22, 2011 11:15 AM in response to A. Richards
    Level 1 (35 points)
    Apr 22, 2011 11:15 AM in response to A. Richards

    Andy is spot on. That is the reason we opted for installing the server on OSX server. It made dealing with things like that much easier, and avoiding having to tweak servers that are doing other things.