On Sat, 22 Dec 2007, Phil Pennock wrote:
So you can rotate all you like; provided that you retry from the same IP
at least once, more than 10 minutes after the first attempt from that
IP, then it will go through.
I just had this section in each of the server;s configration, of course
the
On Fri, 21 Dec 2007, Phil Pennock wrote:
On 2007-12-21 at 23:47 +0100, Leonardo Boselli wrote:
Try later ... after 24 hours
No, but from the same IP is appreciated.
actually at least the last 3 tries came from the same server (althought it
has 4 addresses)
I dislike greylisting but use
On 2007-12-21 at 23:47 +0100, Leonardo Boselli wrote:
Try later ... after 24 hours
No, but from the same IP is appreciated.
I dislike greylisting but use it, with the daemon from Debian, munged
about a bit to work on FreeBSD. The retry time is 10 minutes: retrying
just 10 minutes after
Leonardo Boselli wrote:
I (or better my server) does not bounce around: just has a rule that if
the two main servers (that offer pop3 and imap service to users,
an that act as smarthosts for local users) cannot
send directly within 5 minutes, to save CPU cycles, they pass
the message to one
On 2007-12-22 at 10:37 +0100, Leonardo Boselli wrote:
Ok but what if my MTA has 4 address on 4 subnets from 3 different
providers an use each one in turn ? (none of provider warrant a 100% up
time, but just a nominal 98.5).
Each (IP, sender, recipient) triple is recorded, together with first
Try later ... after 24 hours
-- Forwarded message --
Date: Fri, 21 Dec 2007 17:23:01 +0100
From: Mail Delivery System [EMAIL PROTECTED]
To: [EMAIL PROTECTED]
Subject: Warning: message 1J5JXM-4y-74 delayed 24 hours
This message was created automatically by mail delivery
