FileBot

Hmm, okay. Well seems more and more unlikely this is the reason. I don't have much else to go on right now though so i guess i'll test it out anyway when I have the time. I'll post back what I find.

Hi Guys,

I also have had emails start failing - first logged for me on 16th Feb - working fine prior to that, so it does seem that something has changed.
[mail] Failed to send email: Can't send command to SMTP host

I can telnet to the mail server to send an email as follows:
220 XXXXXX Microsoft ESMTP MAIL Service, Version: 8.5.9600.16384 ready at Sun, 12 Mar 2017 15:22:53 +1100
ehlo test
250-XXXXXX Hello [XXXXXX]
250-TURN
250-SIZE 2097152
250-ETRN
250-PIPELINING
250-DSN
250-ENHANCEDSTATUSCODES
250-8bitmime
250-BINARYMIME
250-CHUNKING
250-VRFY
250-TLS
250-STARTTLS
250 OK
mail from:[email protected]
250 2.1.0 [email protected] OK
rcpt to:XXXXXX
250 2.1.5 XXXXXX
data
354 Start mail input; end with <CRLF>.<CRLF>
test
.
250 2.6.0 <HNDC01Boe2U8QVjp3b60000004d@XXXXXX> Queued mail for delivery
221 2.0.0 XXXXXX Service closing transmission channel

However when when filebot sends an email, the mail server logs the following:
2017-03-12 04:15:43 XXXXXXX MAIN SMTPSVC1 HNDC01 192.168.10.50 0 EHLO - +MAIN 250 0 226 9 0 SMTP - - - -
2017-03-12 04:15:43 XXXXXXX MAIN SMTPSVC1 HNDC01 192.168.10.50 0 STARTTLS - - 220 0 0 8 0 SMTP - - - -
2017-03-12 04:15:43 XXXXXXX MAIN SMTPSVC1 HNDC01 192.168.10.50 0 STARTTLS - - 220 0 29 8 0 SMTP - - - -
2017-03-12 04:15:48 XXXXXXX MAIN SMTPSVC1 HNDC01 192.168.10.50 0 STARTTLS - MAIN 503 2148074279 29 8 5297 SMTP - - - -
2017-03-12 04:15:48 XXXXXXX MAIN SMTPSVC1 HNDC01 192.168.10.50 0 QUIT - MAIN 240 6313 29 8 5297 SMTP - - - -

My commandline is as follows:
filebot -script fn:amc --output "E:\tv_current" --action copy --conflict skip -non-strict --log-file amc.log --def unsorted=y subtitles=en "ut_dir=D:/p2p/tixati_seeds" "ut_kind=multi" mail=XXXXXXXX:25:[email protected] mailto=XXXXXXX reportError=y excludeList=amc.txt "seriesFormat=E:/tv_current/{n}/{'Season '+s.pad(2)}/{n} - {s.pad(2)+'x'+e.pad(2)} - {t}" "movieFormat=E:/mount/17a/17a_movies/{n} - ({y}) - [{source+', '}{fn.match(/3D/)+', '}{vf}, {ac}, {af}]"

Any help would be appreciated.

Regards,
Matt

Thanks for chipping in Matt, nice to see I wasn't the only one affected by this.

I finally got round to testing removing the default STARTTLS option and I can confirm that without it emails are sent no problem. So it definitely seems the introduction of this default is what started the issue.

The actual root cause could be a problem with my mailserver configuration. However, since I am using TLS to connect in to/out from other services such as mandrill and gmail without issue, and another user has also reported the same problem, I'm not really inclined to go hunting for potential configuration issues which may not exist. Also since this change was introduced to help out the other guy in this thread who has since said he is now using gmail, so doesn't even need the option, hopefully rednoah will consider removing it.

@rednoah I've submitted a pull request for the change if you are willing to merge it: https://github.com/filebot/scripts/pull/45

Hey Despian,

Thanks for the info.

How have you gone about "removing the default STARTTLS option"? I have no concern disabling if it will get emails flowing again.. Is the a CLI option, or a mail server side change?

Appreciate the assistance!

Matt

Why is everyone so keen on sending email from FileBot itself?

Wouldn't it be easier and more modular to just collect the console output and sending it of via the mail command?