Prevent exim from dropping mail after limit hit

S

shadowq

Verified User
Joined
Dec 5, 2010
Messages
97
Hi,

I know the previous Exim behaviour (pre exim v15 I think) used to place emails in the queue after the daily limit was set and they would simply continue sending the following day once the limit was reset. However, the new behaviour with newer versions of Exim simply discards emails that exceed the daily limit. I would much prefer the former behaviour with my set of clients.

Can someone please either tell me how to achieve this, or possibly where to find an older version of exim to compare and figure it out myself?

Thanks,
Jarrod.
 
shadowq said:
However, the new behaviour with newer versions of Exim simply discards emails that exceed the daily limit. I would much prefer the former behaviour with my set of clients.
Click to expand...
As zEitEr points out, newest versions of the DirectAdmin exim configuration don't accept the email at all; they don't drop it.

My recollection is that older versions simply marked the emails as unrouteable, so they would end up on the queue in a return-to-sender status, and then later, once the sender's mailbox was full would then remain on the queue. So they'd never get delivered anyway.

The problem with leaving them on the queue, whether for ongoing delivery or return, is that the queue will continue to expand if an account is hacked, and more and more spam will make the queue unmanageable, perhaps even make email completely unusable (outgoing and incoming email can both use the queue), and in extreme situations even bring the server to it's knees.

That's why the change was made.

Do you really want more spam to go out the next day? That's what would happen (in addition to the problems I mentioned above).

Jeff
 
Thanks Jeff and Alex. I'm terribly sorry for the delay, I was just wondering why I hadn't received any replies and logged in to post again. For some reason I didn't get an email notification letting me know (despite subscription being turned on for this thread).

I understand the risks involved. Since we have a relatively small client base, with virtually all clients being managed by us, any SPAM issues are acted upon straight away by us, and then removed from the queue. During a SPAM attack in the past, I have had over 55k+ SPAM messages in the mail queue, and the queue still functioning correctly. Once the issue had been resolved, we simply removed all SPAM from the queue using a small script.

The primary reason for wanting to have mail kept in queue once their limit is exceeded, is that we set a relatively low mail limit for our clients so that we can monitor their mail usage and ensure it isn't being abused. However, if they do send out a mailout or similar, all messages after the limit is hit are dropped (or as you pointed out Jeff, not even accepted).

So to answer your question, yes, I would like mail (be that SPAM if we didn't get to it) to be sent out the next day from the queue. Is there a way to achieve this?

Thanks again for your help!
 
Sorry to bump the thread- I was just wondering how I might achieve the mail being frozen or just sitting in the queue rather than being rejected once a user hits their limit?
 
I know it's been a year- But I'd been very interested to push all emails to a queue, and nullroute the ones for users that have hit the email limit for the day. Can anyone please help me here?
 
You must log in or register to reply here.
Back
Top