> 
> > Hi,
> > 
> >     Thanks for the reply. In as much as I'd like to help the community,
> > I'm under a set of constraints. Starting a whole other server to start
> > doing
> > this isn't something that fits under those constraints. It looks like
> > I'll probably just end up having to /dev/null them as I have been.
> > 
> >             Tuc
> 
> Tuc
> 
> Didn't it come out that you were accepting emails to any email address
> whether it is a valid email address or not?
> 
> If so, that is where to start...
> 
> do not accept those emails... reject them properly.
> 
>  - rh
>
        There are "considerations" in doing this. Right now,
all my systems are set up running sendmail, and all with the
config of :

        define(`confCOPY_ERRORS_TO',`Postmaster')

        As such, true to its name, anytime there is an error, the
postmaster gets a copy. 120K copies of 

The original message was received at Sun, 9 Mar 2008 15:12:41 -0400 (EDT)
from pD9E3AE30.dip.t-dialin.net [217.227.174.48]

   ----- The following addresses had permanent fatal errors -----
<[EMAIL PROTECTED]>
    (reason: 550 5.0.0 <[EMAIL PROTECTED]>... No such user here)

   ----- Transcript of session follows -----
... while talking to smtp.example.com.:
>>> DATA
<<< 550 5.0.0 <[EMAIL PROTECTED]>... No such user here
550 5.1.1 <[EMAIL PROTECTED]>... User unknown
<<< 503 5.0.0 Need RCPT (recipient)

   ----- Message header follows -----

        isn't acceptable. Yes, I could take out the COPY_ERRORS_TO,
but we also run alot of things that are piped to programs, and we
usually don't see the errors unless that is set. If there is some way
to have my errors copied to me, but "User unknown" not, then I'll
implement it. My way of preventing it from happening, but still seeing
my errors, was to /dev/null addresses that don't exist. I could have
the COPY_ERRORS_TO sent to a special user that uses procmail to weed
them out, but then it defeats my attempts to reduce disk space wear
and tear, CPU, etc.

        Even if I did that, though, the next thing I run into is
MX's. The MX blindly accepts the mail. If the destination server
rejects it, then usually the original sender is forged or invalid,
etc. That then causes a mail spool backup on the MX host until it
then errors out after 5 days of inability to make its delivery. 

        I'd love to take advantage of some functionality ZoneEdit 
(My DNS provider) gives and letting them scan and forward the email. 
However, with the amount of emails and databits it is, I think the
cost would be more than I care to pay given its a "favor" account.
(Also why setting up another server doesn't make sense.)

                Tuc

Reply via email to