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
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)
Did someone look at a "old" howto here?
Postfix manual shows clearly.
/etc/postfix/main.cf:
# Postfix ?? 2.6
milter_protocol = 6
# 2.3 ?? Postfix ?? 2.5
milter_protocol = 2
This works fine on Debian Stretch, if you set milter_protocol = 6
dpkg -l | egrep "postfix|opend[m,k]"
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
> 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
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 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
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 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
Oops forgot to send to list, sorry:
‐‐‐ Original Message ‐‐‐
On Wednesday, February 13, 2019 3:48 PM, Noah Huppert wrote:
> Louis:
>
> > 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?
>
> I am not v
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
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
Greetings, Viktor Dukhovni!
> On Mon, Feb 11, 2019 at 01:56:56PM -0700, Zach Callear wrote:
>> Viktor Dukhovni:
>> > Have you tried:
>> > strict_rfc821_envelopes = yes
>>
>> I just tested it. With "strict_rfc821_envelopes = yes", and with a
>> blank "smtpd_helo_restrictions" setting, email
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
On Thu, Feb 14, 2019 at 12:45:37AM +0300, Andrey Repin wrote:
> > Indeed I forgot that this does not enforce an ASCII character-set:
> >
> > http://www.postfix.org/postconf.5.html#strict_rfc821_envelopes
> >
> > However, right below that is:
> >
> > http://www.postfix.org/postconf.5.html#s
Viktor Dukhovni:
> On Thu, Feb 14, 2019 at 12:45:37AM +0300, Andrey Repin wrote:
>
> > > Indeed I forgot that this does not enforce an ASCII character-set:
> > >
> > > http://www.postfix.org/postconf.5.html#strict_rfc821_envelopes
> > >
> > > However, right below that is:
> > >
> > > http:
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
Greetings, Wietse Venema!
> Viktor Dukhovni:
>> On Thu, Feb 14, 2019 at 12:45:37AM +0300, Andrey Repin wrote:
>>
>> > > Indeed I forgot that this does not enforce an ASCII character-set:
>> > >
>> > > http://www.postfix.org/postconf.5.html#strict_rfc821_envelopes
>> > >
>> > > However, right
On Thu, Feb 14, 2019 at 03:48:45AM +0300, Andrey Repin wrote:
> Makes sense, thank you.
>
> So, next question is, do you want it to be mentioned in "Enabling Postfix
> SMTPUTF8 support" [2] or separately?
>
> [2] http://www.postfix.org/SMTPUTF8_README.html#enabling
My guess would be under:
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 ‐
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.
Original Message
From: cont...@noahh.io
Sent: February 13, 2019 9:27 PM
To: postfix-us
> 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
22 matches
Mail list logo
