1702840 - New mailnews.smtp.jsmodule code broke my mail sending connectivity (pfsense and suricata)

Status: RESOLVED DUPLICATE of bug 1701804

(MailNews Core :: Networking: SMTP, defect)

Description

[Mike]

User Agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:87.0) Gecko/20100101 Firefox/87.0

Steps to reproduce:

1. Update from TB 87 to TB88
2. Create new mail message
3. Click "Send"

Actual results:

Sending popup spins, but does not complete successfully. Sits on popup indefinitely.

Expected results:

Send successful

Comment 1

[Mike]

Further information:

As the subject says, simply updating from TB 87 to TB 88b1 (or 2) my ability to send messages was crippled.

Reverting to "false" for mailnews.smtp.jsmodule reverts mail functionality to working status. I can leave mailnews.send.jsmodule as "true"

The internet facing portion of my firewall/router is a pfsense box running suricata for security.

Prior to reverting the smtp FLAG, even after whitelisting the new triggered suricata events (since TB88b1, they did not occur in TB 87 or prior), mail was still not sending and at that point simply spins until it times out. Here are the new triggered caught security exceptions, with my ISP, shaw.ca

SURICATA SMTP duplicate fields 

suppress gen_id 1, sig_id 2220018, track by_dst, ip 64.59.136.142

SURICATA SMTP duplicate fields 

suppress gen_id 1, sig_id 2220018, track by_dst, ip 64.59.128.135

Comment 2

[Ping Chen [:rnons] (away)]

Hi, can you try bug 1701804 comment 15?

If it doesn't help, can you please do the following

1. set mailnews.smtp.jsmodule to true and mailnews.smtp.loglevel to All
2. send a mail
3. filter logs containing mailnews.smtp and paste them here

Thanks

Comment 3

[Mike]

Ping,

Where do I find the logged output?

Comment 4

[José M. Muñoz]

In the error console: Tools > Developer Tools > Error Console. Or just press Ctrl+Shift+J.

On the top there is a filter box, so paste mailnews.smtp in there to reduce the output to the relevant lines. Instead of pasting the log in to a comment, it would be better to paste it into a file and attach that ("Attach New File" button above). It's also a good idea to switch on the timestamp using the sprocket menu (top right) in the error console.

Comment 5

[Mike]

Attachment: smtp-error.txt

Here's the error console output as requested, Ping.

Let me know if I can do anything else to help.

Comment 6

[José M. Muñoz]

OK, the relevant line is:
12:30:41.945 mailnews.smtp: EHLO not successful, trying HELO localhost SmtpClient.jsm:803:19
So your SMTP server isn't happy with the EHLO. This should be fixed in today's Daily build, or you need to wait for TB 88 beta 3 or TB 89 beta.
Or you can set the EHLO parameter by setting this preference: mail.smtpserver.default.hello_argument. You can set it to any value, like foo or 192.168.1.1. In TB 78 is uses the name of your local machine. This preference doesn't exist at all, so you need to create it as a string. It's possible that setting the pref still doesn't help, since this is the default pref. In that case you'd need to set the server-specific pref, see bug 1701804 comment #15 for details.

Comment 7

[Ping Chen [:rnons] (away)]

José is correct, for the moment, you can add a mail.smtpserver.default.hello_argument pref.

Comment 8

[Mike]

Thanks