OSEC

Neohapsis is currently accepting applications for employment. For more information, please visit our website www.neohapsis.com or email hr@neohapsis.com
R: Programmatic access to the showq daemon/data

From: Benelli Luca (Luca.Benellinetengineering.it)
Date: Tue Oct 02 2007 - 02:01:59 CDT


 

-----Messaggio originale-----
Da: owner-postfix-userspostfix.org [mailto:owner-postfix-userspostfix.org] Per conto di Victor Duchovni
Inviato: marted́ 2 ottobre 2007 1.16
A: Ward, Martin
Cc: postfix-userspostfix.org
Oggetto: Re: Programmatic access to the showq daemon/data

On Tue, Oct 02, 2007 at 12:05:42AM +0100, Ward, Martin wrote:

> Unfortunately I can't do that without more power than most countries have,
> or at least a few assassins...
>
> I work for an ISP so a lot of mail we try and route is junk (I don't like
> it but I have to live with it). The customer, quite rightly, won't accept
> it but since we already have we must deal with the concequences.

Are you a backup MX provider? If so, phase out this service for customers who don't provide valid recipient lists. Consider enabling recipient verification for relay domains that don't provide valid user lists, but reject email for invalid addresses.

Finally, if clients reject messages from your relay even for valid recipients, based on spam scores, ... phase out service to them also, one must not filter traffic from the backup MX, if the backup MX's anti-spam policy is not satisfactory, one must drop the find or build a more suitable backup MX whose ingress policy is satisfactory.

--
        Viktor.

I'm not sure i understood correctly, but if you are accepting emails as backup MX for somebody else it may help using greylisting.
I started using greylisting on our small company backup MX server and got somewhere near 99% rejects... on ISP mail numbers it may make quite a difference. At least it might be worth considering if anything else is not acceptable due to some "political" (un)reason from above :)

Luca

--
Luca Benelli