Matt,
Just to reply, config.h look ok to me:
[r...@vmfc12 vpopmail-5.4.29]# cat config.h | grep -P "usr|bin|vpop"#define
LOG_NAME "vpopmail"#define MAILDROP_PROG "/usr/local/hcp/bin/maildrop"#define
OPEN_SMTP_CUR_FILE "/usr/local/hcp/vpopmail/etc/open-smtp"#define
OPEN_SMTP_LOK_FILE "/usr/local
Tom/Matt,
I recompiled with spamassassin and maildrop, reinstalled, and vpopmail.mysql
went back to mode 640, which caused this error:
@40004b184f6a0be9e37c new msg 207...@40004b184f6a0be9ef34 info msg
207176: bytes 496 from qp 15404 uid
0...@40004b184f6a0be9f704 starting delivery
Tom,
I reckon you might be on to something. I did su to mike4, and couldn't even
list the ~vpopmail/bin directory, let alone execute vdelivermail - in fact I
got "Permission denied"!
And I fixed it!
I changed permissions as follows:
~vpopmail/ - to mode 2755~vpopmail/etc/ - to mode
40755~vp
Sorry to just jump in at a random point in the conversation, but here are some
thoughts.
If you su to the mike4 user, can you run ~vpopmail/bin/vdelivermail (i.e., do
you have execute access on the file)? It needs to be able to do that. Can you
cd into the directory with email for that domain
spamassassin was already disabled in vlimits.default, but I recompiled again
without it.Same problem.
Mike.
Date: Thu, 3 Dec 2009 15:16:45 -0800
From: t...@eotnetworks.com
To: vchkpw@inter7.com
Subject: Re: [vchkpw] vdeliver perimission denied for vadddomain -u
Try disabling spamassassin
Try disabling spamassassin support as well.
t
From: Michael Mussulis
To: vchkpw@inter7.com
Sent: Thu Dec 03 15:13:25 2009
Subject: RE: [vchkpw] vdeliver perimission denied for vadddomain -u
Matt,
Just to make sure we're on the page, I've done a brand new
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Michael Mussulis wrote:
> Matt,
>
> Just to make sure we're on the page, I've done a brand new build using
> version 5.4.29 you recently released, without maildrop as shown below.
> Installed, restarted qmail, still getting permission denied.
Check c
Matt,
Just to make sure we're on the page, I've done a brand new build using version
5.4.29 you recently released, without maildrop as shown below. Installed,
restarted qmail, still getting permission denied.
Mike.
configure: creating ./config.statusconfig.status: creating
Makefileconfig.statu
Tren,
No need to apologize, and I thought of the exact same thing, so I did two tests:
1. disable maildrop in ./etc/vlimits.default2. recompiled vpopmail without
maildrop
Still got the same error. I even went as far as renaming the maildroprc file,
but still no go.
Thanks,Michael.
--
Exc
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Tren Blackburn wrote:
> Excuse my interjection but could the issue be with maildrop being called
> during the delivery process? What do your maildroprc file have in it?
> Does maildrop have permission to delivery to that directory?
Ah. Also, does vde
Excuse my interjection but could the issue be with maildrop being called during
the delivery process? What do your maildroprc file have in it? Does maildrop
have permission to delivery to that directory?
- Original Message -
From: Matt Brookings
To: vchkpw@inter7.com
Sent: Thu Dec 03 1
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Michael Mussulis wrote:
> Matt,
>
> Is there any way to manually debug vdelivermail?
Of course. Look at the qmail-command manpage.
- --
/*
Matt BrookingsGnuPG Key FAE0672C
Software developer Systems technician
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Michael Mussulis wrote:
> Matt,
>
> I am running version 5.4.28 downloaded from sourceforge and compiled with:
>
> #!/bin/sh
>
> ./configure \
> --prefix=/usr/local/hcp \
> --enable-qmaildir=/usr/local/hcp/var/qmail \
> --enable-qmail-ne
Matt,
Is there any way to manually debug vdelivermail?
Cheers,Michael.
> Date: Thu, 3 Dec 2009 16:45:56 -0600
> From: m...@inter7.com
> To: vchkpw@inter7.com
> Subject: Re: [vchkpw] vdeliver perimission denied for vadddomain -u
>
> -BEGIN PGP SIGNED MESSAGE-
> Hash: SHA1
>
> Michael Mus
Matt,
I am running version 5.4.28 downloaded from sourceforge and compiled with:
#!/bin/sh
./configure \--prefix=/usr/local/hcp \
--enable-qmaildir=/usr/local/hcp/var/qmail \
--enable-qmail-newu=/usr/local/hcp/var/qmail/bin/qmail-newu \
--enable-qmail-inject=/usr/local/hcp/var/qmai
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Michael Mussulis wrote:
> Furthermore, having followed the instructions to the letter, I would
> expect it to simply work - unless there's something silly I've missed
> (or perhaps undocumented). If other people have -u to work perhaps they
> can shed
Matt,
First of, I have not made any changes whatsoever to the codebase. I merely had
a peek at the code to study it's inner workings due to this problem - and that
was just looking at at the vpopmail source code, nothing else. I followed the
instructions very carefully, and as I've said before,
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Michael Mussulis wrote:
> It looks like I am talking partly nonsense, apologies for that. I've had
> another stab at the code, and it looks like the sql insert command
> statement has gid hardcoded to '0', and uid is the 'apop' value - which
> from wha
Michael Mussulis wrote:
It looks like I am talking partly nonsense, apologies for that. I've had
another stab at the code, and it looks like the sql insert command
statement has gid hardcoded to '0', and uid is the 'apop' value - which
from what I gather (correct me if I am wrong), only works i
It looks like I am talking partly nonsense, apologies for that. I've had
another stab at the code, and it looks like the sql insert command statement
has gid hardcoded to '0', and uid is the 'apop' value - which from what I
gather (correct me if I am wrong), only works in clear text mode. So si
It looks like I am talking partly nonsense, apologies for that. I've had
another stab at the code, and it looks like the sql insert command statement
has gid hardcoded to '0', and uid is the 'apop' value - which from what I
gather (correct me if I am wrong), only works in clear text mode. So si
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
I'll be releasing 5.4.29 on Sourceforge in tarball form shortly. This version
fixes
some bugs that were in 5.4.28, as well as fixing support for Solaris and
FreeBSD.
Again, no new features will be added to the 5.4 branch. 5.4 is feature-locked
an
22 matches
Mail list logo
