=pod =head1 Before Asking For Help Mojo Mail is released under the GNU Public License. Among other things, it means that there isn't any official support given for the script. It's one of the comprimised that you give for a program released for free. But, as a community, support for the program can be created. If you're having problems with Mojo Mail, make sure you B. Mojo Mail distributions are hosted by Source Forge. You can see all the files that are available here: http://sourceforge.net/project/showfiles.php?group_id=13002 The latest stable version will most likely be listed on the Mojo Mail download page: http://mojo.skazat.com/download/ Depending on what you use Mojo Mail for, you may want to at least try out an alpha or beta version. In a production environment, it's better to stick to "stable" releases. That's not to say stable releases have any less bugs in them, it's more like it's known what the bugs (and workarounds) are. If you're following a bug and want to know when it has been fixed, it's best to check the changelog: http://mojo.skazat.com/support/documentation/changes.pod.html If a bug you're experiencing has been fixed, await the release of a stable version, or risk using a development version. =head2 Other Resources to Check Before Asking For Help B http://mojo.skazat.com/support/documentation/error_faq.pod.html B http://mojo.skazat.com/support/documentation/NOTES.pod.html This will have incompatibilities, if any, between versions, as well as any "gotchas" =head1 What Information You Should Have When Asking For Help =head2 The Version of Mojo Mail It's very very important to know what version of the program you're using. The differences between even small version increases can be dramatic. The version of Mojo Mail is stored in the B<$VER> Config.pm variable. =head2 What program/script is giving you the error Mojo Mail is composed of many different scripts. Most of what goes on happens in the main B script and, if you don't install any plugins or extensions, that's all you have to worry about. It's a good idea to specifically say what script is giving you the problem. =head2 Your Server Setup Different servers can give you different problems. If you think this is relevent, post the B information. if you don't know anything about your server, try installing a script, like this one: http://www.scriptsolutions.com/programs/free/perldiver/ To help. =head2 What Browser You're Using Even though Mojo Mail is a server-based program, differences in browsers may cause problems in formatting. Information you should be able to view may be hidden, or various browser technologies could be malfunctioning (example: cookies) Mojo is mostly developed on Mac OS X using IE 5.2 and Mozilla. =head2 What Mail Reader You're Using If you're having problems with the format of emails you're sending, it may be the mail reader that's causing the problems. Different mail readers render complex messages differently. Mojo is mostly developed using Entourage X. =head2 Logged Errors Before reporting errors, find out if any of the errors were logged by Mojo Mail or your server. Mojo can set its own error log. You may find that the error message is enough of a hint to help you out. If not, it might be enough for someone else to help. Copy and Paste the relevant log snippets with any help you ask. =head2 Finding Error Logs =over =item * Check your server error logs. It's very likely that the server you run your account on keeps track of errors from programs, like Mojo Mail. It seems that these error logs are kept in a different place in every different hosting company's account setup. If you can't find it, you may want to ask them. If you simply cannot find the error log, set one up specifically for Mojo Mail. =item * Setting up the Mojo Mail Error Log. There's a variable in the Config.pm file called, $MOJO_ERROR_LOG. Setting this variable to an B will produce a error log at that location. Usually, the file does not have to exist beforehand, but Mojo must have permissions to write a file at the location you specify. If you simply cannot set up an error log for Mojo Mail, have Mojo print errors to your web browser =item * Having Mojo Mail Print Errors to your Web Browser. Somewhere close to the top of the B is a line that reads: # use CGI::Carp "fatalsToBrowser"; By changing this one line to read: use CGI::Carp "fatalsToBrowser"; You will print errors to your web browser. This is off by default for security reasons. =back =head1 Where To Get Help It's best not to ask the developer (meaning me) for help right off the bat. Support questions take time away from development of the program itself and possibly fixing the problems found. The following resources are places that I use myself to answer questions and give support. It's much better to answer a question once than to have to answer it a million times. If you do email me personally and don't get a reply, please don't feel like you've been forgotten, it's just not a very good way to ask support q's about the program. I hope you can imagine how much e-mail I receive a day. I am presently a full time student and I try to have my various projects/lives conflict as little as possible with each other. Try to search for the same problem you're having in the below resources before starting a new thread: =head2 Mailing Lists http://knowledgematters.net currently hosts discussion lists on Mojo Mail: http://www.knowledgematters.net/bin/mojo/mojo.cgi =head2 Discussion Forums MojoHelp hosts a discussion forum about Mojo Mail: http://www.mojohelp.com/forums/ =head1 Filling Out a Bug Report Bug Reports are very much welcome, as the resources I have to test are limited. Bug reports can be filled out here: http://sourceforge.net/tracker/?group_id=13002&atid=113002 Please put the version of Mojo Mail that you're using in the subject of the bug report, it really helps. If a bug is already reported, don't report it again, but if you can add anything to the previous report, that's just fine. =head1 Be A Part of the Support Community If you do see a problem posted that you know the solution to, feel free to put your two cents in! =cut