From: "Kevin O'Gorman" <kogorman@gmail.com>
To: gentoo-user@lists.gentoo.org
Subject: [gentoo-user] Is my postfix being used as a relay?
Date: Thu, 16 Mar 2006 11:12:28 -0800 [thread overview]
Message-ID: <9acccfe50603161112w58714973p5984984fafefb47a@mail.gmail.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 410 bytes --]
I get a lot of bounce messages from Postfix relating to emails
that are not actually from me, and the mail q shows lots of
stuff I don't recognize.
I'd like to know how to interpret this, and if it is called-for,
to secure this daemon a bit more. Can somebody point
me in the right direction? I'll RTFM if it's not *too* big,
if I know the appropriate FM to R.
++ kevin
--
Kevin O'Gorman, PhD
[-- Attachment #2: Type: text/html, Size: 474 bytes --]
next reply other threads:[~2006-03-16 19:22 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-03-16 19:12 Kevin O'Gorman [this message]
2006-03-16 19:35 ` [gentoo-user] Is my postfix being used as a relay? Gerhard Hoogterp
2006-03-17 17:36 ` Kevin O'Gorman
2006-03-16 19:52 ` JimD
2006-03-16 23:30 ` Iain Buchanan
2006-03-17 17:15 ` Kevin O'Gorman
2006-03-17 17:24 ` John Jolet
2006-03-17 17:41 ` Kevin O'Gorman
2006-03-17 18:11 ` Thomas T. Veldhouse
2006-03-20 2:38 ` Nick Rout
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=9acccfe50603161112w58714973p5984984fafefb47a@mail.gmail.com \
--to=kogorman@gmail.com \
--cc=gentoo-user@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