| Age | Commit message (Collapse) | Author | Files | Lines |
|---|
|
would otherwise cause a chown of the trigger file. (with DESTDIR,
the "nullmail" user & group are not yet created)
Because this leaves the trigger file possibly owned by root, add
a test in the rc "start" path to [re]make it when necessary.
put this test and the daemon background and logging into a
separate script so that it can be run by the rc framework as the
nullmail user in the normal way, and add a procname argument to
allow the "status" and "stop" rc commands to work properly.
bump PKGREVISION
|
|
|
|
- Fixed problem with multiple arguments to protocol modules.
Thanks Sascha Silbe.
- Fixed extraneous spaces in SMTP sender.
- Made permissions on queued files more strict.
- Handle the "-bs" flag in the sendmail wrapper by dieing when we see it.
- Fixed the address parser handling domain names with trailing periods.
- Fixed bug in header parsing that would cause the last header line to
be repeated if there was no body.
- Fixed bug in handling headers containing CR+LF line endings.
pkgsrc changes:
* Replace @exec and @unexec in PLIST with bsd.pkginstall.mk incantations
* sort PLIST
* Honor VARBASE in manpages and rc.d script
* Enable logging in rc.d script
* Allow rc.d script to start nullmailer without rc.subr
* Take MAINTAINER.
|
|
And always is defined as share/examples/rc.d
which was the default before.
This rc.d scripts are not automatically added to PLISTs now also.
So add to each corresponding PLIST as required.
This was discussed on tech-pkg in late January and late April.
Todo: remove the RCD_SCRIPTS_EXAMPLEDIR uses in MESSAGES and elsewhere
and remove the RCD_SCRIPTS_EXAMPLEDIR itself.
|
|
the RCD_SCRIPTS rc.d script(s) to the PLIST.
This GENERATE_PLIST idea is part of Greg A. Woods'
PR #22954.
This helps when the RC_SCRIPTS are installed to
a different ${RCD_SCRIPTS_EXAMPLEDIR}. (Later,
the default RCD_SCRIPTS_EXAMPLEDIR will be changed
to be more clear that they are the examples.)
These patches also remove the etc/rc.d/ scripts from PLISTs
(of packages that use RCD_SCRIPTS). (This also removes
now unused references from openssh* makefiles. Note that
qmail package has not been changed yet.)
I have been doing automatic PLIST registration for RC_SCRIPTS
for over a year. Not all of these packages have been tested,
but many have been tested and used.
Somethings maybe to do:
- a few packages still manually install the rc.d scripts to
hard-coded etc/rc.d. These need to be fixed.
- maybe remove from mk/${OPSYS}.pkg.dist mtree specifications too.
|
|
- use 1.0.0.7 as PKGVERSION, 1.00RC7 is invalid
- USE_PKGINSTALL, don't include bsd.pkg.install.mk directly
- use automatic rc.d scripts handling
- install example mailer.conf
- minor cleanups
|
|
Changes for pkgsrc:
* Added an rc.d/nullmailer script
* Added brief instructions on how to set up nullmailer in MESSAGE.
* Changed spool directory from /var/nullmailer to /var/spool/nullmailer
Changes in nullmailer itself:
Changes in version 1.00RC7
- Fixed typo in smtp protocol module that caused HELO to be sent without
a hostname.
- Added a one-shot mode to nullmailer-send, triggered by setting the
pausetime to zero.
Note: If no further bugs are found, this will become the official
version 1.00 release.
Changes in version 1.00RC6
- Protocol modules now report all failure and success messages.
- Removed the whole gethostname/getdomainname mess and replaced it with
code to read the hostname from the "me" control file, and the default
domain name from the "defaultdomain" control file.
- Fixed a bug that would cause lines starting with a period to have that
period stripped when it was sent via SMTP.
- Added some missing includes to fix compilation failures in various
sources.
- Fixed a bug in the setenv function in sendmail.cc.
NOTE! Make sure to set up the new "me" control file before using this
version. The RPM install does this automatically.
|
|
|
|
Fix paths in manual pages.
|
|
This is nullmailer, a sendmail/qmail/etc replacement MTA for hosts
which relay to a fixed set of smart relays. It is designed to be
simple to configure, secure, and easily extendable.
|
