pkg://jitterbug-1.6.2-1.src.rpm:100906/jitterbug-1.6.2.tar.gz
info downloads
jitterbug-1.6.2/ 40755 1776 1756 0 6627124533 14211 5 ustar jitter-bugs jitterbug jitterbug-1.6.2/COPYING 100644 1776 1756 43076 6424366260 15373 0 ustar jitter-bugs jitterbug GNU GENERAL PUBLIC LICENSE
Version 2, June 1991
Copyright (C) 1989, 1991 Free Software Foundation, Inc.
675 Mass Ave, Cambridge, MA 02139, USA
Everyone is permitted to copy and distribute verbatim copies
of this license document, but changing it is not allowed.
Preamble
The licenses for most software are designed to take away your
freedom to share and change it. By contrast, the GNU General Public
License is intended to guarantee your freedom to share and change free
software--to make sure the software is free for all its users. This
General Public License applies to most of the Free Software
Foundation's software and to any other program whose authors commit to
using it. (Some other Free Software Foundation software is covered by
the GNU Library General Public License instead.) You can apply it to
your programs, too.
When we speak of free software, we are referring to freedom, not
price. Our General Public Licenses are designed to make sure that you
have the freedom to distribute copies of free software (and charge for
this service if you wish), that you receive source code or can get it
if you want it, that you can change the software or use pieces of it
in new free programs; and that you know you can do these things.
To protect your rights, we need to make restrictions that forbid
anyone to deny you these rights or to ask you to surrender the rights.
These restrictions translate to certain responsibilities for you if you
distribute copies of the software, or if you modify it.
For example, if you distribute copies of such a program, whether
gratis or for a fee, you must give the recipients all the rights that
you have. You must make sure that they, too, receive or can get the
source code. And you must show them these terms so they know their
rights.
We protect your rights with two steps: (1) copyright the software, and
(2) offer you this license which gives you legal permission to copy,
distribute and/or modify the software.
Also, for each author's protection and ours, we want to make certain
that everyone understands that there is no warranty for this free
software. If the software is modified by someone else and passed on, we
want its recipients to know that what they have is not the original, so
that any problems introduced by others will not reflect on the original
authors' reputations.
Finally, any free program is threatened constantly by software
patents. We wish to avoid the danger that redistributors of a free
program will individually obtain patent licenses, in effect making the
program proprietary. To prevent this, we have made it clear that any
patent must be licensed for everyone's free use or not licensed at all.
The precise terms and conditions for copying, distribution and
modification follow.
GNU GENERAL PUBLIC LICENSE
TERMS AND CONDITIONS FOR COPYING, DISTRIBUTION AND MODIFICATION
0. This License applies to any program or other work which contains
a notice placed by the copyright holder saying it may be distributed
under the terms of this General Public License. The "Program", below,
refers to any such program or work, and a "work based on the Program"
means either the Program or any derivative work under copyright law:
that is to say, a work containing the Program or a portion of it,
either verbatim or with modifications and/or translated into another
language. (Hereinafter, translation is included without limitation in
the term "modification".) Each licensee is addressed as "you".
Activities other than copying, distribution and modification are not
covered by this License; they are outside its scope. The act of
running the Program is not restricted, and the output from the Program
is covered only if its contents constitute a work based on the
Program (independent of having been made by running the Program).
Whether that is true depends on what the Program does.
1. You may copy and distribute verbatim copies of the Program's
source code as you receive it, in any medium, provided that you
conspicuously and appropriately publish on each copy an appropriate
copyright notice and disclaimer of warranty; keep intact all the
notices that refer to this License and to the absence of any warranty;
and give any other recipients of the Program a copy of this License
along with the Program.
You may charge a fee for the physical act of transferring a copy, and
you may at your option offer warranty protection in exchange for a fee.
2. You may modify your copy or copies of the Program or any portion
of it, thus forming a work based on the Program, and copy and
distribute such modifications or work under the terms of Section 1
above, provided that you also meet all of these conditions:
a) You must cause the modified files to carry prominent notices
stating that you changed the files and the date of any change.
b) You must cause any work that you distribute or publish, that in
whole or in part contains or is derived from the Program or any
part thereof, to be licensed as a whole at no charge to all third
parties under the terms of this License.
c) If the modified program normally reads commands interactively
when run, you must cause it, when started running for such
interactive use in the most ordinary way, to print or display an
announcement including an appropriate copyright notice and a
notice that there is no warranty (or else, saying that you provide
a warranty) and that users may redistribute the program under
these conditions, and telling the user how to view a copy of this
License. (Exception: if the Program itself is interactive but
does not normally print such an announcement, your work based on
the Program is not required to print an announcement.)
These requirements apply to the modified work as a whole. If
identifiable sections of that work are not derived from the Program,
and can be reasonably considered independent and separate works in
themselves, then this License, and its terms, do not apply to those
sections when you distribute them as separate works. But when you
distribute the same sections as part of a whole which is a work based
on the Program, the distribution of the whole must be on the terms of
this License, whose permissions for other licensees extend to the
entire whole, and thus to each and every part regardless of who wrote it.
Thus, it is not the intent of this section to claim rights or contest
your rights to work written entirely by you; rather, the intent is to
exercise the right to control the distribution of derivative or
collective works based on the Program.
In addition, mere aggregation of another work not based on the Program
with the Program (or with a work based on the Program) on a volume of
a storage or distribution medium does not bring the other work under
the scope of this License.
3. You may copy and distribute the Program (or a work based on it,
under Section 2) in object code or executable form under the terms of
Sections 1 and 2 above provided that you also do one of the following:
a) Accompany it with the complete corresponding machine-readable
source code, which must be distributed under the terms of Sections
1 and 2 above on a medium customarily used for software interchange; or,
b) Accompany it with a written offer, valid for at least three
years, to give any third party, for a charge no more than your
cost of physically performing source distribution, a complete
machine-readable copy of the corresponding source code, to be
distributed under the terms of Sections 1 and 2 above on a medium
customarily used for software interchange; or,
c) Accompany it with the information you received as to the offer
to distribute corresponding source code. (This alternative is
allowed only for noncommercial distribution and only if you
received the program in object code or executable form with such
an offer, in accord with Subsection b above.)
The source code for a work means the preferred form of the work for
making modifications to it. For an executable work, complete source
code means all the source code for all modules it contains, plus any
associated interface definition files, plus the scripts used to
control compilation and installation of the executable. However, as a
special exception, the source code distributed need not include
anything that is normally distributed (in either source or binary
form) with the major components (compiler, kernel, and so on) of the
operating system on which the executable runs, unless that component
itself accompanies the executable.
If distribution of executable or object code is made by offering
access to copy from a designated place, then offering equivalent
access to copy the source code from the same place counts as
distribution of the source code, even though third parties are not
compelled to copy the source along with the object code.
4. You may not copy, modify, sublicense, or distribute the Program
except as expressly provided under this License. Any attempt
otherwise to copy, modify, sublicense or distribute the Program is
void, and will automatically terminate your rights under this License.
However, parties who have received copies, or rights, from you under
this License will not have their licenses terminated so long as such
parties remain in full compliance.
5. You are not required to accept this License, since you have not
signed it. However, nothing else grants you permission to modify or
distribute the Program or its derivative works. These actions are
prohibited by law if you do not accept this License. Therefore, by
modifying or distributing the Program (or any work based on the
Program), you indicate your acceptance of this License to do so, and
all its terms and conditions for copying, distributing or modifying
the Program or works based on it.
6. Each time you redistribute the Program (or any work based on the
Program), the recipient automatically receives a license from the
original licensor to copy, distribute or modify the Program subject to
these terms and conditions. You may not impose any further
restrictions on the recipients' exercise of the rights granted herein.
You are not responsible for enforcing compliance by third parties to
this License.
7. If, as a consequence of a court judgment or allegation of patent
infringement or for any other reason (not limited to patent issues),
conditions are imposed on you (whether by court order, agreement or
otherwise) that contradict the conditions of this License, they do not
excuse you from the conditions of this License. If you cannot
distribute so as to satisfy simultaneously your obligations under this
License and any other pertinent obligations, then as a consequence you
may not distribute the Program at all. For example, if a patent
license would not permit royalty-free redistribution of the Program by
all those who receive copies directly or indirectly through you, then
the only way you could satisfy both it and this License would be to
refrain entirely from distribution of the Program.
If any portion of this section is held invalid or unenforceable under
any particular circumstance, the balance of the section is intended to
apply and the section as a whole is intended to apply in other
circumstances.
It is not the purpose of this section to induce you to infringe any
patents or other property right claims or to contest validity of any
such claims; this section has the sole purpose of protecting the
integrity of the free software distribution system, which is
implemented by public license practices. Many people have made
generous contributions to the wide range of software distributed
through that system in reliance on consistent application of that
system; it is up to the author/donor to decide if he or she is willing
to distribute software through any other system and a licensee cannot
impose that choice.
This section is intended to make thoroughly clear what is believed to
be a consequence of the rest of this License.
8. If the distribution and/or use of the Program is restricted in
certain countries either by patents or by copyrighted interfaces, the
original copyright holder who places the Program under this License
may add an explicit geographical distribution limitation excluding
those countries, so that distribution is permitted only in or among
countries not thus excluded. In such case, this License incorporates
the limitation as if written in the body of this License.
9. The Free Software Foundation may publish revised and/or new versions
of the General Public License from time to time. Such new versions will
be similar in spirit to the present version, but may differ in detail to
address new problems or concerns.
Each version is given a distinguishing version number. If the Program
specifies a version number of this License which applies to it and "any
later version", you have the option of following the terms and conditions
either of that version or of any later version published by the Free
Software Foundation. If the Program does not specify a version number of
this License, you may choose any version ever published by the Free Software
Foundation.
10. If you wish to incorporate parts of the Program into other free
programs whose distribution conditions are different, write to the author
to ask for permission. For software which is copyrighted by the Free
Software Foundation, write to the Free Software Foundation; we sometimes
make exceptions for this. Our decision will be guided by the two goals
of preserving the free status of all derivatives of our free software and
of promoting the sharing and reuse of software generally.
NO WARRANTY
11. BECAUSE THE PROGRAM IS LICENSED FREE OF CHARGE, THERE IS NO WARRANTY
FOR THE PROGRAM, TO THE EXTENT PERMITTED BY APPLICABLE LAW. EXCEPT WHEN
OTHERWISE STATED IN WRITING THE COPYRIGHT HOLDERS AND/OR OTHER PARTIES
PROVIDE THE PROGRAM "AS IS" WITHOUT WARRANTY OF ANY KIND, EITHER EXPRESSED
OR IMPLIED, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF
MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE. THE ENTIRE RISK AS
TO THE QUALITY AND PERFORMANCE OF THE PROGRAM IS WITH YOU. SHOULD THE
PROGRAM PROVE DEFECTIVE, YOU ASSUME THE COST OF ALL NECESSARY SERVICING,
REPAIR OR CORRECTION.
12. IN NO EVENT UNLESS REQUIRED BY APPLICABLE LAW OR AGREED TO IN WRITING
WILL ANY COPYRIGHT HOLDER, OR ANY OTHER PARTY WHO MAY MODIFY AND/OR
REDISTRIBUTE THE PROGRAM AS PERMITTED ABOVE, BE LIABLE TO YOU FOR DAMAGES,
INCLUDING ANY GENERAL, SPECIAL, INCIDENTAL OR CONSEQUENTIAL DAMAGES ARISING
OUT OF THE USE OR INABILITY TO USE THE PROGRAM (INCLUDING BUT NOT LIMITED
TO LOSS OF DATA OR DATA BEING RENDERED INACCURATE OR LOSSES SUSTAINED BY
YOU OR THIRD PARTIES OR A FAILURE OF THE PROGRAM TO OPERATE WITH ANY OTHER
PROGRAMS), EVEN IF SUCH HOLDER OR OTHER PARTY HAS BEEN ADVISED OF THE
POSSIBILITY OF SUCH DAMAGES.
END OF TERMS AND CONDITIONS
Appendix: How to Apply These Terms to Your New Programs
If you develop a new program, and you want it to be of the greatest
possible use to the public, the best way to achieve this is to make it
free software which everyone can redistribute and change under these terms.
To do so, attach the following notices to the program. It is safest
to attach them to the start of each source file to most effectively
convey the exclusion of warranty; and each file should have at least
the "copyright" line and a pointer to where the full notice is found.
<one line to give the program's name and a brief idea of what it does.>
Copyright (C) 19yy <name of author>
This program is free software; you can redistribute it and/or modify
it under the terms of the GNU General Public License as published by
the Free Software Foundation; either version 2 of the License, or
(at your option) any later version.
This program is distributed in the hope that it will be useful,
but WITHOUT ANY WARRANTY; without even the implied warranty of
MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the
GNU General Public License for more details.
You should have received a copy of the GNU General Public License
along with this program; if not, write to the Free Software
Foundation, Inc., 675 Mass Ave, Cambridge, MA 02139, USA.
Also add information on how to contact you by electronic and paper mail.
If the program is interactive, make it output a short notice like this
when it starts in an interactive mode:
Gnomovision version 69, Copyright (C) 19yy name of author
Gnomovision comes with ABSOLUTELY NO WARRANTY; for details type `show w'.
This is free software, and you are welcome to redistribute it
under certain conditions; type `show c' for details.
The hypothetical commands `show w' and `show c' should show the appropriate
parts of the General Public License. Of course, the commands you use may
be called something other than `show w' and `show c'; they could even be
mouse-clicks or menu items--whatever suits your program.
You should also get your employer (if you work as a programmer) or your
school, if any, to sign a "copyright disclaimer" for the program, if
necessary. Here is a sample; alter the names:
Yoyodyne, Inc., hereby disclaims all copyright interest in the program
`Gnomovision' (which makes passes at compilers) written by James Hacker.
<signature of Ty Coon>, 1 April 1989
Ty Coon, President of Vice
This General Public License does not permit incorporating your program into
proprietary programs. If your program is a subroutine library, you may
consider it more useful to permit linking proprietary applications with the
library. If this is what you want to do, use the GNU Library General
Public License instead of this License.
jitterbug-1.6.2/docs/ 40755 1776 1756 0 6627124477 15150 5 ustar jitter-bugs jitterbug jitterbug-1.6.2/docs/JitterBug.txt 100644 1776 1756 15205 6516537373 17730 0 ustar jitter-bugs jitterbug JitterBug 1.5
-------------
This file describes the basic usage of JitterBug and what all the
different fields are for. The documentation is by no means complete
but it should be enough to get new users going.
It is *highly* recommended that you read both this file and all of
CONFIG.txt.
Login Screen
------------
The first screen (ie. web page) you see when you connect to JitterBug
is the login screen. If you are connecting as a guest user then this
screen is automatically bypassed and you are taken straight to the
main screen. This screen is also bypassed if you use the "group
authentication" option.
At the login screen you should select your JitterBug username from the
supplied list and press "Enter System".
If you do not have a username yet then enter the username you want in
the space provided and press "Create User". After that your new
username should appear in the supplied list.
The first time a new user enters the system they will be required to
fill out their user preferences in the preferences screen.
The login screen is also displayed as the bottom pane of the main
screen. This allows you to change user easily. You can also edit your
user preferences and view the system audit trail.
Main Screen
-----------
The main screen is divided into 4 panes.
The top pane is the introduction. It is based on intro.html or
guestintro.html depending on whether you are connected as a guest user
or not. Often these will be setup to contain links to related
resources.
The next pane is the search pane. You can select search criterion here
and press "Select Messages". This affects what messages are displayed
in the directory list pane. See the section on searching for more
details.
The directory list pane is next. This contains a list of the
directories containing all the messages in the system. Next to each
directory the number of messages that match the current search
criterion is displayed. To look at the messages in a directory click
on the directory name. You can also create a new directory by entering
its name and pressing "Create".
The login pane is next. See the description of the login screen above.
Directory View
--------------
The directory view screen shows you the messages in the selected
directory matching the current search criterion. You can page through
the messages using the "next", "prev", "first" and "last" links. The
number of messages displayed per page is customisable in the user
preferences page.
At the top of the directory view there are links to all the other
directories in the system. This is useful for jumping between
directories.
Below this the search pane appears with the same options as the search
pane on the main screen. Changes to the search criterion are carried
over between screens.
The messages themselves are shown in 3 columns. The first column shows
the message id and the number of replies and followups for that
message. Clicking on the message id takes you to the message view
screen for that message.
The 2nd column gives the subject, sender and date of the message. The
3rd column allows you to move the message to another directory. You
can move several messages at once. When you have finished selecting
movements click on "Submit Changes".
The "Notification" field allows you to select who will receive
notification when something changes in this directory. See the
nofification section for details.
Message View
------------
The message view screen views the contents of one message. The initial
message plus any replies and followups are shown, along with any
message notes.
From this screen you can change the notes attached to the message, move
the message to another directory or reply to the message. You can also
edit the notifcation list for this message, allowing you to track
changes to the message.
The "View Audit Trail" button allows you to view changes that have
been made to the message since it arrived.
Compose Screen
--------------
The compose screen is used to compose a reply to a message. You can
change the various mail headers and quote sections of the original
message.
You can also load a previous written FAQ answer or create a new FAQ
answer.
When you have finished composing the reply press "Send" and the reply
is sent. Your signature is added if you selected the signature
checkbox.
Preferences Screen
------------------
The only obligatory fields in the preferences screen are the full name
and email address. The other fields are optional and should be
experimented with for best results.
Replies and Followups
---------------------
A reply is a message that has been sent from JitterBug to answer an
incoming message.
A followup is a reply to a reply. Followups are created when a user
sends a email reply to a JitterBug generated message. Followups are
detected by looking for the PR# automatically added to the subject
line in replies.
Notification
------------
You can ask JitterBug to notify you automatically via email when
certain actions happen. There are two types of notification lists, one
for directories and one for messages.
Notifications will be sent to the email address specified in your user
preferences. Notifications are sent for message movements, incoming
messages or changes to the notes on a message.
Notifications are not sent for actions that you peform yourself.
The names you specify in the notification list can either be JitterBug
usernames or email addresses. You can specify as many as you like in a
comma separated list.
Searching
---------
The search pane allows you to select messages using a regular
expression string search and by looking for particular message
attributes. The regular expression is applies to the full message and
any replies, followups or notes. It can be case sensitive or
case-insensitive.
The message type radio buttons allow you to select what sort of
messages you want. The only option that really needs explanation there
is the "pending" option. A pending message is one where the date on
the last followup is later than both the last reply and the last
change to the message notes.
FAQ Handling
------------
JitterBug maintains a list of FAQ replies. When you have composed a
reply that you think you will need again then before you press send
you should type in a name for the FAQ in the space provided and press
create. The text of your reply will be added as a FAQ. You can then
press send.
When you next are replying to a message and you wish to use a
previously created FAQ then select the FAQ from the drop down list
provided and press load. You can then add any extra comments you wish
and press send.
You can update a FAQ entry by using the save button after loading
it. The current contents of the message window will replace the FAQ.
jitterbug-1.6.2/docs/INSTALL 100644 1776 1756 21633 6555023430 16306 0 ustar jitter-bugs jitterbug INSTALLING Jitterbug
--------------------
This file explains how to set up a basic installation of Jitterbug.
You will need to be owner of the web daemon to setup Jitterbug, and
root to install the binary. You will also probably want to add a mail
alias for your system, since Jitterbug reports are ordinary mail
messages. Some hints about doing this are in the mail subdirectory,
but they are far from complete and will need to be modified or
replaced to do anything useful.
NOTE: In the following I have used as an example the setting up of
JitterBug page for a mythical PACKAGE bug-tracking system. Please
replace PACKAGE in all the following with whatever you want to call
your site. Using different names allows you to setup several JitterBug
sites on one machine.
Also note that the following instructions describe the "standard" way
to setup JitterBug. There are in fact several different ways to do it
each with their own advantges and disadvantages. See the
"ALTERNATIVES" section at the end for more info.
1) Create an account for JitterBug to run in. This isn't strictly
necessary but is the simplest thing to do. I often create an account
called PACKAGE-bugs. This means that new bug reports
enter the system by mailing to PACKAGE-bugs@your.host.name
2) unpack the jitterbug sources somewhere. If you have CVS then it may
be a good idea to fetch the sources via anonymous CVS as this will
allow you to trivailly update them to the latest version at any time
by running "cvs update -d" in the jitterbug directory. See
http://samba.anu.edu.au/cvs.html for details.
3) Go to the source directory and run ./configure
This is an autoconf script, and should pick a reasonable set of
defaults for your system. You may also want to edit jconfig.h, but
most sites won't need to.
4) type 'make' to build the binaries.
5) Create a directory where the JitterBug data files will live. This
must be owned by the account created in step 1. The directory is
normally outside your normal public HTML area. For example, I normally
create a ~PACKAGE-bugs/bug_tracking/ directory.
6) Set up secure access to the jitterbug binary through your web
server. I normally only setup authentication for PACKAGE.private and
leave out authentication for PACKAGE. This way you will have a public
interface called PACKAGE and a private interface called
PACKAGE.private. To do this under Apache edit the file access.conf
like this:
<Location /cgi-bin/PACKAGE.private>
AuthType Basic
AuthName PACKAGE
AuthUserFile /etc/httpd/auth/apache.auth
<Limit GET POST>
require user PACKAGE
</Limit>
</Location>
Then you follow the Apache documentation for the process of setting up
apache.auth. If you don't want to have 'cgi-bin' appear in the URL you can
specify something like this in the Apache file srm.conf:
ScriptAlias /PACKAGE /data/httpd/cgi-bin/PACKAGE
Have a look at the existing ScriptAlias entry for cgi-bin first. You
will need to restart apache (or send it a USR1 signal) for these
changes to take effect.
7) Set up some initial files in the Jitterbug area. Start by copying the
files in config/* to the directory you created in step 5.
8) Copy the jitterbug binary to the cgi-bin directory of your web
daemon. In Apache this is defined by 'ScriptAlias' in srm.conf. You
should name the binary PACKAGE and PACKAGE.private. The two binaries
should be identical. (a hard or soft link will do nicely).
9) Make the permissions on the jitterbug binaries "-rws--x---". The
binaries must be owned by user root. The group of the binary must
be the group that your web server runs as. You have to have root
access to set this up.
On most unixes the commands to achieve this will be:
chown root.nobody PACKAGE PACKAGE.private
chmod 04710 PACKAGE PACKAGE.private
assuming that "nobody" is the group your web server runs as.
The reason that jitterbug should be installed setuid root is to allow it
to use chroot() to limit access to files and to use setuid() and
setgid() to change uid/gid. The first thing jitterbug does after
starting up is to do the chroot() and lose root privilages. This is
done before any processing begins.
Be very careful that these binaries can only be run by your web
server. If an ordinary user can run these binaries (because you setup
the permissions incorrectly) then that user may be able to gain root
access.
Note: it can be run without being setuid root. See the ALTERNATIVES
section below.
10) create a directory called /etc/jitterbug/. Then create a file
called /etc/jitterbug/PACKAGE. This file is your JitterBug config
file for PACKAGE. A simple config file would be:
from address = PACKAGE-bugs@your.host.name
chroot directory = /home/PACKAGE-bugs/bug_tracking
base directory = /
guest gid = 65534
guest uid = 65534
uid = XXXX
gid = YYYY
You must set uid/gid to those of the account you created in step 1.
Set "guest uid" and "guest gid" to an account with minimal privileges
(such as the nobody account) or to an unused uid/gid pair.
There are lots of other options you can set in this config file. See
the rest of the docs for details.
11) copy /etc/jitterbug/PACKAGE to /etc/jitterbug/PACKAGE.private or
make a symbolic link.
12) Connect to http://your.server/cgi-bin/PACKAGE. You should get the
JitterBug guest interface.
13) Connect to http://your.server/cgi-bin/PACKAGE.private. The web
server should first prompt you for a user name and password. You
should then be able to create a new user.
Please note that JitterBug itself does not contain any authentication
code. The username/password prompt is being generated by your web
server. If you have authentication problems then see your web server
documentation.
14) Copy the new_message binary to a directory where it will be
accessible by mail scripts. The usual location would be $HOME/bin/
in the account of the user you setup in step 1. The new_message binary
should not be setuid.
15) Add a mail alias and scripts so that new messages arrive in an
appropriate directory in Jitterbug. In the simplest case this would just
be a .forward file containing:
"|/path/to/new_message PACKAGE"
(the quotes are important).
In more complex cases you may wish to use procmail.
The new_message program accepts a single mail message on standard
input and examines it to see if it is a reply to an existing message
in the system. If it is then the message is processed as a
followup. Otherwise a new problem report number is assigned and the
message is placed in the incoming directory.
new_message should be run by your mailer with a uid/gid which has
write permission in the base directory. This will happen automatically
if you have setup a jitterbug user as recommended in step 1 and you
use a .forward file.
16) Customise the files that were copied from the config directory to
your data directory in step 7. The main files that need customising
are intro.html, guestintro.html, footer.html and reportform.html.
If you have problems then look at
http://samba.anu.edu.au/cgi-bin/jitterbug. Maybe someone has reported something
similar, or perhaps after you have checked the documentation again and looked
through the jitterbug system you may like to submit your own bug report.
ALTERNATIVES
------------
It is possible to setup JitterBug in many ways. For example, you can
avoid the chroot() by setting "base directory" to your data directory
and removing the "chroot directory" config line. This may allow you to
get JitterBug working on systems such as Solaris where it is difficult
to make socket calls in a chrooted environment.
You can also also avoid making the binaries setuid-root by not using
chroot and setting the "guest uid" and "guest gid" to those of your
web server. You will need to make PACKAGE.private setuid/setgid to the
uid/gid of the account that you created in step 1, or you can even
avoid that by setting uid/gid to those of your web server.
Using either of these two alternatives changes the security
implications of JitterBug. If it is not run setuid-root then it can't
chroot() which means that if a bug is discovered in JitterBug then
access to files outside the data directory may be possible. You have
to weigh up this risk against the risk that a local user manages to
run the jitterbug binary from outside the web server.
CONFIG FILE
-----------
A more complete description of each option in the JitterBug config
file is given in CONFIG.txt
SOLARIS
-------
If you are running JitterBug under Solaris and use the chroot option
and use the internal mailer then you will need a bunch of
device/config files in the chroot directory to enable socket calls
to be used. The following commands may help:
mkdir dev
mknod dev/tcp c 11 42
chmod a+rw dev/tcp
mknod dev/conslog c 11 42
chmod a+rw dev/conslog
mkdir etc
cp /etc/netconfig etc/netconfig
You may also like to set your chroot directory to one level above your
base directory so the dev and etc directories don't appear inside
JitterBug. For example, you could set:
chroot directory = /home/PACKAGE-bugs
base directory = /bug_tracking
jitterbug-1.6.2/docs/CONFIG.txt 100644 1776 1756 24002 6627124477 16771 0 ustar jitter-bugs jitterbug This describes the JitterBug config file option. The config file is
stored in the directory /etc/jitterbug/ and should be readable by the
user that your web server runs as.
The name of the config file is taken as the name of the cgi-bin binary
that JitterBug is installed as. This allows you to have several
different JitterBug pages on one site by using different cgi-bin names
and different config files.
Simple Example
--------------
A simple example config file is:
from address = rsync-bugs@samba.anu.edu.au
chroot directory = /usr/people/rsync-bugs/bug_tracking
base directory = /
guest gid = 65534
guest uid = 65534
uid = 1021
gid = 1005
This is the one I use for rsync at http://samba.anu.edu.au/rsync/
CONFIGRATION OPTIONS
--------------------
from address
------------
This is the address that mail from JitterBug will appear to come
from. It is also the address that new bugs reports should be sent to.
chroot directory
----------------
This is the absolute path of the directory that JitterBug should
chroot() to on startup. This is one as a security measure as it
ensures that JitterBug cannot access any files outside the specified
directory. You can avoid the chroot() by leaving out this line in the
config file.
base directory
--------------
This is the directory that contains the JitterBug data files. The
pathname is relative to the chroot directory if you have specified
one. Normally base directory is set to /.
base url
--------
This is the base URL you want to appear in emailed notifications. If
you set this then JitterBug will supply a complete URL that points
directly at the message, allowing users to view the message with one
click from their mail program. The url will be constructed from this
URL with ?findid=PRNUM appended.
guest gid, guest uid
--------------------
These options specify the uid/gid that JitterBug should use when a
guest connection is made. This uid/gid pair should have minimal
privileges.
uid, gid
--------
These options specify the uid/gid that JitterBug should use when a
non-guest connection is made. This uid/gid pair should have write
permission in the data directory.
You must use the numeric form of the uid and gid.
incoming
--------
This is the default directory which new files are placed into when
processed by new_message. It defaults to "incoming".
mailer
------
Normally JitterBug uses an internal SMTP mailer for sending mail. You
can force it to instead use an external mailer by specifying the
"mailer" option. This should be the full path (relative to the
chrooted directory) of a mailer that accepts mail on standard input.
To use sendmail as your mailer you may wish to use the option
mailer = /usr/sbin/sendmail -oi -oem -t
The main reason for using the mailer option is if the internal mailer
in JitterBug fails to work correctly. This may happen because it is
very fussy and does not handle a wide range of SMTP server responses.
If you do use a external mailer and run JitterBug with the chroot
option then you will need to setup libraries, devices and config files
for your mailer in the chrooted area.
smtp address
------------
If using the internal mailer (ie. you have not set the "mailer"
option) then this specifies the IP address of the SMTP server you wish
to use for delivery. You normally don't need to specify this as the
default of "127.0.0.1" is correct in most situations.
title
-----
This sets the title shown at the top of the JitterBug web pages. It
defaults to "JitterBug".
auth user
---------
This sets the username that must be entered for authentication to be
accepted from your web server. Normally you can leave this option out
and JitterBug will accept any user that your web server
authenticates.
display binary
--------------
Normally JitterBug replaces any binary characters in emails with a
full-stop. This is to prevent browsers from getting very confused with
some binary characters. JitterBug decides whether a character is
binary using your systems isprint() macro. For some languages/systems
you will find that this prevents you from properly displaying local
character sets. In that case set "display binary = yes" and you will
see all characters.
background
----------
JitterBug normally puts a default background image on each web
page. This can be overridden with solid colour backgrounds in each
users preferences page or you can override it in the config file by
specifying a different background image. It defaults to
"/images/back.gif"
group authentication
--------------------
If you use the group authentication features in your web server
(apache can do this) then you may wish to set "group authentication =
yes" in your config file. This tell JitterBug to skip the login page
and use the username supplied by your web server. Note that the
username must already exist within JitterBug and that if it doesn't
then the normal login page is shown.
search program
--------------
Normally the searching in JitterBug is done using internal regular
expression routines. If you have lot of messages in the system then
this gets too slow and you will need to specify a fast external search
program that uses a pre-built index. For example, you can use glimpse
by specifying
search program = /usr/bin/glimpse -wyli -H /path/to/data/directory -e
You will also need to setup a cron job to automatically reindex the
data at regular intervals.
Note that if you specify a search program and use the chroot option
then you will need to setup appropriate libraries, devices etc for it
to use in the chrooted area.
gzip path
---------
When users enable "gzip encoding" in their preferences page JitterBug
needs to launch gzip to compress all pages being sent. The default
path is /usr/bin/gzip. If this isn't correct then use the gzip path
option to specify the path to a local version of gzip. Make sure this
path is valid in the chrooted directory.
forward all
-----------
You can set "forward all" to a comma separated list of email addresses
that should receive copies of all messages entering the
system. new_message will forward incoming messages to these addresses
after adding the PR# to the subject line and setting the bug tracking
reply address in the CC line.
forward public
--------------
"forward public" is like "forward all" except that messges that are
marked as PRIVATE are not forwarded.
reply strings
-------------
When a message arrives it is scanned for a PR#. If a PR# is found then
normally the message is appended as a followup to the existing
message. If reply strings is set then the From address in the followup
is checked against each of the reply strings and if a reply string is
found as a substring of the From then the message is treated as a
reply not a followup. This is useful in combination with the "forward
all" code.
guest download
--------------
Normally JitterBug does not allow file download for guest users. You
can enable file download for guests by setting "guest download = yes"
gzip download
-------------
If this is enabled with "gzip download = yes" then all guest downloads
will be gzipped regardless of the setting of the guest gzip encoding
preference.
pr identifier
-------------
Some sites may be running many JitterBugs. This option allows the 'PR#'
string to be set to something else, i.e NUM#, or BUG#.
OTHER FILES
-----------
This section lists the various files used by JitterBug. Some of these
are automatically generated by JitterBug and others must be hand
edited to reflect your local configuration. Most list in the base
directory as specified in your config file.
users
This file contains the list of JitterBug users on your
system. It is updated automatically by the "create user"
action.
system.audit
This file is where system actions (such as logging in or
creating users) are logged. If you want guest logins to be
logged then this file must be writeable by both the guest and
non-guest uids.
autoreply.txt
If this file exists then any new messages arriving in the
"incoming" directory when processed by new_message will
automatically generate a reply message with this file as the
message body. You would typically use this for a "thanks for
your bug report style message". A sample script for
automatically generating this file from your current FAQ list
is supplied in the source directory. You may wish to call this
script from cron.
If the string %PRNUM% appears in this file then the message id
is subsitutued. This is useful for somehting like:
please see http://my.host/package?findid=%PRNUM%
which allows users to click on the supplied URL to see
progress on the message.
JitterBug won't send an autoreply if the subject of the
message starts with "Re:".
intro.html
This contains the basic welcome screen you wish to display to
non-guest users. Put in any html you like.
guestintro.html
This contains the basic welcome screen you wish to display to
guest users. Put in any html you like.
footer.html
This file is inserted at the bottom of every JitterBug
page. You may wish to put a contact email address or similar
in here.
header.html
If this file exists then it will be put at the top of each
page displayed instead of the automatically generated
headers. This is useful if you don't like the default layout
of JitterBug and want to change it a lot. For example, several
sites use header.html to enclose the whole of JitterBug in a
table and place a border around the table with a logo.
.nextid
This file contains the net message id the system will
assign. It is automatically generated.
.faq/
This directory is where JitterBug places FAQ entries as you
create them. The file names in the directory are the FAQ
titles.
*.prefs
These files contain the preferences of individual users. Don't
edit by hand, instead use the preferences page.
reportform.html
This file contains the "bug submission" form you wish to use
for your package. It can contain anything you like, but make
sure you name any form variables starting with opt_ otherwise
they won't get processed by JitterBug.
jitterbug-1.6.2/mail/ 40755 1776 1756 0 6523241065 15126 5 ustar jitter-bugs jitterbug jitterbug-1.6.2/mail/forward 100644 1776 1756 31 6445635016 16552 0 ustar jitter-bugs jitterbug |/usr/local/bin/procmail
jitterbug-1.6.2/mail/README 100644 1776 1756 1370 6523241065 16104 0 ustar jitter-bugs jitterbug Jitterbug Mail Processing
-------------------------
This directory contains an example of how to get JitterBug to place
different incoming messages into different JitterBug directories.
If you just want all messages to go into an "incoming" directory then
just use a .forward file of
"|/path/to/new_message PACKAGE"
(the quotes are important)
To do something fancier you can use procmail to select what messages
go where. Copy the sample forward file to ~/.forward and the
procmailrc file to ~/.procmailrc. Edit to suit.
The new_message program takes an optional second argument which
specifies which JitterBug directory to put messages in. In the example
given in procmailrc CVS commit messages are automatically put into the
CVS JitterBug directory.
jitterbug-1.6.2/mail/procmailrc 100644 1776 1756 376 6516540072 17271 0 ustar jitter-bugs jitterbug PATH=/bin:/usr/bin:/usr/local/bin:/usr/contrib/bin
MAILDIR=$HOME/Mail
DEFAULT=$HOME/InBox
LOGFILE=$MAILDIR/procmail.log
LOCKFILE=$HOME/.lockmail
:0
* ^Subject: CVS update:
| $HOME/bin/new_message PACKAGE CVS
:0 c
| $HOME/bin/new_message PACKAGE incoming
jitterbug-1.6.2/cvs.log 100644 1776 1756 262766 6627124534 15670 0 ustar jitter-bugs jitterbug
****************************************
Date: Saturday October 25, 1997 @ 18:54
Author: tridge
Update of /data/cvs/jitterbug/source
In directory samba:/data/people/tridge/jitterbug/source
Modified Files:
config.h
Log Message:
This is C code, not a shell script.
Lines starting with a # aren't comments :-)
****************************************
Date: Saturday October 25, 1997 @ 18:54
Author: tridge
Update of /data/cvs/jitterbug/source
In directory samba:/data/people/tridge/jitterbug/source
Modified Files:
jitterbug.c
Log Message:
fix some coding errors
****************************************
Date: Monday October 27, 1997 @ 0:54
Author: tridge
Update of /data/cvs/jitterbug/source
In directory samba:/data/people/tridge/jitterbug/source
Modified Files:
jitterbug.c
Log Message:
change the mail headers handling
****************************************
Date: Monday October 27, 1997 @ 1:30
Author: tridge
Update of /data/cvs/jitterbug/source
In directory samba:/data/people/tridge/jitterbug/source
Modified Files:
jitterbug.c
Log Message:
display URLs in mail messages as clickable links
****************************************
Date: Monday October 27, 1997 @ 12:39
Author: tridge
Update of /data/cvs/jitterbug
In directory samba:/data/people/tridge/jitterbug
Modified Files:
README
Log Message:
minor README change
****************************************
Date: Monday October 27, 1997 @ 12:39
Author: tridge
Update of /data/cvs/jitterbug/config
In directory samba:/data/people/tridge/jitterbug/config
Modified Files:
guestintro.html intro.html jitterbug_help.html
Log Message:
minor changes
****************************************
Date: Monday October 27, 1997 @ 12:42
Author: tridge
Update of /data/cvs/jitterbug/docs
In directory samba:/data/people/tridge/jitterbug/docs
Modified Files:
INSTALL
Log Message:
there were lots of things that needed changing in the INSTALL
instructions. There is more to do but at least this is a bit more
accurate.
- The binary needs to have permissions 04710
- it need to be owned by root
- the group needs to match the web server
- the data area should (normally) be _outside_ your normal web document area.
- there is no file called "incoming"
****************************************
Date: Monday October 27, 1997 @ 12:44
Author: tridge
Update of /data/cvs/jitterbug/docs
In directory samba:/data/people/tridge/jitterbug/docs
Modified Files:
jitterbug.doc
Log Message:
fix the notes on security
remove the note about not being able to use checkboxes. You _can_ use
checkboxes. See the addsignature and the fullheaders example. You just
have to use them carefully.
****************************************
Date: Monday October 27, 1997 @ 12:52
Author: tridge
Update of /data/cvs/jitterbug/source
In directory samba:/data/people/tridge/jitterbug/source
Modified Files:
config.h
Log Message:
more explanations in config.h
****************************************
Date: Monday October 27, 1997 @ 15:44
Author: tridge
Update of /data/cvs/jitterbug/source
In directory samba:/data/people/tridge/jitterbug/source
Modified Files:
cgi.c
Log Message:
removed cgi_flush_variables(). I didn't realise Dan had added it! The
main code relies on the variables NOT being flushed.
****************************************
Date: Monday October 27, 1997 @ 15:51
Author: tridge
Update of /data/cvs/jitterbug/source
In directory samba:/data/people/tridge/jitterbug/source
Modified Files:
Makefile
Log Message:
add an install target
****************************************
Date: Monday October 27, 1997 @ 15:53
Author: tridge
Update of /data/cvs/jitterbug/source
In directory samba:/data/people/tridge/jitterbug/source
Modified Files:
jitterbug.c
Log Message:
support _ and - in URLs
change to generic bug submission code. You can now customise
reportform.html without changing the source code
****************************************
Date: Monday October 27, 1997 @ 15:53
Author: tridge
Update of /data/cvs/jitterbug/source
In directory samba:/data/people/tridge/jitterbug/source
Modified Files:
proto.h
Log Message:
****************************************
Date: Monday October 27, 1997 @ 15:54
Author: tridge
Update of /data/cvs/jitterbug/config
In directory samba:/data/people/tridge/jitterbug/config
Modified Files:
reportform.html
Log Message:
updated example to use generic method
****************************************
Date: Monday October 27, 1997 @ 23:43
Author: dan
Update of /data/cvs/jitterbug/source
In directory samba:/tmp/cvs-serv4718
Removed Files:
jitterbug.doc
Log Message:
This was a second copy of docs/jitterbug.doc
****************************************
Date: Friday October 31, 1997 @ 18:07
Author: dan
Update of /data/cvs/jitterbug/source
In directory samba:/tmp/cvs-serv26608
Removed Files:
Makefile
Log Message:
?For some reason cvs gave me "Up-to-date check failed for `Makefile'" when
trying to remove it at the same time as adding other files.
****************************************
Date: Friday October 31, 1997 @ 18:11
Author: dan
Update of /data/cvs/jitterbug/source
In directory samba:/tmp/cvs-serv12221
Added Files:
Makefile.in config.guess config.sub configure configure.in
install-sh
Log Message:
Use autoconf to generate Makefile. Tested on Linux and IRIX, Solaris
might work too. Autoconf really _is_ good, except that it involves a whole
stack of files in the source directory (unless you get a bit clever.)
A side effect of using autoconf is that it doesn't matter how much you change
your local Makefile it doesn't hurt the CVS tree and other developers :-)
Dan Shearer
****************************************
Date: Friday October 31, 1997 @ 18:33
Author: dan
Update of /data/cvs/jitterbug/docs
In directory samba:/tmp/cvs-serv13767/docs
Modified Files:
INSTALL
Log Message:
Update docs/INSTALL for autoconf
Remove unused var in jitterbug.c
****************************************
Date: Friday October 31, 1997 @ 18:33
Author: dan
Update of /data/cvs/jitterbug/source
In directory samba:/tmp/cvs-serv13767/source
Modified Files:
jitterbug.c
Log Message:
Update docs/INSTALL for autoconf
Remove unused var in jitterbug.c
****************************************
Date: Monday November 3, 1997 @ 22:53
Author: dan
Update of /data/cvs/jitterbug/source
In directory samba:/tmp/cvs-serv23323
Modified Files:
jitterbug.c
Log Message:
Make fullheaders setting case insensitive. Some silly PC mailers like to use
uppercase for certain headers.
RFC822 says:
When matching any other syntactic unit, case is to be ignored.
For example, the field-names "From", "FROM", "from", and even
"FroM" are semantically equal and should all be treated identically."
Dan
****************************************
Date: Monday November 3, 1997 @ 23:18
Author: dan
Update of /data/cvs/jitterbug/source
In directory samba:/tmp/cvs-serv20270
Modified Files:
util.c
Log Message:
Make getmailheader() case insensitive
****************************************
Date: Tuesday November 4, 1997 @ 16:37
Author: tridge
Update of /data/cvs/jitterbug/source
In directory samba:/data/people/tridge/jitterbug/source
Modified Files:
jitterbug.c
Log Message:
when replying to a followup use the From address in the followup, not
the original From address
****************************************
Date: Thursday November 20, 1997 @ 16:18
Author: tridge
Update of /data/cvs/jitterbug/source
In directory samba:/tmp/cvs-serv16399
Modified Files:
util.c
Log Message:
change from NULL to %c in the strftime() format. NULL should have
worked, but it seems to be not supported under Linux.
****************************************
Date: Friday November 21, 1997 @ 13:02
Author: tridge
Update of /data/cvs/jitterbug/source
In directory samba:/tmp/cvs-serv5769
Modified Files:
jitterbug.c smtp.c
Log Message:
allow ? as a wildcard in smtp_waitfor() and use it to handle sendmail
systems
****************************************
Date: Monday November 24, 1997 @ 22:23
Author: dan
Update of /data/cvs/jitterbug/source
In directory samba:/tmp/cvs-serv21153
Modified Files:
jitterbug.c proto.h util.c
Added Files:
.cvsignore
Removed Files:
config.h
Log Message:
Fixed some bugs, make some changes, prepare for making it possible to make
links between PR nos.
jitterbug.c:
added valid_user()
fix bug where a null username was offered as the default choice when first
entering the system
added count_links (but not used yet because links aren't done)
added "." every time load_dir_list called so it doesn't have to be assumed
in util.c
make it clear to user that "status level" == directory
replace code to read in users and put in a sorted array with a call to new
util.c function load_file_list
util.c:
Add MAX_LINES const
add dirname parameter to load_dir_list. If util.c is meant to be general it
shouldn't assume the default dir any more than load_file_list should assume
a file name of "users".
add load_file_list, very similar to load_dir_list
Fixed some bugs, make some changes, prepare for making it possible to
link PRs to one another via a file called <id>.links but haven't done the
code for it yet.
jitterbug.c:
added valid_user()
fix bug where a null username was offered as the default choice when first
entering the system
added count_links (but not used yet because links aren't done)
added "." every time load_dir_list called to match new definition in util.c
make it clear to user that "status level" == directory
replace code to read in users and put in a sorted array with a call to new
util.c function load_file_list
util.c:
Add MAX_LINES const
add dirname parameter to load_dir_list. If util.c is meant to be general it
shouldn't assume the default dir any more than load_file_list should assume
a file name of "users".
add load_file_list, very similar to load_dir_list
proto.h: the usual
added count_links (but not used yet because links aren't done)
added "." every time load_dir_list called to match new definition in util.c
make it clear to user that "status level" == directory
replace code to read in users and put in a sorted array with a call to new
util.c function load_file_list
util.c:
Add MAX_LINES const
add dirname parameter to load_dir_list. If util.c is meant to be general it
shouldn't assume the default dir any more than load_file_list should assume
a file name of "users".
add load_file_list, very similar to load_dir_list
proto.h: the usual
Renamed config.h to jconfig.h because it got lost among all the
autoconf config* stuff.
****************************************
Date: Monday November 24, 1997 @ 23:11
Author: tridge
Update of /data/cvs/jitterbug/source
In directory samba:/tmp/cvs-serv15310
Modified Files:
jitterbug.c
Log Message:
put back in the wildcard check in the EHLO response that Dans commit
removed. This is needed for sendmail based systems to work correctly.
removed some unused variables
****************************************
Date: Monday November 24, 1997 @ 23:11
Author: tridge
Update of /data/cvs/jitterbug/source
In directory samba:/tmp/cvs-serv9670
Modified Files:
util.c
Log Message:
removed an unused variable
****************************************
Date: Monday November 24, 1997 @ 23:18
Author: tridge
Update of /data/cvs/jitterbug/source
In directory samba:/tmp/cvs-serv5380
Modified Files:
jitterbug.c
Log Message:
the new select_user() code defaults clients to the first name in the
list (Chris Hertel in our case) making it too easy to enter as that
user without selecting from the list. Change back to the old
behaviour.
****************************************
Date: Tuesday November 25, 1997 @ 5:07
Author: dan
Update of /data/cvs/jitterbug/source
In directory samba:/tmp/cvs-serv26271
Added Files:
jconfig.h
Log Message:
Really add jconfig.h this time. See comments for previous dps commit.
****************************************
Date: Sunday November 30, 1997 @ 2:53
Author: dan
Update of /data/cvs/jitterbug/source
In directory samba:/tmp/cvs-serv13491
Modified Files:
util.c
Log Message:
Added recursive find_file function. Prep for message linking.
****************************************
Date: Sunday November 30, 1997 @ 16:18
Author: tridge
Update of /data/cvs/jitterbug/source
In directory samba:/data/people/tridge/jitterbug/source
Modified Files:
cgi.c jconfig.h jitterbug.c proto.h util.c
Log Message:
added the ability to use/edit/create FAQ entries on the fly
****************************************
Date: Monday December 1, 1997 @ 13:26
Author: tridge
Update of /data/cvs/jitterbug/source
In directory samba:/data/people/tridge/jitterbug/source
Modified Files:
util.c
Log Message:
always use a blank entry in select_list()
****************************************
Date: Monday December 1, 1997 @ 13:27
Author: tridge
Update of /data/cvs/jitterbug/source
In directory samba:/data/people/tridge/jitterbug/source
Modified Files:
jitterbug.c
Log Message:
space things out better in show_directories()
****************************************
Date: Tuesday December 2, 1997 @ 10:24
Author: dan
Update of /data/cvs/jitterbug/source
In directory samba:/tmp/cvs-serv13968
Modified Files:
jitterbug.c proto.h util.c
Log Message:
jitterbug.c : first rough version of links code. <msgid>.links is a list of
message ids that are linked to <msgid>. These can be in any directory in the
system. The presence of a links file is announced in much the same way as
replies or followups in the main directory view. The individual message
view screen has an edit/view links anchor (even if it doesn't currently have
any links). Can't edit yet but this is trivial, need to see if the idea works.
This is John's idea and should be checked with him to see if it makes sense.
Added a couple of missing free_list calls.
****************************************
Date: Wednesday December 3, 1997 @ 0:36
Author: tridge
Update of /data/cvs/jitterbug/source
In directory samba:/tmp/cvs-serv2501
Modified Files:
jitterbug.c
Log Message:
zero the addsignature variable at the right time so it can be
reset. (checkboxes need to be treated like this)
****************************************
Date: Wednesday December 3, 1997 @ 0:41
Author: tridge
Update of /data/cvs/jitterbug/source
In directory samba:/tmp/cvs-serv13919
Modified Files:
jitterbug.c
Log Message:
stop the links code from coredumping
****************************************
Date: Wednesday December 3, 1997 @ 14:08
Author: tridge
Update of /data/cvs/jitterbug/source
In directory samba:/data/people/tridge/jitterbug/source
Modified Files:
jitterbug.c
Log Message:
don't free s twice
****************************************
Date: Thursday December 4, 1997 @ 13:58
Author: tridge
Update of /data/cvs/jitterbug/source
In directory samba:/data/people/tridge/jitterbug/source
Modified Files:
jitterbug.c
Log Message:
log the creation and saving of FAQ entries
****************************************
Date: Thursday December 4, 1997 @ 17:46
Author: dan
Update of /data/cvs/jitterbug/source
In directory samba:/tmp/cvs-serv5969
Modified Files:
jitterbug.c
Log Message:
Bug where null strings were being treated as null pointers, this won't work :-)
get_info() assumed util.c/getmailheader() returned NULL where it returns
strdup(""). Tridge, I'd prefer to return NULL in getmailheader but you might
have had a reason so I've left it for now and just used strcmp and free instead.
This fixes the problem where nonsense messages are sort-of displayed.
Added code to put the per-dir notes.html in the TITLE= tag of each directory
name's anchor in display_dir() but took most of it out again when I discovered
that the big browsers (netscape, ie, lynx) ignore this. Uncomment this when
these browsers catch up with Arena and I think Red Baron!
****************************************
Date: Thursday December 4, 1997 @ 23:01
Author: dan
Update of /data/cvs/jitterbug/source
In directory samba:/tmp/cvs-serv23094
Modified Files:
jitterbug.c
Log Message:
Minor stuff.
valid_user: change correct but mildly confusing 'user' to 'username'
add_audit: fatal error if audit file can't be opened
login_page: use valid_user more instead of *user etc
bug fixed where it lets you in even if you entered an invalid
new user with a valid user; now prints an error message instead.
put "/" in front of guestintro.html and intro.html to be
consistent with other similar files
load_users: fatal error now if can't open audit file
use valid_user more
main: check for invalid newuser var
****************************************
Date: Friday December 5, 1997 @ 12:05
Author: tridge
Update of /data/cvs/jitterbug/source
In directory samba:/data/people/tridge/jitterbug/source
Modified Files:
jitterbug.c
Log Message:
reverted some bits of code back to what it was
- removed some of the new strlen() checks Dan put in. Some were just
wrong, and others checked for NULL string instead of zero length
string deliberately. The reason is that we want to be able to view
messages with blank fields but we don't want to core dump.
- check only for valid_user(user) when deciding whether to do a
login. the newuser variable has already been processed.
****************************************
Date: Friday December 5, 1997 @ 12:07
Author: tridge
Update of /data/cvs/jitterbug/source
In directory samba:/data/people/tridge/jitterbug/source
Modified Files:
jitterbug.c
Log Message:
need quotequotes() on subject after quoting or you lose part of
subject line if thery have a " in it.
****************************************
Date: Saturday December 6, 1997 @ 23:03
Author: dan
Update of /data/cvs/jitterbug/source
In directory samba:/tmp/cvs-serv7314
Modified Files:
jitterbug.c proto.h util.c
Log Message:
Simple stuff and Links code
Simple stuff
------------
I've been testing with some really dud messages which is why I started
fiddling here. If we are going to go ahead and display messages
with blank fields (which I agree is the best strategy) then we need to
do it consistently for all fields.
jitterbug.c
display_email: print warning if no message body
slight indentation change for reading ease
get_info: return "unknown" on missing From: or Date: fields
at last! I understand what tridge meant in testing
for NULL: out of memory test. Changed to a fatal() for
this rather than returning 0 to match everywhere else
Links code
----------
I wish I had time to do this in one go, its painful to drip-feed the code :-)
Done work in jitterbug.c on this and in process built some more general
string list functions in util.c.
jitterbug.c
do_links: handles link adding/deleting. not quite finished.
util.c
delete_list_item: created
write_list: created
proto.h usual
****************************************
Date: Sunday December 7, 1997 @ 0:28
Author: dan
Update of /data/cvs/jitterbug/source
In directory samba:/tmp/cvs-serv10231
Modified Files:
jitterbug.c proto.h util.c
Log Message:
Got links working except for what is probably a simple current directory
thing with handling "newlinks". Be a week before I get to spend any more
time but it really is only a few minutes from being 100% <sigh>.
****************************************
Date: Tuesday December 16, 1997 @ 1:00
Author: dan
Update of /data/cvs/jitterbug/source
In directory samba:/tmp/cvs-serv9796
Modified Files:
jitterbug.c util.c
Log Message:
Links code works for me now, add and delete with sanity checks on all ids
and audit messages.
jitterbug.c:
do_links()
- don't return on null links file
- sensible audit log message
display_links()
- get message count right if links file has non-existant PR numbers in it
util.c:
write_links()
- delete file if mode "w" and null list
****************************************
Date: Tuesday December 16, 1997 @ 1:33
Author: dan
Update of /data/cvs/jitterbug
In directory samba:/tmp/cvs-serv4364
Added Files:
ToDo
Log Message:
Added file for wishful thinking
****************************************
Date: Tuesday December 16, 1997 @ 1:35
Author: dan
Update of /data/cvs/jitterbug
In directory samba:/tmp/cvs-serv16503
Modified Files:
ToDo
Log Message:
More
****************************************
Date: Tuesday December 16, 1997 @ 14:44
Author: tridge
Update of /data/cvs/jitterbug/source
In directory samba:/tmp/cvs-serv6834
Modified Files:
jitterbug.c
Log Message:
allow add_audit() to be called by guest if the file is writeable. This
way the admin can choose to make (for example) system.audit world
writeable so they know who is using the system.
****************************************
Date: Tuesday December 16, 1997 @ 14:47
Author: tridge
Update of /data/cvs/jitterbug/source
In directory samba:/tmp/cvs-serv13771
Modified Files:
jitterbug.c
Log Message:
record guest connections
****************************************
Date: Wednesday December 17, 1997 @ 13:05
Author: tridge
Update of /data/cvs/jitterbug
In directory samba:/tmp/cvs-serv25969
Modified Files:
README
Log Message:
updated the docs a bit. better INSTALL file.
****************************************
Date: Wednesday December 17, 1997 @ 13:06
Author: tridge
Update of /data/cvs/jitterbug/docs
In directory samba:/tmp/cvs-serv24494
Modified Files:
INSTALL
Log Message:
updated the docs a bit. better INSTALL file.
****************************************
Date: Wednesday December 17, 1997 @ 13:13
Author: tridge
Update of /data/cvs/jitterbug/config
In directory samba:/data/people/tridge/jitterbug/config
Modified Files:
guestintro.html intro.html reportform.html
Added Files:
.nextid footer.html guest.prefs
Log Message:
setup some better example config stuff
****************************************
Date: Wednesday December 17, 1997 @ 13:17
Author: tridge
Update of /data/cvs/jitterbug/docs
In directory samba:/tmp/cvs-serv6684
Modified Files:
INSTALL
Log Message:
add note about customising the *.html files.
****************************************
Date: Wednesday December 17, 1997 @ 13:38
Author: jitter-bugs
Update of /data/cvs/jitterbug/mail
In directory samba:/data/people/jitter-bugs/jitterbug/mail
Modified Files:
README procmailrc
Added Files:
cvs_message forward
Log Message:
improved the mail installation instructions
****************************************
Date: Wednesday December 17, 1997 @ 13:39
Author: jitter-bugs
Update of /data/cvs/jitterbug/mail
In directory samba:/data/people/jitter-bugs/jitterbug/mail
Removed Files:
reprocess
Log Message:
don't want this
****************************************
Date: Wednesday December 17, 1997 @ 13:40
Author: jitter-bugs
Update of /data/cvs/jitterbug/mail
In directory samba:/data/people/jitter-bugs/jitterbug/mail
Removed Files:
auto_reply
Log Message:
don't want this either (too specialised)
****************************************
Date: Wednesday December 17, 1997 @ 13:46
Author: tridge
Update of /data/cvs/jitterbug/docs
In directory samba:/tmp/cvs-serv25871
Modified Files:
INSTALL
Log Message:
add usr for anon cvs
****************************************
Date: Wednesday December 17, 1997 @ 13:46
Author: tridge
Update of /data/cvs/jitterbug/source
In directory samba:/tmp/cvs-serv19590
Modified Files:
jitterbug.c
Log Message:
no error message when creating a new user
****************************************
Date: Wednesday December 17, 1997 @ 14:06
Author: tridge
Update of /data/cvs/jitterbug/source
In directory samba:/tmp/cvs-serv9675
Modified Files:
jconfig.h jitterbug.c
Added Files:
version.h
Log Message:
use version.h so it can be auto-updated by the release script
****************************************
Date: Wednesday December 17, 1997 @ 14:08
Author: jitter-bugs
Update of /data/cvs/jitterbug/source
In directory samba:/data/people/jitter-bugs/jitterbug/source
Modified Files:
.cvsignore
Log Message:
ignore a couple more files
****************************************
Date: Wednesday December 17, 1997 @ 14:09
Author: jitter-bugs
Update of /data/cvs/jitterbug/source
In directory samba:/data/people/jitter-bugs/jitterbug/source
Modified Files:
jconfig.h
Log Message:
make the default jconfig.h the one from jitter-bugs@samba to make the
release process easy
****************************************
Date: Saturday December 20, 1997 @ 16:35
Author: jitter-bugs
Update of /data/cvs/jitterbug/source
In directory samba:/data/people/jitter-bugs/jitterbug/source
Modified Files:
jconfig.h jitterbug.c
Log Message:
allow the AUTH_USER macro to be left blank which leaves the
authentication totally up to the web server. This is useful for group
authentication.
****************************************
Date: Tuesday December 23, 1997 @ 23:18
Author: dan
Update of /data/cvs/jitterbug/source
In directory samba:/tmp/cvs-serv18349
Modified Files:
Makefile.in proto.h util.c
Added Files:
list.c
Log Message:
Moved list stuff out of util.c. Not tested properly but better than
nothing.
****************************************
Date: Wednesday December 24, 1997 @ 12:29
Author: tridge
Update of /data/cvs/jitterbug/source
In directory samba:/tmp/cvs-serv1928
Modified Files:
Makefile.in jitterbug.c list.c
Added Files:
notify.c
Log Message:
The start of some auto-notification changes. Only the gui parts are
done so far, the actual email notification is next
****************************************
Date: Wednesday December 24, 1997 @ 12:45
Author: tridge
Update of /data/cvs/jitterbug/source
In directory samba:/tmp/cvs-serv19220
Modified Files:
jitterbug.c proto.h smtp.c
Log Message:
cleaned up the smtp mail handling a bit ready for more extensive
use in the notification code
****************************************
Date: Wednesday December 24, 1997 @ 13:43
Author: tridge
Update of /data/cvs/jitterbug/source
In directory samba:/tmp/cvs-serv13916
Modified Files:
jitterbug.c notify.c proto.h
Log Message:
implemented the notification sending for message movements.
****************************************
Date: Wednesday December 24, 1997 @ 14:00
Author: tridge
Update of /data/cvs/jitterbug/source
In directory samba:/tmp/cvs-serv4176
Modified Files:
jitterbug.c
Log Message:
notify both src and dest directory on msg movements
****************************************
Date: Wednesday December 24, 1997 @ 16:02
Author: tridge
Update of /data/cvs/jitterbug/source
In directory samba:/tmp/cvs-serv10271
Modified Files:
Makefile.in cgi.c jitterbug.c notify.c proto.h smtp.c util.c
Added Files:
new_message.c
Log Message:
full notification done (but untested)
this replaces the new_message script with a C program that does all
the work, handling locks and sending notifications. This also gets rid
of those ugly mail scripts
****************************************
Date: Wednesday December 24, 1997 @ 16:09
Author: tridge
Update of /data/cvs/jitterbug/source
In directory samba:/tmp/cvs-serv11574
Modified Files:
lock.c
Log Message:
get the locking right in new_message
****************************************
Date: Wednesday December 24, 1997 @ 16:34
Author: tridge
Update of /data/cvs/jitterbug/mail
In directory samba:/tmp/cvs-serv4589
Modified Files:
README procmailrc
Removed Files:
cvs_message followup_message new_message
Log Message:
much simpler mail processing now
****************************************
Date: Wednesday December 24, 1997 @ 16:35
Author: tridge
Update of /data/cvs/jitterbug/mail
In directory samba:/tmp/cvs-serv15539
Removed Files:
.procmailrc
Log Message:
much simpler mail processing now
****************************************
Date: Wednesday December 24, 1997 @ 16:36
Author: tridge
Update of /data/cvs/jitterbug
In directory samba:/tmp/cvs-serv10427
Modified Files:
README
Log Message:
much simpler mail processing now
a few minor fixes in new_message
****************************************
Date: Wednesday December 24, 1997 @ 16:36
Author: tridge
Update of /data/cvs/jitterbug/config
In directory samba:/tmp/cvs-serv10071
Removed Files:
.nextid
Log Message:
much simpler mail processing now
a few minor fixes in new_message
****************************************
Date: Wednesday December 24, 1997 @ 16:36
Author: tridge
Update of /data/cvs/jitterbug/docs
In directory samba:/tmp/cvs-serv1507
Modified Files:
INSTALL jitterbug.doc
Log Message:
much simpler mail processing now
a few minor fixes in new_message
****************************************
Date: Wednesday December 24, 1997 @ 16:36
Author: tridge
Update of /data/cvs/jitterbug/source
In directory samba:/tmp/cvs-serv4463
Modified Files:
.cvsignore new_message.c notify.c
Log Message:
much simpler mail processing now
a few minor fixes in new_message
****************************************
Date: Wednesday December 24, 1997 @ 16:55
Author: tridge
Update of /data/cvs/jitterbug/source
In directory samba:/tmp/cvs-serv13652
Modified Files:
jitterbug.c new_message.c notify.c
Log Message:
don't send notification to the user that causes the action
so for example, if tridge is in the notify list for a message, and
tridge moves the message then don't send tridge a notification
****************************************
Date: Wednesday December 24, 1997 @ 16:57
Author: tridge
Update of /data/cvs/jitterbug/source
In directory samba:/tmp/cvs-serv7500
Modified Files:
notify.c
Log Message:
fix bug in clean_notify
****************************************
Date: Wednesday December 24, 1997 @ 16:59
Author: tridge
Update of /data/cvs/jitterbug/source
In directory samba:/tmp/cvs-serv4545
Modified Files:
jitterbug.c
Log Message:
use "directory" instead of "status level"
****************************************
Date: Wednesday December 24, 1997 @ 17:02
Author: jitter-b
Update of /data/cvs/jitterbug/source
In directory samba:/data/people/jitter-bugs/jitterbug/source
Modified Files:
version.h
Log Message:
preparing for release of 1.1
****************************************
Date: Wednesday December 24, 1997 @ 18:04
Author: tridge
Update of /data/cvs/jitterbug/docs
In directory samba:/tmp/cvs-serv5037
Added Files:
JitterBug.txt internals.txt
Removed Files:
Problems.txt jitterbug.doc
Log Message:
cleaned up the docs a bit
JitterBug.txt is now a basic user guide
****************************************
Date: Wednesday December 24, 1997 @ 20:37
Author: tridge
Update of /data/cvs/jitterbug/source
In directory samba:/tmp/cvs-serv3148
Modified Files:
includes.h jitterbug.c list.c lock.c new_message.c notify.c
proto.h smtp.c util.c
Added Files:
jitterbug.h
Removed Files:
getid.c
Log Message:
- some code cleanups
- send a summary of the message along with the notification emails
****************************************
Date: Wednesday December 24, 1997 @ 20:39
Author: tridge
Update of /data/cvs/jitterbug/source
In directory samba:/tmp/cvs-serv13498
Modified Files:
jitterbug.c
Log Message:
only send notes once in changed notes notification
****************************************
Date: Wednesday December 24, 1997 @ 20:52
Author: tridge
Update of /data/cvs/jitterbug/source
In directory samba:/tmp/cvs-serv22235
Modified Files:
cgi.c notify.c proto.h
Log Message:
fix some layout problems in the notification summaries
****************************************
Date: Wednesday December 24, 1997 @ 20:57
Author: tridge
Update of /data/cvs/jitterbug/source
In directory samba:/tmp/cvs-serv22851
Modified Files:
jitterbug.c new_message.c
Log Message:
missing argument in new_message notification
****************************************
Date: Wednesday December 24, 1997 @ 21:02
Author: tridge
Update of /data/cvs/jitterbug/source
In directory samba:/tmp/cvs-serv22153
Modified Files:
new_message.c
Log Message:
another new_message notification bug!
****************************************
Date: Wednesday December 24, 1997 @ 21:05
Author: tridge
Update of /data/cvs/jitterbug/source
In directory samba:/tmp/cvs-serv18141
Modified Files:
new_message.c
Log Message:
another new_message notification bug!
****************************************
Date: Wednesday December 24, 1997 @ 21:27
Author: tridge
Update of /data/cvs/jitterbug/source
In directory samba:/tmp/cvs-serv24063
Modified Files:
cgi.c util.c
Log Message:
hopefully fix a bug in getmailheader() where it would recognise
"headers" half way along a line.
also make the case insensitive handling in getmailheader much more
efficient
****************************************
Date: Wednesday December 24, 1997 @ 21:31
Author: tridge
Update of /data/cvs/jitterbug/source
In directory samba:/tmp/cvs-serv27897
Modified Files:
util.c
Log Message:
use strncasecmp() not strcasecmp() in getmailheader()
****************************************
Date: Wednesday December 24, 1997 @ 21:37
Author: jitter-b
Update of /data/cvs/jitterbug/source
In directory samba:/data/people/jitter-bugs/jitterbug/source
Modified Files:
version.h
Log Message:
preparing for release of 1.2
****************************************
Date: Thursday December 25, 1997 @ 14:17
Author: dan
Update of /data/cvs/jitterbug/source
In directory samba:/tmp/cvs-serv25086
Modified Files:
jitterbug.c list.c proto.h util.c
Log Message:
list.c:
fixed various list handling bugs
added new fn debug_print_list()
added new fn new_list()
jitterbug.c:
do_links(): added new_list() call, messages without a links
file already weren't being dealt with.
util.c:
find_file(): small bugfix. There is still a bug in here somewhere.
****************************************
Date: Thursday December 25, 1997 @ 23:49
Author: tridge
Update of /data/cvs/jitterbug/source
In directory samba:/tmp/cvs-serv23001
Modified Files:
util.c
Log Message:
got rid of debug lines
****************************************
Date: Thursday December 25, 1997 @ 23:57
Author: dan
Update of /data/cvs/jitterbug/source
In directory samba:/tmp/cvs-serv6755
Modified Files:
jitterbug.c
Log Message:
use correct cgi variable for title of links page
****************************************
Date: Friday December 26, 1997 @ 12:23
Author: tridge
Update of /data/cvs/jitterbug/source
In directory samba:/tmp/cvs-serv12091
Modified Files:
new_message.c
Log Message:
needed to set the umask in new_message to make the messages publicly
readable!
****************************************
Date: Friday December 26, 1997 @ 13:12
Author: tridge
Update of /data/cvs/jitterbug/source
In directory samba:/tmp/cvs-serv17612
Modified Files:
jitterbug.c
Log Message:
put #if MESSAGE_LINKS around all the message links code. this code is
just too dodgy at the moment. I fixed a pile of bugs in it but until
it is fully working I don't think it should be included
- added some buffer overflow checks in links code. All cgi variables
must not be trusted for size!
- allow , and \t in strtok() list separation for links
- fixed a C coding error. Dan, in C you must specify "else", it is not
implicit. So for example:
if (foo) {
statement1;
}{
statement2;
}
is *not* a valid if/else statement. I noticed you used this syntax in
a couple of places. The result was core dumps. You must use an else
like this:
if (foo) {
statement1;
} else {
statement2;
}
maybe I should give you a separate CVS branch to work in? I know C
isn't your language of choice so maybe it would be better if I
transferred stuff from your branch to the main branch when I've checked
it over?
****************************************
Date: Friday December 26, 1997 @ 13:16
Author: tridge
Update of /data/cvs/jitterbug/source
In directory samba:/tmp/cvs-serv25297
Modified Files:
list.c
Log Message:
fixed several C coding errors
- use unlink() not remove(). Never use remove() unless you know it
might be a directory (very rare!)
- strcmp() returns 0 on a match, not non-0
- need <br> in html debug printfs
- delete_list_item had several bugs, core dumps would have been common.
Note that I haven't tested these fixes, they were just errors I found
by reading the code. Testing needed.
****************************************
Date: Friday December 26, 1997 @ 13:21
Author: tridge
Update of /data/cvs/jitterbug/source
In directory samba:/tmp/cvs-serv25233
Modified Files:
jitterbug.c
Log Message:
don't dipslay link to view/edit linked messaged unless MESSAGE_LINKS
is set
****************************************
Date: Friday December 26, 1997 @ 13:26
Author: jitter-b
Update of /data/cvs/jitterbug/source
In directory samba:/data/people/jitter-bugs/jitterbug/source
Modified Files:
version.h
Log Message:
preparing for release of 1.3
****************************************
Date: Friday December 26, 1997 @ 13:52
Author: tridge
Update of /data/cvs/jitterbug/source
In directory samba:/tmp/cvs-serv21647
Modified Files:
configure.in
Log Message:
- don't use -Wall on solaris (they might not have gcc!)
- I'm also very suspicious of the direct/dirent stuff. It looks wrong.
****************************************
Date: Friday December 26, 1997 @ 15:24
Author: tridge
Update of /data/cvs/jitterbug/source
In directory samba:/tmp/cvs-serv1482
Modified Files:
Makefile.in cgi.c configure configure.in includes.h
jitterbug.h list.c search.c util.c
Added Files:
config.h.in
Log Message:
make JitterBug reasonably portable
Although we had a configure script we weren't actually using autoconf
up till now. To use autoconf you need to base your #includes on
autoconf output
I've now test compiled JitterBug on SunOS 4.1.3, Solaris/gcc,
Solaris/cc, IRIX 6.4, Linux, Ultrix and OSF1 3.2. Lots of changes were
needed.
****************************************
Date: Friday December 26, 1997 @ 15:27
Author: jitter-b
Update of /data/cvs/jitterbug/source
In directory samba:/data/people/jitter-bugs/jitterbug/source
Modified Files:
.cvsignore version.h
Log Message:
preparing for release of 1.4
****************************************
Date: Friday December 26, 1997 @ 23:12
Author: tridge
Update of /data/cvs/jitterbug/source
In directory samba:/tmp/cvs-serv27294
Modified Files:
.cvsignore install-sh
Log Message:
update .cvsignore
don't need a full install-sh as JitterBug installation is manual
(which is how it should be for a cgi-bin program!)
****************************************
Date: Friday December 26, 1997 @ 23:13
Author: tridge
Update of /data/cvs/jitterbug/source
In directory samba:/tmp/cvs-serv6862
Modified Files:
install-sh
Log Message:
make install-sh report an error
****************************************
Date: Sunday December 28, 1997 @ 0:07
Author: tridge
Update of /data/cvs/jitterbug/source
In directory samba:/tmp/cvs-serv17559
Modified Files:
jitterbug.c list.c smtp.c util.c
Log Message:
- fixed a bug in the SIZE argument in smtp.c
- case insensitive usernames in notification code
- minor cleanups
****************************************
Date: Sunday December 28, 1997 @ 0:24
Author: tridge
Update of /data/cvs/jitterbug/source
In directory samba:/tmp/cvs-serv25246
Modified Files:
notify.c
Log Message:
- case insensitive usernames in notification code
****************************************
Date: Sunday December 28, 1997 @ 0:28
Author: jitter-b
Update of /data/cvs/jitterbug/source
In directory samba:/data/people/jitter-bugs/jitterbug/source
Modified Files:
version.h
Log Message:
preparing for release of 1.4.1
****************************************
Date: Sunday December 28, 1997 @ 22:40
Author: tridge
Update of /data/cvs/jitterbug/source
In directory samba:/tmp/cvs-serv1566
Modified Files:
config.h.in jitterbug.c
Log Message:
an HTML validator found a bug in the search table html format. fixed.
****************************************
Date: Sunday December 28, 1997 @ 22:51
Author: tridge
Update of /data/cvs/jitterbug/source
In directory samba:/tmp/cvs-serv7210
Modified Files:
jitterbug.c
Log Message:
more minor html fixes
****************************************
Date: Monday December 29, 1997 @ 16:54
Author: tridge
Update of /data/cvs/jitterbug/source
In directory samba:/tmp/cvs-serv27248
Modified Files:
cgi.c
Log Message:
handle non-printable characters in quotedup()
****************************************
Date: Monday December 29, 1997 @ 16:56
Author: tridge
Update of /data/cvs/jitterbug/source
In directory samba:/tmp/cvs-serv27286
Modified Files:
cgi.c
Log Message:
handle non-printable characters in quotedup()
****************************************
Date: Monday December 29, 1997 @ 17:23
Author: tridge
Update of /data/cvs/jitterbug/source
In directory samba:/tmp/cvs-serv10545
Modified Files:
jitterbug.c
Log Message:
allow guests to view but not change the preferences
****************************************
Date: Monday December 29, 1997 @ 17:26
Author: tridge
Update of /data/cvs/jitterbug/source
In directory samba:/tmp/cvs-serv16671
Modified Files:
jitterbug.c
Log Message:
allow guests to view but not change the preferences
****************************************
Date: Wednesday December 31, 1997 @ 14:24
Author: tridge
Update of /data/cvs/jitterbug/config
In directory samba:/tmp/cvs-serv23476
Modified Files:
footer.html guestintro.html reportform.html
Log Message:
some updates to the installation instructions and default config
****************************************
Date: Wednesday December 31, 1997 @ 14:24
Author: tridge
Update of /data/cvs/jitterbug/docs
In directory samba:/tmp/cvs-serv25252
Modified Files:
INSTALL
Log Message:
some updates to the installation instructions and default config
****************************************
Date: Wednesday December 31, 1997 @ 14:24
Author: tridge
Update of /data/cvs/jitterbug/mail
In directory samba:/tmp/cvs-serv27987
Modified Files:
README
Log Message:
some updates to the installation instructions and default config
****************************************
Date: Wednesday December 31, 1997 @ 14:27
Author: tridge
Update of /data/cvs/jitterbug
In directory samba:/tmp/cvs-serv1923
Modified Files:
README
Removed Files:
ToDo
Log Message:
got rid of ToDo. We don't really want to distribute this, I'd rather
use the todo directory in JitterBug.
update README a bit
****************************************
Date: Wednesday December 31, 1997 @ 14:33
Author: jitter-b
Update of /data/cvs/jitterbug/source
In directory samba:/data/people/jitter-bugs/jitterbug/source
Modified Files:
version.h
Log Message:
preparing for release of 1.4.2
****************************************
Date: Thursday January 1, 1998 @ 23:08
Author: tridge
Update of /data/cvs/jitterbug/source
In directory samba:/tmp/cvs-serv28531
Modified Files:
jitterbug.c jitterbug.h new_message.c notify.c proto.h util.c
Log Message:
speedups
- only load the message body when it is really needed
- when searching only load max_message_size bytes of the message
****************************************
Date: Thursday January 1, 1998 @ 23:27
Author: tridge
Update of /data/cvs/jitterbug/source
In directory samba:/tmp/cvs-serv24479
Modified Files:
jitterbug.c jitterbug.h notify.c proto.h util.c
Log Message:
need to load raw in get_info() to prevent loading twice
****************************************
Date: Saturday January 3, 1998 @ 17:50
Author: tridge
Update of /data/cvs/jitterbug/source
In directory samba:/tmp/cvs-serv24873
Modified Files:
jitterbug.c util.c
Log Message:
use the Reply-To: header if it exists
****************************************
Date: Saturday January 3, 1998 @ 17:58
Author: tridge
Update of /data/cvs/jitterbug/source
In directory samba:/tmp/cvs-serv25780
Modified Files:
jitterbug.c notify.c
Log Message:
fix usage of load_ext()
****************************************
Date: Monday January 5, 1998 @ 20:57
Author: tridge
Update of /data/cvs/jitterbug/source
In directory samba:/tmp/cvs-serv26033
Modified Files:
search.c
Log Message:
- more portable regexp usage
- only compile regexp once
****************************************
Date: Tuesday January 6, 1998 @ 11:28
Author: tridge
Update of /data/cvs/jitterbug/source
In directory samba:/tmp/cvs-serv8775
Modified Files:
jitterbug.c list.c
Log Message:
- fixed a segv bug in the user_list handling
- don't qsort zero length lists
****************************************
Date: Tuesday January 6, 1998 @ 11:31
Author: jitter-b
Update of /data/cvs/jitterbug/source
In directory samba:/data/people/jitter-bugs/jitterbug/source
Modified Files:
version.h
Log Message:
preparing for release of 1.4.3
****************************************
Date: Thursday February 5, 1998 @ 11:35
Author: samba-bugs
Update of /data/cvs/jitterbug/source
In directory samba:/data/people/samba-bugs/jitterbug/source
Modified Files:
jitterbug.c
Log Message:
add a 5 minute alarm so that JitterBug cannot run forever. This
prevents processes building up if a bug does occur.
****************************************
Date: Thursday February 5, 1998 @ 11:36
Author: samba-bugs
Update of /data/cvs/jitterbug/source
In directory samba:/data/people/samba-bugs/jitterbug/source
Modified Files:
util.c
Log Message:
handle From: addresses with names containing <, often occuring
in kanji or other foreign names.
****************************************
Date: Thursday February 5, 1998 @ 12:12
Author: tridge
Update of /data/cvs/jitterbug/source
In directory samba:/tmp/cvs-serv2475
Modified Files:
jitterbug.c
Log Message:
fixed a core dump in the faq handling.
Thanks to d3moine@bst.bsf.alcatel.fr for pointing it out.
****************************************
Date: Thursday February 5, 1998 @ 15:38
Author: tridge
Update of /data/cvs/jitterbug/source
In directory samba:/tmp/cvs-serv7005
Modified Files:
jitterbug.c
Log Message:
fix download for guest users (shouldn't die!)
****************************************
Date: Thursday February 5, 1998 @ 15:42
Author: tridge
Update of /data/cvs/jitterbug/source
In directory samba:/tmp/cvs-serv5485
Modified Files:
jitterbug.c
Log Message:
show a footer when a guest attempts file download
****************************************
Date: Thursday February 12, 1998 @ 22:26
Author: tridge
Update of /data/cvs/jitterbug/source
In directory samba:/tmp/cvs-serv27890
Modified Files:
jconfig.h
Log Message:
testing CVS
****************************************
Date: Thursday March 26, 1998 @ 11:36
Author: dan
Update of /data/cvs/jitterbug/docs
In directory samba:/tmp/cvs-serv4271
Modified Files:
INSTALL
Log Message:
Updated Apache instructions. Minor corrections.
****************************************
Date: Friday April 3, 1998 @ 12:27
Author: jitter-bugs
Update of /data/cvs/jitterbug/config
In directory samba:/data/people/jitter-bugs/jitterbug/config
Modified Files:
intro.html
Log Message:
refer to correct file in intro.html
****************************************
Date: Saturday April 18, 1998 @ 13:32
Author: tridge
Update of /data/cvs/jitterbug/source
In directory samba:/tmp/cvs-serv23734
Modified Files:
cgi.c
Log Message:
no print_title() with DEBUG_COMMENTS
****************************************
Date: Saturday April 18, 1998 @ 16:26
Author: tridge
Update of /data/cvs/jitterbug/source
In directory samba:/tmp/cvs-serv11139
Modified Files:
Makefile.in jconfig.h jitterbug.c lock.c new_message.c
notify.c proto.h smtp.c util.c
Added Files:
loadparm.c
Log Message:
implemented a runtime configuration system. All options are now
configurable at runtime via config files in /etc/jitterbug/. This will
allow us to distribute binaries if we want to.
****************************************
Date: Saturday April 18, 1998 @ 17:29
Author: tridge
Update of /data/cvs/jitterbug/source
In directory samba:/tmp/cvs-serv14386
Modified Files:
jitterbug.c loadparm.c lock.c proto.h util.c
Log Message:
changes to support running either with or without the chroot() and
with the chroot() directory set above the base directory. This should
make things much easier for Solaris users.
****************************************
Date: Saturday April 18, 1998 @ 18:18
Author: tridge
Update of /data/cvs/jitterbug/source
In directory samba:/tmp/cvs-serv22636
Modified Files:
loadparm.c proto.h smtp.c
Log Message:
added support for using either an external mail (such as sendmail) or
the internal one. The internal one doesn't work on all systems and
there are some situations where an external mailer is preferable.
****************************************
Date: Saturday April 18, 1998 @ 18:29
Author: tridge
Update of /data/cvs/jitterbug/source
In directory samba:/tmp/cvs-serv19476
Modified Files:
cgi.c loadparm.c proto.h
Log Message:
added a "display binary" option. When enabled all characters will be
displayed, rather than only those passing isprint(). Useful for
foreign language support.
****************************************
Date: Saturday April 18, 1998 @ 22:04
Author: tridge
Update of /data/cvs/jitterbug/source
In directory samba:/tmp/cvs-serv27309
Modified Files:
Makefile.in jconfig.h loadparm.c new_message.c proto.h smtp.c
util.c
Log Message:
- added tags target in Makefile
- added autoreply code to new_message. This allows the PR# to be added
to the subject of autoreplies.
- added incoming parameter
****************************************
Date: Saturday April 18, 1998 @ 22:05
Author: tridge
Update of /data/cvs/jitterbug/source
In directory samba:/tmp/cvs-serv23493
Modified Files:
new_message.c
Log Message:
only autoreply to messages in the incoming directory
****************************************
Date: Saturday April 18, 1998 @ 22:08
Author: tridge
Update of /data/cvs/jitterbug/source
In directory samba:/tmp/cvs-serv22191
Modified Files:
smtp.c
Log Message:
no void return
****************************************
Date: Saturday April 18, 1998 @ 22:38
Author: jitter-bugs
Update of /data/cvs/jitterbug/source
In directory samba:/data/people/jitter-bugs/jitterbug/source
Modified Files:
new_message.c
Log Message:
fixed some bugs in the autoreply code
****************************************
Date: Saturday April 18, 1998 @ 22:46
Author: jitter-bugs
Update of /data/cvs/jitterbug/source
In directory samba:/data/people/jitter-bugs/jitterbug/source
Modified Files:
jitterbug.c
Log Message:
fixed audit trail bug
****************************************
Date: Saturday April 18, 1998 @ 23:31
Author: tridge
Update of /data/cvs/jitterbug/source
In directory samba:/tmp/cvs-serv22320
Modified Files:
jitterbug.c jitterbug.h notify.c util.c
Log Message:
- include the message with notifications. This should fulfill Jeremys
needs.
****************************************
Date: Saturday April 18, 1998 @ 23:45
Author: tridge
Update of /data/cvs/jitterbug/source
In directory samba:/tmp/cvs-serv24086
Modified Files:
notify.c version.h
Log Message:
layout change and set new version number
****************************************
Date: Sunday April 19, 1998 @ 0:09
Author: tridge
Update of /data/cvs/jitterbug/source
In directory samba:/tmp/cvs-serv27680
Modified Files:
jitterbug.c
Log Message:
fixed duplicate users bug
****************************************
Date: Sunday April 19, 1998 @ 0:22
Author: tridge
Update of /data/cvs/jitterbug/source
In directory samba:/tmp/cvs-serv4032
Modified Files:
jconfig.h jitterbug.c
Log Message:
fixed faq dir with no chroot
****************************************
Date: Sunday April 19, 1998 @ 0:30
Author: tridge
Update of /data/cvs/jitterbug/source
In directory samba:/tmp/cvs-serv9394
Modified Files:
cgi.c
Log Message:
stop unquote() from looping forever!
****************************************
Date: Sunday April 19, 1998 @ 10:37
Author: tridge
Update of /data/cvs/jitterbug/source
In directory samba:/tmp/cvs-serv2816
Modified Files:
new_message.c
Log Message:
fixed root_dir in new_message.c
****************************************
Date: Sunday April 19, 1998 @ 11:28
Author: tridge
Update of /data/cvs/jitterbug/source
In directory samba:/tmp/cvs-serv3657
Modified Files:
jitterbug.c loadparm.c proto.h
Log Message:
added background option for specifying background image
****************************************
Date: Sunday April 19, 1998 @ 12:21
Author: tridge
Update of /data/cvs/jitterbug/source
In directory samba:/tmp/cvs-serv10325
Modified Files:
jitterbug.c new_message.c notify.c smtp.c
Log Message:
ensure that we always use \r\n in SMTP
****************************************
Date: Sunday April 19, 1998 @ 12:30
Author: tridge
Update of /data/cvs/jitterbug/source
In directory samba:/tmp/cvs-serv7398
Modified Files:
jitterbug.c
Log Message:
always report errno in fatal()
****************************************
Date: Sunday April 19, 1998 @ 12:38
Author: tridge
Update of /data/cvs/jitterbug/source
In directory samba:/tmp/cvs-serv2407
Modified Files:
new_message.c
Log Message:
prevent mail loops in new_message
****************************************
Date: Sunday April 19, 1998 @ 12:44
Author: tridge
Update of /data/cvs/jitterbug/source
In directory samba:/tmp/cvs-serv13894
Modified Files:
loadparm.c
Log Message:
added boolean type in parameter loading
****************************************
Date: Sunday April 19, 1998 @ 13:25
Author: tridge
Update of /data/cvs/jitterbug/source
In directory samba:/tmp/cvs-serv27699
Modified Files:
jitterbug.c loadparm.c proto.h util.c
Log Message:
added "group authentication" option
****************************************
Date: Sunday April 19, 1998 @ 13:38
Author: tridge
Update of /data/cvs/jitterbug/source
In directory samba:/tmp/cvs-serv11993
Modified Files:
jitterbug.c
Log Message:
modifications to allow JitterBug to run without being setuid
****************************************
Date: Sunday April 19, 1998 @ 22:46
Author: tridge
Update of /data/cvs/jitterbug/source
In directory samba:/tmp/cvs-serv10913
Modified Files:
jitterbug.c lock.c new_message.c notify.c proto.h util.c
Log Message:
lots of paranoid buffer overflow checks
****************************************
Date: Sunday April 19, 1998 @ 22:49
Author: tridge
Update of /data/cvs/jitterbug/source
In directory samba:/tmp/cvs-serv14400
Modified Files:
util.c
Log Message:
fixed bug in user_address()
****************************************
Date: Monday April 20, 1998 @ 10:19
Author: tridge
Update of /data/cvs/jitterbug/source
In directory samba:/tmp/cvs-serv1135
Modified Files:
smtp.c
Log Message:
some code to help debugging of the internal smtp code
****************************************
Date: Monday April 20, 1998 @ 10:25
Author: tridge
Update of /data/cvs/jitterbug/source
In directory samba:/tmp/cvs-serv27203
Modified Files:
smtp.c
Log Message:
fixed an end-of-mail bug
****************************************
Date: Monday April 20, 1998 @ 10:51
Author: dan
Update of /data/cvs/jitterbug/source
In directory samba:/tmp/cvs-serv5381/source
Added Files:
jitterbug-conf-sample
Log Message:
Sample /etc/jitterbug/jitterbug file
****************************************
Date: Monday April 20, 1998 @ 10:52
Author: dan
Update of /data/cvs/jitterbug/docs
In directory samba:/tmp/cvs-serv26173/docs
Modified Files:
INSTALL
Log Message:
Updated for 1.5. Doesn't cover non-suid installs yet.
****************************************
Date: Monday April 20, 1998 @ 11:49
Author: tridge
Update of /data/cvs/jitterbug
In directory samba:/tmp/cvs-serv8209
Modified Files:
README
Log Message:
changed the docs for runtime config
****************************************
Date: Monday April 20, 1998 @ 11:49
Author: tridge
Update of /data/cvs/jitterbug/docs
In directory samba:/tmp/cvs-serv8543
Modified Files:
INSTALL JitterBug.txt
Log Message:
changed the docs for runtime config
****************************************
Date: Monday April 20, 1998 @ 11:49
Author: tridge
Update of /data/cvs/jitterbug/docs
In directory samba:/tmp/cvs-serv26121
Added Files:
CONFIG.txt
Log Message:
changed the docs for runtime config
****************************************
Date: Monday April 20, 1998 @ 11:49
Author: tridge
Update of /data/cvs/jitterbug/source
In directory samba:/tmp/cvs-serv24434
Modified Files:
smtp.c
Log Message:
added a comment
****************************************
Date: Monday April 20, 1998 @ 11:57
Author: tridge
Update of /data/cvs/jitterbug/docs
In directory samba:/tmp/cvs-serv12905
Modified Files:
INSTALL
Log Message:
a few more docs changes. More to come.
Dan, please leave the CVS tree and docs alone for a while. Your
changes are conflicting with mine. I have a lot more changes to do.
****************************************
Date: Monday April 20, 1998 @ 12:11
Author: tridge
Update of /data/cvs/jitterbug/docs
In directory samba:/tmp/cvs-serv11239
Modified Files:
CONFIG.txt INSTALL
Log Message:
a few more docs changes. More to come.
****************************************
Date: Monday April 20, 1998 @ 12:11
Author: tridge
Update of /data/cvs/jitterbug/source
In directory samba:/tmp/cvs-serv3556
Modified Files:
util.c
Log Message:
changed the handling of root_directory()
****************************************
Date: Monday April 20, 1998 @ 12:14
Author: tridge
Update of /data/cvs/jitterbug/source
In directory samba:/tmp/cvs-serv14062
Removed Files:
jitterbug-conf-sample
Log Message:
Dan, please let me do the initial docs of my changes.
****************************************
Date: Monday April 20, 1998 @ 12:16
Author: tridge
Update of /data/cvs/jitterbug/source
In directory samba:/tmp/cvs-serv8519
Modified Files:
jitterbug.c
Log Message:
don't force JitterBug version in each title. Users can set "title ="
in their config file.
****************************************
Date: Monday April 20, 1998 @ 12:24
Author: tridge
Update of /data/cvs/jitterbug/source
In directory samba:/tmp/cvs-serv17680
Modified Files:
smtp.c
Log Message:
ensure we don't get double CR in mails
****************************************
Date: Monday April 20, 1998 @ 12:39
Author: jitter-b
Update of /data/cvs/jitterbug/source
In directory samba:/data/people/jitter-bugs/jitterbug/source
Added Files:
build_autoreply
Log Message:
a simple autoreply builder
****************************************
Date: Monday April 20, 1998 @ 12:45
Author: tridge
Update of /data/cvs/jitterbug/docs
In directory samba:/tmp/cvs-serv8825
Modified Files:
CONFIG.txt
Log Message:
explain the purpose of files used in JitterBug
****************************************
Date: Monday April 20, 1998 @ 12:48
Author: tridge
Update of /data/cvs/jitterbug/source
In directory samba:/tmp/cvs-serv9870
Modified Files:
build_autoreply
Log Message:
add some comments to build_autoreply
****************************************
Date: Monday April 20, 1998 @ 12:56
Author: tridge
Update of /data/cvs/jitterbug/docs
In directory samba:/tmp/cvs-serv8788
Modified Files:
JitterBug.txt
Log Message:
better FAQ handling explanation
****************************************
Date: Monday April 20, 1998 @ 13:08
Author: tridge
Update of /data/cvs/jitterbug/docs
In directory samba:/tmp/cvs-serv4905
Removed Files:
internals.txt
Log Message:
this file is so out of date we are better off without it.
****************************************
Date: Monday April 20, 1998 @ 13:09
Author: tridge
Update of /data/cvs/jitterbug/docs
In directory samba:/tmp/cvs-serv6053
Modified Files:
CONFIG.txt
Log Message:
give a sample sendmail command line for using an external mailer
****************************************
Date: Monday April 20, 1998 @ 13:13
Author: tridge
Update of /data/cvs/jitterbug/source
In directory samba:/tmp/cvs-serv3355
Modified Files:
smtp.c
Log Message:
strip CR from mail sent to the external mailer
****************************************
Date: Monday April 20, 1998 @ 13:17
Author: tridge
Update of /data/cvs/jitterbug/source
In directory samba:/tmp/cvs-serv19217
Modified Files:
util.c
Log Message:
changed save_file() to strip CR
****************************************
Date: Monday April 20, 1998 @ 13:25
Author: tridge
Update of /data/cvs/jitterbug/mail
In directory samba:/tmp/cvs-serv15718
Modified Files:
README procmailrc
Log Message:
i forgot to update these
****************************************
Date: Monday April 20, 1998 @ 16:07
Author: tridge
Update of /data/cvs/jitterbug/docs
In directory samba:/tmp/cvs-serv5038
Modified Files:
INSTALL
Log Message:
added some notes about Solaris
****************************************
Date: Monday April 20, 1998 @ 17:15
Author: tridge
Update of /data/cvs/jitterbug/source
In directory samba:/tmp/cvs-serv19388
Modified Files:
jitterbug.c loadparm.c proto.h search.c
Log Message:
support an external search program such as glimpse
****************************************
Date: Monday April 20, 1998 @ 17:27
Author: tridge
Update of /data/cvs/jitterbug/source
In directory samba:/tmp/cvs-serv14437
Modified Files:
search.c
Log Message:
bug fixes to external search code
****************************************
Date: Monday April 20, 1998 @ 17:47
Author: jitter-bugs
Update of /data/cvs/jitterbug/source
In directory samba:/data/people/jitter-bugs/jitterbug/source
Modified Files:
search.c
Log Message:
finally got the fast external searching working properly
****************************************
Date: Monday April 20, 1998 @ 18:06
Author: tridge
Update of /data/cvs/jitterbug/source
In directory samba:/tmp/cvs-serv27608
Modified Files:
proto.h search.c
Log Message:
check for illegal chars in the search expression
****************************************
Date: Monday April 20, 1998 @ 18:08
Author: tridge
Update of /data/cvs/jitterbug/source
In directory samba:/tmp/cvs-serv28133
Modified Files:
search.c
Log Message:
check for illegal chars in the search expression
****************************************
Date: Monday April 20, 1998 @ 23:20
Author: tridge
Update of /data/cvs/jitterbug/source
In directory samba:/tmp/cvs-serv12362
Modified Files:
new_message.c
Log Message:
fixed an autoreply bug
****************************************
Date: Monday April 20, 1998 @ 23:28
Author: tridge
Update of /data/cvs/jitterbug/docs
In directory samba:/tmp/cvs-serv12733
Modified Files:
CONFIG.txt
Log Message:
documented the search program option
****************************************
Date: Monday April 20, 1998 @ 23:31
Author: jitter-b
Update of /data/cvs/jitterbug/source
In directory samba:/data/people/jitter-bugs/jitterbug/source
Modified Files:
version.h
Log Message:
preparing for release of 1.5.1
****************************************
Date: Wednesday April 22, 1998 @ 17:57
Author: jitter-bugs
Update of /data/cvs/jitterbug/source
In directory samba:/data/people/jitter-bugs/jitterbug/source
Modified Files:
jitterbug.c new_message.c
Log Message:
fixed another autoreply bug in the way extract_address() is used
****************************************
Date: Wednesday April 22, 1998 @ 18:11
Author: tridge
Update of /data/cvs/jitterbug/source
In directory samba:/tmp/cvs-serv2039
Modified Files:
jitterbug.c proto.h
Log Message:
search the followups and repies when using an external search program
****************************************
Date: Wednesday April 22, 1998 @ 20:57
Author: tridge
Update of /data/cvs/jitterbug/source
In directory samba:/tmp/cvs-serv9854
Modified Files:
loadparm.c new_message.c proto.h
Log Message:
added "forward all" support (also known as Jeremy mode!)
****************************************
Date: Wednesday April 22, 1998 @ 21:08
Author: tridge
Update of /data/cvs/jitterbug/source
In directory samba:/tmp/cvs-serv26924
Modified Files:
new_message.c
Log Message:
don't need re: on auto forwarded mail
****************************************
Date: Thursday April 23, 1998 @ 10:18
Author: tridge
Update of /data/cvs/jitterbug/source
In directory samba:/tmp/cvs-serv27921
Modified Files:
jitterbug.c
Log Message:
fixed view audit trail bug. Thanks to jseymour@medar.com
****************************************
Date: Monday May 4, 1998 @ 11:58
Author: tridge
Update of /data/cvs/jitterbug/source
In directory samba:/tmp/cvs-serv19459
Modified Files:
lock.c
Log Message:
don't create fname string unless necessary
****************************************
Date: Monday May 4, 1998 @ 12:32
Author: tridge
Update of /data/cvs/jitterbug/docs
In directory samba:/tmp/cvs-serv2780
Modified Files:
INSTALL
Log Message:
examples usng .forward were missing the quotes
****************************************
Date: Monday May 4, 1998 @ 12:32
Author: tridge
Update of /data/cvs/jitterbug/mail
In directory samba:/tmp/cvs-serv24031
Modified Files:
README
Log Message:
examples usng .forward were missing the quotes
****************************************
Date: Monday May 4, 1998 @ 12:42
Author: tridge
Update of /data/cvs/jitterbug/source
In directory samba:/tmp/cvs-serv48
Modified Files:
jitterbug.c new_message.c util.c
Log Message:
fix string verwrite problems with extract_address()
****************************************
Date: Monday May 4, 1998 @ 13:05
Author: tridge
Update of /data/cvs/jitterbug/source
In directory samba:/tmp/cvs-serv20588
Modified Files:
jitterbug.c jitterbug.h
Log Message:
fixed some possible null string problems
****************************************
Date: Monday May 4, 1998 @ 14:21
Author: jitter-b
Update of /data/cvs/jitterbug/source
In directory samba:/data/people/jitter-bugs/jitterbug/source
Modified Files:
version.h
Log Message:
preparing for release of 1.5.2
****************************************
Date: Tuesday May 5, 1998 @ 21:41
Author: jitter-bugs
Update of /data/cvs/jitterbug/source
In directory samba:/data/people/jitter-bugs/jitterbug/source
Modified Files:
util.c
Log Message:
fixed a bug in getmailheader()
****************************************
Date: Wednesday May 6, 1998 @ 22:17
Author: tridge
Update of /data/cvs/jitterbug/source
In directory samba:/tmp/cvs-serv11370
Modified Files:
cgi.c jitterbug.c loadparm.c proto.h
Log Message:
added support for gzip encoding of all pages
****************************************
Date: Wednesday May 6, 1998 @ 22:41
Author: tridge
Update of /data/cvs/jitterbug/source
In directory samba:/tmp/cvs-serv25139
Modified Files:
jconfig.h jitterbug.c
Log Message:
added support for gzip encoding of downloads
****************************************
Date: Wednesday May 6, 1998 @ 22:53
Author: tridge
Update of /data/cvs/jitterbug/docs
In directory samba:/tmp/cvs-serv21446
Modified Files:
CONFIG.txt
Log Message:
document new "gzip path" option
****************************************
Date: Thursday May 7, 1998 @ 12:45
Author: tridge
Update of /data/cvs/jitterbug/source
In directory samba:/tmp/cvs-serv22142
Modified Files:
jitterbug.c
Log Message:
added some sanity checks on some variables, such a dir_cols and
max_message_size
****************************************
Date: Thursday May 7, 1998 @ 13:18
Author: tridge
Update of /data/cvs/jitterbug/source
In directory samba:/tmp/cvs-serv9540
Modified Files:
config.h.in configure configure.in includes.h search.c
Log Message:
add support for POSIX regex searches
****************************************
Date: Thursday May 7, 1998 @ 14:14
Author: tridge
Update of /data/cvs/jitterbug/source
In directory samba:/tmp/cvs-serv6703
Modified Files:
jitterbug.c
Log Message:
a couple of layout changes from dsdee@csc.com
****************************************
Date: Thursday May 7, 1998 @ 15:18
Author: tridge
Update of /data/cvs/jitterbug/source
In directory samba:/tmp/cvs-serv2618
Modified Files:
config.h.in configure configure.in list.c proto.h util.c
Added Files:
acconfig.h
Log Message:
add a check for broken readdir() call on solaris
****************************************
Date: Thursday May 7, 1998 @ 15:26
Author: tridge
Update of /data/cvs/jitterbug/config
In directory samba:/tmp/cvs-serv2990
Modified Files:
footer.html guest.prefs
Removed Files:
jitterbug_help.html
Log Message:
minor updates
****************************************
Date: Thursday May 7, 1998 @ 15:28
Author: jitter-b
Update of /data/cvs/jitterbug/source
In directory samba:/data/people/jitter-bugs/jitterbug/source
Modified Files:
version.h
Log Message:
preparing for release of 1.5.3
****************************************
Date: Thursday May 7, 1998 @ 17:19
Author: tridge
Update of /data/cvs/jitterbug/docs
In directory samba:/tmp/cvs-serv16117
Modified Files:
CONFIG.txt
Log Message:
added "reply strings" option
****************************************
Date: Thursday May 7, 1998 @ 17:19
Author: tridge
Update of /data/cvs/jitterbug/source
In directory samba:/tmp/cvs-serv18442
Modified Files:
loadparm.c new_message.c proto.h util.c
Log Message:
added "reply strings" option
****************************************
Date: Thursday May 7, 1998 @ 17:36
Author: tridge
Update of /data/cvs/jitterbug/source
In directory samba:/tmp/cvs-serv17427
Modified Files:
new_message.c
Log Message:
don't forward all if it is a reply and matches the reply strings
****************************************
Date: Thursday May 7, 1998 @ 17:45
Author: tridge
Update of /data/cvs/jitterbug/source
In directory samba:/tmp/cvs-serv15983
Modified Files:
jitterbug.c
Log Message:
put quotes around all value= HTML (netscape 4.05 needs this?)
****************************************
Date: Thursday May 7, 1998 @ 17:49
Author: jitter-b
Update of /data/cvs/jitterbug/source
In directory samba:/data/people/jitter-bugs/jitterbug/source
Modified Files:
version.h
Log Message:
preparing for release of 1.5.4
****************************************
Date: Thursday May 7, 1998 @ 18:10
Author: jitter-bugs
Update of /data/cvs/jitterbug/source
In directory samba:/data/people/jitter-bugs/jitterbug/source
Modified Files:
util.c
Log Message:
don't check valid_id in count_replies()
****************************************
Date: Thursday May 7, 1998 @ 18:10
Author: jitter-b
Update of /data/cvs/jitterbug/source
In directory samba:/data/people/jitter-bugs/jitterbug/source
Modified Files:
version.h
Log Message:
preparing for release of 1.5.5
****************************************
Date: Friday May 8, 1998 @ 17:15
Author: jitter-bugs
Update of /data/cvs/jitterbug/source
In directory samba:/data/people/jitter-bugs/jitterbug/source
Modified Files:
new_message.c
Log Message:
don't truncate the forward all messages
****************************************
Date: Saturday May 9, 1998 @ 12:45
Author: tridge
Update of /data/cvs/jitterbug/source
In directory samba:/tmp/cvs-serv997
Modified Files:
jitterbug.c proto.h util.c
Log Message:
added "notes lines" option to preferences
****************************************
Date: Saturday May 9, 1998 @ 12:50
Author: tridge
Update of /data/cvs/jitterbug/source
In directory samba:/tmp/cvs-serv26931
Modified Files:
jitterbug.c util.c
Log Message:
added "notes lines" option to preferences
****************************************
Date: Saturday May 9, 1998 @ 13:05
Author: tridge
Update of /data/cvs/jitterbug/source
In directory samba:/tmp/cvs-serv20585
Modified Files:
jitterbug.c
Log Message:
better notes formatting
****************************************
Date: Saturday May 9, 1998 @ 13:24
Author: tridge
Update of /data/cvs/jitterbug/source
In directory samba:/tmp/cvs-serv5357
Modified Files:
jitterbug.c
Log Message:
bold the ... in extra notes
****************************************
Date: Saturday May 9, 1998 @ 13:37
Author: tridge
Update of /data/cvs/jitterbug/source
In directory samba:/tmp/cvs-serv26682
Modified Files:
jitterbug.c
Log Message:
sanity check on notes_lines
****************************************
Date: Tuesday May 12, 1998 @ 0:10
Author: tridge
Update of /data/cvs/jitterbug/source
In directory samba:/tmp/cvs-serv7488
Modified Files:
jitterbug.c
Log Message:
formatting changes from David Dee
****************************************
Date: Tuesday May 12, 1998 @ 0:13
Author: tridge
Update of /data/cvs/jitterbug/source
In directory samba:/tmp/cvs-serv6074
Modified Files:
jitterbug.c
Log Message:
use labels consistently
****************************************
Date: Tuesday May 12, 1998 @ 0:20
Author: tridge
Update of /data/cvs/jitterbug/so 