hello Greg,

thanks for your help. I wanted to ask do you know why these emails are
coming
in to the server? This is suppose to be a mailout server.

regards
Roger

Greg Hackney wrote:
> rogv24@yahoo.com wrote:
> > I am recieving several of these log errors when I do a mailq.
> > How can I prevent that from coming into the queue?
> >
> > 2F38DEC1D2 3459 Mon Sep 18 03:33:53 MAILER-DAEMON
> > (connect to brmail1.brassring.com[66.77.22.180]: Connection
> > refused)
> > cbrown@1-jobs.com
> >
> > 20A3CEC0DF 834 Tue Sep 19 12:54:54 email@test.com
> > (connect to test.com[208.48.34.132]: Connection
> > timed out)
> > dfddfdt@test.com
> >
> > Also I am recieving connection refused.
> >
> > thanks
>
> The MAILER-DAEMON message is probably a bounced email which will likely
> sit in the queue retrying delivery, until it finally times out and
> gets automatically deleted.
>
> In main.cf, you can set
> bounce_queue_lifetime = 0
> and then for _bounced_ messages Postfix will try 1 immediate delivery,
> and then delete the message. The logic is: "Hey, you just sent my system
> a non-deliverable email, and you ought to be able to take it back right now.
> If you won't, it's probably a relayed spam, so I'm deleting it".
>
> Regarding the second message, you'd probably need to take a look at it's headers
> and see how it got onto your system. You can look at it with the command:
> postcat -q 20A3CEC0DF | less
>
> If you decide to delete it: postsuper -d 20A3CEC0DF
>
> It's probably some message that Postfix could have originally blocked if it
> were configured better.
>
> In either case, both messages are sitting in queue, retrying delivery to
> the remote system, using an exponential backoff algorithm (each time it
> fails, it waits longer before retrying).
>
> Eventually the non-bounce will reach "maximal_queue_lifetime", which by default
> is 5 days, but can be adjusted however you want.
>
> --
> Greg