-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
On 12 Oct 2000, at 14:58, Mauro Tablo' wrote:
> My goal is to block spamming through my host, allowing relay for my
> customers. Is there a way for doing that, without installing ucspi
> (and setting relayclients in tcp.smtp file)?
Yes. Hand your clients X.509 certificates and require the certificate
to establish SMTP connection.
Jokes aside: Your question sounds like you don't want to spend
any effort. In that case, the reply is a sound NO - you don't get that
for free.
When you decide to invest some effort, please ask yourself a
question: How do you tell your client from a spammer? Is it that:
* your client has IP address of some form?
* your client knows some username and password? (like for his
POP account?)
* your client knows some secret port number?
* your client has a certain X.509 certificate?
* your client has a certain PGP key?
* your client has local account?
After you answer these questions, we'll tell you which mechanism
can be employed to allow only authorized relay.
You might want to start from RFC2505 which explains quite a bit
about (un)authorized relaying.
-----BEGIN PGP SIGNATURE-----
Version: PGP 6.5.2 -- QDPGP 2.61a
Comment: http://community.wow.net/grt/qdpgp.html
iQA/AwUBOeWpV1MwP8g7qbw/EQJ46wCfS9CJTTQ5nzv2szRirGgBdxz+tXQAoNZm
2mYNzT2JaqpoZloxJ3islUR0
=f25f
-----END PGP SIGNATURE-----
--
Petr Novotny, ANTEK CS
[EMAIL PROTECTED]
http://www.antek.cz
PGP key ID: 0x3BA9BC3F
-- Don't you know there ain't no devil there's just God when he's drunk.
[Tom Waits]
