Problems sending Mail between Webs

[DiOmega]

We have some Problems with Mails from one web (web15) to an other web (web20) on one Server. Bothe webs belong to one Company but two Locations who Exchange a lot of Mails. Most of them are marked as Spam. In one Location there is Groupware-Server (Tobit) on an dynamic IP DSL Connection. On the other Location are Outlook-Clients who send directly over an dynamic IP DSL Connection.

This is theSpamAssasin Report of one Mail:

Content analysis details: (8.9 points, 5.0 required)

pts rule name description
---- ---------------------- --------------------------------------------------
3.3 TVD_RCVD_IP4 TVD_RCVD_IP4
1.6 TVD_RCVD_IP TVD_RCVD_IP
0.0 HTML_MESSAGE BODY: HTML included in message
1.8 MIME_QP_LONG_LINE RAW: Quoted-printable line longer than 76 chars
1.6 RCVD_IN_SORBS_DUL RBL: SORBS: sent directly from dynamic IP address
[84.169.38.131 listed in dnsbl.sorbs.net]
0.5 RCVD_IN_PBL RBL: Received via a relay in Spamhaus PBL
[84.169.38.131 listed in zen.spamhaus.org]
-0.0 AWL AWL: From: address is in the auto white-list


Why are those Mails get their IPs checked?
(These Clients connect directly to our Server. I thought Clients authenticated by our Server doesn't need to be scanned.)

Why do the AWL score -0.0?
(In http://www.howtoforge.com/forums/showthread.php?t=9745 you discussed about the "score AWL -100.0" and these setting is set to -100 in our configs.)

Is their anything i can do to improve the E-Mail settings?

Thanks a lot for yor help.

[falko]

Is the mail server using a dynamic IP address?

This thread might help you as well: http://www.howtoforge.com/forums/sho...highlight=spam

[DiOmega]

No, our Mailserver has static IP address and Reverse DNS.
I even checked our address in SORBS and it is not listed.

The IP address in the SpamAssasin Reports are the IP adresses of our Costumers. They are dynamic. Why does SpamAssasin check these IP's because they authenticate themselves to Postfix?

[falko]

Did you try the suggestions from this thread? http://www.howtoforge.com/forums/sho...highlight=spam

[DiOmega]

Originally Posted by falko

Did you try the suggestions from this thread? http://www.howtoforge.com/forums/sho...highlight=spam

If i add
"skip_rbl_checks 1"
to
"/home/admispconfig/ispconfig/tools/spamassassin/etc/mail/spamassassin/local.cf"
does it disable the RBL-Checks globally or only for incoming mail from local users?

[DiOmega]

I read some posts in the Mailinglist mentioned in the other thread and found a Mail regarding a Sendmail macro to filter the Mails from local Users which use SMTP AUTH.

http://lists.roaringpenguin.com/pipe...er/017522.html

Is there a way to implement a similar filter for Postfix and ISPConfig?

[Ben]

I had the same problem once, and only "fixed" it by skipping the rbl checks.
If SA would no be started via procmail but e.g. via clamav (out of postfix), you could tell postfix to not use SA for mails incominfg via smtp-auth (587 or sth. like this). But this is not possbile here.
So what you would have to do is change _all_ (of every user) procmail scripts that run SA and change it the way to not run SA for authenticated users.

-> http://www.howtoforge.com/forums/showthread.php?t=13815

[DiOmega]

Originally Posted by Ben

So what you would have to do is change _all_ (of every user) procmail scripts that run SA and change it the way to not run SA for authenticated users.
-> http://www.howtoforge.com/forums/showthread.php?t=13815

How could i do that?

In this Thread you posted to insert "skip_rbl_checks 1" in "/home/admispconfig/ispconfig/tools/spamassassin/etc/mail/spamassassin/local.cf".

Does this disable it only for Mails from authenticated users and not for all Mails?

[falko]

Find the template for .user_prefs in /root/ispconfig/isp/conf and place your modified version in the /root/ispconfig/isp/conf/customized_templates directory.

Then change something in ISPConfig for all users. The .user_prefs file will then be rewritten for all users.

[jmroth]

You could also correctly set up spamassassin's trusted and internal network lists. Then it will at least be flagged "ALL_TRUSTED".