Facebook
Twitter
M
maedde
Guest
Hi all,
we are using Plesk 8.1 on Debian 3.1 with Qmail and Spamassassin.
--- 8< ---
ii drweb-qmail 4.33-debian3.1 qmail Mail Transfer Agent
ii psa-qmail 1.03-debian3.1 qmail Mail Transfer Agent
ii psa-qmail-rbls 0.70-debian3.1 Antispam DNS-based block lists
ii psa-spamassass 8.1.0-debian3. SpamAssassin support for Plesk
ii spamassassin 3.0.3-2sarge1 Perl-based spam filter using text analysis
--- >8 ---
Mails are delivered using a .qmail file in /var/qmail/mailnames/DOMAIN/EMAIL/:
--- 8< ---
| /opt/psa/bin/psa-spamc reject
| true
./Maildir/
--- >8 ---
Customers can use SMTP AUTH our SMTP-after-POP for getting send permissions.
Our problem is the following:
[email protected] and [email protected] are both located on our server.
1. [email protected] sends an email to [email protected] from his dial-up IP, which is listed at Spamhaus RBL and so on.
2. the message is accepted by Qmail and local delivery is started.
3. SpamAssassin examines the email before delivering it to the user's Maildir and tags it as spam as it was delivered from a dial-up host.
The mail has the following received headers:
--- 8< ---
Received: (qmail 17357 invoked from network); 20 Mar 2007 00:43:38 +0100
Received: from ip-1-2-3-4.web.vodafone.de (HELO HADRIAN) (1.2.3.4)
by mail.domain.tld with SMTP; 20 Mar 2007 00:43:38 +0100
--- >8 ---
There is no hint about an authentification token or anything similar so SpamAssassin makes a correct decision.
But this behavior SUCKS definitely as our customers have to be able to send mails between each other without being tagged as spammers.
Is there any solution out there like a Qmail patch or something like that?
This behaviour started when going from Plesk 7.5/SuSE to Plesk 8.x/Debian.
Kind Regards,
Matthias K.
we are using Plesk 8.1 on Debian 3.1 with Qmail and Spamassassin.
--- 8< ---
ii drweb-qmail 4.33-debian3.1 qmail Mail Transfer Agent
ii psa-qmail 1.03-debian3.1 qmail Mail Transfer Agent
ii psa-qmail-rbls 0.70-debian3.1 Antispam DNS-based block lists
ii psa-spamassass 8.1.0-debian3. SpamAssassin support for Plesk
ii spamassassin 3.0.3-2sarge1 Perl-based spam filter using text analysis
--- >8 ---
Mails are delivered using a .qmail file in /var/qmail/mailnames/DOMAIN/EMAIL/:
--- 8< ---
| /opt/psa/bin/psa-spamc reject
| true
./Maildir/
--- >8 ---
Customers can use SMTP AUTH our SMTP-after-POP for getting send permissions.
Our problem is the following:
[email protected] and [email protected] are both located on our server.
1. [email protected] sends an email to [email protected] from his dial-up IP, which is listed at Spamhaus RBL and so on.
2. the message is accepted by Qmail and local delivery is started.
3. SpamAssassin examines the email before delivering it to the user's Maildir and tags it as spam as it was delivered from a dial-up host.
The mail has the following received headers:
--- 8< ---
Received: (qmail 17357 invoked from network); 20 Mar 2007 00:43:38 +0100
Received: from ip-1-2-3-4.web.vodafone.de (HELO HADRIAN) (1.2.3.4)
by mail.domain.tld with SMTP; 20 Mar 2007 00:43:38 +0100
--- >8 ---
There is no hint about an authentification token or anything similar so SpamAssassin makes a correct decision.
But this behavior SUCKS definitely as our customers have to be able to send mails between each other without being tagged as spammers.
Is there any solution out there like a Qmail patch or something like that?
This behaviour started when going from Plesk 7.5/SuSE to Plesk 8.x/Debian.
Kind Regards,
Matthias K.
