-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 03/21/2011 06:20 PM, Eric Shubert wrote:
> 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-to
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.1
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 securit
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 03/17/2011 10:58 AM, Eric Shubert wrote:
> On 03/17/2011 08:50 AM, Matt Brookings wrote:
>> -BEGIN PGP SIGNED MESSAGE-
>> Hash: SHA1
>>
>> On 03/17/2011 10:42 AM, Eric Shubert wrote:
>>> I noticed a while back that after changing someone's n
On 03/17/2011 08:50 AM, Matt Brookings wrote:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
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 qma
