Re: [spamdyke-users] New version: 4.0.0

[BC]

Bravo and Thank You!!!

On 7/14/2008 [EMAIL PROTECTED] wrote:
>  At long, long last, the moment we've all been waiting for!  spamdyke
>  version 4.0.0 is now available:
> http://www.spamdyke.org/

___
spamdyke-users mailing list
spamdyke-users@spamdyke.org
http://www.spamdyke.org/mailman/listinfo/spamdyke-users

Re: [spamdyke-users] New version: 4.0.0

[David Stiller]

I agree. Great work!

One thing i just noticed: Spamdyke gave me an error writing to the
greylist. To a folder and file called "_none". Maybe it's a config- 
issue?

It tried to write to my graylist like this:

/var/qmail/spamdyke/greylist-dir//_none/_none

Maybe it was an exception, but where did _none come from? Generally
the greylist works on all domains, although the one where the error
occured on.

Regards,
Blackbit

Am 15.07.2008 um 03:09 schrieb BC:

>
> Bravo and Thank You!!!
>
> On 7/14/2008 [EMAIL PROTECTED] wrote:
>>  At long, long last, the moment we've all been waiting for!  spamdyke
>>  version 4.0.0 is now available:
>> http://www.spamdyke.org/
>
> ___
> spamdyke-users mailing list
> spamdyke-users@spamdyke.org
> http://www.spamdyke.org/mailman/listinfo/spamdyke-users


___
spamdyke-users mailing list
spamdyke-users@spamdyke.org
http://www.spamdyke.org/mailman/listinfo/spamdyke-users

Re: [spamdyke-users] New version: 4.0.0

[Daniel Anliker]

David Stiller schrieb:
> I agree. Great work!
>
> One thing i just noticed: Spamdyke gave me an error writing to the
> greylist. To a folder and file called "_none". Maybe it's a config- 
> issue?
>
> It tried to write to my graylist like this:
>
> /var/qmail/spamdyke/greylist-dir//_none/_none
>
> Maybe it was an exception, but where did _none come from? Generally
> the greylist works on all domains, although the one where the error
> occured on.
>
>   

I see the same messages on my Server with spamdyke 4.

Jul 15 02:45:12 ally spamdyke[19051]: ERROR: unable to move file 
/var/qmail/spamdyke/greylist/xyz.ch/akstcjuristereimnsdgs/_none to 
/var/qmail/spamdyke/greylist/xyz.ch/akstcjuristereimnsdgs/_none/_none: 
Not a directory

Jul 15 02:45:12 ally spamdyke[19051]: ERROR: cannot write to graylist 
file 
/var/qmail/spamdyke/greylist/xyz.ch/akstcjuristereimnsdgs/_none/_none: 
No such file or directory

___
spamdyke-users mailing list
spamdyke-users@spamdyke.org
http://www.spamdyke.org/mailman/listinfo/spamdyke-users

Re: [spamdyke-users] New version: 4.0.0

[Sam Clippinger]

The first version 4 bug!  Fantastic! :)

spamdyke 3.x uses a file named "_none" to graylist connections that 
don't provide a sender address (bounce messages are typically delivered 
this way).

spamdyke 4.0.0 changes the layout of the graylist directory structure by 
creating folders for the sender domains.  For example, spamdyke 3.x 
might have created a file named:

/var/qmail/spamdyke/graylist/localdomain.com/localuser/[EMAIL PROTECTED]
Now spamdyke 4.0.0 will use the same information to create another 
subdirectory using the sender's domain name:

/var/qmail/spamdyke/graylist/localdomain.com/localuser/remotedomain.com/[EMAIL 
PROTECTED]

The error you're seeing is occurring because spamdyke is trying to 
convert your 3.x graylist directory into the 4.0.0 structure.  It does 
this by first creating a directory for the domain, then moving the 
existing file into the new subdirectory.  However, because "_none" 
doesn't contain a domain name, it tries to create a folder named "_none" 
and fails (because a file already exists with that name).  Then it tries 
to move the file, which also fails because the directory doesn't exist.

Because an error is encountered, the connection isn't graylisted but the 
message should still be received properly.

I'll get this fixed right away.  A quick workaround is to simply find 
and delete all of the files named "_none".  spamdyke will then be able 
to create the "_none" subdirectories and graylisting will work without 
errors.  On most Unix systems (with GNU tools), the following command 
should work (your mileage may vary):
find GRAYLISTDIR -name _none -type f -print0 | xargs -0 rm -f

-- Sam Clippinger

Daniel Anliker wrote:
> David Stiller schrieb:
>   
>> I agree. Great work!
>>
>> One thing i just noticed: Spamdyke gave me an error writing to the
>> greylist. To a folder and file called "_none". Maybe it's a config- 
>> issue?
>>
>> It tried to write to my graylist like this:
>>
>> /var/qmail/spamdyke/greylist-dir//_none/_none
>>
>> Maybe it was an exception, but where did _none come from? Generally
>> the greylist works on all domains, although the one where the error
>> occured on.
>>
>>   
>> 
>
> I see the same messages on my Server with spamdyke 4.
>
> Jul 15 02:45:12 ally spamdyke[19051]: ERROR: unable to move file 
> /var/qmail/spamdyke/greylist/xyz.ch/akstcjuristereimnsdgs/_none to 
> /var/qmail/spamdyke/greylist/xyz.ch/akstcjuristereimnsdgs/_none/_none: 
> Not a directory
>
> Jul 15 02:45:12 ally spamdyke[19051]: ERROR: cannot write to graylist 
> file 
> /var/qmail/spamdyke/greylist/xyz.ch/akstcjuristereimnsdgs/_none/_none: 
> No such file or directory
>
> ___
> spamdyke-users mailing list
> spamdyke-users@spamdyke.org
> http://www.spamdyke.org/mailman/listinfo/spamdyke-users
>   
___
spamdyke-users mailing list
spamdyke-users@spamdyke.org
http://www.spamdyke.org/mailman/listinfo/spamdyke-users

Re: [spamdyke-users] New version: 4.0.0

[Juliano Valente]

Hi, I update the spamdyke but it don't work. When I see in my
/var/log/maillog haven't nothing.


2008/7/15 Sam Clippinger <[EMAIL PROTECTED]>:

> The first version 4 bug!  Fantastic! :)
>
> spamdyke 3.x uses a file named "_none" to graylist connections that
> don't provide a sender address (bounce messages are typically delivered
> this way).
>
> spamdyke 4.0.0 changes the layout of the graylist directory structure by
> creating folders for the sender domains.  For example, spamdyke 3.x
> might have created a file named:
>
> /var/qmail/spamdyke/graylist/
> localdomain.com/localuser/[EMAIL PROTECTED]
> Now spamdyke 4.0.0 will use the same information to create another
> subdirectory using the sender's domain name:
>
> /var/qmail/spamdyke/graylist/
> localdomain.com/localuser/remotedomain.com/[EMAIL PROTECTED]
>
> The error you're seeing is occurring because spamdyke is trying to
> convert your 3.x graylist directory into the 4.0.0 structure.  It does
> this by first creating a directory for the domain, then moving the
> existing file into the new subdirectory.  However, because "_none"
> doesn't contain a domain name, it tries to create a folder named "_none"
> and fails (because a file already exists with that name).  Then it tries
> to move the file, which also fails because the directory doesn't exist.
>
> Because an error is encountered, the connection isn't graylisted but the
> message should still be received properly.
>
> I'll get this fixed right away.  A quick workaround is to simply find
> and delete all of the files named "_none".  spamdyke will then be able
> to create the "_none" subdirectories and graylisting will work without
> errors.  On most Unix systems (with GNU tools), the following command
> should work (your mileage may vary):
>find GRAYLISTDIR -name _none -type f -print0 | xargs -0 rm -f
>
> -- Sam Clippinger
>
> Daniel Anliker wrote:
> > David Stiller schrieb:
> >
> >> I agree. Great work!
> >>
> >> One thing i just noticed: Spamdyke gave me an error writing to the
> >> greylist. To a folder and file called "_none". Maybe it's a config-
> >> issue?
> >>
> >> It tried to write to my graylist like this:
> >>
> >> /var/qmail/spamdyke/greylist-dir//_none/_none
> >>
> >> Maybe it was an exception, but where did _none come from? Generally
> >> the greylist works on all domains, although the one where the error
> >> occured on.
> >>
> >>
> >>
> >
> > I see the same messages on my Server with spamdyke 4.
> >
> > Jul 15 02:45:12 ally spamdyke[19051]: ERROR: unable to move file
> > /var/qmail/spamdyke/greylist/xyz.ch/akstcjuristereimnsdgs/_none to
> > /var/qmail/spamdyke/greylist/xyz.ch/akstcjuristereimnsdgs/_none/_none:
> > Not a directory
> >
> > Jul 15 02:45:12 ally spamdyke[19051]: ERROR: cannot write to graylist
> > file
> > /var/qmail/spamdyke/greylist/xyz.ch/akstcjuristereimnsdgs/_none/_none:
> > No such file or directory
> >
> > ___
> > spamdyke-users mailing list
> > spamdyke-users@spamdyke.org
> > http://www.spamdyke.org/mailman/listinfo/spamdyke-users
> >
> ___
> spamdyke-users mailing list
> spamdyke-users@spamdyke.org
> http://www.spamdyke.org/mailman/listinfo/spamdyke-users
>
___
spamdyke-users mailing list
spamdyke-users@spamdyke.org
http://www.spamdyke.org/mailman/listinfo/spamdyke-users

Re: [spamdyke-users] New version: 4.0.0

[Sam Clippinger]

A few things you can check:
Did you set the "log-target" option to "stderr"?  If so, then 
spamdyke's messages will appear in the qmail logs, not in the syslog.
Did you set the "log-level" option to "error" or "none"?  If so, 
then only error messages or none at all will appear in your logs.  Try 
"info" or higher.
Are you using Plesk?  If so, the messages will appear in 
"/usr/local/psa/var/log/maillog".
Did you restart qmail after you installed spamdyke?  If not, then 
spamdyke may not actually be running.
Have you used the "config-test" feature to look for problems with 
your configuration?

If none of that helps, please post your configuration file, your "run" 
script and your spamdyke version.

-- Sam Clippinger

Juliano Valente wrote:
> Hi, I update the spamdyke but it don't work. When I see in my 
> /var/log/maillog haven't nothing.
>
>
> 2008/7/15 Sam Clippinger <[EMAIL PROTECTED] >:
>
> The first version 4 bug!  Fantastic! :)
>
> spamdyke 3.x uses a file named "_none" to graylist connections that
> don't provide a sender address (bounce messages are typically
> delivered
> this way).
>
> spamdyke 4.0.0 changes the layout of the graylist directory
> structure by
> creating folders for the sender domains.  For example, spamdyke 3.x
> might have created a file named:
>
> /var/qmail/spamdyke/graylist/localdomain.com/localuser/[EMAIL PROTECTED]
> 
> Now spamdyke 4.0.0 will use the same information to create another
> subdirectory using the sender's domain name:
>
> 
> /var/qmail/spamdyke/graylist/localdomain.com/localuser/remotedomain.com/[EMAIL
>  PROTECTED]
> 
>
> The error you're seeing is occurring because spamdyke is trying to
> convert your 3.x graylist directory into the 4.0.0 structure.  It does
> this by first creating a directory for the domain, then moving the
> existing file into the new subdirectory.  However, because "_none"
> doesn't contain a domain name, it tries to create a folder named
> "_none"
> and fails (because a file already exists with that name).  Then it
> tries
> to move the file, which also fails because the directory doesn't
> exist.
>
> Because an error is encountered, the connection isn't graylisted
> but the
> message should still be received properly.
>
> I'll get this fixed right away.  A quick workaround is to simply find
> and delete all of the files named "_none".  spamdyke will then be able
> to create the "_none" subdirectories and graylisting will work without
> errors.  On most Unix systems (with GNU tools), the following command
> should work (your mileage may vary):
>find GRAYLISTDIR -name _none -type f -print0 | xargs -0 rm -f
>
> -- Sam Clippinger
>
> Daniel Anliker wrote:
> > David Stiller schrieb:
> >
> >> I agree. Great work!
> >>
> >> One thing i just noticed: Spamdyke gave me an error writing to the
> >> greylist. To a folder and file called "_none". Maybe it's a config-
> >> issue?
> >>
> >> It tried to write to my graylist like this:
> >>
> >> /var/qmail/spamdyke/greylist-dir//_none/_none
> >>
> >> Maybe it was an exception, but where did _none come from? Generally
> >> the greylist works on all domains, although the one where the error
> >> occured on.
> >>
> >>
> >>
> >
> > I see the same messages on my Server with spamdyke 4.
> >
> > Jul 15 02:45:12 ally spamdyke[19051]: ERROR: unable to move file
> > /var/qmail/spamdyke/greylist/xyz.ch/akstcjuristereimnsdgs/_none to
> >
> /var/qmail/spamdyke/greylist/xyz.ch/akstcjuristereimnsdgs/_none/_none:
> > Not a directory
> >
> > Jul 15 02:45:12 ally spamdyke[19051]: ERROR: cannot write to
> graylist
> > file
> >
> /var/qmail/spamdyke/greylist/xyz.ch/akstcjuristereimnsdgs/_none/_none:
> > No such file or directory
> >
> > ___
> > spamdyke-users mailing list
> > spamdyke-users@spamdyke.org 
> > http://www.spamdyke.org/mailman/listinfo/spamdyke-users
> >
> ___
> spamdyke-users mailing list
> spamdyke-users@spamdyke.org 
> http://www.spamdyke.org/mailman/listinfo/spamdyke-users
>
>
> 
>
> ___
> spamdyke-users mailing list
> spamdyke-users@spamdyke.org
> http://www.spamdyke.org/mailman/listinfo/spamdyke-users
>   
___
spamdyke-users mailing list
spamdyke-users@spamdyke.org
http://www.spamdyke.org/mailman/listinfo/spamd

Re: [spamdyke-users] New version: 4.0.0

[Juliano Valente]

I think that problem is in my run:
#!/bin/sh

export QMAILQUEUE="/var/qmail/bin/qmail-scanner-queue.pl"
export QMAILDUID=`id -u qmaild`
export NOFILESGID=`id -g qmaild`
export MAXSMTPD=`cat /var/qmail/control/concurrencyincoming`
export LOCAL=`head -1 /var/qmail/control/me`

if [ -z "$QMAILDUID" -o -z "$NOFILESGID" -o -z "$MAXSMTPD" -o -z "$LOCAL" ];
then
echo QMAILDUID, NOFILESGID, MAXSMTPD, or LOCAL is unset in
echo /var/qmail/supervise/qmail-smtpd/run
exit 1
fi

if [ ! -f /var/qmail/control/rcpthosts ]; then
echo "No /var/qmail/control/rcpthosts!"
echo "Refusing to start SMTP listener because it'll create an open
relay"
exit 1
fi

exec /usr/local/bin/softlimit -m 10 \
/usr/local/bin/tcpserver -v -R -l "$LOCAL" -x /etc/tcp.smtp.cdb -c
"$MAXSMTPD" \
-u "$QMAILDUID" -g "$NOFILESGID" 0 smtp \
*/usr/local/bin/spamdyke -f /etc/spamdyke.conf \
#--smtp-auth-command-encryption "/home/vpopmail/bin/vchkpw /usr/bin/true" \
/var/qmail/bin/qmail-smtpd /home/vpopmail/bin/vchkpw /bin/true \
2>&1
*


2008/7/16 Sam Clippinger <[EMAIL PROTECTED]>:

> A few things you can check:
>Did you set the "log-target" option to "stderr"?  If so, then
> spamdyke's messages will appear in the qmail logs, not in the syslog.
>Did you set the "log-level" option to "error" or "none"?  If so,
> then only error messages or none at all will appear in your logs.  Try
> "info" or higher.
>Are you using Plesk?  If so, the messages will appear in
> "/usr/local/psa/var/log/maillog".
>Did you restart qmail after you installed spamdyke?  If not, then
> spamdyke may not actually be running.
>Have you used the "config-test" feature to look for problems with
> your configuration?
>
> If none of that helps, please post your configuration file, your "run"
> script and your spamdyke version.
>
> -- Sam Clippinger
>
> Juliano Valente wrote:
> > Hi, I update the spamdyke but it don't work. When I see in my
> > /var/log/maillog haven't nothing.
> >
> >
> > 2008/7/15 Sam Clippinger <[EMAIL PROTECTED] >:
> >
> > The first version 4 bug!  Fantastic! :)
> >
> > spamdyke 3.x uses a file named "_none" to graylist connections that
> > don't provide a sender address (bounce messages are typically
> > delivered
> > this way).
> >
> > spamdyke 4.0.0 changes the layout of the graylist directory
> > structure by
> > creating folders for the sender domains.  For example, spamdyke 3.x
> > might have created a file named:
> >
> > /var/qmail/spamdyke/graylist/
> localdomain.com/localuser/[EMAIL PROTECTED]
> > 
> > Now spamdyke 4.0.0 will use the same information to create another
> > subdirectory using the sender's domain name:
> >
> > /var/qmail/spamdyke/graylist/
> localdomain.com/localuser/remotedomain.com/[EMAIL PROTECTED]
> > <
> http://localdomain.com/localuser/remotedomain.com/[EMAIL PROTECTED]
> >
> >
> > The error you're seeing is occurring because spamdyke is trying to
> > convert your 3.x graylist directory into the 4.0.0 structure.  It
> does
> > this by first creating a directory for the domain, then moving the
> > existing file into the new subdirectory.  However, because "_none"
> > doesn't contain a domain name, it tries to create a folder named
> > "_none"
> > and fails (because a file already exists with that name).  Then it
> > tries
> > to move the file, which also fails because the directory doesn't
> > exist.
> >
> > Because an error is encountered, the connection isn't graylisted
> > but the
> > message should still be received properly.
> >
> > I'll get this fixed right away.  A quick workaround is to simply find
> > and delete all of the files named "_none".  spamdyke will then be
> able
> > to create the "_none" subdirectories and graylisting will work
> without
> > errors.  On most Unix systems (with GNU tools), the following command
> > should work (your mileage may vary):
> >find GRAYLISTDIR -name _none -type f -print0 | xargs -0 rm -f
> >
> > -- Sam Clippinger
> >
> > Daniel Anliker wrote:
> > > David Stiller schrieb:
> > >
> > >> I agree. Great work!
> > >>
> > >> One thing i just noticed: Spamdyke gave me an error writing to the
> > >> greylist. To a folder and file called "_none". Maybe it's a
> config-
> > >> issue?
> > >>
> > >> It tried to write to my graylist like this:
> > >>
> > >> /var/qmail/spamdyke/greylist-dir//_none/_none
> > >>
> > >> Maybe it was an exception, but where did _none come from?
> Generally
> > >> the greylist works on all domains, although the one where the
> error
> > >> occured on.
> > >>
> > >>
> > >>
> > >
> > > I see the same messages on my Server with spamdyke 4.
> > >
> > > Jul 15 02:45:12 ally spamdyke[19051]: ERROR: unable to move 

Re: [spamdyke-users] New version: 4.0.0

[K. Shantanu]

* Juliano Valente <[EMAIL PROTECTED]> [080716 23:29]:
> I think that problem is in my run:
[...]

> -u "$QMAILDUID" -g "$NOFILESGID" 0 smtp \
> */usr/local/bin/spamdyke -f /etc/spamdyke.conf \
> #--smtp-auth-command-encryption "/home/vpopmail/bin/vchkpw /usr/bin/true" \

These lines are fishy. You cannot comment like this there. And what is
that with the "*" on second line above?

Shantanu
-- 
___
spamdyke-users mailing list
spamdyke-users@spamdyke.org
http://www.spamdyke.org/mailman/listinfo/spamdyke-users