reply-o-matic / News: Recent posts

A new bugfix version of reply-o-matic is avaliable.
This version fixes a segfault class bug related to the -f flag, detected and diagnosed by Simon Allen.
Thank you for the feedback, Simon.

mastermind-x was kind enough to join the project and provide us with a Slackware package for reply-o-matic, which is now avaliable under the "3rd Party Binaries" file group. Welcome aboard, mastermind-x, and thank you.

We now started on the Reply-o-matic v2 development. Several changes are planned, and some other considred (not sure we will implement them). There are a few of them:
- Rewrite of the Rate Control code, which was never that good to start with. The new code will most likely use SQLite, and be much more clean and efficient
- Creating a real configuration file, so we can get rid of some ugly (gid etc) hacks.
- We are at this point considering adding alternative methods of message delivery, including pipe (for procmail etc), file (directly to mbox) and smtp. Any, all or none of these might be implemented.
- A new paranoid option should be made avaliable: SenderOnly. This option will disregard all address headers from the original e-mail (From, Reply-To etc), and only reply to the SMTP Sender address. This will be, as with other paranoid options, optional and off by default.... read more

This release is marked as a minor security fix.
The security problem it fixes is only theoretical, and so far no one was able to prove it exists. But since fixing it is a good idea anyway, here it is.
The better handling of the child process on exit is another minor improvement. It will make no difference in most cases, but it can help in some specific situations.

Dag Wieers and the nice folks at RPMForge are now providing RPMs for reply-o-matic, so I'll no longer be providing them here.
If you want reply-o-matic as a rpm, you get them them at:
http://dag.wieers.com/packages/reply-o-matic/

After almost 3 years, a new stable version o replay-o-matic is avaliable.
No new functionalities were added, but many, many bugs were fixed.

After a long, long time, we have a new release.
This release should solve all of your problems. :)

Okey, I'm back. Errr, sort of, anyway.
I'll start working on the bug reported so far.
Hope we can have a brand new version which will fix everything in no time.

With the upcoming 1.0 release, I deviced it was time to branch the cvs repository in two: stable and devel.
The old 'rom' repository still exists, but contains only 1 file (MOVED) which notifies about the change.
As of today, the 'stable' repository contains 0.99.1, which is 0.99.0 + spelling corrections.
The 'devel' repository will contains the 1.1 development tree, which should start today or tomorrow. New features will go only on the development tree.
1.0release should be out friday.

1) Create a manpage -> 0.6.X (2002/01/09)
2) Make ROM automaticaly detect the correct mimetype for the attachment -> 0.7.X (2002/01/11)
3) Organize the documentation and final tests -> 0.99.X (2002/01/12-13)
4) Official Release -> 1.0 (2002/01/18)

As you can see, nothing fancy. I'll be accepting sujections before I release 0.99. After that, only bugfixes. So, if you want ROM to do something new, hurry and send me an e-mail.... read more

This is a know problem. Just change p_info to p_log.
0.5.2 will solve this problem, and be up shortly.