EFM -- Feature requests for Ver. 2.0

[songdog]

Thought I'd start a thread for these. If DB or Sheila would prefer another place for recording these, just let us know.

Rejection Logging -- Record the IP address of the sender, if confidence is high that the address isn't spoofed.

I'm not sure about this, but I think you can look for the IP address furthest "down" (i.e. chronologically earliest) in the list of headers. If the IP address is enclosed in square brackets, then it's reliable (probably not spoofed).

Again, I'm not sure if this is how to do it, but I think so. If other people like this feature request, I'll research the exact technique and report back.

[sheila]

The only IP address you can 100% rely on, is the one that connects to the FutureQuest servwers to deliver the mail.

Spamcop has some way of testing the "chain" of IP addresses for whether a given IP address in the Received lines is believable or not (i.e. forged or not forged). Personally, I don't have any desire to re-write the logic that Spamcop has already developed for this. I believe that the Spamcop source code for this part of their set up is open source and you can download and study it.

They also have a newsgroup for developers to discuss the code and code developement:
spamcop.dev

Possibly you could ask questions about the code in that newsgroup if you were studying it and had questions.

[Bill3555]

It would be nice if there was an automatic notification of updates on the password page. Maybe somebody doesn't want to be on the email list, or somebody forgets about an update notification, and little text reminder on a person's efm page would tell them that the latest version is 2.0, or whatever.

efm is a-okay.

Best,
Bill

[DB]

It would be nice if there was an automatic notification of updates on the password page. I actually have a "version check" page included in most of my software, but not EFM. When the version update page is viewed, a small graphic from my website is displayed, which graphic depends on which version you are currently running. The graphic may be a green "No update required", a yellow "Update available" or a red "Update required"... it all depends on whether the update contains a minor new feature or a critical bug fix. But I usually don't start this until the software is out of beta and the updates become infrequent (too many new graphics to display during beta). I haven't really decided whether to take this approach with EFM, I figured since we are all part of the same FQ community that the e-mail list would be enough. ;)

[sheila]

I figured since we are all part of the same FQ community that the e-mail list would be enough.
Or posted announcements in the AOTA forums?

[DB]

Or posted announcements in the AOTA forums? That, too. ;)

I don't foresee many e-mail notices going out, at least after the program is out of beta. The notices may be more convenient for those who don't read the forums on a regular basis. Either way, signing-up is optional.