New mailnews.smtp.jsmodule code broke my mail connectivity (pfsense and suricata)
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 headend 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
Modified
Chosen solution
Hey Matt,
You read that wrong, I don't want to block anyone. Or you posted the wrong link, because there are no comments on that link.
Either way, I've already filed a bug against it in bugzilla. Bug ID=1702840
Read this answer in context 👍 0All Replies (3)
I suggest you follow the bug report as there is nothing much can happen in support you might want to try the action in Comment 6 and report your results there. The bug is about Charter, but I seriously doubt it will be the only one to pop up in the post JS implementation.
Chosen Solution
Hey Matt,
You read that wrong, I don't want to block anyone. Or you posted the wrong link, because there are no comments on that link.
Either way, I've already filed a bug against it in bugzilla. Bug ID=1702840
yes I did post the wrong link. https://bugzilla.mozilla.org/show_bug.cgi?id=1701268 was what I intended, but https://bugzilla.mozilla.org/show_bug.cgi?id=1701804 might also be relevant.