Debian Postfix UNSOLICITED BULK EMAIL, apparently from you

[unclecameron]

I followed the How-To for Debian Etch/Postfix/Virtual and after a week of successful testing started getting the following error:

From: Content-filter at mail1.server.com
 [postmaster@mail1.server.com]
Sent: Sunday, June 24, 2007 1:01 PM To: name@server.com 
Subject: Considered UNSOLICITED BULK EMAIL, apparently from you

A message from <name@server.com> to: -> somename@yahoo.com was considered unsolicited bulk e-mail (UBE). Our internal reference code for your message is 15973-07/ipyPfF8DMCzg The message carried your return address, so it was either a genuine mail from you, or a sender address was faked and your e-mail address abused by third party, in which case we apologize for undesired notification. We do try to minimize backscatter for more prominent cases of UBE and for infected mail, but for less obvious cases of UBE some balance between losing genuine mail and sending undesired backscatter is sought, and there can be some collateral damage on both sides. 

First upstream SMTP client IP address: [xx.xx.152.161] xxxxx.res.rr.com According to a 'Received:' trace, the message originated at: [xx.xx.152.161], design1 (xxxx.res.rr.com [xx.xx.152.161]) Return-Path: <name@server.com> Message-ID: <6A6ED8E39D444ECCB967390EFA5A9DE2@design1> Subject: RE: Question about shipping for xxxxxxx

 Delivery of the email was stopped!

this is sent from my wife's Outlook account, although I also get similar messages from Logwatch and other local processes where I can guarantee I am the sender. I have run the test at abuse.net for relaying and it passed. What process is blocking this? Is it postfix or something amavisd is calling up?

BTW, I'm a supporter with a subscription, but the forum doesn't list me as one, how do I change that?

Thanks,
Cameron
San Diego

[till]

Originally Posted by unclecameron

I followed the How-To for Debian Etch/Postfix/Virtual and after a week of successful testing started getting the following error:

From: Content-filter at mail1.server.com
 [postmaster@mail1.server.com]
Sent: Sunday, June 24, 2007 1:01 PM To: name@server.com 
Subject: Considered UNSOLICITED BULK EMAIL, apparently from you

A message from <name@server.com> to: -> somename@yahoo.com was considered unsolicited bulk e-mail (UBE). Our internal reference code for your message is 15973-07/ipyPfF8DMCzg The message carried your return address, so it was either a genuine mail from you, or a sender address was faked and your e-mail address abused by third party, in which case we apologize for undesired notification. We do try to minimize backscatter for more prominent cases of UBE and for infected mail, but for less obvious cases of UBE some balance between losing genuine mail and sending undesired backscatter is sought, and there can be some collateral damage on both sides. 

First upstream SMTP client IP address: [xx.xx.152.161] xxxxx.res.rr.com According to a 'Received:' trace, the message originated at: [xx.xx.152.161], design1 (xxxx.res.rr.com [xx.xx.152.161]) Return-Path: <name@server.com> Message-ID: <6A6ED8E39D444ECCB967390EFA5A9DE2@design1> Subject: RE: Question about shipping for xxxxxxx

 Delivery of the email was stopped!

this is sent from my wife's Outlook account, although I also get similar messages from Logwatch and other local processes where I can guarantee I am the sender. I have run the test at abuse.net for relaying and it passed. What process is blocking this? Is it postfix or something amavisd is calling up?

Is your server located in a adatacenter or do you host it on a dynamic IP address?

BTW, I'm a supporter with a subscription, but the forum doesn't list me as one, how do I change that?

http://www.howtoforge.com/howtoforge_supporter_howto

[unclecameron]

I am at a datacenter as a colo box running a mailserver on dom2 on a Debian Etch xen SMP Xeon. I just added a valid reverse DNS entry, and the IP isn't blacklisted anywhere.

Thanks,
Cameron
San Diego

[falko]

Originally Posted by unclecameron

I just added a valid reverse DNS entry

Do you manage your IP address yourself, or is it managed by your ISP? Usually the ISP does that, and then he'd have to create the reverse record.

[unclecameron]

My ISP created the reverse DNS record, well, I sent a ticket in to them to have it done.

I just editted /etc/amavis/conf.d/20-debian_defaults and added my domain to the read hash list:

# read_hash("/var/amavis/sender_scores_sitewide"),

{ # a hash-type lookup table (associative array)
'nobody@cert.org' => -3.0,
'cert-advisory@us-cert.gov' => -3.0,
....
'.server.com' => -8.0,

and it fixed it, but I doubt I really fixed it, I can't do this for all the virtual hosts , yet I don't want to raise the detection much above the standard 6.31, that's higher than I'm used to having it.

Thanks,
Cameron
San Diego

[tiscarabee]

Hi !
I have the same problem... No fresh idea to help me ?
I have not change my reverseDNS, seems not to be a good idea at all... ?!
I've haded my domain in /etc/amavis/conf.d/20-debian_defaults too...
I don't receive the logwatch emails, it's not practical.
Recently, on one of my two servers encounter the problem, the mail arrived, but that this day there...
Probably a ghooost
Falko, an idea ?
Thx,
Tisc

[falko]

Any errors in your mail log?

[tiscarabee]

Hi Falko,

Sorry for long time, little holidays
The problem is checked, I received again my logwatch mails : I've modified the /etc/amavis/conf.d/20-debian_defaults and added my domain to the read hash list, like uncleCameron, with -18
I've made the modification too, proposed here :
http://www200.pair.com/mecham/spam/c...avisd-new.html

Clamav don't speak anymore in my logwatch to annonce his updates (freshclam), so I've just modified my freshclam.conf and putting true on the following options : LogVerbose true & LogSyslog true. Wait and see my tomorrow logwatch.

have a nice day !

[wanabewired]

Originally Posted by till

Is your server located in a a datacenter or do you host it on a dynamic IP address?

Hi,

I'm having this same problem after moving the virtual domains onto another identical etch set up as described in the howto but on another server on a different IP.

Most addresses have moved over okay but a couple of addresses are having UBE problems when they send. Is this a local configuration which is causing the problem?

One user uses microsoft outlook express and the other uses microsoft outlook 2003. Not sure if this has any impact but I thought I'd add it in.

Is there anything reported in the below code which might be a symptom of my mis-configuring anything in the howto?

Any help would be greatly appreciated.

Return-Path: <>
X-Original-To: problemaddress@problemdomain.co.uk
Delivered-To: problemaddress@problemdomain.co.uk
Received: from localhost (localhost.localdomain [127.0.0.1])
        by serverdomain.co.uk (Postfix) with ESMTP id 13D9E15199
        for <problemaddress@problemdomain.co.uk>; Wed,  4 Feb 2009 14:44:32 +0000 (GMT)
Content-Type: multipart/report; report-type=delivery-status;
 boundary="----------=_1233758672-15655-0"
Content-Transfer-Encoding: 7bit
MIME-Version: 1.0
Subject: Considered UNSOLICITED BULK EMAIL, apparently from you
In-Reply-To: <!&!AAAAAAAAAAAYAAAAAAAAAI3rdRyPkWFLnHwKoEQrVgDCgAAAEAAAAKN/BOt2OcRAjMwvSqvBd28BAAAAAA==@problemdomain.co.uk>
Message-ID: <SSidKKN469WFto@serveraddress.co.uk>
From: "Content-filter at serverdomain.co.uk" <postmaster@serverdomain.co.uk>
To: <problemaddress@problemdomain.co.uk>
Date: Wed,  4 Feb 2009 14:44:32 +0000 (GMT)

This is a multi-part message in MIME format...

------------=_1233758672-15655-0
Content-Type: text/plain; charset="iso-8859-1"
Content-Disposition: inline
Content-Transfer-Encoding: 7bit

A message from <problemaddress@problemdomain.co.uk> to:
-> anyaddress@anydomain.co.uk

was considered unsolicited bulk e-mail (UBE).

Our internal reference code for your message is 15655-02/idKKN469WFto

The message carried your return address, so it was either a genuine mail
from you, or a sender address was faked and your e-mail address abused
by third party, in which case we apologize for undesired notification.

We do try to minimize backscatter for more prominent cases of UBE and
for infected mail, but for less obvious cases of UBE some balance
between losing genuine mail and sending undesired backscatter is sought,
and there can be some collateral damage on both sides.

First upstream SMTP client IP address: [xxx.xxx.xxx.xxx] unknown
According to a 'Received:' trace, the message originated at:
  [xxx.xxx.xxx.xxx], ParkwoodPC (unknown [xxx.xxx.xxx.xxx])

Return-Path: <problemaddress@problemdomain.co.uk>
Message-ID:
  <!&!AAAAAAAAAAAYAAAAAAAAAI3rdRyPkWFLnHwKoEQrVgDCgAAAEAAAAKN/BOt2OcRAjMwvSqvBd28BAAAAAA==@problemdomain.co.uk>
Subject: test

Delivery of the email was stopped!

------------=_1233758672-15655-0
Content-Type: message/delivery-status; name="dsn_status"
Content-Disposition: inline; filename="dsn_status"
Content-Transfer-Encoding: 7bit
Content-Description: Delivery error report

Reporting-MTA: dns; serverdomain.co.uk
Received-From-MTA: smtp; serverdomain.co.uk ([127.0.0.1])
Arrival-Date: Wed,  4 Feb 2009 14:44:29 +0000 (GMT)

Original-Recipient: rfc822;anyaddress@anydomain.co.uk
Final-Recipient: rfc822;anyaddress@anydomain.co.uk
Action: failed
Status: 5.7.1
Diagnostic-Code: smtp; 554 5.7.1 Rejected, id=15655-02 - SPAM
Last-Attempt-Date: Wed,  4 Feb 2009 14:44:32 +0000 (GMT)

------------=_1233758672-15655-0
Content-Type: text/rfc822-headers; name="header"
Content-Disposition: inline; filename="header"
Content-Transfer-Encoding: 7bit
Content-Description: Message headers

Return-Path: <problemaddress@problemdomain.co.uk>
Received: from ParkwoodPC (unknown [xxx.xxx.xxx.xxx])
        by serverdomain.co.uk (Postfix) with ESMTP id 48E7B150F0
        for <anyaddress@anydomain.co.uk>; Wed,  4 Feb 2009 14:44:29 +0000 (GMT)
Return-Receipt-To: "Senders Name" <problemaddress@problemdomain.co.uk>
From: "Senders Name" <problemaddress@problemdomain.co.uk>
To: <anyaddress@anydomain.co.uk>
Subject: test
Date: Wed, 4 Feb 2009 14:44:21 -0000
Message-ID: <!&!AAAAAAAAAAAYAAAAAAAAAI3rdRyPkWFLnHwKoEQrVgDCgAAAEAAAAKN/BOt2OcRAjMwvSqvBd28BAAAAAA==@problemdomain.co.uk>
MIME-Version: 1.0
Content-Type: multipart/alternative;
        boundary="----=_NextPart_000_0000_01C986D7.1747EC90"
X-Mailer: Microsoft Office Outlook 12.0
Thread-Index: AcmG1xB5HDi1RrI/QS+DebUcG1cRwA==
Content-Language: en-gb

------------=_1233758672-15655-0--

[falko]

Please make sure that the MX, PTR, and SPF records for your domains are ok.