Wietse Venema:
> # postfix stop
> > /usr/sbin/postconf: warning: read "ldap" configuration
> > "/etc/postfix-submission/ldap": Is a directory
>
> I'm closing this bug, so that I can unblock the Postfix 3.3 release.
>
> The reporter has not provided configuration details for reproducing this.
>
It's binded to both, the problem seems to be somewhere in chrooting as
Wietse already supposed, will try that tomorrow
Am 17.02.2018 um 23:48 schrieb Benny Pedersen:
> TG Servers skrev den 2018-02-17 22:45:
>> I had a typo in my config it it now listening on 127.0.0.1:11332 but I
>> am getting the
Ok thanks will turn off all chroots and go stepwise forward tomorrow
Thanks
Am 17.02.2018 um 23:42 schrieb Wietse Venema:
> TG Servers:
>> Hi,
>>
>> I am getting the following error messages when starting up postfix 3.2.4
>>
>> 2018-02-17T21:50:34.594521+01:00 ms2 postfix/cleanup[9220]: fatal
> Then why don't you setup a relay using port 587 elsewhere which you login to
> to send/get emails? I don't think Verizon blocks that port at all...
Cause it would be easier to setup the relay to listen on 2525 in addition to
port 25 rather than setting up authentication on 587. They are doin
TG Servers skrev den 2018-02-17 22:45:
I had a typo in my config it it now listening on 127.0.0.1:11332 but I
am getting the same startup errors actually.
milter_rspamd = inet:[localhost]:11332
non_smtp_milters = $milter_rspamd
smtpd_milters = $milter_rspamd
and lastly why is localhost unknow
TG Servers:
> Hi,
>
> I am getting the following error messages when starting up postfix 3.2.4
>
> 2018-02-17T21:50:34.594521+01:00 ms2 postfix/cleanup[9220]: fatal:
> host/service localhost/11332 not found: Name or service not known
>
> 2018-02-17T21:50:35.594843+01:00 ms2 postfix/pickup[8886]:
Viktor Dukhovni:
> [...]. One can of course automate periodic SMTP TLS policy
> updates from the STS URIs of a handful of providers, and let the
> usual outbound TLS policy take care of the rest:
>
>http://www.postfix.org/TLS_README.html#client_tls_policy
I'm much in favor of reusing the Pos
I had a typo in my config it it now listening on 127.0.0.1:11332 but I
am getting the same startup errors actually.
Am 17.02.2018 um 21:57 schrieb TG Servers:
> Hi,
>
> I am getting the following error messages when starting up postfix 3.2.4
>
> 2018-02-17T21:50:34.594521+01:00 ms2 postfix/clean
> "Dino" == Dino Edwards writes:
>> The main question is, why do you need port other than 25?
Dino> Cause Verizon blocks all incoming and outgoing traffic to port
Dino> 25 unless it's to their SMTP servers and I have an Exchange
Dino> server that needs to send/receive email through an outsid
>The main question is, why do you need port other than 25?
Cause Verizon blocks all incoming and outgoing traffic to port 25 unless it's
to their SMTP servers and I have an Exchange server that needs to send/receive
email through an outside relay.
Hi,
I am getting the following error messages when starting up postfix 3.2.4
2018-02-17T21:50:34.594521+01:00 ms2 postfix/cleanup[9220]: fatal:
host/service localhost/11332 not found: Name or service not known
2018-02-17T21:50:35.594843+01:00 ms2 postfix/pickup[8886]: warning:
maildrop/4612EA0DC
> On Feb 17, 2018, at 2:35 PM, Scott Kitterman wrote:
>
> Here's the current draft:
>
> https://tools.ietf.org/html/draft-ietf-uta-mta-sts-14
>
> Having given it a quick read, I don't know that postfix needs to make any
> changes for this. I believe it could be readily manged by an external
On Saturday, February 17, 2018 07:04:23 PM Jonathan Sélea wrote:
> Hi
>
> Hopefully, I am not one of several who already has asked this question
> before, but here it goes:
>
> When does postfix plans to implement MTA-STS? Big providers (Google,
> Yahoo, Comcast and soon Microsoft) has already im
Hi
Hopefully, I am not one of several who already has asked this question
before, but here it goes:
When does postfix plans to implement MTA-STS? Big providers (Google,
Yahoo, Comcast and soon Microsoft) has already implemented it and
ofcourse - it would be nice if postfix could support it too,
On 17.02.18 12:11, Dino Edwards wrote:
I need to add an additional port for postfix to listen for incoming connections
(port 2525).
why?
Most of the stuff I've seen on the Internet simply states to add the following
in my master.cf
smtp inet n - n - - sm
# postfix stop
> /usr/sbin/postconf: warning: read "ldap" configuration
> "/etc/postfix-submission/ldap": Is a directory
I'm closing this bug, so that I can unblock the Postfix 3.3 release.
The reporter has not provided configuration details for reproducing this.
Based on a reverse code analysi
> 2525 inet n- n -- smtpd
That should work, regardless of what other ports are open, and
regardless of what programs handle those ports.
Wietse
Hello all,
I need to add an additional port for postfix to listen for incoming connections
(port 2525). Most of the stuff I've seen on the Internet simply states to add
the following in my master.cf
smtp inet n - n - - smtpd
2525 inet n- n
18 matches
Mail list logo
