Hi,
I get this error when I try to create chkuser.o
./compile chkuser.c chkuser.h chkuser_settings.h
chkuser.h:43: error: expected ')' before '*' token
chkuser.h:44: error: expected ')' before '*' token
I saw those 2 lines as followed,
line
43 int chkuser_realrcpt (stralloc *sender, stralloc *rc
Hi,
I get this error when I try to create chkuser.o
./compile chkuser.c chkuser.h chkuser_settings.h
chkuser.h:43: error: expected ')' before '*' token
chkuser.h:44: error: expected ')' before '*' token
I saw those 2 lines as followed,
line
43 int chkuser_realrcpt (stralloc *sender, stralloc *rc
On Wednesday 26 Oct 2005 22:51, ISP Lists wrote:
> CHKUSER 2.0.8b on qmail 1.03 and vpopmail 5.4.10.
>
> I LOVE that CHKUSER can single out the unknown recipients and block the
> offending SMTP session - big traffic control helper! However, I've got
> one domain that's really being hit hard by dic
CHKUSER 2.0.8b on qmail 1.03 and vpopmail 5.4.10.
I LOVE that CHKUSER can single out the unknown recipients and block the
offending SMTP session - big traffic control helper! However, I've got
one domain that's really being hit hard by dictionary attacks. Some
attack traffic is a few hits from m
On 2005-09-22, at 1627, Erwin Hoffmann wrote:
At 18:12 22.09.2005 +0100, tonix (Antonio Nati) wrote:
At 17.34 22/09/2005, you wrote:
On Sep 22, 2005, at 1:42 AM, John Simpson wrote:
if you're supporting AUTH, you really should use TLS as well.
otherwise you're allowing your users to send the
On 2005-09-22, at 1234, Tom Collins wrote:
On Sep 22, 2005, at 1:42 AM, John Simpson wrote:
if you're supporting AUTH, you really should use TLS as well.
otherwise you're allowing your users to send their passwords
across the internet in plain text- and all it takes is one spammer
with a pa
On Sep 22, 2005, at 2:10 PM, Erwin Hoffmann wrote:
C'm on. The generation of the "challenge" and the way its used in
qmail is well documented on my web site
http://www.fehcom.de/qmail/smtpauth.html.
Everyone can read that and download the code to do it.
The only free parameters are the timest
> C'm on. The generation of the "challenge" and the way its used in
qmail is
> well documented on my web site
http://www.fehcom.de/qmail/smtpauth.html.
>
> Everyone can read that and download the code to do it.
>
> The only free parameters are the timestamp and the pid of the current
> process.
Hi,
At 15:41 22.09.2005 -0500, you wrote:
> On Sep 22, 2005, at 1:27 PM, Erwin Hoffmann wrote:
> >>> If you use CRAM-MD5 for the AUTH method, it's impossible to sniff
> >>> the cleartext password.
> >
> > I don't bet on this. If you tape the SMTP dialoge, its easy to
encrypt
> > the password.
>
> >A better idea... The most of probably use qmail because there is
> vpopmail.
> >What about rewriting around vpopmail a modern, robust and
customizable
> MTA
> >that does not force us to be acrobats in order to add functionalities
to
> qmail?
>
> Do you have considered how many changes vpopmail
> On Sep 22, 2005, at 1:27 PM, Erwin Hoffmann wrote:
> >>> If you use CRAM-MD5 for the AUTH method, it's impossible to sniff
> >>> the cleartext password.
> >
> > I don't bet on this. If you tape the SMTP dialoge, its easy to
encrypt
> > the password.
>
> I think you're wrong. AUTH PLAIN and AUTH
On Sep 22, 2005, at 1:27 PM, Erwin Hoffmann wrote:
If you use CRAM-MD5 for the AUTH method, it's impossible to sniff
the cleartext password.
I don't bet on this. If you tape the SMTP dialoge, its easy to encrypt
the password.
I think you're wrong. AUTH PLAIN and AUTH LOGIN are just base64
Hi,
At 18:12 22.09.2005 +0100, tonix (Antonio Nati) wrote:
At 17.34 22/09/2005, you wrote:
On Sep 22, 2005, at 1:42 AM, John Simpson wrote:
if you're supporting AUTH, you really should use TLS as well. otherwise
you're allowing your users to send their passwords across the internet
in plain t
At 17.34 22/09/2005, you wrote:
On Sep 22, 2005, at 1:42 AM, John Simpson wrote:
if you're supporting AUTH, you really should use TLS as well.
otherwise you're allowing your users to send their passwords across
the internet in plain text- and all it takes is one spammer with a
packet sniffer t
I would Dave..
Remo
- Original Message -
From: "DAve" <[EMAIL PROTECTED]>
To:
Sent: Thursday, September 22, 2005 10:50
Subject: Re: [vchkpw] chkuser 2.0.8b
> Tom Collins wrote:
>> On Sep 22, 2005, at 1:42 AM, John Simpson wrote:
>>
>>> if you&#
Tom Collins wrote:
On Sep 22, 2005, at 1:42 AM, John Simpson wrote:
if you're supporting AUTH, you really should use TLS as well.
otherwise you're allowing your users to send their passwords across
the internet in plain text- and all it takes is one spammer with a
packet sniffer to use your m
sounds good to me!
Remo
- Original Message -
From: "Tom Collins" <[EMAIL PROTECTED]>
To:
Sent: Thursday, September 22, 2005 10:34
Subject: Re: [vchkpw] chkuser 2.0.8b
> On Sep 22, 2005, at 1:42 AM, John Simpson wrote:
>> if you're supporting AUTH, you
On Sep 22, 2005, at 1:42 AM, John Simpson wrote:
if you're supporting AUTH, you really should use TLS as well.
otherwise you're allowing your users to send their passwords across
the internet in plain text- and all it takes is one spammer with a
packet sniffer to use your machine as a relay.
I have just rebuild it last week and it works fine.
Remo
- Original Message -
From: "tonix (Antonio Nati)" <[EMAIL PROTECTED]>
To:
Sent: Thursday, September 22, 2005 08:07
Subject: Re: [vchkpw] chkuser 2.0.8b
> Aleks,
>
> sorry to repeat what has been alr
Aleks,
sorry to repeat what has been already said, but to make it short use
Shupp's Toaster. There inside chkuser + TLS + auth work fine together
(since years). You'll build it in minuts, and will never regret of
making this step.
Ciao,
Tonino
At 13.18 22/09/2005, you wrote:
Just for the
Just for the fun of it; If I was to, (in this lifetime) get tls/auth
to work with chkuser, what/who's tls and auth code should i use?
Since jms obvious dont need to make he's patches compatible since he's
got the needed stuff for himself in validrcptto, i was hoping someone
knew what works or not.
On 2005-09-21, at 0623, tonix (Antonio Nati) wrote:
Why are you running it with -u $QMAILDUID ?
You should run it as vpopmail, excluding any uidswitching (if you
enabled uidswitching within chkuser_settings.h, comment it).
Cert must be owned by vpopmail as well.
qmail is, and has always
On 2005-09-21, at 0614, Aleks Olsen wrote:
-
Now, it seems the patch didnt like working with auth-jms1.4a.patch
(auth
patch) and/or qmail-1.03-jms1.5.patch (tls patch).
both of which are ANCIENT. my combined patch is up to version 6b now.
and it doesn't use "chkuser"... i doctored up a diffe
ally for qmail-toaster, but not for netqmail.
>
> It seems to me that there's a lot of people supporting
qmail-toaster. Maybe you'd like to try qmail-toaster installation
instead of installing all these patches by hand (this is what I'm
trying to get with qmail-toaster).
le supporting qmail-toaster. Maybe
> you'd like to try qmail-toaster installation instead of installing all these
> patches by hand (this is what I'm trying to get with qmail-toaster).
>
> Regards,
> bnegrao
>- Original Message -
> From: Aleks Olsen
>
with qmail-toaster).
Regards,
bnegrao
- Original Message -
From: Aleks Olsen
To: vchkpw@inter7.com
Sent: Wednesday, September 21, 2005 7:14 AM
Subject: Re: [vchkpw] chkuser 2.0.8b
Hi
I didnt. I missed the trailing */ on that line it seems. Thanks!
-
Now, it seems the patc
--- Original Message -
From:
Aleks Olsen
To: vchkpw@inter7.com
Sent: Wednesday, September 21, 2005 10:38
AM
Subject: Re: [vchkpw] chkuser
2.0.8b
Thanks Bruno, but im not that keen on the TLS support
anymore. Perhaps i'll toast next time :)For now im going to figure out
vchkpw /usr/bin/true 2>&1'
regards,
bnegrao
- Original Message -
From: Aleks Olsen
To: vchkpw@inter7.com
Sent: Wednesday, September 21, 2005 10:38 AM
Subject: Re: [vchkpw] chkuser 2.0.8b
Thanks Bruno, but im not that keen on the TLS support anymore. Perhaps i'll
toast
's a lot of people
supporting qmail-toaster. Maybe you'd like to try qmail-toaster installation
instead of installing all these patches by hand (this is what I'm trying to get
with qmail-toaster).
Regards,
bnegrao
- Original Message -
From:
Aleks Olsen
To:
v
hes by hand (this is what I'm trying to get
with qmail-toaster).
Regards,
bnegrao
- Original Message -
From:
Aleks Olsen
To: vchkpw@inter7.com
Sent: Wednesday, September 21, 2005 7:14
AM
Subject: Re: [vchkpw] chkuser
2.0.8b
Hi I didnt. I missed the trailing */ on
At 11.56 21/09/2005, you wrote:
-
Now, it seems the patch didnt like working with
auth-jms1.4a.patch(auth patch) and/or qmail-1.03-jms1.5.patch (tls
patch).
I got the auth patch from the vpopmail contrib dir and tried with
that, leaving the ones mentioned above out of it and then patched
S
Sorry, ill include the complete run file;
#!/bin/sh
QMAILQUEUE="/var/qmail/bin/qmail-scanner-queue.pl" ; export QMAILQUEUE
QMAILDUID=`id -u vpopmail`
NOFILESGID=`id -g vpopmail`
MAXSMTPD=`cat /var/qmail/control/concurrencyincoming`
LOCAL=`head -1 /var/qmail/control/me`
if [ -z "$QMAILDUID" -o -z "
At 11.14 21/09/2005, you wrote:
Hi
I didnt. I missed the trailing */ on that line it seems. Thanks!
-
Now, it seems the patch didnt like working with auth-jms1.4a.patch(auth
patch) and/or qmail-1.03-jms1.5.patch (tls patch).
I got the auth patch from the vpopmail contrib dir and tried with that
Hi
I didnt. I missed the trailing */ on that line it seems. Thanks!
-
Now, it seems the patch didnt like working with auth-jms1.4a.patch(auth patch) and/or qmail-1.03-jms1.5.patch (tls patch).
I got the auth patch from the vpopmail contrib dir and tried with that,
leaving the ones mentioned abo
At 11.51 20/09/2005, you wrote:
Tried to patch up a clean src of
qmail-1.03. I get the same error as I get with the already patched up
src.
Hope this is right.
Yes. How did you define CHKUSER_STARTING_VARIABLE within
chkuser_settings.h?
Tonino
Thanks,
/Aleksander
-
static void first_time_init (v
Tried to patch up a clean src of qmail-1.03. I get the same error as I get with the already patched up src.
Hope this is right.
Thanks,
/Aleksander
-
static void first_time_init (void) {
char * temp_string;
#if !defined CHKUSER_ALWAYS_ON && defined CHKUSER_STARTING_VARIABLE
starting
At 11.26 20/09/2005, you wrote:
Hi,
Trying to patch up an already auth+tls+spf patched qmail-smtpd and seems
i hit a rock and
hoping for some guidance.
I followed the manual patch guide at
http://www.interazioni.it/opensource/chkuser/documentation/installation/manual.html
and think I so
Hi,
Trying to patch up an already auth+tls+spf patched qmail-smtpd and seems i hit a rock and
hoping for some guidance.
I followed the manual patch guide at http://www.interazioni.it/opensource/chkuser/documentation/installation/manual.html
and think I somewhat
fit all the pices in the rig
At 18.58 26/07/2005, you wrote:
>
> If it works telnetting to port 25, then it should work from anywhere,
> as the protocol is the same and the programs are the same.
>
> What are logs saying about rejected/lost messages?
The logs say nothing.
Is there any chkuser log in /var/log/maillog (or w
> At 07.28 26/07/2005, you wrote:
>>I am having a problem with chkuser. When qmail is running with the
>> patch,
>>everthing appears to be working fine.
>>i can telnet into port 25 of my server and send a test message from my
>>local box and a remote box.
>>this test appears in my inbox as normal.
At 07.28 26/07/2005, you wrote:
I am having a problem with chkuser. When qmail is running with the patch,
everthing appears to be working fine.
i can telnet into port 25 of my server and send a test message from my
local box and a remote box.
this test appears in my inbox as normal.
but when i s
I am having a problem with chkuser. When qmail is running with the patch,
everthing appears to be working fine.
i can telnet into port 25 of my server and send a test message from my
local box and a remote box.
this test appears in my inbox as normal.
but when i send through a mail client, such wa
42 matches
Mail list logo
