Re: [vchkpw] vpopmail with SA

2004-02-05 Thread Charles Sprickman
On Thu, 5 Feb 2004, Tom Collins wrote:

> This is a bug we've tried to squash multiple times in vdelivermail.  I
> thought that in 5.4.0, we had finally ironed out the problems that
> resulted in Delivered-To containing the domain name twice.

At least I'm not crazy.  I've never been able to get "[EMAIL PROTECTED]" to work
right.

> If you have a .qmail-alias file with direct Maildir delivery, qmail
> handles the delivery directly, and vdelivermail doesn't have an
> opportunity to rewrite that header.

It seems this hack that's floating around (and that I'm using) takes care
of that:

VDIR=`pwd`
USERNAME=`echo ${VDIR##*/}`
USERHOST=`PWDTMP=${VDIR%/*}; echo ${PWDTMP##*/}`

(USERNAME in place of EXT, USERHOST in place of HOST for readability in a
very long default maildrop config)

Charles

> --
> Tom Collins  -  [EMAIL PROTECTED]
> QmailAdmin: http://qmailadmin.sf.net/  Vpopmail: http://vpopmail.sf.net/
> Info on the Sniffter handheld Network Tester: http://sniffter.com/
>
>


Re: [vchkpw] vpopmail with SA

2004-02-05 Thread Tom Collins
On Feb 5, 2004, at 5:23 AM, Jean wrote:
The problem is that the [EMAIL PROTECTED] variable provided by .qmail 
provides the
information in the form of "virtualhost-virtual_user"@domain.
So, for my [EMAIL PROTECTED] it provides:
[EMAIL PROTECTED]
This is a bug we've tried to squash multiple times in vdelivermail.  I 
thought that in 5.4.0, we had finally ironed out the problems that 
resulted in Delivered-To containing the domain name twice.

If you have a .qmail-alias file with direct Maildir delivery, qmail 
handles the delivery directly, and vdelivermail doesn't have an 
opportunity to rewrite that header.

--
Tom Collins  -  [EMAIL PROTECTED]
QmailAdmin: http://qmailadmin.sf.net/  Vpopmail: http://vpopmail.sf.net/
Info on the Sniffter handheld Network Tester: http://sniffter.com/


Re: [vchkpw] vpopmail with SA

2004-02-05 Thread Jean
From: "Jeremy Kitchen" <[EMAIL PROTECTED]>

> $EXT should only give you 'systest'
>
> [EMAIL PROTECTED]:~$ cat .qmail-test
> |echo $EXT > testfile
> [EMAIL PROTECTED]:~$ echo "hi" | mailsubj "test" kitchen-test | qmail-inject
> [EMAIL PROTECTED]:~$ cat testfile
> test

Hm, that's right, I just changed it back to [EMAIL PROTECTED] and it works again. I
must have tried something really stupid the first time I tried. Sorry for
the unnecessary thread.

thanks,

Jw.



Re: [vchkpw] vpopmail with SA

2004-02-05 Thread Jeremy Kitchen
On Thu, 2004-02-05 at 06:23, Jean wrote:
> Hi,
> 
> I just installed SpamAssassin in my vpopmail installation, with maildrop.
> The thing is that the sample script (provided everywhere, including SA
> distribution), uses the following command lines to get the users home dir:
> 
> VHOME=`/var/vpopmail/pop/bin/vuserinfo -d [EMAIL PROTECTED]
> 
> First, the path is not the default vpopmail installation (/home/vpopmail),
> but I can live with that :P
> 
> The problem is that the [EMAIL PROTECTED] variable provided by .qmail provides the
> information in the form of "virtualhost-virtual_user"@domain.
> So, for my [EMAIL PROTECTED] it provides:
> [EMAIL PROTECTED]

$EXT should only give you 'systest'

[EMAIL PROTECTED]:~$ cat .qmail-test
|echo $EXT > testfile
[EMAIL PROTECTED]:~$ echo "hi" | mailsubj "test" kitchen-test | qmail-inject
[EMAIL PROTECTED]:~$ cat testfile
test
[EMAIL PROTECTED]:~$

> I'm using pretty much the default settings for everything, and i guess this
> is the normal behaviour of qmail. Just wondering if i'm missing something
> obvious or anyone has got around that. I am temporary using my full email on
> the 'vuserinfo -d' command instead of the variables, but I didnt want to go
> that way for each user.

shouldn't have to

-Jeremy

-- 
Jeremy Kitchen
Systems Administrator
[EMAIL PROTECTED]
Kitchen @ #qmail on EFNet - Join the party!
.
Inter7 Internet Technologies, Inc.
www.inter7.com
866.528.3530 toll free
847.492.0470 int'l
847.492.0632 fax
GNUPG key ID: 93BDD6CE



Re: [vchkpw] vpopmail with SA

2004-02-05 Thread Jean
Thanks, but I would like to try it with maildrop.
Any ideas?

TIA,

Jw.
- Original Message - 
From: "Vpopmail Mailinglist" <[EMAIL PROTECTED]>
To: <[EMAIL PROTECTED]>
Sent: Thursday, February 05, 2004 10:26 AM
Subject: Re: [vchkpw] vpopmail with SA


> Hi im using that howto for that:
>
>
http://www.google.de/search?q=cache:MxZQmN41SL0J:sylvestre.ledru.info/howto/howto_qmail_spamassassin_with_pref.php+spamassassin+support+in+vpopmail&hl=de&ie=UTF-8
>
> it works very good here .. but you must use qmail-scanner 1.16 for that.
> There is no patch aviable vor Version 1.20
>
> Bye
>
> Am Do, den 05.02.2004 schrieb Jean um 13:23:
> > Hi,
> >
> > I just installed SpamAssassin in my vpopmail installation, with
maildrop.
> > The thing is that the sample script (provided everywhere, including SA
> > distribution), uses the following command lines to get the users home
dir:
> >
> > VHOME=`/var/vpopmail/pop/bin/vuserinfo -d [EMAIL PROTECTED]
> >
> > First, the path is not the default vpopmail installation
(/home/vpopmail),
> > but I can live with that :P
> >
> > The problem is that the [EMAIL PROTECTED] variable provided by .qmail provides
the
> > information in the form of "virtualhost-virtual_user"@domain.
> > So, for my [EMAIL PROTECTED] it provides:
> > [EMAIL PROTECTED]
> >
> > I'm using pretty much the default settings for everything, and i guess
this
> > is the normal behaviour of qmail. Just wondering if i'm missing
something
> > obvious or anyone has got around that. I am temporary using my full
email on
> > the 'vuserinfo -d' command instead of the variables, but I didnt want to
go
> > that way for each user.
> >
> > In case it matters, i'm using the latest stable version (vpopmail 5.4.0)
> > with netqmail-1.04, and the latest SA (2.63).
> >
> > thanks in advance!
> >
> > Jw.
> >
>
>



Re: [vchkpw] vpopmail with SA

2004-02-05 Thread Vpopmail Mailinglist
Hi im using that howto for that:

http://www.google.de/search?q=cache:MxZQmN41SL0J:sylvestre.ledru.info/howto/howto_qmail_spamassassin_with_pref.php+spamassassin+support+in+vpopmail&hl=de&ie=UTF-8

it works very good here .. but you must use qmail-scanner 1.16 for that.
There is no patch aviable vor Version 1.20

Bye

Am Do, den 05.02.2004 schrieb Jean um 13:23:
> Hi,
> 
> I just installed SpamAssassin in my vpopmail installation, with maildrop.
> The thing is that the sample script (provided everywhere, including SA
> distribution), uses the following command lines to get the users home dir:
> 
> VHOME=`/var/vpopmail/pop/bin/vuserinfo -d [EMAIL PROTECTED]
> 
> First, the path is not the default vpopmail installation (/home/vpopmail),
> but I can live with that :P
> 
> The problem is that the [EMAIL PROTECTED] variable provided by .qmail provides the
> information in the form of "virtualhost-virtual_user"@domain.
> So, for my [EMAIL PROTECTED] it provides:
> [EMAIL PROTECTED]
> 
> I'm using pretty much the default settings for everything, and i guess this
> is the normal behaviour of qmail. Just wondering if i'm missing something
> obvious or anyone has got around that. I am temporary using my full email on
> the 'vuserinfo -d' command instead of the variables, but I didnt want to go
> that way for each user.
> 
> In case it matters, i'm using the latest stable version (vpopmail 5.4.0)
> with netqmail-1.04, and the latest SA (2.63).
> 
> thanks in advance!
> 
> Jw.
>