From: David vasil <vasil@cs.utk.edu>
To: gentoo-security@lists.gentoo.org
Subject: Re: Fwd: Re: Fwd: Re: [gentoo-security] postfix and SASL
Date: Wed, 05 Oct 2005 10:59:28 -0400 [thread overview]
Message-ID: <4343EA50.7030402@cs.utk.edu> (raw)
In-Reply-To: <001901c5c9bb$373e1510$1301a8c0@oxpub.com>
Joe Strusz wrote:
> Well dave, actually yes. I have read every Artcile on the wiki remotely
> close to SASL, even the ones using mysql for authentication/databasing
> etc... Ive read the ENTIRE postfix handbook, just for giggles, and Ive
> gone over any thread on the forum remotely related to this issue in the
> past 12 months...
>
>
> So...
>
> With that said, what would be the approprate mailing list to debug this
> problem DAVE?
I would suggest gentoo-users. Since this is not a security related
question with regard to gentoo, the gentoo-security list is obviously
not the proper place to post a topic like this.
-dave
--
gentoo-security@gentoo.org mailing list
next prev parent reply other threads:[~2005-10-05 15:05 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-10-05 14:05 Fwd: Re: Fwd: Re: [gentoo-security] postfix and SASL Joe Strusz
2005-10-05 14:40 ` David vasil
2005-10-05 14:43 ` Joe Strusz
2005-10-05 14:59 ` David vasil [this message]
2005-10-05 15:04 ` Joe Strusz
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=4343EA50.7030402@cs.utk.edu \
--to=vasil@cs.utk.edu \
--cc=gentoo-security@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