27 messages in net.sourceforge.lists.courier-users[courier-users] Re: grrrr
FromSent OnAttachments
Robert HortonMay 21, 2004 7:38 am 
Lloyd ZusmanMay 21, 2004 8:45 am 
Gordon MessmerMay 21, 2004 9:39 am 
Robert HortonMay 21, 2004 10:03 am 
Jerry AmundsonMay 21, 2004 10:04 am 
Robert HortonMay 21, 2004 10:14 am 
William HueMay 21, 2004 10:45 am 
Gordon MessmerMay 21, 2004 11:47 am 
Jeff JansenMay 21, 2004 12:07 pm 
Jerry AmundsonMay 21, 2004 12:24 pm 
David GomillionMay 21, 2004 12:33 pm 
Robert HortonMay 21, 2004 12:53 pm 
Robert HortonMay 21, 2004 1:03 pm 
Robert HortonMay 21, 2004 1:04 pm 
keithMay 21, 2004 1:25 pm 
Robert HortonMay 21, 2004 2:58 pm 
Robert HortonMay 21, 2004 2:58 pm 
Robert HortonMay 21, 2004 3:04 pm 
Sam VarshavchikMay 21, 2004 3:31 pm 
Chris PetersenMay 21, 2004 3:52 pm 
Robert HortonMay 21, 2004 4:04 pm 
Jeff JansenMay 21, 2004 4:30 pm 
Sam VarshavchikMay 21, 2004 4:56 pm 
Jeff JansenMay 21, 2004 5:26 pm 
William HueMay 21, 2004 5:34 pm 
m...@rtij.nlMay 24, 2004 4:11 am 
Sam VarshavchikMay 24, 2004 3:47 pm 
Actions with this message:
Paste this link in email or IM:
Paste this link in email or IM:
Atom feed for this thread
Paste this URL into your reader:
Subject:[courier-users] Re: grrrrActions...
From:Lloyd Zusman (lj@asfast.com)
Date:May 21, 2004 8:45:52 am
List:net.sourceforge.lists.courier-users

The other day, I posted a syslog-based proceure that you can use to detect when undeliverable error bounces are getting repeatedly queued on your side, and then to automatically remove them from your queue.

Look back in the mailing list for posts by me during this week, and you'll find a description of the method that I use within syslog, and in a second message by me, you'll find the Perl script that I use to actually delete the messages.

This script can be modified to look at any criteria in the queue control file and any headers or body data in the message, and to use that info to decide whether the message should be removed from the queue.

It's a bit of a hack, but it works well for me.

I am sorry to keep bringing this up, but I have tried everything and am not sure where to turn next!

The issue: one particular domain *appears* to be using me as a relay. The messages sit in my mailq and my log grows and grows. I have only a few actual users right now and I want to get this addressed before I get too many.

My smtpaccess file ONLY has allow,RELAYCLIENT for localhost and the IP I registered for my domain. My locals file only has localhost and my domain and my esmtpacceptmailfor also is localhost and my domain as is hosteddomains. My installation is nothing special nor have I made any drastic changes to anything.

Now, to be clear, I do not receive ANY spam from this domain or any other for that matter so I do not think this is a filtering issue, although it may be.

So I guess my question has a few options:

A.) How do I prevent this one domain from attempting to go through me and further HOW are they doing it?

B.) How can I set the mailq so it does not hold onto these emails thereby slowing MY mail down? NOTE: I am not asking how to remove all the messages, I know how to do that. :)

C.) Is there some place that I have not looked that I should be looking? Is this perhaps not even a courier issue but perhaps something in my system? (I don't think so but it does not hurt to consider it.)

I am running an LFS system with the 2.4.25 kernel.

Again I apologize for the continued whining and posting, but this is very frustrating to me and I would very much like to make it stop, so any help whatsoever, even if you think it is obscure, would be greatly appreciated.

Thanks in advance,