450 plugin timeout

[Jose Antonio Espinosa Villanueva]

After upgrading to 2.1.1 FREE I had memory problems, so I enlarge the available RAM to 8GB and restarted everything. Afther that it is impossible to send mail to the server receiving a 450 plugin timeout message (enclosed a trace of test)

#!

Connection: opening to mail.la-demo.com:25, timeout=300, options=array (
                 )
Connection: opened
SERVER -> CLIENT: 220 mail.la-demo.com ESMTP Haraka ready
CLIENT -> SERVER: EHLO tools.wormly.com
SERVER -> CLIENT: 250-mail.la-demo.com Hello tools.wormly.com [96.126.113.160], Poste.io is at your service
                 250-PIPELINING
                 250-8BITMIME
                 250-SMTPUTF8
                 250-SIZE 26214400
                 250 STARTTLS
CLIENT -> SERVER: STARTTLS
SERVER -> CLIENT: 220 Go ahead.
CLIENT -> SERVER: EHLO tools.wormly.com
SERVER -> CLIENT: 250-mail.la-demo.com Hello tools.wormly.com [96.126.113.160], Poste.io is at your service
                 250-PIPELINING
                 250-8BITMIME
                 250-SMTPUTF8
                 250-SIZE 26214400
                 250 AUTH PLAIN LOGIN
CLIENT -> SERVER: MAIL FROM:
SERVER -> CLIENT: 450 plugin timeout
**SMTP ERROR: MAIL FROM command failed: 450 plugin timeout
2019-02-23 08:49:40 The following From address failed: [e-mail] : MAIL FROM command failed,plugin timeout
                                      ,450,SMTP server error: MAIL FROM command failed Detail: plugin timeout
                                       SMTP code: 450**
CLIENT -> SERVER: QUIT
SERVER -> CLIENT: 221 mail.la-demo.com closing connection. Have a jolly good day.
Connection: closed
Message sending failed.

What is happening and how to solve?

[Jose Antonio Espinosa Villanueva]

I don't know if this helps, but I receive this messages in the docker logs:

#!

FATAL ERROR: CALL_AND_RETRY_LAST Allocation failed - JavaScript heap out of memory
 1: node::Abort() [node]
 2: 0x8ccf9c [node]
 3: v8::Utils::ReportOOMFailure(char const*, bool) [node]
 4: v8::internal::V8::FatalProcessOutOfMemory(char const*, bool) [node]
 5: v8::internal::Factory::NewRawTwoByteString(int, v8::internal::PretenureFlag) [node]
 6: v8::internal::String::SlowFlatten(v8::internal::Handle<v8::internal::ConsString>, v8::internal::PretenureFlag) [node]
 7: v8::internal::String::Flatten(v8::internal::Handle<v8::internal::String>, v8::internal::PretenureFlag) [node]
 8: v8::String::WriteOneByte(unsigned char*, int, int, int) const [node]
 9: node::StringBytes::Write(v8::Isolate*, char*, unsigned long, v8::Local<v8::Value>, node::encoding, int*) [node]
10: node::Buffer::New(v8::Isolate*, v8::Local<v8::String>, node::encoding) [node]
11: 0x8e9444 [node]
12: 0x1f509db90be7

[Scott MacDonald]

Anyone else running v2.1.1 and have problems? I'm still at v2.0.23. I know v2.1.0 had delivery issues but no one has posted whether they'd rolled back or upgraded to v2.1.1.

[Jose Antonio Espinosa Villanueva]

I purge completely the /data/queue/smtp and the system is now running... I continue to diagnose the possible problem.

[Scott MacDonald]

Was it possibly something else connected to also needing to purge your logs?

[Jose Antonio Espinosa Villanueva]

I had problems with the logs before (a lot of connection log files). I have to purge them too.

[SB]

This sounds like the problem. See #601 for more details. https://blogs.msdn.microsoft.com/mast/2017/11/15/enhanced-azure-security-for-sending-emails-november-2017-update/

A simple phone call sorted this for me, but I had previously verified using passport and bank statement as we use a lot of Microsoft services

[Jose Antonio Espinosa Villanueva]

No, I think this is not the case because we had not any trouble in sending emails (we have sent some thousands until now), I think we have an older subscription to Azure.

[SH]

I believe it was caused by Node 8. Node 2.1.3 introduced Node 10...

I am closing it for now, if it is still issue please reopen