PDA

View Full Version : Postfix and Spam !!!


brainz
28th November 2007, 09:30
Hi All,

I just edited the main.cf file for the mail server that i am running and i added this to it....


smtpd_helo_required = yes
disable_vrfy_command = yes
strict_rfc821_envelopes = yes
invalid_hostname_reject_code = 554
multi_recipient_bounce_reject_code = 554
non_fqdn_reject_code = 554
relay_domains_reject_code = 554
unknown_address_reject_code = 554
unknown_client_reject_code = 554
unknown_hostname_reject_code = 554
unknown_local_recipient_reject_code = 554
unknown_relay_recipient_reject_code = 554
unknown_sender_reject_code = 554
unknown_virtual_alias_reject_code = 554
unknown_virtual_mailbox_reject_code = 554
unverified_recipient_reject_code = 554
unverified_sender_reject_code = 554

smtpd_recipient_restrictions = reject_invalid_hostname, reject_unknown_recipient_domain, reject_unauth_pipelining, permit_mynetworks, permit_sasl_authenticated, reject_unauth_destination, reject_rbl_client multi.uribl.com, reject_rbl_client dsn.rfc-ignorant.org, reject_rbl_client dul.dnsbl.sorbs.net, reject_rbl_client list.dsbl.org, reject_rbl_client sbl-xbl.spamhaus.org, reject_rbl_client bl.spamcop.net, reject_rbl_client dnsbl.sorbs.net, reject_rbl_client cbl.abuseat.org, reject_rbl_client ix.dnsbl.manitu.net, reject_rbl_client combined.rbl.msrbl.net, reject_rbl_client rabl.nuclearelephant.com, permit

Which seems ok and the mail server is running fine...

However in the mail.log i get a message like this...

Nov 28 14:02:20 servername postfix/smtpd[29028]: warning: xxx.xxx.xx.xxx.bl.spamcop.net: RBL lookup error: Host or domain name not found. Name service error for name=xxx.xxx.xx.xxx.bl.spamcop.net type=A: Host not found, try again

The xxx.xxx.xx.xxx is a ip address i would say form the recipient sending email to the server.

It seems the incoming ip adress is being added to the spam server for some reason...

like

xxx.xxx.xx.xxx . bl.spamcop.net

which is not being recognised.

Please if anyone has a idea....??

regards
brainz

falko
29th November 2007, 16:51
This explains how bl.spamcop.net works: http://www.spamcop.net/fom-serve/cache/351.html

I think you should simply remove reject_rbl_client bl.spamcop.net from your main.cf.

brainz
29th November 2007, 22:26
Hi Falko,

Im sorry but this was just one example, however it seems all the spam list servers are producing the same message....

If i take out all of them there i cant see the sense in this type of protection from spam.

Unfortunantly there all doing the same thing....

Any help would be apreciated

regards
brainz

falko
30th November 2007, 15:33
What's in /etc/resolv.conf?

brainz
1st December 2007, 12:46
Hi Falko,

The /etc/resolv.conf has in it a internal servers ip address that is running a internal domain. It does run dns but only for the local domain.

but in /etc/resolv.cong its simply nameserver 192.168.0.xxx which is the server inside the local network that runs a local domain.

regards
brainz

falko
2nd December 2007, 20:25
Try this resolv.conf instead:
nameserver 145.253.2.75
nameserver 193.174.32.18

brainz
3rd December 2007, 07:20
Hi Falko,


i tried these nameservers...

nameserver 145.253.2.75
nameserver 193.174.32.18

but this not made a difference...

i cant even do a simple ping google.com i get this..

ping: unknown host google.com

i can ping the default gateway 192.168.0.1 and i can ping our external ip address 60.229.253.45 just find it seems anything beyond i cannot ping anything beyond this...

any help would be appreciated... Thankyou..

regards
brainz

falko
4th December 2007, 21:14
What's the output of ping -c2 64.233.187.99? (64.233.187.99 is a Google server.)

brainz
5th December 2007, 01:46
Hi Falko,

Thankyou for your help...

I have sorted the issue.... The server is now resolving domains.

I used the 2 nameservers you provided... Now it is resolving... What i actually did is disonnected the whole network and connected the server directly to the router as the only box on the network and then i changed the nameservers to the ones you provided. Then restarted the server which i did not need to do actually but i did.

The server started to resolve...

Thankyou for you help once again.

regards
brainz