On Monday, February 10, 2003, at 08:50 AM, Dzuy Nguyen wrote:
The correct thing to do is put the external email address in the vdelivermail line, like so:Juraj Hantak wrote:Hi all, I have a problem with vdelivermail it is not correctly proceeding .qmail- files. Imagine situation you have a domain called test.com. Do you want to forward the whole domain <everything>@test.com into address [EMAIL PROTECTED] and the address should be proceed acording its .qmail file. {local deliverded and forwarded to external address} do you have in .qmail-default | <path to vdelivermail> vdelivermail '' [EMAIL PROTECTED] and there is a file called .qmail-john &[EMAIL PROTECTED] <path to domain>/test.com/john/Maildir/ there is a mailbox [EMAIL PROTECTED] And the behaviour is now: when you send mail directly to [EMAIL PROTECTED] its correctly proceed and is local delivered and a copy is forwarded to external address. But when you send mail to [EMAIL PROTECTED] its only localy delivered it is not forwarded to external mail address. Can somebody help me with this problem, I have tested the stable 5.2.1 version and developement 5.3.14
| /home/vpopmail/bin/vdelivermail '' [EMAIL PROTECTED]
.qmal files in the domain directory are for qmail-local processing, NOT vdelivermail. This is why the setup you described fails. vdelivermail checks for a vpasswd entry for john since test.com is the local domain. It does NOT look at .qmail files in the domain's directory, just .qmail files in the user's directory.
There is a bug in vdelivermail since 5.2 which I identified and reported. I'mBest regards Juraj Hantak
surprised it didn't make it to 5.3 development releases. Basically, forward and
keeps a copy works fine, but forward alone does not. Please check the archive
for details of the problem.
I assume you are referring to this message:
http://www.mail-archive.com/vchkpw@inter7.com/msg11007.html See the argument above. The same logic applies, and it's not a bug. Regards, Bill Shupp
