Help with postgrey

[robbo007]

Hello all,
After a recent upgrade of Debain 6 and ISP 1.0.7 RC some clients are complaining email is not getting through.

/var/log/mail.log show the some recipients are getting rejected by Post grey

Recipient address rejected: Greylisted

Is there a way to reduce weight checks so more mail gets though? I prefer to have more spam and less mails being greylisted.

Here is my postfix config:

/etc/postfix/main.cf

smtpd_recipient_restrictions = reject_non_fqdn_recipient,
reject_unknown_recipient_domain,
permit_mynetworks,
permit_sasl_authenticated,
reject_unauth_destination,
reject_unlisted_recipient,
check_policy_service inet:127.0.0.1:12525,
check_policy_service inet:127.0.0.1:10023,
permit

Thanks,
Rob

[joximu]

Hi

you need to understand greylisting...

Maybe with the update the database of postgrey are starting from scratch - so they have to greylist almost everything what's coming in. With the time postgrey has learned who is sending mails from which mailserver to which mail account... and then the delivery will be faster.

Normally greylisting only extends the time until a mail is delivered... this is maybe an hour or less (also depends on the sending server).

/J

[robbo007]

Thanks for the reply. So errors like:

Recipient address rejected: Mail appeared to be SPAM or forged. Ask your Mail/DNS-Administrator to correct HELO and DNS MX settings or to get removed from DNSBLs; please relay via your ISP

and

Recipient address rejected: Greylisted, see http://postgrey.schweikert.ch/

These emails will be "delayed" but later delivered? Or they will be blocked? Can I change the weight level for the database?
Rob

[joximu]

The first one is rejected by policyd-weight - and I doubt it will be send again.

The second one should be delivered again...


You really have to sort out which service is a problem for you. Often policyd-weight can be problem because the default configuraton is not really flexible...

But there are enough examples in this forum.


If a mail is rejected with an error code 4xx - then it's temporary and therefore further delivery attempts should be made... if the error number is a 5xx number then it's a permanent error and the mail is sent back/definetly refused.


/J

[robbo007]

Ok thanks for your help. I'll look into policyd-weight to fine tune it.
Much appreciated,
Rob

[robbo007]

One question if I may? Where is the default policyd-weight.conf ?? I don't see it in /etc and I've done a search and only have reference to:

/usr/share/man/man5/policyd-weight.conf.5.gz
/var/lib/dpkg/info/policyd-weight.conffiles

Is it included in ISPCP file somewhere else?

I'm seeing the rejected errors as mentioned above are coming from the external mail servers not having their FQDN configure correctly. My server then thinks its forged. From other posts I see changing the policyd-wiehgt config file seems to resolve this.

Thanks,
Rob

[joximu]

policyd-weight --help

->

policyd-weight defaults > /etc/policyd-weight.conf.default

put in the policyd-weight.conf what you want different...

I have

***
$REJECTLEVEL = 8;

## DNSBL settings
@dnsbl_score = (
# HOST, HIT SCORE, MISS SCORE, LOG NAME
'pbl.spamhaus.org', 3.25, 0, 'DYN_PBL_SPAMHAUS',
'sbl-xbl.spamhaus.org', 4.35, -1.5, 'SBL_XBL_SPAMHAUS',
'bl.spamcop.net', 3.75, -1.5, 'SPAMCOP',
'dnsbl.njabl.org', 4.25, -1.5, 'BL_NJABL',
# 'ix.dnsbl.manitu.net', 4.35, 0, 'IX_MANITU',
# 'rbl.ipv6-world.net', 4.25, 0, 'IPv6_RBL'
);

$CACHEREJECTMSG = '450 temporarily blocked because of previous errors';
***

/J

[robbo007]

Much apprciated. In the end I created the /etc/policyd-weight.conf file from the template and I'm using a score of 4.5 which seems to work well. I'll watch the log over the next few days.

[fitzhall27]

This post is better than others because of useful and meaningful posts.