* Tomas Korbar:
> This feature is useful for container deployment as you can have
> unified configuration for multiple images.
If you are, for some reason I cannot fathom, unable to provision each
container with a transports table (i.e. a text file), you are doing
containers wrong. ;-) It is not
On 30/07/2020 12:47 am, Wietse Venema wrote:
Henry Miller:
Asking user to type in ?_submission._tcp? seems like a poor
workaround. This being Autodiscovery it?d be logical for Postfix
to automagically derive SRV lookup address based on relayhost
setting.
?relayhost = example.com? is an obvious
On Wed, 29 Jul 2020 11:00:52 -0400 (EDT), Wietse Venema stated:
>Tomas Korbar:
>> Finally,
>> This feature is useful for container deployment as you can have
>> unified configuration for multiple images.
>
>Well, I think I solved THAT problem 20 years ago, with:
>
>relayhost = $mydomain
>
>wh
Tomas Korbar:
> Finally,
> This feature is useful for container deployment as you can have unified
> configuration for multiple images.
Well, I think I solved THAT problem 20 years ago, with:
relayhost = $mydomain
which nowadays might look like
relayhost = $mydomain:587
or
relayho
Henry Miller:
> Asking user to type in ?_submission._tcp? seems like a poor
> workaround. This being Autodiscovery it?d be logical for Postfix
> to automagically derive SRV lookup address based on relayhost
> setting.
>
> ?relayhost = example.com? is an obvious candidate for SRV autodiscovery
> if
Hi,
I'm glad that so many of you stated your opinion.
To be honest, i did not expect this feature to have any security
implications.
Before i post another version of patch i would like to answer to your
questions and then summarize current opinion how this should be done,
so nobody is wasting their
On 7/29/20 9:53 AM, Bastian Blank wrote:
> However, please describe how you would implement the requirements of RFC
> 6125 section 6[2]? You can't use SRV records without support for useful
> server authentication.
Full ack.
That's something most people overlook / ignore when naively asking for
Hi Peter
On Wed, Jul 29, 2020 at 02:46:55PM +1200, Peter wrote:
> On 29/07/20 8:19 am, Jaroslaw Rafa wrote:
> > Could anybody explain *why* using this record by Postfix is needed at all?
> > As far as I understand, SRV records are meant to be use by mail *clients*,
> > to
> > simplify MUA configu
Asking user to type in “_submission._tcp” seems like a poor workaround. This
being Autodiscovery it’d be logical for Postfix to automagically derive SRV
lookup address based on relayhost setting.
“relayhost = example.com” is an obvious candidate for SRV autodiscovery if an
MX lookup fails or if
On 29/07/20 8:19 am, Jaroslaw Rafa wrote:
Could anybody explain *why* using this record by Postfix is needed at all?
As far as I understand, SRV records are meant to be use by mail *clients*, to
simplify MUA configuration by the end user (no need to type in hostnames of
IMAP and SMTP servers, et
On 27/07/20 7:46 pm, Tomas Korbar wrote:
I used this patch [1] to make postfix 3.5.4 support resolving of this:
"relayhost = [_submission._tcp.$mydomain]:587"
as a valid host for submission of mail in my domain.
I don't particularly care for this syntax because it clashes with syntax
for a
Could anybody explain *why* using this record by Postfix is needed at all?
As far as I understand, SRV records are meant to be use by mail *clients*, to
simplify MUA configuration by the end user (no need to type in hostnames of
IMAP and SMTP servers, etc.)
Postfix is not supposed to be configure
I wrote:
> SRV lookup can return more than one record, and those records
> specify a TCP or UDP port. It basically means that SRV returns
> someothing similar to MX lookup except that it also returns a port
> to connect to.
And:
> This means that we'd have to extend the DNS_RR with at least a
> fi
On Tue, Jul 28, 2020 at 02:02:06PM -0400, Wietse Venema wrote:
> > The MSA needs be authenticated before password-equivalent authentication
> > is performed.
>
> Authenticate what hostname? The SRV record is like an MX record on
> steroids, there are no guarantees about what hostname to expect.
Viktor Dukhovni:
> On Mon, Jul 27, 2020 at 09:46:10AM +0200, Tomas Korbar wrote:
>
> > Hi guys,
> > I would like to start a discussion about support for SRV records, mainly
> > record for submission service of a domain.
> > As is stated in [0], domain can publish dns record, which tells services
>
On Mon, Jul 27, 2020 at 09:46:10AM +0200, Tomas Korbar wrote:
> Hi guys,
> I would like to start a discussion about support for SRV records, mainly
> record for submission service of a domain.
> As is stated in [0], domain can publish dns record, which tells services
> where the submission service
Wietse Venema:
> Whoa. SRV specifies a lot of things that your patch is ignoring.
>
> - TCP or UDP port
> - priority and weight
> - there can be more than one record
Looking at RFC 6186, the Postfix client definitely should not ignore
the port in the SRV record.
Also, the Postfix DNS client shou
Tomas Korbar:
> Hi,
>
> > Is "_submission._tcp" special only in the SMTP client? What happens
> > with "_submission._tcp.$mydomain in other Postfix programs?
>
> _submission._tcp is special only to SMTP client. Behaviour of all other
> programs remains the same.
>
> > The patch changes the globa
Hi,
> Is "_submission._tcp" special only in the SMTP client? What happens
> with "_submission._tcp.$mydomain in other Postfix programs?
_submission._tcp is special only to SMTP client. Behaviour of all other
programs remains the same.
> The patch changes the global proto_info structure. That is
Tomas Korbar:
> Hi guys,
> I would like to start a discussion about support for SRV records, mainly
> record for submission service of a domain.
> As is stated in [0], domain can publish dns record, which tells services
> where the submission service of this domain is.
> This could be used for auto
Hi guys,
I would like to start a discussion about support for SRV records, mainly
record for submission service of a domain.
As is stated in [0], domain can publish dns record, which tells services
where the submission service of this domain is.
This could be used for auto configuration of postfixs
21 matches
Mail list logo
