Since we did use the "essential" means of reporting this problem, we still
got back:
"No. Declude Confirm hasn't been changed in a number of years, so it is not
currently a high priority.
-Scott"
And:
"As for Declude Confirm, I understand that it is a priority for you. The
reasons why it isn't a very high priority right now are that [1] it is a
free program, and taking time to modify it takes away from time making
changes to products our customers are paying for, and [2] this is an issue
that has been in the Declude Confirm code for many years without anyone
reporting it. Unfortunately, there are just too many things that need to be
done, and not enough time for everything.
-Scott"
-----Original Message-----
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On Behalf Of David Franco-Rocha
Sent: Tuesday, March 01, 2005 7:43 PM
To: [email protected]
Subject: [Declude.JunkMail] Declude 2.0 Issues
No issue reported to us regarding Declude software will ever be considered
trivial or unimportant. It is essential that all issues be reported to
Declude Support. A number of comments made recently on these lists refer to
issues never reported to Declude.
It should also be understood that the Declude forums are very informative
for finding out from others whether they have experienced similar issues
with the software. They are not, however, intended to be a mechanism for
reporting problems to us.
We have been monitoring the list messages regarding the DELETE action when
there is a COPYALL account and we are concerned as to perceptions that there
is a problem or issue with the software.
There is a difference of opinion on how a COPYALL account should actually
function: (a) to receive a copy of every message processed by the mail
server, whether legitimate or not; (b) to receive a copy of only those
messages for which there is at least one valid delivery.
Aside from differing opinions on how the COPYALL account should function,
our tests show that individual recipients whose per-user configurations
specified DELETE were in fact being deleted from the recipient list and were
not receiving the messages. At the same time, however, we discovered
that
there was information in the log file that would lead one to believe that
the recipient was not being deleted. If the last recipient did not have
DELETE as the action to take, the last action in the log file would not read
DELETE, even if the previous recipient had been deleted. We are making the
appropriate changes to the log file to ensure that all actions taken will be
accurately recorded. In addition, we are implementing a configurable
parameter to allow or disallow actions to apply to the COPYALL account. This
release will be available after user testing and
acceptance.
It is important to know that we respond to each and every issue raised
through our support system and also that when making a quote as to what
'Declude' may have said that the correct words are used within the
appropriate context.
---
[This E-mail was scanned for viruses by Declude Virus
(http://www.declude.com)]
---
This E-mail came from the Declude.JunkMail mailing list. To unsubscribe,
just send an E-mail to [EMAIL PROTECTED], and type "unsubscribe
Declude.JunkMail". The archives can be found at
http://www.mail-archive.com.
---
[This E-mail was scanned for viruses by Declude Virus (http://www.declude.com)]
---
This E-mail came from the Declude.JunkMail mailing list. To
unsubscribe, just send an E-mail to [EMAIL PROTECTED], and
type "unsubscribe Declude.JunkMail". The archives can be found
at http://www.mail-archive.com.
