qmail-smtpd-auth
Hi, I've successfully installed the qmail-smtpd-auth-0.30, but I would like to log the username and IP address in /var/qmail/log/smtpd/current. Is it possible?? Currently it only logs the IP address. My /var/qmail/supervise/smtpd/run #!/bin/sh QMAILDUID=`id -u qmaild` NOFILESGID=`id -g qmaild` exec /usr/local/bin/softlimit -m 200 \ /usr/local/bin/tcpserver -v -H -x /etc/tcp.smtp.cdb \ -u "$QMAILDUID" -g "$NOFILESGID" 0 smtp /var/qmail/bin/qmail-smtpd \ /bin/checkpassword /bin/true /bin/cmd5checkpw /bin/true 2>&1 Thanks, Ari
NEW qmail-smtpd-auth patch v. 0.30
Hello. I'm proud to announce a new version of qmail-smtpd-auth patch. We have merged our effors with Eric M. Johnston so now there is again only one qmail-smtpd-auth patch. We have also set up a mailing list, which is available on http://list.elysium.pl/mailman/listinfo/smtpauth . Subscribe there is you want to discuss any qmail-smtpd-auth related matters. Also notice that from now on, i will answer support question ONLY on the maling list. All questions sent to my normal address will be ignored (except when they are f.e. bug fixes and other important things). The patch now uses djb's string library so i supose that it'll be easier to accept for some of you. Changes include: - codebase switch. From now on have merged efforts with Eric M. Johnston <[EMAIL PROTECTED]> so now there are no more 2 separate auth patches but just one. - arguments to qmail-smtpd have changed! See README.auth for further info. - the code is djbized right now - TCPREMOTEINFO is set if sender is properly authenticated. I would also like to invite qmail-ldap, vpopmail , vmailmgr and other qmail addons/modification to share their success stories with us (on the mailing list preferably) so other people can learn from them. Also if you have a modified version of this patch to suit a specific need but does not fit into the main distrio, then i will gladly host it on my site. Finally the URL for qmail-smtpd-auth homepage is: http://members.elysium.pl/brush/qmail-smtpd-auth/ Kris
qmail-smtpd-auth
Hi, I've installed the patch of qmail-smtpd-auth-0.26 and it not working. I'm running smtp with tcpserver: #!/bin/sh QMAILDUID=`id -u qmaild` NOFILESGID=`id -g qmaild` MAXSMTPD=20 exec /usr/local/bin/softlimit -m 200 \ /usr/local/bin/tcpserver -v -p -x /etc/tcp.smtp.cdb -c "$MAXSMTPD" \ -u "$QMAILDUID" -g "$NOFILESGID" 0 smtp /var/qmail/bin/qmail-smtpd \ /bin/checkpassword /bin/true /bin/cmd5checkpw /bin/true 2>&1 How can I test it like checkpassword and POP: # /var/qmail/bin/qmail-popup blah /bin/checkpassword pwd +OK <...@blah> user Frodo +OK pass Friend -ERR authorization failed ???
Re: How can I patch qmail-smtpd-auth?
[EMAIL PROTECTED] <[EMAIL PROTECTED]> wrote: > I have get qmail-smtpd-auth-0.26.tar.gz. > "tar xvfz qmail-smtpd-auth-0.26.tar.gz" > Then I get qmail-smtpd.patch > Now I do not know how to use is. > Please tell me how to do it. Thanks. Read `man patch` (and probably `man diff`). If you're not familiar with how to apply patches to software source code, you may not want to use modifications which change qmail's behaviour. It may make it more difficult to diagnose problems from the existing documentation. Charles -- --- Charles Cazabon<[EMAIL PROTECTED]> GPL'ed software available at: http://www.qcc.sk.ca/~charlesc/software/ Any opinions expressed are just that -- my opinions. ---
How can I patch qmail-smtpd-auth?
I have get qmail-smtpd-auth-0.26.tar.gz. "tar xvfz qmail-smtpd-auth-0.26.tar.gz" Then I get qmail-smtpd.patch Now I do not know how to use is. Please tell me how to do it. Thanks. -- »¶ÓʹÓà 21CN µç×ÓÓʼþϵͳ http://www.21cn.com Thank you for using 21cn.com Email system
Re: qmail-smtpd-auth
Thus spake Henning Brauer ([EMAIL PROTECTED]): > > This is completely false. smtp-poplock doesn't require patching the > > qmail source. You can find a link to it on www.qmail.org. > This is a smtp after pop solution, no SMTP AUTH. SMTP AUTH is an SMTP > protocol extension allowing clients to authentificate via username+password > during the smtp session, not before through pop as with smtp poplock. As > everybody could easily see this requires always patching qmail. Why? You could install a smtpd wrapper that answers the smtp auth stuff and updates the pop tcpserver database on the fly. Felix
Re: qmail-smtpd-auth
On Thu, Jan 11, 2001 at 06:09:48PM -0500, Vince Vielhaber wrote: > On Thu, 11 Jan 2001, Kris Kelley wrote: > > > You're not going to find any ESMTP AUTH solutions for qmail that don't > > involve patching qmail's source. > > This is completely false. smtp-poplock doesn't require patching the > qmail source. You can find a link to it on www.qmail.org. This is a smtp after pop solution, no SMTP AUTH. SMTP AUTH is an SMTP protocol extension allowing clients to authentificate via username+password during the smtp session, not before through pop as with smtp poplock. As everybody could easily see this requires always patching qmail. -- Henning Brauer | BS Web Services Hostmaster BSWS| Roedingsmarkt 14 [EMAIL PROTECTED] | 20459 Hamburg http://www.bsws.de | Germany
Re: qmail-smtpd-auth
On Fri, Jan 12, 2001 at 11:44:09AM +1300, Bjorn Nilsen wrote: > smtp-poplock is just another implementation of "pop before smtp" which I > already have with vpopmail. I will explain in more detail why this solution > doesn't work for me. Many mail clients the default or only action is to send > mail before checking mail. So what happens is the mail client happily sends > all mail in the outbox then checks there mail via pop. This works fine until > all that mail just sent gets bounced right back from the smtp server because > the mail client had not authenticated with pop first allowing them relay > access. Then I end up with a very annoyed and confused user (is there any > other kind?). So the best solution I can see for this is smtp auth. Not all clients out are supporting smtp-auth (unfortunately). If your clients are employees, this is fixable, if they are customers, i don't see an alternative to smtp after pop - smtp auth additionally is a good idea. > Also another question with qmail-smtp-auth if a host is already set up as a > relay client do they need to still provide a login password to get relay > access? no. -- Henning Brauer | BS Web Services Hostmaster BSWS| Roedingsmarkt 14 [EMAIL PROTECTED] | 20459 Hamburg http://www.bsws.de | Germany
Re: qmail-smtpd-auth
On Thu, 11 Jan 2001, Kris Kelley wrote: > Vince Vielhaber wrote: > > > If I'm wrong, my apologies. I'm not familiar with smtp-poplock, and I > was > > > basing what I said on Bjorn Nilsen's last reply, which said, > "smtp-poplock > > > is just another implementation of 'pop before smtp.'" > > > > It does the same thing - allow any client to send mail provided they > > successfully authenticated with the POP3 server first - but that's > > the only way they're the same. > > No, ESMTP AUTH is different from pop-before-smtp. With ESMTP AUTH, clients > authenticate themselves via the SMTP server for each SMTP session. The POP > server is not involved at all. > > The way the qmai-smtpd-auth patch works, if a client connects to the SMTP > server and successfully authenticates itself, the patched qmail-smtpd > process sets RELAYCLIENT for that session, thereby allowing relaying. When > the SMTP session is closed, the relaying permissions, along with the rest of > that process, disappear. Ok it is different, but the same drawback remains... You have to patch your qmail installation. I got stuck running a 1.02 for awhile after 1.03 came out because of patches. That was the last version I patched. Vince. -- == Vince Vielhaber -- KA8CSHemail: [EMAIL PROTECTED]http://www.pop4.net 128K ISDN from $22.00/mo - 56K Dialup from $16.00/mo at Pop4 Networking Online Campground Directoryhttp://www.camping-usa.com Online Giftshop Superstorehttp://www.cloudninegifts.com ==
Re: qmail-smtpd-auth
Vince Vielhaber wrote: > > If I'm wrong, my apologies. I'm not familiar with smtp-poplock, and I was > > basing what I said on Bjorn Nilsen's last reply, which said, "smtp-poplock > > is just another implementation of 'pop before smtp.'" > > It does the same thing - allow any client to send mail provided they > successfully authenticated with the POP3 server first - but that's > the only way they're the same. No, ESMTP AUTH is different from pop-before-smtp. With ESMTP AUTH, clients authenticate themselves via the SMTP server for each SMTP session. The POP server is not involved at all. The way the qmai-smtpd-auth patch works, if a client connects to the SMTP server and successfully authenticates itself, the patched qmail-smtpd process sets RELAYCLIENT for that session, thereby allowing relaying. When the SMTP session is closed, the relaying permissions, along with the rest of that process, disappear. ---Kris Kelley
Re: qmail-smtpd-auth
On Thu, 11 Jan 2001, Kris Kelley wrote: > Vince Vielhaber wrote: > > > > You're not going to find any ESMTP AUTH solutions for qmail that don't > > > involve patching qmail's source. > > > > This is completely false. smtp-poplock doesn't require patching the > > qmail source. You can find a link to it on www.qmail.org. > > If I'm wrong, my apologies. I'm not familiar with smtp-poplock, and I was > basing what I said on Bjorn Nilsen's last reply, which said, "smtp-poplock > is just another implementation of 'pop before smtp.'" It does the same thing - allow any client to send mail provided they successfully authenticated with the POP3 server first - but that's the only way they're the same. smtp-poplock reads a log (or pipe, it's configurable) and updates its database with the IP. When someone attempts to connect to qmail-smtpd it checks the database and sets RELAYCLIENT before launching it, just like tcpserver would if the IP was in the cdb file it looks at. It works off of the same concept as qmail - modular and simple. Vince. -- == Vince Vielhaber -- KA8CSHemail: [EMAIL PROTECTED]http://www.pop4.net 128K ISDN from $22.00/mo - 56K Dialup from $16.00/mo at Pop4 Networking Online Campground Directoryhttp://www.camping-usa.com Online Giftshop Superstorehttp://www.cloudninegifts.com ==
Re: qmail-smtpd-auth
On Fri, 12 Jan 2001, Bjorn Nilsen wrote: > on 12/1/01 12:15 AM, Vince Vielhaber wrote: > > > On Thu, 11 Jan 2001, Bjorn Nilsen wrote: > > > >> I'm considering patching qmail with the qmail-smtpd-auth patch. The reason > >> is that the roaming user pop before smtp function in vpopmail doesn't work > >> very well with my clients mail clients. In particular if Outlook has mail in > >> the Outbox it will always send that first no matter what. It does not have > >> the option to just check pop. > >> I am rather nervous about patching rock solid qmail with a 3rd party patch. > >> So I'm interested in what experience people have had with it and if it works > >> well. Also if it works well with vpopmail which I also depend on. > > > > David Harris wrote smtp-poplock which doesn't require patching qmail. > > You should be able to find it on www.qmail.org. > > > > Vince. > > smtp-poplock is just another implementation of "pop before smtp" which I > already have with vpopmail. I will explain in more detail why this solution > doesn't work for me. Many mail clients the default or only action is to send > mail before checking mail. So what happens is the mail client happily sends > all mail in the outbox then checks there mail via pop. This works fine until > all that mail just sent gets bounced right back from the smtp server because > the mail client had not authenticated with pop first allowing them relay > access. Then I end up with a very annoyed and confused user (is there any > other kind?). So the best solution I can see for this is smtp auth. I've been using it for over a year and the only problem any of my customers have had was when they didn't understand they had to check mail first. Noone's ever complained about losing outgoing mail because of it. The SMTP transaction should fail before it completes so the mail should remain in the user's queue. I chose this version over the other one(s) BECAUSE I didn't have to patch qmail. > Also another question with qmail-smtp-auth if a host is already set up as a > relay client do they need to still provide a login password to get relay > access? Nope, they're renewed for a configurable time period (I have it set for 10 minutes) each time they check mail. As long as they're sending from the IP that checked mail RELAYCLIENT is set. Vince. -- == Vince Vielhaber -- KA8CSHemail: [EMAIL PROTECTED]http://www.pop4.net 128K ISDN from $22.00/mo - 56K Dialup from $16.00/mo at Pop4 Networking Online Campground Directoryhttp://www.camping-usa.com Online Giftshop Superstorehttp://www.cloudninegifts.com ==
Re: qmail-smtpd-auth
Vince Vielhaber wrote: > > You're not going to find any ESMTP AUTH solutions for qmail that don't > > involve patching qmail's source. > > This is completely false. smtp-poplock doesn't require patching the > qmail source. You can find a link to it on www.qmail.org. If I'm wrong, my apologies. I'm not familiar with smtp-poplock, and I was basing what I said on Bjorn Nilsen's last reply, which said, "smtp-poplock is just another implementation of 'pop before smtp.'" ---Kris Kelley
Re: qmail-smtpd-auth
Vince Vielhaber wrote: > > You're not going to find any ESMTP AUTH solutions for qmail that don't > > involve patching qmail's source. > > This is completely false. smtp-poplock doesn't require patching the > qmail source. You can find a link to it on www.qmail.org. If I'm wrong, my apologies. I'm not familiar with smtp-poplock, and I was basing what I said on Bjorn Nilsen's last reply, which said, "smtp-poplock is just another implementation of 'pop before smtp.'" ---Kris Kelley
Re: qmail-smtpd-auth
On Thu, 11 Jan 2001, Kris Kelley wrote: > You're not going to find any ESMTP AUTH solutions for qmail that don't > involve patching qmail's source. This is completely false. smtp-poplock doesn't require patching the qmail source. You can find a link to it on www.qmail.org. Vince. -- == Vince Vielhaber -- KA8CSHemail: [EMAIL PROTECTED]http://www.pop4.net 128K ISDN from $22.00/mo - 56K Dialup from $16.00/mo at Pop4 Networking Online Campground Directoryhttp://www.camping-usa.com Online Giftshop Superstorehttp://www.cloudninegifts.com ==
Re: qmail-smtpd-auth
Bjorn Nilsen wrote: > I'm considering patching qmail with the qmail-smtpd-auth patch... > I am rather nervous about patching rock solid qmail with a 3rd party patch... You're not going to find any ESMTP AUTH solutions for qmail that don't involve patching qmail's source. I use Krzysztof Dabrowski's patch, and it works like a charm. There was no problem applying the patch, no problem compiling the patched source, and it has worked as advertised. > Also another question with qmail-smtp-auth if a host is already set up as a > relay client do they need to still provide a login password to get relay > access? No. If the remote server doesn't try to authenticate itself, the RELAYCLIENT environment variable is not changed. That means that if the variable was already set by tcpserver, it will remain set. ---Kris
Re: qmail-smtpd-auth
on 12/1/01 12:15 AM, Vince Vielhaber wrote: > On Thu, 11 Jan 2001, Bjorn Nilsen wrote: > >> I'm considering patching qmail with the qmail-smtpd-auth patch. The reason >> is that the roaming user pop before smtp function in vpopmail doesn't work >> very well with my clients mail clients. In particular if Outlook has mail in >> the Outbox it will always send that first no matter what. It does not have >> the option to just check pop. >> I am rather nervous about patching rock solid qmail with a 3rd party patch. >> So I'm interested in what experience people have had with it and if it works >> well. Also if it works well with vpopmail which I also depend on. > > David Harris wrote smtp-poplock which doesn't require patching qmail. > You should be able to find it on www.qmail.org. > > Vince. smtp-poplock is just another implementation of "pop before smtp" which I already have with vpopmail. I will explain in more detail why this solution doesn't work for me. Many mail clients the default or only action is to send mail before checking mail. So what happens is the mail client happily sends all mail in the outbox then checks there mail via pop. This works fine until all that mail just sent gets bounced right back from the smtp server because the mail client had not authenticated with pop first allowing them relay access. Then I end up with a very annoyed and confused user (is there any other kind?). So the best solution I can see for this is smtp auth. Also another question with qmail-smtp-auth if a host is already set up as a relay client do they need to still provide a login password to get relay access? cheers, Bjorn -- Bjorn Nilsen <[EMAIL PROTECTED]> Manux Solutions Ltd Ph +64 3 343 2031 Fax +64 3 343 3064 Level 1, 39 Leslie Hills Drive, Riccarton PO Box 3074 Christchurch
Re: qmail-smtpd-auth
On Thu, 11 Jan 2001, Bjorn Nilsen wrote: > I'm considering patching qmail with the qmail-smtpd-auth patch. The reason > is that the roaming user pop before smtp function in vpopmail doesn't work > very well with my clients mail clients. In particular if Outlook has mail in > the Outbox it will always send that first no matter what. It does not have > the option to just check pop. > I am rather nervous about patching rock solid qmail with a 3rd party patch. > So I'm interested in what experience people have had with it and if it works > well. Also if it works well with vpopmail which I also depend on. David Harris wrote smtp-poplock which doesn't require patching qmail. You should be able to find it on www.qmail.org. Vince. -- == Vince Vielhaber -- KA8CSHemail: [EMAIL PROTECTED]http://www.pop4.net 128K ISDN from $22.00/mo - 56K Dialup from $16.00/mo at Pop4 Networking Online Campground Directoryhttp://www.camping-usa.com Online Giftshop Superstorehttp://www.cloudninegifts.com ==
qmail-smtpd-auth
I'm considering patching qmail with the qmail-smtpd-auth patch. The reason is that the roaming user pop before smtp function in vpopmail doesn't work very well with my clients mail clients. In particular if Outlook has mail in the Outbox it will always send that first no matter what. It does not have the option to just check pop. I am rather nervous about patching rock solid qmail with a 3rd party patch. So I'm interested in what experience people have had with it and if it works well. Also if it works well with vpopmail which I also depend on. cheers, Bjorn -- Bjorn Nilsen <[EMAIL PROTECTED]> Manux Solutions Ltd Ph +64 3 343 2031 Fax +64 3 343 3064 Level 1, 39 Leslie Hills Drive, Riccarton PO Box 3074 Christchurch
Re: qmail-smtpd-auth-0.26 - security fix
At 18:41 2000-10-17 +0200, Olivier M. wrote: >On Tue, Oct 17, 2000 at 11:44:39AM +0200, Krzysztof Dabrowski wrote: > > Hello, > > A new version of qmail-smtpd-auth patch has been released. > > http://members.elysium.pl/brush/qmail-smtpd-auth/ > >looks nice. Do you know if it works with qmail+vmailmgr ? >(your doc only talk about vpopmail) it should work with anything that is checkpassword compatible. Kris
Re: qmail-smtpd-auth-0.26 - security fix
On Tue, Oct 17, 2000 at 11:44:39AM +0200, Krzysztof Dabrowski wrote: > Hello, > A new version of qmail-smtpd-auth patch has been released. > http://members.elysium.pl/brush/qmail-smtpd-auth/ looks nice. Do you know if it works with qmail+vmailmgr ? (your doc only talk about vpopmail) Olivier -- _ Olivier Mueller - [EMAIL PROTECTED] - PGPkeyID: 0E84D2EA - Switzerland
qmail-smtpd-auth-0.26 - security fix
Hello, A new version of qmail-smtpd-auth patch has been released. Changes: - security fix - if your checkpassword crashed, attacker would get the relay permission. Now it should work. You can download it from the usual place: http://members.elysium.pl/brush/qmail-smtpd-auth/ NOTICE: this problam also affects users of Mrs.Brisby patch, so you should consider upgrading (my patch has more features, is actively maintained and is 100% backwards compatible). Kris
Re: qmail-smtpd-auth crashes!!!
"Manuel Gisbert" <[EMAIL PROTECTED]> wrote: >Now when I connect to the server using outlook or outlook express (both are >mentioned on the above website as working) qmail-smtpd exits with "421 out >of memory (#4.3.0)". > > >#!/bin/sh >QMAILDUID=`id -u qmaild` >NOFILESGID=`id -g vpopmail` >exec /usr/local/bin/softlimit -m 400 /usr/local/bin/tcpserver -H -R -l >mydomain -u $QMAILDUID -g $NOFILESGID 0 smtp /usr/local/bin/rblsmtpd >/var/qmail/bin/qmail-smtpd /usr/vpopmail/bin/vchkpw /bin/true > The "400" in the softlimit command is probably the culprit. Try increasing it or removing "/usr/local/bin/softlimit -m 400" temporarily to confirm that that's the problem. -Dave
qmail-smtpd-auth crashes!!!
Hi there,
I want to enable authenticated smtp between server and mua.
Therefor I installed either mrs.brisbys qmail-smtp patch or
the advanced version from http://members.elysium.pl/brush/qmail-smtpd-auth/
As I use vpopmail I applied all modifications mentioned in
http://members.elysium.pl/brush/qmail-smtpd-auth/faq.html
Now when I connect to the server using outlook or outlook express (both are
mentioned on the above website as working) qmail-smtpd exits with "421 out
of memory (#4.3.0)".
I attached the relevant code so that someone might tell me what the problem
is..
//This is mrs. brisbys version, but its the same problem with the other one
too
switch ((pid=fork())) {
case -1: die_nomem();
case 0: close(fds[1]);
fd_copy(3,fds[0]);
execvp(smtpauth_argv[1], smtpauth_argv+1);
die_nomem();
/*Thats the exception were qmail-smtpd dies. I'm not quite sure why they
inserted die_nomem() here anyway, but it seems as if there's a problem
invoking the external
programm which validates user/pass */
};
close(fds[0]);
write(fds[1], smtpauthlogin, str_len(smtpauthlogin)+1);
write(fds[1], smtpauthpass, str_len(smtpauthpass)+1);
close(fds[1]);
wait_pid(&st, pid);
if (wait_exitcode(st) == 0) {
out("235 go ahead\r\n");
flush();
relayclient="";
return;
}
sleep(2);
out("535 auth failure\r\n"); flush(); _exit(0);
#!/bin/sh
QMAILDUID=`id -u qmaild`
NOFILESGID=`id -g vpopmail`
exec /usr/local/bin/softlimit -m 400 /usr/local/bin/tcpserver -H -R -l
mydomain -u $QMAILDUID -g $NOFILESGID 0 smtp /usr/local/bin/rblsmtpd
/var/qmail/bin/qmail-smtpd /usr/vpopmail/bin/vchkpw /bin/true
Thanx in advance
Manuel, the confused one
Re: qmail-smtpd-auth + mysql...
At 08:22 2000-06-19 +0200, Goran Blazic wrote: >Has anyone tried patching qmail with qmail-smtpd-auth and Iain Patterson's >MySQL+QMAIL patch? >I plan on doing this and would like to know in advance whether I can expect >trouble... :-) > >Thanks in advance, Goran Send me the resulting patch or suggestion. I can include it on my page. Brush
qmail-smtpd-auth + mysql...
Has anyone tried patching qmail with qmail-smtpd-auth and Iain Patterson's MySQL+QMAIL patch? I plan on doing this and would like to know in advance whether I can expect trouble... :-) Thanks in advance, Goran
qmail-smtpd-auth 0.24
Hello.. New version of qmail-stmpd-auth patch is available at: http://members.elysium.pl/brush/qmail-smtpd-auth/ It fixes a nasty problem with cram-md5 auth. It worked perfectly for me for 2 months and i've found the bug only recently. Brush
qmail-smtpd-auth patch seems to have no effect and I can no longer receive mail.
I have installed the smtpd-auth-patch to my qmail server, Now I have two problems. One is the server does not require me to log in to send mail, and seems to be sending mail(as far as I can tell). The MAJOR problem I am having is that it does not seem to receive any mail. I tried to send myself some e-mail from my hotmail account, and I never receive it, or get a bounce message back from Hotmail. Where is my mail going? Has anyone seen this problem? I am calling qmail-smtpd with the following script: #! /bin/sh QMAILDUID='id -u qmaild' NOFILESGID='id -g qmaild' exec /usr/local/bin/softlimit -m 400 \ /usr/local/bin/tcpserver -g $NOFILESGID 0 smtp /var/qmail/bin/qmail-smtpd \ /bin/checkpassword /bin/true 2>&1 Any help would be appreciated. Steve P
Re: qmail-smtpd-auth
At 10:33 2000-03-21 -0600, you wrote: >I'm having trouble getting this patch to work with $M outlook express or the >2000 client. When I turn on smtp auth on in these clients - it just prompts >me for a user name and password over and over again - same thing with >Netscape. The problem is that both Outlook Express and Netscape does not use the CRAM-MD5 authentication. In this case they are using your normal, checkpassword (the first one, you are providing to the qmail-smtpd) and if it works with qmail-pop3d then it should also work here. Double check it... Kris
qmail-smtpd-auth
I'm having trouble getting this patch to work with $M outlook express or the 2000 client. When I turn on smtp auth on in these clients - it just prompts me for a user name and password over and over again - same thing with Netscape. smtp startup file [bucknum@mail1 qmail-smtpd]$ less run #!/bin/sh QMAILDUID=`id -u qmaild` NOFILESGID=`id -g qmaild` exec /usr/local/bin/softlimit -m 200 \ /usr/local/bin/tcpserver -v -p -x /etc/tcp.smtp.cdb \ -u $QMAILDUID -g $NOFILESGID 0 smtp /var/qmail/bin/qmail-smtpd /bin/checkpassword /bin/true /bin/cmd5checkpw /bin/true run (END) tcp.smtp file contents [bucknum@mail1 /etc]$ less tcp.smtp 127.:allow,RELAYCLIENT="" 10.1.1.:allow,RELAYCLIENT="" tcp.smtp (END) Contents of my poppasswd file [bucknum@mail1 /etc]# less poppasswd brush:dupa98 poppasswd (END) I put this back to as it was shipped as part of testing - I've changed this to my username and password and get the same results What I get when I log in on SMTP 220 lcr-m.dhs.org ESMTP ehlo 250-lcr-m.dhs.org 250-AUTH=LOGIN CRAM-MD5 PLAIN 250-AUTH LOGIN CRAM-MD5 PLAIN 250-PIPELINING 250 8BITMIME I put the old binary back log in and this is what I get 220 lcr-m.dhs.org ESMTP ehlo 250-lcr-m.dhs.org 250-PIPELINING 250 8BITMIME What am I screwing up here??
