FYI:
A new (Jan 2018) RFC is now re-adopting port 465 for mail submission:
https://tools.ietf.org/html/rfc8314
It discusses the rationale, and it is the first RFC that I've found to
be an interesting read. It advocates "Implicit TLS" on port 465 over
either cleartext OR STARTTLS.
On 4/10/
I've been lurking on this list for a long time but I've never posted.
I've attached a perl program I threw together a couple years ago which
does recursive SPF resolution. This might help your debugging.
For this type of testing, pass it a domain on STDIN:
echo 'gmail.com' | spf2ip.pl
I use
As a proof of concept, I have a setup doing that which I think you are
trying to do:
---
table vdomains file:/etc/mail/table_vmail_domains
table vaddr file:/etc/mail/table_vmail_addresses
table vmailstub { '@' = vmail }
listen on em0
action "deliver_vmail" maildir
"/home/vm
Where I said "user virtual" I meant "user vmail". I've not had enough
coffee yet.
On 11/23/2019 9:23 AM, Andrew Swartz wrote:
> As a proof of concept, I have a setup doing that which I think you are
> trying to do:
>
> --
Try removing "rcpt-to " from the 2nd match line and see
what happens.
I put it there because, in my setup, that is the only thing which
prevents accepting mail for a valid virtual domain but invalid name.
But your setup has a subsequent mapping lookup in the action line which
may (or may not) a
This is one possible configuration which should do that which I think
you are describing:
-
table vdomains file:/etc/mail/table_vmail_domains
table vaddr file:/etc/mail/table_vmail_addresses
table vmailstub { '
ed the email for the user "vmail". But now
with the rcpt-to it works perfectly.
Thank you all so much for the help and greetings from Vienna
Leo
Am 07.04.2020 um 01:36 schrieb Andrew Swartz:
This is one possible configuration which should do that whi
