We have not checked for this KEYWORD for a long time now, so this
is a complete noop, and thus no PORTREVISION bump. Removing it at
this point is mostly for pedantic reasons, and partly to avoid
perpetuating this anachronism by copy and paste to future scripts.
The reason is strong. A quote from submitter:
In current state choose of native or nullmailer's
sendmail/mailq depends on order of paths in $PATH
instead of sysadmins choose. (/etc/mail/mail.conf in general case)
PR: ports/45152
Submitted by: "."@babolo.ru
After this patch, the action of piping mails out won't stop,
even if all of your mails were failed to deliver. Nullmailer
itself will keep throwing mails to smart relay as long as
there're incoming mails, no matter how broken the recipients
of the previous mails.
Still leave this port in FORBIDDEN state until I address
PR ports/45152
Obtained from: http://www.debian.org/security/2002/dsa-198
Noted by: Volker Stolz <stolz@i2.informatik.rwth-aachen.de>
vulnerability.
No trojan, no privilege gain. Because nullmailer is not DSN aware,
it has nothing to do if the smart relay refuses to relay correctly.
Stopping itself in such condition is a bug, or not a proper feature.
On bugtraq, it's a vulnerability anyway.
o Completely package-safe (with evil tricks)
o Bump PORTREVISION
Because I haven't invented any convenient dialog script to ask people
what protocol (smtp/qmqp) and what address of their mail server, there
still one comment left in pkg-message.
If there's any, please tell me where to steal^h^h^hudy.
Reviewed by: Sybolt de Boer <bolt@xs4all.nl>
If you want to create a file, visit that file with C-x C-f,
then enter the text in that file's own buffer.
Add nullmailer, a sendmail compatible MTA which only does one thing:
send mail to a SMTP or QMQP smart relay.
NOTICE: This port is usable now, but not yet dumb-safe. Please pay
attention on its pkg-message.
