Hello and thanks for the suggestion.
The thing is I need this in the transport map, as we have to do this for each
sub domain.
Vessel A = *@vessel_A.domain.com
Has smtp relay 1 = a ip adress:25
Has Smtp 2 relay as backup with ipadress and port 20026
Vessel b = *@vessel_b.domain.com
Has smtp re
All i can think of is.
Setup 3 postfix dual smtp.
Server 1, incoming relay.
Which delivers on server 2 and 3 with dual smtp.
Server 2 to
Vessel A = *@vessel_A.domain.com
Has smtp relay 1 = a ip adress:25
Server 3 to
Vessel A = *@vessel_A.domain.com
Has Smtp 2 relay as backup with ipadress
De Petter Mattheas:
> Hello and thanks for the suggestion.
>
>
> The thing is I need this in the transport map, as we have to do this for each
> sub domain.
There is no support for multiple TCP ports in transport maps,
but there is a different solution.
> Vessel A = *@vessel_A.domain.com
> Ha
I learned the hard way that if you don't set $myhostname to a FQDN you can
quickly end up on a black list despite having valid SPF records.
The documentation is IMO insufficiently clear that $myhostname MUST be fully
qualified and that Postfix will NOT tack on $mydomain if no 'dots' are detected.
Patton, Matthew [Contractor]:
> I learned the hard way that if you don't set $myhostname to a FQDN
> you can quickly end up on a black list despite having valid SPF
> records. The documentation is IMO insufficiently clear that
> $myhostname MUST be fully qualified and that Postfix will NOT tack
>
> On Feb 5, 2019, at 3:50 PM, Wietse Venema wrote:
>
> If someone registers the domain 'foo', then that is a valid name,
> and they have right to use "helo foo", "mail from:user@foo", and
> so on.
>
> The problem is not sending helo without a dot, the problem is sending
> helo with a name that d
> Returning to the OP's question, Postfix does append $mydomain to the
> automatically derived value of $myhostname when the latter is not explicitly
> set
> in main.cf and is not fully qualified.
Except that it doesn't. (or I misunderstood what you wrote)
I set $myhostname = 'smtp'.
$mydomain w
On Wed, Feb 06, 2019 at 02:42:58AM +, Patton, Matthew [Contractor] wrote:
> > Returning to the OP's question, Postfix does append $mydomain to the
> > automatically derived value of $myhostname when the latter is not
> > explicitly set
> >
> > -
> If that's what you want, and you're setting myhostname explicitly, then it is
> your
> responsibility to do that. This allows users who do want dotless hostnames to
> have those if that's right for them.
In Internet-connected SMTP (which is something like 99.9% of installations)
if $myh
> On Feb 5, 2019, at 11:36 PM, Patton, Matthew [Contractor]
> wrote:
>
>> You misunderstood the documentation, the domain is only appended when
>> computing the *default* value
>
> No I didn't misunderstand the documentation. I provided both pieces of
> information via main.cf and I damn well
> I repeat, you misunderstood the documentation. Postfix computes its best
> guess at the FQDN when you DO NOT *explicitly* set myhostname, in main.cf.
The issue is NOT that I wanted Postfix to willy-nilly mangle $myhostname into a
FQDN on my behalf. If there were a private keyword of $fqdn th
> On Feb 6, 2019, at 12:50 AM, Patton, Matthew [Contractor]
> wrote:
>
> By perverting the very definition of what is a hostname, Postfix [...]
Such a belligerent, indignant tone never endears an OP to the
project maintainers, and creates a strong disincentive to making
any effort to address th
12 matches
Mail list logo
