Users cannot release spam

[Ehlo]

Hello,
I'm aware there's another topic with the same subject, but it seems to me I've a different problem.
The problem is that the users receive the mail with the link to release the mail; but when they click on it, the message appears that the mail is being released. And then...nothing happens...
And when they click once more, they get this message:
Your message has not been released from quarantine.
Our system indicates that this message has already been released once, or the original notification message has expired. Notification messages to release spam expire after 3 days. Your message can be released again by accessing your spam quarantine.

Users cannot access the spam quarantaine, so we (admins) have to release the mail...

I did some basic checks: see log files (but I don't see anything about releasing mail), rights etc. no succes...
Can somebody help me out? Point me in the right direction?

[DaN]

Hi
which version do you use?

/etc/EFA-Version

Code: Select all

3.0.0.7 

[shawniverson]

Are you seeing anything in /var/log/maillog when the link is clicked?

I'm going to run some tests on my end too...want to make sure this isn't a bug from the update....

[Ehlo]

Thank you for your replies!
No, I didn't see anything in maillog when I clicked on the link...

As for the version: I guess it's 3.0.0.6, but I'm not sure...and I can't login and see (weekend... )

[Ehlo]

[root@EFA01 log]# cat /etc/EFA-Version
EFA-3.0.0.6


So, it's not the latest version... maybe an update would help solve this problem?

[Ehlo]

Found something in maillog!

when the user clicks the first time on the link:

Mar 2 08:29:09 EFA01 postfix/sendmail[13677]: fatal: apache(48): No recipient addresses found in message header

[DaN]

The releasenotes: viewtopic.php?f=8&p=2935#p2935

I don't see any related problem. Because of POODLE, GHOST and co. an update is recommended.

[shawniverson]

Mar 2 08:29:09 EFA01 postfix/sendmail[13677]: fatal: apache(48): No recipient addresses found in message header

What we need to do is look up one of the emails that is causing this and take a look at its header. This error means that postfix is having problems relaying the message to the recipient(s) becuase it can find the recipient address for some reason.

[Ehlo]

Thank you again...

I've updated to version .7, but the problem still exists.
You were right: there is a problem with the headers.

I've attached two screenshots:
(on another server) showing adresses

not working

EFA1.JPG (97 KiB) Viewed 13825 times

not showing adresses.

Working

EFA2.JPG (88.96 KiB) Viewed 13825 times

How can I solve this issue?

[DaN]

The "Message Headers" are one click earlier, shown by "detail.php" (after the click on "[ ]").

[Ehlo]

Here you are:
X-Greylist: from auto-whitelisted by SQLgrey-1.8.0
Received: from DOMAIN (DOMAIN.DOM [IP ADRESS])
(using TLSv1 with cipher AES128-SHA (128/128 bits))
(No client certificate requested)
by EFA01.DUMMY (Postfix) with ESMTPS id 1D90160053
for <DUMMY TO>; Wed, 4 Mar 2015 15:14:40 +0100 (CET)
Received: from LED-SBS.LED.local ([fe80::24d2:c651:b9c2:5d50]) by
LED-SBS.LED.local ([fe80::24d2:c651:b9c2:5d50%10]) with mapi id
14.03.0224.002; Wed, 4 Mar 2015 15:14:38 +0100
From: DUMMY FROM>
To: DUMMY TO>
Subject: RE: OFFERTE MUG/MUD
Thread-Topic: OFFERTE MUG/MUD
Thread-Index: AQHQVOKctYyIgh8Nj0yyftD5ei6RN50MSdZw////N4CAABWLQP//8boAgAAQ6LA=
Date: Wed, 4 Mar 2015 14:14:38 +0000
Message-ID: <1235BB46E6AAF545BC43E7D04B2BB32324C00B32@LED-SBS.LED.local>
References: <DC975D4C23EECE40AF9DBAA3957B9AC81CD05231@LED-SBS.LED.local>
<8F91C63751B4434BBE2A21864D44D2E3E3CB5F47@DUMMY>
<8F91C63751B4434BBE2A21864D44D2E3E3CB61A3@DUMMY>
<8F91C63751B4434BBE2A21864D44D2E3E3CB6204@DUMMY>
<1235BB46E6AAF545BC43E7D04B2BB32324C007AF@LED-SBS.LED.local>
<8F91C63751B4434BBE2A21864D44D2E3E3CB8389@DUMMY>
<1235BB46E6AAF545BC43E7D04B2BB32324C00AB6@LED-SBS.LED.local>
<8F91C63751B4434BBE2A21864D44D2E3E3CB8546@DUMMY>
In-Reply-To: <8F91C63751B4434BBE2A21864D44D2E3E3CB8546@DUMMY>
Accept-Language: nl-BE, en-US
Content-Language: nl-NL
X-MS-Has-Attach: yes
X-MS-TNEF-Correlator:
x-originating-ip: [192.168.1.35]
Content-Type: multipart/related;
boundary="_004_1235BB46E6AAF545BC43E7D04B2BB32324C00B32LEDSBSLEDlocal_";
type="multipart/alternative"
MIME-Version: 1.0

[shawniverson]

This header is malformed.

From: FROM MAIL ADRESSl>
To: Receiver mail adress>

[DaN]

Just a wrong search and replace handlig?

[shawniverson]

Can you lookup the message ID and locate the message in the quarantine under the hood?

Code: Select all

sudo view /var/spool/MailScanner/quarantine/<date>/<messagid>

We need to see the raw message to determine if this is us or the remote mailserver causing your issue.

[Ehlo]

Hope this is better. However, I have censored the message a bit (mail.server etc):

X-Greylist: from auto-whitelisted by SQLgrey-1.8.0
Received: from mail.server.be (mail.server.be [99.99.99.99])
(using TLSv1 with cipher AES128-SHA (128/128 bits))
(No client certificate requested)
by our.EFA.server (Postfix) with ESMTPS id 1D90160053
for <receiver@mail.addr>; Wed, 4 Mar 2015 15:14:40 +0100 (CET)
Received: from LED-SBS.LED.local ([fe80::24d2:c651:b9c2:5d50]) by
LED-SBS.LED.local ([fe80::24d2:c651:b9c2:5d50%10]) with mapi id
14.03.0224.002; Wed, 4 Mar 2015 15:14:38 +0100
From: Sender <sender@mail.addr>
To: receiver <receiver@mail.addr>
Subject: RE: OFFERTE MUG/MUD
Thread-Topic: OFFERTE MUG/MUD
Thread-Index: AQHQVOKctYyIgh8Nj0yyftD5ei6RN50MSdZw////N4CAABWLQP//8boAgAAQ6LA=
Date: Wed, 4 Mar 2015 14:14:38 +0000
Message-ID: <1235BB46E6AAF545BC43E7D04B2BB32324C00B32@LED-SBS.LED.local>
References: <DC975D4C23EECE40AF9DBAA3957B9AC81CD05231@LED-SBS.LED.local>
<8F91C63751B4434BBE2A21864D44D2E3E3CB5F47@mail.server.nl>
<8F91C63751B4434BBE2A21864D44D2E3E3CB61A3@mail.server.nl>
<8F91C63751B4434BBE2A21864D44D2E3E3CB6204@mail.server.nl>
<1235BB46E6AAF545BC43E7D04B2BB32324C007AF@LED-SBS.LED.local>
<8F91C63751B4434BBE2A21864D44D2E3E3CB8389@mail.server.nl>
<1235BB46E6AAF545BC43E7D04B2BB32324C00AB6@LED-SBS.LED.local>
<8F91C63751B4434BBE2A21864D44D2E3E3CB8546@mail.server.nl>
In-Reply-To: <8F91C63751B4434BBE2A21864D44D2E3E3CB8546@mail.server.nl>
Accept-Language: nl-BE, en-US
Content-Language: nl-NL
X-MS-Has-Attach: yes
X-MS-TNEF-Correlator:
x-originating-ip: [192.168.1.35]
Content-Type: multipart/related;
boundary="_004_1235BB46E6AAF545BC43E7D04B2BB32324C00B32LEDSBSLEDlocal_";
type="multipart/alternative"
MIME-Version: 1.0

--_004_1235BB46E6AAF545BC43E7D04B2BB32324C00B32LEDSBSLEDlocal_
Content-Type: multipart/alternative;
boundary="_000_1235BB46E6AAF545BC43E7D04B2BB32324C00B32LEDSBSLEDlocal_"

--_000_1235BB46E6AAF545BC43E7D04B2BB32324C00B32LEDSBSLEDlocal_
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable

[shawniverson]

Thanks.

Based on the information you have posted, I have to say the header is getting mangled during processing of these emails.

To troubleshoot this further and isolate the issue, please PM me. I am going to need a sample message file from your quarantine that is intact and unaltered.

[Ehlo]

I have sent you a PM, but it's stuck in my outbox.
Seems I cannot attach the file you requested to that message. Can I send it to you otherwise?