[Gllug] How to handle spam bounces from secondary MX server

[Bruce Richardson]

On Mon, Dec 08, 2008 at 04:02:54PM +0000, Ryan wrote:
> > And I disagree, having had the opposite experience by using greylisting
> > on my secondary and not my primary.  That and call forwarding has been a
> > winning combination (for me; may not work for everybody).
> 
> Okay then let's say it has to be at least the same level as your
> primary. I'm intrigued as to how your set-up can be as effective
> though. Greylisting causes enough confusion among some users as it is,
> if the greylisting delay only occured when the mail came in via the
> secondary MX I think it would make my phone glow an even brighter
> shade of red. :o)

As I said, it's my personal mail system and only has a few users.  It
wouldn't be appropriate for a large organisation where you could
reasonably expect load spikes to push mail to your secondary(ies) on a
regular basis.  That said, there are plenty of small/medium outfits for
whome it would work (and plenty who have worse solutions).

-- 
Bruce

What would Edward Woodward do?
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 204 bytes
Desc: Digital signature
URL: <http://mailman.lug.org.uk/pipermail/gllug/attachments/20081208/8c67f6f3/attachment.pgp>
-------------- next part --------------
-- 
Gllug mailing list  -  Gllug at gllug.org.uk
http://lists.gllug.org.uk/mailman/listinfo/gllug