Heads-up! The .poprc compatibility hack that allows the first user declaration of more than one in a server entry to omit the "username" keyword has been causing some confusion (see question F3 in the FAQ for details). This now generates a warning to standard error. In a future release, probably 4.0, this hack will be removed and the leading `username' token required for every user entry in a multi-user poll declaration. Known But Unresolved Bugs: * In multidrop mode without an applicable localdomain, addresses of the form "foo"@bar.com are not parsed correctly, even though they are technically RFC822 legal. The general problem is mentioned on the man page. * Dave Holland thinks it's a misfeature that --fetchall overrides --limit. He may have a point. Perhaps I should re-code this so --limit is still operative with --fetchall on, but you can turn off the size limit with --limit 0. * Use the libmd functions for md5 under Free BSD? (Low priority.) Release Notes: ------------------------------------------------------------------------------ pl 3.9.6 (): * Fix the libc6 configuration stuff (thanks to Jesse Thilo). * Support for Kerberos-v4-authenticated IMAP. * Don't choke on RFC822 group names. * More improvements in RFC822 name parsing. * Interval skip feature, courtesy of Hal DeVore. pl 3.9.5 (Sun May 18 01:05:13 EDT 1997): * Add an error notification when an incoming message has embedded NULs. * Throw out >From lines in headers to prevent getting hosed by upstream sendmails with the 'E' option on. * Enable forcecr to work on the \r\n header terminator line. * Multiple-folder support for POP2 and IMAP. * Under IMAP, bodies of messages refused by SMTP's 571 response are no longer fetched. * Configure should do the right thing with libc6 now. There are 249 people on the fetchmail-friends list. pl 3.9.4 (Wed May 14 12:27:22 EDT 1997): * Fixed a compilation glitch for systems like SunOS & others without atexit(3). * Fixed a compilation glitch in daemonize for HP-UX. * Changes to compile correctly on systems that have on_exit() but not atexit(). * Changes to forbid duplicate server names in the rc file. * Do caseblind comparisons of host and user names everywhere. * IMAP retrieval can now handle messages with embedded NULs. * Fixed a core dump in .netrc searching reported by Jim Spath. There are 248 people on the fetchmail-friends list. pl 3.9.3 (Wed May 7 11:40:47 EDT 1997): * Fix for -I option from George Sipe. * Finally got error.c to compile under AIX, thanks to Dave Vinish. * Prevent header rewrite logic from appending mailserver name to blank To. * When header rewrite is on, hack Return-Path as well. There are 240 people on the fetchmail-friends list. pl 3.9.2 (Wed Apr 23 14:07:03 EDT 1997): * Fixed a glitch in the Makefile yacc and lex productions * Add logic for X-Fetchmail-Warning emission of \r\n to pacify qmail. * Yet another try at getting error.c to play nice with AIX. There are 224 people on the fetchmail-friends list. pl 3.9.1 (Thu Apr 17 11:37:14 EDT 1997): * Hypertext FAQ added to distribution manifest. * RPM builder production fixed. * Minor additions and corrections to man page. * Delivery failures are now syslogged as LOG_ERR, not LOG_INFO. * --check now turns off --daemon. * --syslog is now independent of --daemon. * Multiple-error X- headers are improved. * Added `forcecr' to fix qmail problems by forcing CRLF termination. There are 222 people on the fetchmail-friends list. (many bad addresses were dropped after the switchover to SmartList) ------------------------------------------------------------------------------ fetchmail-3.9 (Wed Apr 2 13:36:22 EST 1997) features -- * It is now possible to set a default poll interval with `set daemon'. * -U/uidl option to force UIDL use under POP3 (thanks, Ingmar Baumgart). bugs -- * Server-response timeouts were broken. Various symptoms of this problem were reported by Klee Dienes , Dirk Eddelbuettel , Robert V. Schipper , and Steven Brown . * George Sipe sent a fix for the --monitor code. * --norewrite was a no-op. Fixed. * Fetchmail was aborting with "partial message buffer overflow" on Suns due to unreliable vsprintf return. This has been fixed with changes to error.c. There are 268 people on the fetchmail-friends list. ------------------------------------------------------------------------------ fetchmail-3.8 (Fri Mar 7 17:34:02 EST 1997) features -- * More FAQ material on using `localdomains'. * Compilation hacks for ISC 4.0 (thanks, Larry Jones!). bugs -- * Enabled ETRN and RPOP command-line options. * Yet another attempt to fix the error.c compilation problems under Solaris and NEXTSTEP. * Handle \( and \) correctly in RFC822 comments, thanks to Gareth McCaughan. * Fixed off-by-one error fingered by Brian Jones that prevented `localdomains' from working. There are 248 people on the fetchmail-friends list. ------------------------------------------------------------------------------ fetchmail-3.7 (Fri Feb 21 17:38:40 EST 1997) features -- * You can now specify a hunt list of SMTP forwarding hosts. * Treat unexpected EOF as a protocol error. * DNS errors no longer abort an entire poll. Instead they just cause forwarding and deletion of the current message to be suppressed. * -v output now includes the version/pl numbers (help for harried maintainer!). bugs -- * Fix password-shrouding logic so it doesn't crap out on a zero-length password. * Various error-logging fixes by Dave Bodenstab. * Fix parsing bug that broke UIDL-processing code. There are 233 people on the fetchmail-friends list. ------------------------------------------------------------------------------ fetchmail-3.6 (Mon Feb 17 00:19:55 EST 1997) features -- * Use Return-Path for RCPT FROM if possible for better behavior on mailing lists and bouncemail. * New Makefile production to generate an RPM. * The `no received' option of 3.4 is gone. Instead, say `no envelope'. This suppresses all attempts to extract an envelope address and route based on it. If you set `no envelope' in the defaults entry it is possible to undo that in individual entries by using `envelope '. bugs -- * Yet another fix to the password-shrouding logic. * Fix bug that screwed up IMAP mail reception in -v mode *only*. There are 229 people on the fetchmail-friends list. ------------------------------------------------------------------------------ fetchmail-3.5 (Sat Feb 15 15:19:36 EST 1997) features -- * The host that ETRN specifies is now set by the smtphost option. * It is now possible to suppress Received line parsing in multidrop mode with a new `no received' per-server option. * Major FAQ reorganization and additions. * .poprc-style `user'-less entry now triggers a warning. bugs -- * The counter referred to by the batchlimit option used to count not only fetched messages but skipped ones. This has been fixed. * Compilation fixes for Kerberos V4 support and GNU glibc2 support. There are 230 people on the fetchmail-friends list. ------------------------------------------------------------------------------ fetchmail-3.4 (Wed Feb 12 19:23:06 EST 1997) features -- * Support for ESMTP ETRN extension. * It is now possible to turn off option flags in individual server entries that had been turned on in a `defaults' entry. * The code should now deal gracefully with headerless mail. bugs -- * The bug that displayed incorrect sizes for POP3 connections has been fixed. * Upped the %a option in the lexer file so SunOS 4.1.3 lex won't choke with a "Too Many Transitions" error. * Size-ticker dots are now disabled when verbose is on. This should eliminate some alarming but harmless "(message incomplete)" messages from the error-logging machinery. * A core dump in save_str_pair() that only showed up on some systems has been fixed. There are 223 people on the fetchmail-friends list. ------------------------------------------------------------------------------\ pl 3.3.2 (Mon Feb 3 12:59:33 EST 1997): * Minor fixes to stripcr and password-shrouding logic. pl 3.3.1 (Sun Feb 2 02:17:07 EST 1997): * Fix incorrect stripcr processing * Unapply a patch that broke error logging to files. ------------------------------------------------------------------------------\ fetchmail-3.3 (Sat Feb 1 15:15:13 EST 1997) features -- * Whether or not carriage returns will be stripped on output is explicitly controllable with stripcr. * fetchmail -v messages no longer reveal password lengths. bugs -- * Correction to length-extraction code for servers that return (nnn octets). * Correction to RF822 continuation code so it doesn't eat leading blank-led lines in the text. There are 215 people on the fetchmail-friends list. ------------------------------------------------------------------------------ fetchmail-3.2 (Mon Jan 27 02:51:10 EST 1997) features -- * Better error notification on IMAP select failure. bugs -- * The code can now handle arbitrarily long address lists. * Fix RFC822 parsing to strip comments at end of bare addresses. * Explicitly strip CRs out of fetched mail. * Corrections to 8BITMIME processing. There are 207 people on the fetchmail-friends list. ------------------------------------------------------------------------------ fetchmail-3.1 (Fri Jan 24 12:45:18 EST 1997) features -- * Forwarding is now done via ESMTP where possible. * ESMTP 8BITMIME option is supported; when 8BITMIME is supported and the Content-Transfer-Encoding header is 7BIT or 8BIT, it is appended to the MAIL FROM command as a BODY option. * ESMTP SIZE option is supported when using IMAP2bis or IMAP4. This means messages too long for the local ESMTP listener will be rejected *before* they are passed to the ESMTP listener. * IMAP code now detects IMAP4rev1 capabilities (RFC 2060) and uses them. (It will fall back to IMAP4 or IMAP2bis depending on what it sees.) bugs -- * Compilation fixes for non-Linux machines. There are 205 people on the fetchmail-friends list. ------------------------------------------------------------------------------ fetchmail-3.0 (Tue Jan 21 16:44:56 EST 1997) features -- * `interface' and `monitor' options are now per-server. * `batchlimit' option is now per-user. * RFC822 header continuation for long address lists is is now handled properly. * There is now a `nodns' option to suppress DNS checking of address hostname parts in multidrop mode (make sure your aka list is complete before you use this!). * Options such as `nokeep' can now be written `no keep'. * RPOP support is back by user request. Note: The first two changes mean that older .fetchmailrc files using the `set' syntax for these options will cause fetchmail to die with a parse error at initialization time. Conversion is trivial -- for details, see the FAQ. bugs -- * Stricter parsing of greeting message for the host name; eliminates some minor errors when using IMAP and the hostname is something like jet.es. * --quit in root-daemon mode didn't work, fixed this. * Ensure that default server parameters get properly zeroed out after each poll or skip statement in .fetchmailrc. * Arrange an EXPUNGE after each delete when using IMAP, so deletions get done OK even if there's a socket error before termination. * Simpler and better header-rewrite code, fixing some weird cases where it failed. Thanks to Masafumi NAKANE and Carey Evans for pointing out these problems. * Handle zero-length messages properly; thanks to Bob Craycroft. Note: the RFC subdirectory is no longer included with the distribution (this cut its size in half!) Instead, applicable RFCs are listed on the manual page. There are 201 people on the fetchmail-friends list. ------------------------------------------------------------------------------ fetchmail-2.8 (Sat Jan 11 15:48:33 EST 1997) features -- * We now get the hostname used for progress messages from the server greeting. This means you'll get sensible-looking progress messages even when using ssh to redirect secure connections. * Reorganized and improved man page. * Mail header parsing now handles RFC822 escapes properly. bugs -- * Stop netrc parser from complaining about blank lines. * Add ssh recipe correction. * Eliminate infinite-loop bug in defaults handling. * Fixed some address-parsing bugs in rfc822.c:nxtaddr(). * 2.7 broke portability to Solaris. Fix that. There are 184 people on the fetchmail-friends list. ------------------------------------------------------------------------------ fetchmail-2.7 (Thu Jan 9 03:18:15 EST 1997) features -- * New --syslog option by Dave Bodenstab. * Automatic parsing of ~/.netrc for a mailserver password if necessary, thanks to Gordon Matzigkeit. * Added preconnect option for initializing ssh connections. * Added local-domains support for multidrop as requested by Pablo Saratxaga. * More FAQ material on how and when to use --interface. bugs -- * Fixed a minor bug introduced into From handling by 2.6. * Fixed bug in SMTP forwarding of msg lines with leading dot. * Fixed a bug that generated incorrect HELO for second and subsequent poll entries attached to the same SMTP host. There are 177 people on the fetchmail-friends list. ------------------------------------------------------------------------------ fetchmail-2.6 (Fri Dec 27 12:42:56 EST 1996) features -- * IMAP4 code now sets the server "seen" flag on each message if "keep" is on. * New FAQ material on how to use --interface. bugs -- * Dropped back to separate SockGets/SockWrite code with no attempt at stdio buffering -- we hope this will fix the Solaris peoples' problems. * Fixed length-computation bug (apparently introduced in 2.3) that messed up IMAP deletes. There are 169 people on the fetchmail-friends list. ------------------------------------------------------------------------------ fetchmail-2.5 (Mon Dec 23 04:18:54 EST 1996) features -- * New --interface and --monitor options for Linux courtesy of George Sipe. bugs -- * Replaced bug-prone setvbuf with setlinebuf. * Moved lock file to ~/.fetchmail to eliminate various /tmp problems. There are 165 people on the fetchmail-friends list. ------------------------------------------------------------------------------ fetchmail-2.4 (Sat Dec 21 05:24:44 EST 1996) features -- * Add FAQ material on troubleshooting and working around SMTP connection fa
		    GNU GENERAL PUBLIC LICENSE
		       Version 2, June 1991

 Copyright (C) 1989, 1991 Free Software Foundation, Inc.
     59 Temple Place, Suite 330, Boston, MA  02111-1307  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

	    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) <year>  <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., 59 Temple Place, Suite 330, Boston, MA  02111-1307  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) year  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.
generated by cgit v1.2.3 (git 2.46.0) at 2026-04-18 23:38:25 +0000
A_PATH and MDA_ARGS carefully. They should match the values found in your sendmail.cf file on the line which begins with "Mlocal". Other changes from popclient version 2.21: o no longer uses getpass() from the C library. The internal getpassword() function allows the use of long passwords. o integrated GNU getopt() for long options. Long option names will appear in a future beta. o Several compiler warnings fixed. o Fixed problems related to missing include files in Solaris port.