Here's what we do now:
- mail/bogofilter currently depends on lmdb0, a 0.9.X port, so
it continues to work as before
- add a new mail/bogofilter-lmdb1 port that depends on lmdb, the 1.0
version of the LMDB database.
- add the upstream patch for bogofilter 1.3.0.rc1 that I made and
that delphij@ prepared for integration into the ports tree - thanks!
Here's the plan for end of 2026:
- AT THE SAME TIME:
- upgrade mail/bogofilter to depend on LMDB 1.0
- portrm mail/bogofilter-lmdb1
- add a MOVED entry to redirect from bogofilter-lmdb1 to bogofilter.
While here, clean up and rearrange the Makefiles.
PR: 296519
Reviewed by: arrowd
Pull Request: https://github.com/freebsd/freebsd-ports/pull/551
A collection of scripts for manipulating SPF records to stay within
the 10 DNS look-up limit specified in RFC 7208. Also includes scripts
to update SPF records via AWS, Cloudflare, and DNSimple APIs.
PR: 294442
Author: Jordan Montesse <ports@brtsvcs.net>
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.
This is exactly the same as version 6.11.1 but bumps the major version
number to indicate the presence of a BC break in child classes. The
changes in 6.11.0 and 6.11.1 have been reverted in 6.12.0. If you have
code that depends on those changes, please upgrade to 7.0.0 instead.
Apologies for the mix up.
Specifically, lang(), setLanguage(), and $language are now static, and
should be called statically.
Sponsored by: Netzkommune GmbH
Resend is the email API for developers.
The best way to reach humans instead of spam folders. Deliver
transactional and marketing emails at scale.
WWW: https://github.com/resend/resend-python
This filter adds a DKIM signature to emails sent through OpenSMTPd.
The rsa and ed25519 signing algorithms are supported, as well as the
simple and relaxed canonicalization algorithms.
The filter can sign emails for several domains, selecting them
according to the from-header, but can only use a single selector,
managing multiple selectors must be done at the OpenSMTPd level.
It depends on the libopensmtpd port.
An example of a minimal configuration for signing outgoing emails for
domain "example.com" and selector "_selector" would be:
filter "dkimsign" proc-exec "filter-dkimsign -d example.com -s _selector \
-k /usr/local/etc/smtpd/dkim/private.key" user _smtpd group _smtpd
And then you can apply that filter to the mail that needs to be signed:
listen on lo0 filter dkimsign
WWW: https://imperialat.at/dev/filter-dkimsign/
PR: 283823
This library provides an event-based interface for writing OpenSMTPd
filters. It is used by the opensmtpd-filter-dkimsign port as well as
several other filters that do not have ports.
WWW: https://imperialat.at/dev/libopensmtpd/
PR: 283822
tlsrpt-reporter is a TLSRPT reporting service for SMTP TLS Reporting
as defined in RFC 8460. It receives TLSRPT datagrams from a MTA,
collects them, creates a report in conformance with the TLSRPT
Reporting Schema and finally delivers the report either via SMTP,
indirectly by submitting it to a local MTA which ultimately will be
responsible for delivering the report, or directly via HTTP POST.
PR: 285012
Reported by: Yusuf Yaman
Add libtlsrpt shared library. This can be compiled into an MTA
(currently postfix) to enable the sending of TLS reports as defined in
RFC 8460.
I'll be submitting patches to the postfix and postfix-current ports to
enable compiling against this library in the near future.
Changes: https://github.com/sys4/libtlsrpt/blob/v0.5.0/CHANGELOG.md
Take maintainership.
Move port from mail/py-milter to mail/py-pymilter to match the name of
the PyPI package being ported.
Update to version 1.0.6
Use ${PORTSDIR}/mail/sendmail/bsd.milter.mk for consistency with most
other milter ports.
Add options to force selection between the mail/libmilter port and the
libmilter.so bundled with the base FreeBSD-sendmail package. Prefer
the mail/libmilter port on general principles: given that all major
MTA software supports the milter interface, it should be possible to
install milters from pkg(8) without forcing the FreeBSD-sendmail to be
installed.
Changes: https://github.com/sdgathman/pymilter/compare/pymilter-1.0.5...pymilter-1.0.6
Approved by: Gerhard Schmidt (former maintainer)
PR: 286630
This port replaces mail/opensmtpd-extras-table-sqlite.
The opensmtpd-extras-table-* ports got broken by the latest update of
OpenSMTPD, see my message on the mailing list:
https://lists.freebsd.org/archives/dev-commits-ports-main/2025-January/134537.html
I have requested action by fluffy@ both on the message linked above and
privately via email, but I haven't got any response back.
At this point, I want to unblock my workflow and be able to upgrade
OpenSMTPD. I don't have plans to provide alternatives to all the
opensmtpd-extras-table-* ports.
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.
R7 Organizer is a cross-platform Russian office organizer for mail, tasks and contacts.
This is a BASIC version of Organizer package without MS Echange support and less pricing
Sponsored by: Future Crew, LLC
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.
pizauth is a simple program for requesting, showing, and refreshing OAuth2
access tokens. pizauth is formed of two components: a persistent server which
interacts with the user to request tokens, and refreshes them as necessary; and
a command-line interface which can be used by programs such as fdm, neomutt, or
msmtp to authenticate with OAuth2.
https://tratt.net/laurie/src/pizauth/
Many IMAP/SMTP clients, like msmtp, fdm, isync, neomutt or mutt can use OAuth2
access tokens but lack the ability to renew and/or authorize OAuth2
credentials. The purpose of oama is to provide these missing capabilities by
acting as a kind of smart password manager. In particular, access token renewal
happens automatically in the background transparent to the user.
The OAuth2 credentials are kept in a keyring provided by any password manager
with a FreeDesktop.org Secret Service compatible API. Some examples of such
password managers are:
Gnome keyring
KDE Wallet Manager
KeePaasXC
Alternatively GNU PG encrypted files can also be used as a backend for storing
credentials.
https://github.com/pdobsan/oama