On Fri, 4 Sep 2015, Tomas Macek wrote:
On Fri, 4 Sep 2015, Viktor Dukhovni wrote:
On Fri, Sep 04, 2015 at 09:44:50AM +0200, Tomas Macek wrote:
> Here is the result cfg:
>
> submission inet n - n - - smtpd
> -o smtpd_etrn_restrictions=reject
>
Am 06.09.2015 um 12:21 schrieb Benning, Markus:
Am 2015-09-05 20:43, schrieb Viktor Dukhovni:
What I've not yet checked, is whether Fedora (like Debian) has
started splitting up Postfix into multiple RPMs with optional
databases (LDAP, MySQL, ...) in separate packages, now that Postfix
supports
Hi Viktor,
Thank you for the confirmation! We are on AIX 61 TL9 SP5 and AIX71 TL3
SP5 which are most recent version.
We had the same error since postfix v2.11.0 (with AIX61 TL9 sp4 and AIX71
TL3 SP4).
Thank you!
Takae Harrington
Unix Administrator
Cloud Managed Service Delivery (MSD)
IBM GTS
Viktor Dukhovni:
> The solution is a more modern C/resolver library and associated
> header files. Postfix support for DNSSEC could be compiled out of
> this system by adding override macros that disable attempts to
> support DNSSEC even when RES_USE_DNSSEC is present. Apply the
> patch below
On 9/7/2015 12:44 AM, Czarek wrote:
>
> Hello.
> For incomming messages I found in the logs:
> spf: lookup failed: addr is not a string at
> /usr/share/perl5/vendor_perl/IO/Socket/IP.pm line 662
>
> Spamd log:
> Sep 7 10:24:41 kukuniek spamd[11515]: spamd: connection from
> localhost
On 09/06/2015 02:47 PM, Steve Jenkins wrote:
> On Sat, Sep 5, 2015 at 5:59 PM, Viktor Dukhovni
> That's fine. I wasn't trying to pick a fight, or even be contrary. My
> question was sincere as I'm always interested in learning. If there are
> valid reasons why one should completely avoid building
