|
1.0 Build 75 - 4/26/04 11:00am
●First Public Release
1.0 Build 76 -
4/27/04 1:30am
●Updated "Smart Challenge/Response™" to include the manually entered
SMTP server when the email account domain matches that of the
Primary Email Address. This fixed a problem with RoadRunner not
exposing their published internal SMTP server as an MX record in the
DNS system. The challenge kept RoadRunner users from being able to
verify their accounts because the system reported that no SMTP
server would verify their ability to send email.
1.0 Build 102
- 5/1/04 5:00pm
●Updated verification process so that as soon as the short verify
email has arrived the email client can begin receiving email through
ii. The email will be passed unprotected until the "Long" verify
completes, but in the case where the "Long" takes more than a few
seconds to do the round trip or when the email gets "lost" in
transit, the users email client continues to function normally.
Greatly improved the entire process to considerably raise the
likelihood of a successful verification.
●Greatly improved the address book import function. No longer must
the exported file be in the format that Outlook Express uses with
only the "Name" and "Email Address" fields included. Now the file
can be any standard CSV file that contains the needed information.
The user can select the correct fields to use even when more data is
available. This specifically addresses the challenge of importing an
address book exported from Outlook.
●When the product is registered, the previous versions sent an
acknowledgment email to the auto-responder. Now the program sends to
a special account assigned specifically to record registrations so
that the email is not bounced back and shown in the users inbox.
●The manual had several revisions to reflect the changes made and to
clarify the setup process with more bolding and better text. The
address book import section was updated to reflect the new
procedure. Several spelling and grammar errors were also fixed.
●Some spelling and grammar errors were corrected in the program.
●Debug logging to disk was added to support debugging startup
challenges. If the registry key "HKCU\Software\NMIEnterprises\InvisibleInbox\DebugLog"
is creates as a string containing "1", then all logging, without
reference to the logging level selected by the user will be written
to "ii-debug_YYYY-MM-DD.log" within the program folder. Care must be
taken as this file can grow quite large very quickly and having this
feature enabled can significantly slow the program down over time.
●The user has the option to write all logs to file. Only the log
entries that are displayed on the screen are logged to disk, being
written to the "ii_YYYY-MM-DD.log" file within the program folder.
●Added close button to Lists dialog.
●Improved the logic for SMTP2 which is responsible for verifying
email addresses prior to SMTP1 sending them. The logic now includes
even more layers of checking to enhance the "Smart
Challenge/Response™" system. It now checks the email for proper
syntax, then checks the domain against the DNS system to make sure
it exists, then does a DNS lookup for all registered MX records and
does an SMTP check both using VRFY and MAIL FROM/RCPT TO checks
against all listed SMTP servers until a one accepts the address. It
also checks the users SMTP server using VRFY and MAIL FROM/RCPT TO
checks if the domain of the outgoing email matches the domain of the
user's Primary Email Address.
●When a sender was deleted from the Spammer list, the associated
emails were not deleted. This has been fixed.
●If the user is using Outlook Express, the program can detect the
account settings and fill them in automatically.
2.0 Build x
- In development
●Total rewrite of Verify Email routine. ("Smart Challenge/Response™"
system) No more false negatives which kept verification from working
for a large number of users and also kept many valid challenge
emails from being sent.
●Changed method used to send all challenge and verification emails.
●Removed SMTP Log - Merged into Activity Log.
●Fully redesigned Interface.
●Rewriting many portions of the code.
|
