Trouble with releasing messages from spam quarantine

[omgoozles]

As the title suggests, if I release a message from the spam quarantine, it never hits the inbox.
Things I've tried.
1. Turning off all builtin Exchange Antispam stuff
2. ADSIEdit trick I found on the forums
3. Setup receive connector to allow relay from the Untangle box
4. Disabled Drop Super spam from antispam app settings.

Still not receiving messages I'm trying to release to the inbox. What else can I do??? I receive the daily spam quarantine e-mails and can send the test emails no problem. So it has to be my Exchange box somehow dropping the messages I release, right?

[jcoffin]

Version of Untangle?

[omgoozles]

Whatever is the newest. I have it auto updating.

[jcoffin]

I would check your mail server's logs to see what it is doing with a release.

[sky-knight]

I'd also double check the version please. Just because automatic upgrades is on, doesn't mean you're current.

But if you're getting some mail, that usually means it's working fine. Probably your spam filter going bonkers.

[dmorris]

if you have access to the terminal you can run:
tail -f /var/log/exim4/mainlog

that will "tail" the email log

then go release an email from the quarantine.
You will see in the mail log it will try to send the mail.
If you see "completed" it means it was accepted by your mail server and you'll need to look there.
If it was rejected it will say why.

[omgoozles]

I'd also double check the version please. Just because automatic upgrades is on, doesn't mean you're current.

But if you're getting some mail, that usually means it's working fine. Probably your spam filter going bonkers.

Running:
Build: 14.0.1.20180827T111844.4c1932f659-1stretch
Kernel: 3.16.0-4-untangle-amd64

[omgoozles]

if you have access to the terminal you can run:
tail -f /var/log/exim4/mainlog

that will "tail" the email log

then go release an email from the quarantine.
You will see in the mail log it will try to send the mail.
If you see "completed" it means it was accepted by your mail server and you'll need to look there.
If it was rejected it will say why.

By Terminal, do you mean SSH?

[jcoffin]

Ssh or the terminal on the console.

[omgoozles]

Ssh or the terminal on the console.

[ATTACH=CONFIG]9012[/ATTACH]

I can enable SSH, I don't have access to the physical machine right now.

[omgoozles]

So i see this:
2018-11-02 10:49:27 1gIbsF-0000TW-1C H=mail.domain.com [IP Blanked for security] TLS error on connection (send): The specified session has been invalidated for some reason.
2018-11-02 10:49:27 1gIbsF-0000TW-1C == [email protected] R=smarthost T=remote_smtp_smarthost defer (-45) H=mail.domain.com [IP Blanked for security]: SMTP error from remote mail server after pipelined MAIL FROM:<[email protected]> SIZE=2090: 421 4.4.2 Message submission rate for this client has exceeded the configured limit
2018-11-02 10:49:27 1gIbsF-0000TW-1C H=mail.domain.com [IP Blanked for security] TLS error on connection (recv): The TLS connection was non-properly terminated.

Couple things re: this log. The [email protected] doesn't exist. Is there a way to figure out where that connection is coming from so I can block it. It also looks like it's a TLS issue on my Exchange box?

[omgoozles]

Just changed it back to the Cloud hosted relay server, released an email and got this:
2018-11-02 11:00:29 1gIegG-0006zE-HZ => [email protected] R=smarthost T=remote_smtp_smarthost H=127.0.0.2 [127.0.0.2] C="250 2.0.0 Ok: queued as EB7EDE3FB1"
2018-11-02 11:00:29 1gIegG-0006zE-HZ Completed

But I didn't receive it.

[omgoozles]

Scratch that, went to junk mail in Outlook. Seems to be working now using the Cloud relay...i'll just stick with that.

[jcoffin]

Careful enabling ssh on the WAN. I would recommend to VPN to the Untangle and then ssh the internal IP.

[omgoozles]

Careful enabling ssh on the WAN. I would recommend to VPN to the Untangle and then ssh the internal IP.

I didn't. I dialed into the server connected to the Untangle remotely, then enabled SSH. Did what I did, and disabled SSH.