Ok I understood. Thank you guys. I will set for each domain server fqdn as
MX for which is added ssl cert. All things should go well then.
2018-05-28 16:26 GMT+02:00 Ansgar Wiechers :
> Please do not reply off-list.
>
> On 2018-05-28 Poliman - Serwis wrote:
> > 2018-05-28 13:18 GMT+02:00 Ansgar W
@lbutlr:
> I do have one question that I've never noticed before. The settings for =
> mydomain and myhostname show that they are at the default values. Where =
> is postfix getting the defaults for this and does it mean the settings =
> really aren't needed unless your hostname is, for some reason
On Tue, 2018-05-29 at 13:57 -0400, Viktor Dukhovni wrote:
> > On May 29, 2018, at 1:54 PM, Jim P. wrote:
> >
> > It's more of a language "feature". This works:
> >
> > LANG=C comm -1 -2 <(postconf -n) <(postconf -d)
> >
> > this doesn't:
> >
> > LANG=en_US comm -1 -2 <(postconf -n) <(postconf
On 29 May 2018, at 11:57, Viktor Dukhovni wrote:
> The collation rules for "en_US" are abominable. I always set:
>
> LC_CTYPE=en_US.UTF-8 LANG=C
Yep, strongly agree with this. I foolishly had LANG=en_US some time back
thinking it was sensible. It is not. Everything breaks.
> On May 29, 2018, at 1:54 PM, Jim P. wrote:
>
> It's more of a language "feature". This works:
>
> LANG=C comm -1 -2 <(postconf -n) <(postconf -d)
>
> this doesn't:
>
> LANG=en_US comm -1 -2 <(postconf -n) <(postconf -d)
The collation rules for "en_US" are abominable. I always set:
L
On Tue, 2018-05-29 at 13:32 -0400, Viktor Dukhovni wrote:
> > On May 29, 2018, at 12:28 PM, Jim P. wrote:
> >
> > FWIW, I had to use this:
> >
> > comm -1 -2 <(postconf -n|sort) <(postconf -d|sort)
>
> That'd only be needed if you have a funny collation locale.
> Try:
>
> env -i "PATH=$PA
> On May 29, 2018, at 12:28 PM, Jim P. wrote:
>
> FWIW, I had to use this:
>
> comm -1 -2 <(postconf -n|sort) <(postconf -d|sort)
That'd only be needed if you have a funny collation locale.
Try:
env -i "PATH=$PATH" LANG=C LC_COLLATE=C bash -c '
comm -1 -2 <(postconf -n) <(post
On Tue, 2018-05-29 at 10:49 +0200, Stefan Förster wrote:
> * Dirk Stöcker :
> > On Mon, 28 May 2018, Viktor Dukhovni wrote:
> >
> > > > It might be useful, but probably not, to have a version of
> > > > postconf -n that showed the default value along sinde the
> > > > changed value:
> > >
> > > j
On 2018-05-29 (02:35 MDT), Dirk Stöcker wrote:
>
> Do you maybe also have a command to show only changed parameters?
This is doable, but it takes a bit more processing than a single line.
Basically, a shell script that parses the output of
join <(postconf -n) <(postconf -d | sed 's/=/(default
Dirk St?cker:
> On Mon, 28 May 2018, Viktor Dukhovni wrote:
>
> >> It might be useful, but probably not, to have a version of postconf -n
> >> that showed the default value along sinde the changed value:
> >
> > join <(postconf -n) <(postconf -d | sed 's/=/(default:/; s/$/)/')
>
> Do you maybe a
* Dirk Stöcker :
On Mon, 28 May 2018, Viktor Dukhovni wrote:
It might be useful, but probably not, to have a version of postconf -n that
showed the default value along sinde the changed value:
join <(postconf -n) <(postconf -d | sed 's/=/(default:/; s/$/)/')
Do you maybe also have a comman
On Mon, 28 May 2018, Viktor Dukhovni wrote:
It might be useful, but probably not, to have a version of postconf -n that
showed the default value along sinde the changed value:
join <(postconf -n) <(postconf -d | sed 's/=/(default:/; s/$/)/')
Do you maybe also have a command to show only cha
12 matches
Mail list logo
