Emails sent through VOX bounced back "detected as spam"

[Belix]

Hi Folks
can anyone give me an idea of whether this is an issue with my own computer, or a vox server being marked as a spam server?

About 1 in 10 messages I send (and I usually only send maybe 5 a day) is being blocked and bounced as spam. Have not seen any pattern - can be a plain text message asking for pricing, or emailed financials to the accountant. Some get through, some bounce.

The message given is along the lines of
host 209.203.13.121 [209.203.13.121]: 554 5.7.1 Message refused by content analysis check. This email from IP 196.41.6.173 has been rejected. The email message was detected as spam.

The recipient can vary from gmail to hotmail, to local domains.

I've emailed VOX a couple times about the issue, but thus far the issue returns after a couple days.
At least if I could pinpoint whether the issue is with my own PC (anti malware and anti virus report no infections) or VOX, it would help.

 

[Space]

Using Vox Fat Pipe and have not had this issue - look at your firewall and settings within your antivirus program and set the spam filtering one setting less strict to see whether that makes a difference

 

[Belix]

Would my own anti-virus scan outgoing mail? I thought the rejection email was generated by a Vox mail server.
Thanks, I'll check it it has any spam filters set.

 

[Geoff.D]

Would my own anti-virus scan outgoing mail? I thought the rejection email was generated by a Vox mail server.
Thanks, I'll check it it has any spam filters set.

You need to check the settings t be certain that your own AV software is not scanning outgoing mail, or at least if it is, doing it correctly.

 

[WAslayer]

the email is being rejected by the vox mail server.. the vox mail server is detecting spam content within the message based on its spam filtering rules.. chances are it may have appended the spam rule checks to the message headers which may help with finding the source of the so called spam content.. check or post the message headers here and we can check for you.. otherwise vox will, or should, be able to tell you where the spam content is being detected..

 

[Purply]

Agree with WAslayer, 99% of the time it's the actual message header that's at fault.

 

[Belix]

sorry for delay, original message got deleted, but did not have to wait long for another:

Return-Path: <>
Delivered-To: [email protected]
Received: from wav-mail-proxy-03.voxcore.co.za ([172.30.1.142])
by wav-mail-server-04.voxcore.co.za (Dovecot) with LMTP id ElVpOAbS/1f/KAAAhu5nvg
for <[email protected]>; Thu, 13 Oct 2016 20:27:40 +0200
Received: from mail.vox.co.za ([172.30.1.235])
by wav-mail-proxy-03.voxcore.co.za (Dovecot) with LMTP id d5r9OhvS/1eEIAAAEimTmw
; Thu, 13 Oct 2016 20:27:40 +0200
Envelope-to: [email protected]
Received: from alteonadmin.datapro.co.za ([196.41.30.114]:43047 helo=fortimail-02.voxtelecom.co.za)
by mail.vox.co.za with esmtp (Exim 4.82 (FreeBSD))
id 1bukjE-000A7c-JW
for [email protected]; Thu, 13 Oct 2016 20:27:40 +0200
Received: from smtp.voxtelecom.co.za ([196.41.6.173])
by fortimail-02.voxtelecom.co.za with ESMTP id u9DIRdI6030069-u9DIRdI7030069
for <[email protected]>; Thu, 13 Oct 2016 20:27:39 +0200
Received: from [10.0.0.249] (port=10826 helo=vox-outbound-av-03)
by smtp.voxtelecom.co.za with esmtp (Exim 4.80.1 (FreeBSD))
id 1bukjC-0008bi-3K
for [email protected]; Thu, 13 Oct 2016 20:27:38 +0200
X-Virus-Scanned: amavisd-new at spam.voxtelecom.co.za
Received: from smtp.voxtelecom.co.za ([172.50.0.249])
by vox-outbound-av-03 (vox-outbound-av-01.spam.voxtelecom.co.za [172.50.0.143]) (amavisd-new, port 10026)
with ESMTP id FcZrUrc2bip6 for <[email protected]>;
Thu, 13 Oct 2016 20:27:30 +0200 (SAST)
Received: from mailnull by smtp.voxtelecom.co.za with local (Exim 4.80.1 (FreeBSD))
id 1bukj3-0008ay-3y
for [email protected]; Thu, 13 Oct 2016 20:27:29 +0200
X-Failed-Recipients: [email protected]
Auto-Submitted: auto-replied
From: Mail Delivery System <[email protected]>
To: [email protected]
Subject: Mail delivery failed: returning message to sender
Message-Id: <[email protected]>
Date: Thu, 13 Oct 2016 20:27:29 +0200

 

[Belix]

and another

Return-Path: <>
Delivered-To: [email protected]
Received: from wav-mail-proxy-04.voxcore.co.za ([172.30.1.143])
by wav-mail-server-04.voxcore.co.za (Dovecot) with LMTP id 04YGBCMb+le7dgAAhu5nvg
for <[email protected]>; Sun, 09 Oct 2016 12:25:39 +0200
Received: from mail.vox.co.za ([172.30.1.235])
by wav-mail-proxy-04.voxcore.co.za (Dovecot) with LMTP id eUhJLRwb+le2LwAAWBuWlA
; Sun, 09 Oct 2016 12:25:39 +0200
Envelope-to: [email protected]
Received: from alteonadmin.datapro.co.za ([196.41.30.114]:44746 helo=fortimail-02.voxtelecom.co.za)
by mail.vox.co.za with esmtp (Exim 4.82 (FreeBSD))
id 1btBIZ-000HCf-0J
for [email protected]; Sun, 09 Oct 2016 12:25:39 +0200
Received: from smtp.voxtelecom.co.za ([196.41.6.173])
by fortimail-02.voxtelecom.co.za with ESMTP id u999l4lW013352-u999l4lX013352; Sun, 9 Oct 2016 11:47:04 +0200
Received: from [10.0.0.249] (port=27089 helo=vox-outbound-av-14)
by smtp.voxtelecom.co.za with esmtp (Exim 4.80.1 (FreeBSD))
id 1btAhN-0006PC-3f
for [email protected]; Sun, 09 Oct 2016 11:47:13 +0200
X-Virus-Scanned: amavisd-new at spam.voxtelecom.co.za
Received: from smtp.voxtelecom.co.za ([172.50.0.249])
by vox-outbound-av-14 (vox-outbound-av-01.spam.voxtelecom.co.za [172.50.0.156]) (amavisd-new, port 10024)
with ESMTP id PXfHwp9Xw1OQ for <[email protected]>;
Sun, 9 Oct 2016 11:46:47 +0200 (SAST)
Received: from mailnull by smtp.voxtelecom.co.za with local (Exim 4.80.1 (FreeBSD))
id 1btAhL-000GQz-6A
for [email protected]; Sun, 09 Oct 2016 11:47:11 +0200
X-Failed-Recipients: [email protected]
Auto-Submitted: auto-replied
From: Mail Delivery System <[email protected]>
To: [email protected]
Subject: Mail delivery failed: returning message to sender
Message-Id: <[email protected]>
Date: Sun, 09 Oct 2016 11:47:11 +0200
X-FEAS-BEHAVIOR-ANALYSIS: HVFQITovXAVYWVxYXl1FHVFQITovXAZYWVxYXl1SPVIAHBwYUkdHGw0GDEYFGFsaAQYPHAcGDRsMBx8GBAcJDBtGCwcFRyANCRwADRo3KhoHHwY=
X-FEAS-CLIENT-IP: 196.41.6.173

 

[Foxhound5366]

Well that makes it clear then, doesn't it?

The problem is that your behaviour has been analysed and the computer says no ... err ... "HVFQITovXAVYWVxYXl1FHVFQITovXAZYWVxYXl1SPVIAHBwYUk dHGw0GDEYFGFsaAQYPHAcGDRsMBx8GBAcJDBtGCwcFRyANCRwA DRo3KhoHHwY="

You better hope that doesn't translate back into something embarrassing

 

[WAslayer]

get vox to clarify on their spam scoring system and what the X-FEAS-BEHAVIOR-ANALYSIS: HVFQITovXAVYWVxYXl1FHVFQITovXAZYWVxYXl1SPVIAHBwYUk dHGw0GDEYFGFsaAQYPHAcGDRsMBx8GBAcJDBtGCwcFRyANCRwA DRo3KhoHHwY= actually means..