> On Feb 14, 2019, at 1:04 AM, Gary wrote:
>
> If you are going Fedora, you might as well go CentOS. There are minor
> differences in the firewall and the code isn't always cutting edge, but
> CentOS has been a no drama experience for me. It just works.
Fedora should also be fine, and is like
stfix-users@postfix.org
Reply-to: cont...@noahh.io
Subject: Re: Postfix With OpenDKIM: milter: SMFIC_EOH
Completely agree.
I was experimenting to see if this distro would be viable for a sever. After
figuring out that this issue is most likely caused by the oddities of the
distro I am going to s
Completely agree.
I was experimenting to see if this distro would be viable for a sever. After
figuring out that this issue is most likely caused by the oddities of the
distro I am going to switch to something more mainstream like Fedora.
Thank you all for your help.
‐‐‐ Original Message ‐
Viktor Dukhovni:
> On Wed, Feb 13, 2019 at 09:26:29PM +, Noah Huppert wrote:
> > Viktor:
> >
> > > What operating system is this on?
> >
> > Void Linux x86_64-musl
>
> Never heard of it. They seem to have selected LibreSSL, which is
> not supported in Postfix. And with the milter troubles
On Wed, Feb 13, 2019 at 09:26:29PM +, Noah Huppert wrote:
> Viktor:
>
> > What operating system is this on?
>
> Void Linux x86_64-musl
Never heard of it. They seem to have selected LibreSSL, which is
not supported in Postfix. And with the milter troubles you're
having, the simplest solutio
Viktor:
> What operating system is this on?
Void Linux x86_64-musl
> You'd have to do a system call trace of the (IIRC) cleanup(8) process, and
> perhaps also a tcpdump capture on the milter socket to try to tease out
> what's going on.
Oh boy, will do.
‐‐‐ Original Message ‐‐‐
On
On Wed, Feb 13, 2019 at 09:04:41PM +, Noah Huppert wrote:
> > > The key her imo, is finding the source of "Invalid argument"
> >
> > Any tips or guides you could think of that would help debug this issue?
The EINVAL is coming back from a read(2) operation on the Postfix
"vstream" that represe
ouis
> >
> > > -Oorspronkelijk bericht-
> > > Van: cont...@noahh.io
> > > [mailto:owner-postfix-us...@postfix.org] Namens Noah Huppert
> > > Verzonden: woensdag 13 februari 2019 16:35
> > > Aan: Postfix users
> > > Onderwer
On Wed, 13 Feb 2019 at 16:26, Viktor Dukhovni
wrote:
> On Wed, Feb 13, 2019 at 03:52:54PM +, Dominic Raferd wrote:
>
> > > With hostnames the [] are optional and usually not used.
> >
> > OT: is this true generally or just for milter lookups?
>
> Generally, yes, but ...
>
Thanks for the help
On Wed, Feb 13, 2019 at 03:52:54PM +, Dominic Raferd wrote:
> > With hostnames the [] are optional and usually not used.
>
> OT: is this true generally or just for milter lookups?
Generally, yes, but naturally not for the SMTP nexthop syntax.
After all, MX lookups are an SMTP-only feature, a
On Wed, 13 Feb 2019 at 15:10, Viktor Dukhovni
wrote:
> With hostnames the [] are optional and usually not used.
OT: is this true generally or just for milter lookups? I thought that for
hostname-based relay transports (for example), including in transport_maps,
it was recommended to use [] to p
Wietse:
> Did you build Postfix or OpenDKIM yourself?
I installed them with the xbps package manager on Void Linux (x86_64-musl).
Postfix: https://github.com/void-linux/void-packages/tree/master/srcpkgs/postfix
OpenDKIM:
https://github.com/void-linux/void-packages/tree/master/srcpkgs/opendkim
> On Feb 13, 2019, at 9:48 AM, Andrey Repin wrote:
>
>>>
>>> milter_default_action = accept
>>> smtpd_milters = inet:localhost:12301
>>> non_smtpd_milters = inet:localhost:12301
>
> inet:[localhost]:…
> Save a roundtrip to DNS server for MX lookup. It's not needed, nor going to be
> successful
Greetings, Noah Huppert!
> I have a Postfix send only server setup.
> I am attempting to integrate OpenDKIM to mitigate the possibility of being
> blacklisted.
> Whenever I send a message I see the following warning in the syslog:
>> postfix/cleanup[19960]: warning: milter inet:localhost:12301
Verzonden: woensdag 13 februari 2019 14:35
> Aan: Postfix users
> Onderwerp: Re: Postfix With OpenDKIM: milter: SMFIC_EOH
>
> On 13 Feb 2019, at 0:13, Noah Huppert wrote:
>
> > milter_protocol = 2
>
> Why?
>
> It would be shocking if OpenDKIM required
On 13 Feb 2019, at 0:13, Noah Huppert wrote:
milter_protocol = 2
Why?
It would be shocking if OpenDKIM required that. Any milter requiring it
should be considered obsolete.
--
Bill Cole
b...@scconsult.com or billc...@apache.org
(AKA @grumpybozo and many *@billmail.scconsult.com addresses)
Noah Huppert:
> I have a Postfix send only server setup.
>
> I am attempting to integrate OpenDKIM to mitigate the possibility of being
> blacklisted.
>
> Whenever I send a message I see the following warning in the syslog:
>
> > postfix/cleanup[19960]: warning: milter inet:localhost:12301: can
I have a Postfix send only server setup.
I am attempting to integrate OpenDKIM to mitigate the possibility of being
blacklisted.
Whenever I send a message I see the following warning in the syslog:
> postfix/cleanup[19960]: warning: milter inet:localhost:12301: can't read
> SMFIC_EOH reply pac
18 matches
Mail list logo
