Action Mailer is a framework for designing email service layers. These layers
are used to consolidate code for sending out forgotten passwords, welcome wishes
on signup, invoices for billing, and any other use case that requires a written
notification to either a person or another system.
Action Mailer is in essence a wrapper around Action Controller and the Mail gem.
It provides a way to make emails using templates in the same way that Action
Controller renders views using templates.
Additionally, an Action Mailer class can be used to process incoming email, such
as allowing a blog to accept new posts from an email (which could even have been
sent from a phone).
Action Mailbox routes incoming emails to controller-like mailboxes for
processing in Rails. It ships with ingresses for Mailgun, Mandrill, Postmark,
and SendGrid. You can also handle inbound mails directly via the built-in Exim,
Postfix, and Qmail ingresses.
The inbound emails are turned into InboundEmail records using Active Record and
feature lifecycle tracking, storage of the original email on cloud storage via
Active Storage, and responsible data handling with on-by-default incineration.
These inbound emails are routed asynchronously using Active Job to one or
several dedicated mailboxes, which are capable of interacting directly with the
rest of your domain model.
USES=java:ant does not imply USES=java:run so we need to add the run arg
seperately when we are using USES=java:ant. Not all ports require the
the argument so it is better to address the ports individually instead
of handling it automatically by implying run for ant.
Thanks to vvd for carefully going through this.
Reported by: vvd
Approved by: portmgr (blanket)
The following features have been added or changed:
- Instead of USE_JAVA use USES=java. This defaults to
USES=java:build,run if NO_BUILD is undefined. Else it defaults to
USES=java:run
- Instead of USE_ANT=yes use USES=java:ant which also implies
USES=java:build
- Instead of JAVA_BUILD=yes use USES=java:build. Does not imply run or
extract
- Instead of JAVA_EXTRACT=yes use USES=java:extract does not imply
build or run
- Instead of JAVA_RUN=yes use USES=java:run does not imply extract or
build
- Instead of USE_JAVA=<version> use USES=java and JAVA_VERSION=<version>
Approved by: mat (portmgr), glewis
Differential Revision: https://reviews.freebsd.org/D48201
Our botan2 port is going to expire soon (2025-01-31, see eb1217e8e9).
Switching to botan3 is not a trivial change (e.g. botan3 requires C++20),
so I'll rather wait for upstream to make this change first (see
https://bugzilla.mozilla.org/show_bug.cgi?id=1848104). To avoid
breakages and holdups, just switch to the bundled botan2.
- Remove GENTOO MASTER_SITES as it no longer provides flat layout
- Other remaining MASTER_SITES and distfiles are also unavailable
- WWW is also no longer available
- Set EXPIRATION_DATE 2025-01-26