Quote:
|
Originally Posted by papi
1) some spammer sends mail to nonexistant local users but exim for some reason doesn't reject the email during the initial connection and instead tries to send back a bounce to an obviously faked return email and because it's fake, it's rejected by remote smtp server and so the bounce stays in my queue
|
The only place I have seen this become an issue, is if you are using any type of exim ACL to always accept mail for a specific e-mail address. Specifically I remember seeing a post where you could configure exim to always accept
postmaster@domain.com and
abuse@domain.com for every domain on the server, and forward those to a specific e-mail address you as an administrator had set up. I have seen where this can cause problems where the message is rejected but remains in the queue. You see messages in the queue that will say "postmaster@domain.com rejected, user does not exist". Not sure if this describe your problem, but this is where I have seen this problem. If you've done this setup, you might try undoing those changes.
Quote:
|
Originally Posted by papi
3) spammer sends mail to an email hosted by us but the user's mailbox or space quota is full and exim sends a bounce to faked return path and once again the bounce remains in my queue as it's not accepted by remote server
|
There are some posts on the cpanel forums regarding a shell script that you put in cron that runs every 5 minutes and checks to see if an account is over its quota, and if it is, that domain is added to a list where exim denies mail for that domain at the RCPT TO stage. I am using this on most of our servers and it has worked pretty good. I think these are the posts:
http://forums.cpanel.net/showpost.ph...0&postcount=13
http://forums.cpanel.net/showpost.ph...2&postcount=19
Concerning when mailboxes are over quota, this has become one of my pet peeves. I cannot for the life of be think of a situation where mailbox quotas are necessary. When a user creates a mail account, they are either going to be checking that mail account or they are not going to be checking it. If they are checking it, then the mailbox quota is of no real use and unnecessary. If they are not checking the mailbox, then they shouldn't create it in the first place. If I see where an account's mailbox is over quota, I go into the account and remove the quota limit on that mailbox, so that it is unlimited, then if that mailbox continues to fill up mail, eventually the entire account will reach its quota limit and then the above exim deny will kick in. Then when the users write in saying they are not getting mail, then I will tell them that they shouldn't have the mailbox created if they are not going to be checking it for mail regularly.
Quote:
|
Originally Posted by papi
The only thing I can think of is to have a shell script written that inspects the mail queue and deletes mail that matches certain patterns and put it in cron ... But is there any better solution? Some way to tell Exim to stop being so damn stupid and sending bounces to faked return emails...
|
I have tried doing this before, but decided that it was best to find the underlying cause. For example, you could delete all of the bounce messages in your queue saying that a mailbox is full, but at the end of the day, the mailbox is still full and those bounce messages are still occurring. The best solution, in my book, has always been to find what the exact cause of the problem is and then focusing on that problem. If the mailbox is full, then attack that.
Hope this helps.
Linear Mode
