On Wed, 2001-09-12 at 08:21, Sandro Serafini wrote:
> Hi!
> 
> On Wed, 12 Sep 2001 13:05:09 +0200, Sandro wrote:
> 
> > I've just upgraded vpopmail to the last version, needed by last
> > sqwebmail, and I have a big problem with the Delivered-To: header.
> 
> I temporary solved my problem modifying vdelivermail.c adding the following line at 
>line 478 
> (version 5.0pre5), just before the writing of the variable DeliverTo to the 
>destination mail:
> 
>     snprintf(DeliveredTo, AUTH_SIZE,
>             "%s%s", getenv("RPLINE"), getenv("DTLINE"));
> 
> This get rid of the bogus Delivered-To: and writes in the mail the correct one (the 
>qmail supplied one).
> 
Is this for email delivered to the catch all account from the
.qmail-default file, or a straight vdelivermail from the authentication 
database.

> I don't know if this could cause other problem, probably some problems guessing if a 
>mail is looping,
> but it works for me. Isn't mail looping checked by qmail itself? In my case, at the 
>moment,
> having a correct Delivered-To: is more important. You can use another header for 
>your looping-detection
> delivered-to.

Not in all cases. Now that vpopmail supports .qmail files in the users
directories, mail loops can be created, since qmail isn't involved.

example:

email to user1@domain
vdelivermail checks database and gets
/home/vpopmail/domains/domain/user1
from the database. Finds a .qmail file there containing.
&user2@domain.

vdelivermail then checks if user2@domain is in the database. If not
it sends it to qmail-inject. If it finds it then it gets the users
directory /home/vpopmail/domains/domain/user2. If that directory
has a .qmail file containing &user1@domain then it will deliver
to user1@domain.  Hence the loop.

Ken Jones
 


Reply via email to