hi,
i have a problem on my server, i use cpanel with exim .. to shared
hosting server and some clients hung my server by sending alot of mail
so yahoo and msn block me ..
if there is any way to limited the outgoing email to no. for example 100email/hr without killing the other amount of mail and just keep it until the old message send ?
Best Regards
From graeme@??? Mon Aug 03 14:32:57 2009
Envelope-to: exim-users@???
Received: from boom.graemef.net ([82.113.154.29]:42683)
by tahini.csx.cam.ac.uk with esmtp (Exim 4.69)
(envelope-from <graeme@???>) id 1MXxek-0005dd-8S
for exim-users@???; Mon, 03 Aug 2009 14:32:57 +0100
Received: from squonk.lut.ac.uk ([131.231.87.200])
by boom.graemef.net with esmtpsa (TLSv1:AES256-SHA:256) (Exim 4.69)
(envelope-from <graeme@???>) id 1MXxR5-0000c9-PS
for exim-users@???; Mon, 03 Aug 2009 14:18:44 +0100
From: Graeme Fowler <graeme@???>
To: exim-users@???
In-Reply-To: <20090803164448.5c5e1795@???>
References: <20090803164448.5c5e1795@???>
Content-Type: text/plain
Date: Mon, 03 Aug 2009 14:18:36 +0100
Message-Id: <1249305516.26724.8.camel@???>
Mime-Version: 1.0
X-Mailer: Evolution 2.24.5 (2.24.5-2.fc10)
Content-Transfer-Encoding: 7bit
X-Spam-Score: -2.1 (--)
X-Spam-Status: No, score=-2.1 required=5.0 tests=AWL=0.436, BAYES_00=-1.5,
EXIM_EXP_VAR=-1 autolearn=ham version=3.1.8
Subject: Re: [exim] Remote shadow transport
X-BeenThere: exim-users@???
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: A user list for the exim MTA <exim-users.exim.org>
List-Unsubscribe: <http://lists.exim.org/mailman/listinfo/exim-users>,
<mailto:exim-users-request@exim.org?subject=unsubscribe>
List-Archive: <http://lists.exim.org/lurker/list/exim-users.html>
List-Post: <mailto:exim-users@exim.org>
List-Help: <mailto:exim-users-request@exim.org?subject=help>
List-Subscribe: <http://lists.exim.org/mailman/listinfo/exim-users>,
<mailto:exim-users-request@exim.org?subject=subscribe>
X-List-Received-Date: Mon, 03 Aug 2009 13:32:58 -0000
On Mon, 2009-08-03 at 16:44 +0900, Christian Balzer wrote:
> So how do people keep a backup (meaning only mails that actually got a
> final delivery, splitting things off earlier is trivial of course) of
> incoming mails on a remote server then?
I guess this depends upon what you define as "final delivery", doesn't
it? Do you mean:
A. Only take a backup copy of a message once it has successfully
completed delivery into a user's mailbox, or
B. Take a backup copy as part of the operation of delivering into the
user's mailbox
- there's a minor, but significant, difference between those two
statements.
At work, on our Exim+CourierIMAP based "postbox" servers - that is, the
ones which the users access via an IMAP client to read their mail - we
have a shadow router/transport pair which copy the mail to a short-lived
"Incoming Mail Backup" maildir:
Router is:
localuser_backup:
driver = accept
check_local_user
address_data = <condition removed>
transport = local_delivery_backup
unseen
Transport is:
local_delivery_backup:
driver = appendfile
directory = $home/Incoming-Mail-Backup
user = $address_data
delivery_date_add
return_path_add
maildir_format
That pair run immediately before the local delivery router puts the
message in the user's mailbox.
It's not a great stretch of logic to change the transport to be a remote
one.
*However* - this happens immediately before the message is delivered
into the user's mailbox, so could quite conceivably store the backup
copy yet have a problem with the actual delivery, causing the message to
be lost.
Yes, this is the entire point of the backup operation, in case you were
wondering!
I guess you could invert the sequence, and make the *actual* delivery
"unseen" and then do the remote one but that would make error handling
more difficult.
What would your definition of "final delivery" be?
Graeme
