From: "Vinícius Ferrão" <viniciusferrao@cc.if.ufrj.br>
To: gentoo-server@lists.gentoo.org
Subject: [gentoo-server] Postfix Double Bounce Handling
Date: Mon, 14 May 2012 13:38:52 -0300 [thread overview]
Message-ID: <CAKTiq_omQyvZ1EdFGKSkbEhoU=c0Ex9CF9xrZ=eZwpFEkR2o2w@mail.gmail.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 430 bytes --]
Hello,
I'm running a postfix mail filtering gateway in a hardened gentoo box and I
really don't know what to do with double-bounced messages.
Since we have a lot of spam bots attacking our infrastructure, the double
bounce messages cannot be ignored and mail mail queue is growing with
undeliverable double bounce messages.
Any thoughts on what should be done to handle this?
Thanks in advance,
Vinícius Ferrão
[-- Attachment #2: Type: text/html, Size: 548 bytes --]
next reply other threads:[~2012-05-14 16:39 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-05-14 16:38 Vinícius Ferrão [this message]
2012-05-14 17:22 ` [gentoo-server] Postfix Double Bounce Handling Michael Orlitzky
2012-05-14 18:48 ` Vinícius Ferrão
2012-05-14 19:25 ` Michael Orlitzky
2012-05-15 19:02 ` Tanstaafl
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to='CAKTiq_omQyvZ1EdFGKSkbEhoU=c0Ex9CF9xrZ=eZwpFEkR2o2w@mail.gmail.com' \
--to=viniciusferrao@cc.if.ufrj.br \
--cc=gentoo-server@lists.gentoo.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox