until you followed the instructions in pkg-message, the config file didn't
exist and rc.d/dovecot would just silently exit.
While here, also spit out a message reminding you to create the config
files if necessary.
PR: 205761
Submitted by: me@cschwarz.com
SELECTED_OPTIONS is now a framework informational variable, so there
is a name clash with qmail and its slave ports. Just rename the
variable here to remove the conflict (No-op)
Approved by: Just fix it
- install postfix specific mailer.conf.postfix into DATADIR [2]
- use new notation instead PATCH_DIST_STRIP
- bump PORTREVISION
1) detect if the port is installed without TERM, in this case
do not ask the to make postfix the default mailer and respect
the env POSTFIX_DEFAULT_MTA. This helps tools like salt,
ansible, cfengine and puppet during the first package installation.
2) $DATADIR/mailer.conf.postfix can be used by the tools in 1)
MFH: 2016Q1
- install postfix specific mailer.conf.postfix into DATADIR [2]
- make EAI the default, postfix will reject messages if build
w.o. EAI and compatibility_level is set to a value >=1 [3]
- use new notation instead PATCH_DIST_STRIP
- bump PORTREVISION
1) detect if the port is installed without TERM, in this case
do not ask the to make postfix the default mailer and respect
the env POSTFIX_DEFAULT_MTA. This helps tools like salt,
ansible, cfengine and puppet during the first package installation.
2) $DATADIR/mailer.conf.postfix can be used by the tools in 1)
3) Issue noted by Melissa Pilgrim by PM
Short description of the issue:
If compatibility_level is set to a value >= 1, then postfix set
smtputf8_enable=yes. For more information see
$ postconf -d | grep compatibility_level
and
http://www.postfix.org/SMTPUTF8_README.html
MFH: 2016Q1
On system without any IPv6 addresses emailrelay fails to start with messages:
# service emailrelay start
emailrelay: error: cannot bind the listening port: :::25
emailrelay: exception: cannot bind the listening port: :::25
/usr/local/etc/rc.d/emailrelay: WARNING: failed to start emailrelay
PR: 204126
Submitted by: Dmitry Afanasiev
Approved by: maintainer timeout
- Update MASTER_SITES: change from SF to CHEESESHOP
- Update RUN_DEPENDS: always use dns/py-py3dns
- Bump PORTREVISION for dependency change
- Bump PORTREVISION for dependent ports
ALSA currently relies on in-kernel support to enumerate available audio
devices for getUserMedia i.e., to detect a microphone. So, build with
PULSEAUDIO late bindings by default preferred over ALSA, over OSS.
Nop for RUN_DEPENDS or users who previously disabled PULSEAUDIO.
This project is based on the need for a private message system for ging /
social_stream. Instead of creating our core message system heavily dependent on
our development, we are trying to implement a generic and potent messaging gem.
After looking for a good gem to use we noticed the lack of messaging gems and
functionality in them. Mailboxer tries to fill this void delivering a powerful
and flexible message system. It supports the use of conversations with two or
more participants, sending notifications to recipients (intended to be used as
system notifications “Your picture has new comments”, “John Doe has updated his
document”, etc.), and emailing the messageable model (if configured to do so).
It has a complete implementation of a Mailbox object for each messageable with
inbox, sentbox and trash.
The gem is constantly growing and improving its functionality. As it is used
with our parallel development ging / social_stream we are finding and fixing
bugs continously. If you want some functionality not supported yet or marked as
TODO, you can create an issue to ask for it. It will be great feedback for us,
and we will know what you may find useful in the gem.
WWW: https://github.com/mailboxer/mailboxer
Switch to the new location where the tarball is hosted. It is now served as
a tar.bz2 file.
diff -uprN between the old tar.gz file from distcache.FreeBSD.org and the
new one shows no differences.
