luda posch wrote:
It seems my question was misunderstood again, let me explain in as much
detail as I can.
Your subject appears to be an imperfect match to the need you describe.
What you are asking for in message body is a means to discard bounces
*received*. The Subject covers bounces you would *generate*, hence the
'errors_to' suggestion.
But it appears you need both, s.b.
My server, is a relay server, it delivers mail received from other servers I
control and delivers them remotely to wherever the mail should need to go,
like gmail aol yahoo etc.. Now if my relay server receives an incoming
email for "[email protected]" and attempts to deliver it to gmail, gmail
will bounce the email back. Now my server tries to deliver this bounce
notification to the original sender, however the "original sender" may or
may not be a real email address. When ever one of these non-existent
senders tries using my server to deliver to a non-existent email account at
gmail or yahoo, my server tries to send the bounce notification to the
non-existent sender. The bounce notification itself in turn soft bounces,
which sends the bounce notification to the queue. Sometimes ALOT of these
useless bounce notifications accumulate and my queue runners waste a lot of
time trying over and over again to send them despite the fact that there is
real email that is queued and needs to be delivered.
I do not want to continue wasting my resources trying to send bounce
notifications to non-existent addresses. I do not even want to waste my
resources sending bounce notifications to real addresses--since in theory
there should not be any "human" users of this server for which such a
notification may be useful.
I am currently logging bounces to a database, so there is absolutely no use
for my server to try to send a bounce notifications. As a matter of fact,
there is very good reason for my server to never send a bounce notification.
This to me doesn't sound like it should be complicated, in all likelihood
there is a configuration setting that needs to be set to true that can
accomplish this, but I have not found such a setting yet, and I have looked
for some time.
Does anybody know what I need to do, or have any ideas that I can try?
Thank you!
The odd DSN now and again will come back. But relay or otherwise, nothing on
your input side should be generating traffic that gives rise to either large
percentages or large absolute numbers of undeliverables *as 'repeaters'*.
Mailing Lists are the most common scenario where these DO arise, and MLM's
*need* to see DSN's to automagically clean their lists.
IF MLM's are NOT in your scenario, one does wonder WTH you are supporting that
gets an invalid address even ONCE ,let alone repetitively (over quota already
discussed...)
But if you must ....
Look for...
Return-path: <>
...and route according to your needs.
A bit more 'intelligence' than just the '<>' is recommended.
HTH,
Bill
--
## List details at http://lists.exim.org/mailman/listinfo/exim-users
## Exim details at http://www.exim.org/
## Please use the Wiki with this list - http://wiki.exim.org/
