Hello Erwin,

On Thursday, April 1, 2004 at 3:23:49 PM you wrote (at least in part):

[RELAYCLIENT set to something different than ""]
> 2. Relayclients identfied by POP-b4-SMTP carrying RELAYCLIENT="P4S" (sample).
> Ok. qmail-smtpd will append this string to the Recipient address ([EMAIL PROTECTED]
=>> [EMAIL PROTECTED]). However, using ie. ksh capabilities you can do
> ${RECIPIENT%P4S} thus retaining the old RECIPIENT variable.

Why would you want to fork more processes and waste more ressources
than necessary when a SMTP-connection is about to be accepted?

> Even if RELAYCLIENT is set, (the Auth patched) qmail-smtpd *WILL* ask for
> Authentication. 

No. It'll /OFFER/ SMTP-ATUH, for those that want to set up their mail
client to always use SMTP-AUTH instead of relying on a formerly done

You absolutely don't have to make ANY use of this offer. If your IP is
set to RELAYCLIENT="" by a former POP3 (or whatever) connection, or
even is set statically to be allowed to relay, the MUA can simply go
on in SMTP dialog:


The MUA can and should ignore the initial (after EHLO) greeting
telling about smtpd's capabilities, if not explicitly set to do

> If I understood correctly, thats *EXACTLY* what should be avoided.

I read this:

,----- [ <mid:[EMAIL PROTECTED]> ]
| Is there any way to set up SMTP-Auth, while still allowing pop-b4-smtp? 
| So far when I've rebuilt the system with SMTP-Auth patching, it will
| ONLY accept SMTP-Auth to allow relaying... :(

as follows:

- I want both method, SMTP-Auth and POP3-b4-SMTP, for allowing a client
  to relay.
- I don't want the system to /require/ SMTP-Auth when POP3-b4-SMTP
  already set RELAYCLIENT=""

But maybe I got it wrong ... Joel?
Best regards
Peter Palmreuther

Can you imagine a world without men??  No crime and lots of happy, fat

Reply via email to