a...@hypernote.com (Aaron Poffenberger), 2014.02.26 (Wed) 18:30 (CET):
I recently configured smptd to replace a postfix-based solution.
smtpd(8) is a joy to work with. In ~four rules I had a working email
server!
My next goals was to get content filtering in place. I decided on
amavisd-new
On Feb 27, 2014, at 2:17 AM, Marcus MERIGHI mcmer-open...@tor.at wrote:
The question I have for Gilles et al.: Is there a better way to send the
emails to amavisd? It would be more efficient if emails went through
virtual vmap first so invalid recipients were rejected before
content
I recently configured smptd to replace a postfix-based solution.
smtpd(8) is a joy to work with. In ~four rules I had a working email
server!
My next goals was to get content filtering in place. I decided on
amavisd-new with clamav and spamassassin.
I couldn't find any tutorials for using
On Wed, Feb 26, 2014 at 11:30, Aaron Poffenberger wrote:
When amavisd re-injected the email it was rejected by smtpd because To:
user is an invalid recipient. The solution, then, was to defer the
virtual vmap lookup until re-injection. The way to do do that was to
use relay via:
# public
On Feb 26, 2014, at 11:51 AM, Ted Unangst t...@tedunangst.com wrote:
On Wed, Feb 26, 2014 at 11:30, Aaron Poffenberger wrote:
When amavisd re-injected the email it was rejected by smtpd because To:
user is an invalid recipient. The solution, then, was to defer the
virtual vmap lookup until
On Wed, Feb 26, 2014, Aaron Poffenberger wrote:
I tried that. If you telnet into smtpd to manually send an email and set
rcpt to: user you will receive a 553 Recipient address syntax
That's invalid even if you gave a proper address.
RFC 5321:
RCPT TO:forward-path [ SP rcpt-parameters ]
On Feb 26, 2014, at 1:15 PM, Claus Assmann ca+openbsd_m...@esmtp.org wrote:
On Wed, Feb 26, 2014, Aaron Poffenberger wrote:
I tried that. If you telnet into smtpd to manually send an email and set
rcpt to: user you will receive a 553 Recipient address syntax
That's invalid even if you
7 matches
Mail list logo
