Re: duplicate emails with name change

Thanks for the insight, Tom. I should have given these details the first 
time.

Here is .qmail file before:
# cat .qmail
|/var/qmail/bin/preline /usr/bin/maildrop -A 'Content-Filter: 
maildrop-toaster' /etc/mail/mailfilter

Here is .qmail file after changing the name field using qmailadmin-1.2.15:
# cat .qmail
|/var/qmail/bin/preline /usr/bin/maildrop -A 'Content-Filter: 
maildrop-toaster' /etc/mail/mailfilter
/home/vpopmail/domains/shubes.net/someuser/Maildir/

The first example is all one line, and in the 2nd example the 2nd/last 
line has been added, resulting in duplicate delivery.

Thanks for looking into this.
-- 
-Eric 'shubes'

On 03/19/2011 09:09 AM, Tom Collins wrote:
> Matt,
>
> I recall adding code to QmailAdmin to have it parse the .qmail file to identify the entries so that when saving it back out, it wouldn't replace custom delivery lines.  I think this was around the time I removed the ability to enter a program delivery line on that screen -- a huge security hole since any user could then have vdelivermail execute any program as the vchkpw user.
>
> My guess is that it didn't recognize one of the lines, either due to it being a manual edit or because it was written by an older version.
>
> If Eric can produce one of the duplicated .qmail files, or perhaps another .qmail file from the same era, it should be possible to update QmailAdmin to recognize the delivery instruction.
>
> -Tom
>
>
> On Mar 17, 2011, at 12:44 PM, Matt Brookings wrote:
>> On 03/17/2011 10:58 AM, Eric Shubert wrote:
>>> On 03/17/2011 08:50 AM, Matt Brookings wrote:
>>>> On 03/17/2011 10:42 AM, Eric Shubert wrote:
>>>>> I noticed a while back that after changing someone's name with
>>>>> qmailadmin, they began receiving duplicate emails. This was caused by
>>>>> duplicate entries that qmailadmin had created in their .qmail file.
>>>>>
>>>>> It was simple enough to correct, but I think it's a bug that should be
>>>>> fixed. This was in qmailadmin-1.2.15 I believe. Does anyone know if
>>>>> this problem has been fixed?
>>
>> No problem.  I'd like to get a bug of that caliber fixed.
>
>
> 
>
>



!DSPAM:4d87dd5432719019546688!