Re: Postfix With OpenDKIM: milter: SMFIC_EOH
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't read
> > SMFIC_EOH reply packet header: Invalid argument
Postfix was unable to receive end-of-header packet size, which is
a 32-bit number. On the Postfix side we're talking about code that
has not changed in some 10 years and that is being used world-wide.
Did you build Postfix or OpenDKIM yourself?
Wietse
static int milter8_read_resp(MILTER8 *milter, int event, unsigned char *command,
ssize_t *data_len)
{
UINT32_TYPE len;
...
/*
* Receive the packet length.
*/
if ((vstream_fread(milter->fp, (void *) &len, UINT32_SIZE))
!= UINT32_SIZE) {
smfic_name = str_name_code(smfic_table, event);
msg_warn("milter %s: can't read %s reply packet header: %m",
milter->m.name, smfic_name != 0 ?
smfic_name : "(unknown MTA event)");
> Messages are still sent by Postfix, however the emails do not appear to have
> any DKIM related headers in them. I suspect that the warning above indicates
> that OpenDKIM is not communicating with Postfix correctly and as a result
> messages are not being signed.
>
> I setup Postfix to use OpenDKIM in the Postfix main.cf file:
>
> > milter_protocol = 2
> > milter_default_action = accept
> > smtpd_milters = inet:localhost:12301
> > non_smtpd_milters = inet:localhost:12301
>
> The output of postconf -n and postconf -Mf are in this GitHub Gist:
> https://gist.github.com/Noah-Huppert/0e8160dd6a12e0c62292d1c3f5a262b8
>
> This Gist also contains what I believe to be the relevant OpenDKIM
> configuration.
>
> My efforts to debug this issue have mainly been centered around figuring out
> what the SMFIC_EOH error code means. However I have had no luck. Any help
> figuring out what this error code means or how to fix this issue would be
> greatly appreciated.
>
> Best,
> Noah Huppert
>
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 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) Available For Hire: https://linkedin.com/in/billcole
RE: Postfix With OpenDKIM: milter: SMFIC_EOH
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]" ii libopendkim11 2.11.0~alpha-10+deb9u1 amd64 Library for signing and verifying DomainKeys Identified Mail signatures ii libopendmarc2 1.3.2-2+deb9u1 amd64 Library for DMARC validation and reporting ii opendkim 2.11.0~alpha-10+deb9u1 amd64 Milter implementation of DomainKeys Identified Mail ii opendkim-tools2.11.0~alpha-10+deb9u1 amd64 Set of command line tools for OpenDKIM ii opendmarc 1.3.2-2+deb9u1 amd64 Milter implementation of DMARC ii postfix 3.1.8-0+deb9u1 amd64 High-performance mail transport agent ## Added for OpenDKIM (8892) OpenDMARC (8893) milter_default_action = accept milter_protocol = 6 smtpd_milters = inet:localhost:8892 inet:localhost:8893 non_smtpd_milters = inet:localhost:8892 inet:localhost:8893 > -Oorspronkelijk bericht- > Van: postfixlists-070...@billmail.scconsult.com > [mailto:owner-postfix-us...@postfix.org] Namens Bill Cole > 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 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) > Available For Hire: https://linkedin.com/in/billcole > >
Re: Postfix With OpenDKIM: milter: SMFIC_EOH
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: can't read >> SMFIC_EOH reply packet header: Invalid argument > Messages are still sent by Postfix, however the emails do not appear to > have any DKIM related headers in them. I suspect that the warning above > indicates that OpenDKIM is not communicating with Postfix correctly and as a > result messages are not being signed. > I setup Postfix to use OpenDKIM in the Postfix main.cf file: >> milter_protocol = 2 Only explicitly define such things, when you absolutely know you need them. >> 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 here. > The output of postconf -n and postconf -Mf are in this GitHub Gist: > https://gist.github.com/Noah-Huppert/0e8160dd6a12e0c62292d1c3f5a262b8 > This Gist also contains what I believe to be the relevant OpenDKIM > configuration. > My efforts to debug this issue have mainly been centered around figuring > out what the SMFIC_EOH error code means. However I have had no luck. Any > help figuring out what this error code means or how to fix this issue would > be greatly appreciated. > Best, > Noah Huppert -- With best regards, Andrey Repin Wednesday, February 13, 2019 17:46:16 Sorry for my terrible english...
Re: Postfix With OpenDKIM: milter: SMFIC_EOH
> 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 here. For the record, there are no MX lookups involved in resolving the TCP endpoint for a milter. To avoid DNS lookups here, use: inet:[127.0.0.1]:12301 instead. With hostnames the [] are optional and usually not used. With IPv4 address literals, the [] are also optional, but preferred. With IPv6, they're required: inet:[::1]:12301 -- Viktor.
Re: Postfix With OpenDKIM: milter: SMFIC_EOH
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 Bill & L.P.H: Oh I'm definitely following an old guide: https://www.digitalocean.com/community/tutorials/how-to-install-and-configure-dkim-with-postfix-on-debian-wheezy (2014). My main.cf now reads: > milter_protocol = 6 But the issue still persists. If I remove this directive altogether the issue also still occurs. Andrey & Viktor: My configuration now reads: > smtpd_milters = inet:[127.0.0.1]:12301 > non_smtpd_milters = inet:[127.0.0.1]:12301 The warning still shows up, just with a new address: > postfix/cleanup[20180]: warning: milter inet:[127.0.0.1]:12301: can't read > SMFIC_EOH reply packet header: Invalid argument Thanks all for the debugging help so far. Best, Noah Huppert ‐‐‐ Original Message ‐‐‐ On Wednesday, February 13, 2019 10:09 AM, Viktor Dukhovni wrote: > > On Feb 13, 2019, at 9:48 AM, Andrey Repin anrdae...@yandex.ru 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 here. > > For the record, there are no MX lookups involved in resolving the TCP endpoint > for a milter. To avoid DNS lookups here, use: > > inet:[127.0.0.1]:12301 > > instead. With hostnames the [] are optional and usually not used. With IPv4 > address literals, the [] are also optional, but preferred. With IPv6, they're > required: > > inet:[::1]:12301 > > -- > > Viktor. >
Re: Postfix With OpenDKIM: milter: SMFIC_EOH
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 prevent repeated unnecessary MX/DNS lookups? e.g. # postconf relayhost relayhost = [smtp.talktalk.net]
Re: Postfix With OpenDKIM: milter: SMFIC_EOH
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, and are are not applicable in locating milters, policy services, ... One obvious difference is that milters require an "inet:" or "unix:" prefix, but the SMTP nexthop syntax does not. LMTP (implemented in the same underlying executable as SMTP) also does not use MX lookups, and its nexthop syntax is closer to that of milters: http://www.postfix.org/lmtp.8.html LMTP DESTINATION SYNTAX LMTP destinations have the following form: unix:pathname Connect to the local UNIX-domain server that is bound to the specified pathname. If the process runs chrooted, an absolute pathname is interpreted relative to the Postfix queue directory. inet:hostname inet:hostname:port inet:[address] inet:[address]:port Connect to the specified TCP port on the specified local or remote host. If no port is specified, connect to the port defined as lmtp in services(4). If no such service is found, the lmtp_tcp_port configuration parameter (default value of 24) will be used.An IPv6 address must be formatted as [ipv6:address]. > I thought that for hostname-based relay transports (for example), > including in transport_maps, it was recommended to use [] to > prevent repeated unnecessary MX/DNS lookups? e.g. > > # postconf relayhost > relayhost = [smtp.talktalk.net] This is a matter of *correctness* not efficiency. If, with SMTP, you mean to connect to a specific host, then say so, by enclosing the hostname in []. If you mean to connect to the MX hosts of a particular domain, then leave the [] out. Whichover one is the correct way to reach the destination, the other one is liable to wrong in many cases. Some destinations will resolve to the same set of IP addresses either way, but you should not depend on that. -- Viktor.
Re: Postfix With OpenDKIM: milter: SMFIC_EOH
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 helpful explanation. Little by little, I am learning.
Postfix With OpenDKIM: milter: SMFIC_EOH
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 very familiar with this stack, so I don't have a deep enough > understanding to read the config files and know if something wouldn't work. > My strategy so far has just been to live in man pages until I understand > enough to fix this. > > Best, > Noah > > ‐‐‐ Original Message ‐‐‐ > On Wednesday, February 13, 2019 11:46 AM, L.P.H. van Belle be...@bazuin.nl > wrote: > > > Can help much, but if you google this : > > can't read SMFIC_EOH reply packet header: +"Invalid argument" > > I see only 1 hit. And that reffering to a DB file. > > I suggest, have a look at my script. > > https://github.com/thctlo/debian-scripts/blob/master/setup-opendkim-postfix.sh > > Now its not to run it on you VoidLinux, but read it. > > Or if you can script adjust it and run it. > > Almost all my sources are in it and some extra info is in it. > > I suspect a config error.. As in... Error in user setup and not in postfix > > or OpenDkim. > > The key her imo, is finding the source of "Invalid argument" > > Greetz, > > Louis > > > > > -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 > > > Onderwerp: Re: Postfix With OpenDKIM: milter: SMFIC_EOH > > > 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/srcpkg > > > > s/postfix > > > > > OpenDKIM: > > > https://github.com/void-linux/void-packages/tree/master/srcpkg > > > > s/opendkim > > > > > Bill & L.P.H: > > > Oh I'm definitely following an old guide: > > > https://www.digitalocean.com/community/tutorials/how-to-instal > > > l-and-configure-dkim-with-postfix-on-debian-wheezy (2014). > > > My main.cf now reads: > > > > > > > milter_protocol = 6 > > > > > > But the issue still persists. > > > If I remove this directive altogether the issue also still occurs. > > > Andrey & Viktor: > > > My configuration now reads: > > > > > > > smtpd_milters = inet:[127.0.0.1]:12301 > > > > non_smtpd_milters = inet:[127.0.0.1]:12301 > > > > > > The warning still shows up, just with a new address: > > > > > > > postfix/cleanup[20180]: warning: milter > > > > inet:[127.0.0.1]:12301: can't read SMFIC_EOH reply packet > > > > header: Invalid argument > > > > > > Thanks all for the debugging help so far. > > > Best, > > > Noah Huppert > > > ? Original Message ? > > > On Wednesday, February 13, 2019 10:09 AM, Viktor Dukhovni > > > postfix-us...@dukhovni.org wrote: > > > > > > > > On Feb 13, 2019, at 9:48 AM, Andrey Repin > > > > > anrdae...@yandex.ru 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 here. > > > > > > > > For the record, there are no MX lookups involved in > > > > resolving the TCP endpoint > > > > for a milter. To avoid DNS lookups here, use: > > > > inet:[127.0.0.1]:12301 > > > > instead. With hostnames the [] are optional and usually not > > > > used. With IPv4 > > > > address literals, the [] are also optional, but preferred. > > > > With IPv6, they're > > > > required: > > > > inet:[::1]:12301 > > > > > > > Viktor. > > > >
Re: Postfix With OpenDKIM: milter: SMFIC_EOH
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 represents the connection to the milter. This error is surprising, because even if the connectio were reset by the peer, the error you get back should not be "EINVAL". For that you'd need a negative file descriptor, or a bad buffer pointer, neither of which should be the case here. What operating system is this on? 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. -- Viktor.
Re: Postfix With OpenDKIM: milter: SMFIC_EOH
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 Wednesday, February 13, 2019 4:22 PM, Viktor Dukhovni wrote: > 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 represents the connection to the milter. This error > is surprising, because even if the connectio were reset by the peer, > the error you get back should not be "EINVAL". For that you'd need > a negative file descriptor, or a bad buffer pointer, neither of > which should be the case here. > > What operating system is this on? 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. > > - > > Viktor. >
Re: Feature Request: Allow Rejecting UTF BOM in MAIL FROM
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 sent with the example >> SMTP script from my first message (wherein a UTF BOM is used in the >> email address in the MAIL FROM command) is accepted by Postfix. > 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#strict_smtputf8 > which will do the job. Does it disable the mechanics outlined in "SMTPUTF8 autodetection"[1] ? Or I'm grossly misunderstanding the implications? >> Indeed this behavior I'm talking about is without the client specifying >> SMTPUTF8. > In which case it is not specifically the bytes you're reporting > that are problematic. Likely any non-ascii envelope will fail > in exactly the same way. [1] http://www.postfix.org/SMTPUTF8_README.html#detecting -- With best regards, Andrey Repin Thursday, February 14, 2019 0:42:26 Sorry for my terrible english...
Re: Postfix With OpenDKIM: milter: SMFIC_EOH
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 solution may be to use something more mainstream. > > 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. You could start with running "cleanup -v" (change the master.cf entry), and report verbose logging from one session where the milter protocol fails. That may be easier than "strace" and "tcpdump". -- Viktor.
Re: Feature Request: Allow Rejecting UTF BOM in MAIL FROM
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#strict_smtputf8 > > > > which will do the job. > > Does it disable the mechanics outlined in "SMTPUTF8 autodetection"[1] ? > Or I'm grossly misunderstanding the implications? As documented, it only affects the processing of the message envelope, (in the "MAIL FROM", "RCPT TO" and "VRFY" commands), which will reject non-ascii input when SMTPUTF8 is not signalled by the client. -- Viktor.
Re: Feature Request: Allow Rejecting UTF BOM in MAIL FROM
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://www.postfix.org/postconf.5.html#strict_smtputf8 > > > > > > which will do the job. > > > > Does it disable the mechanics outlined in "SMTPUTF8 autodetection"[1] ? > > Or I'm grossly misunderstanding the implications? > > As documented, it only affects the processing of the message envelope, > (in the "MAIL FROM", "RCPT TO" and "VRFY" commands), which will reject > non-ascii input when SMTPUTF8 is not signalled by the client. And perhaps surprisingly, that is what the code does. This setting is used only while parsing SMTP commands, in the SMTP daemon. Wietse
Re: Postfix With OpenDKIM: milter: SMFIC_EOH
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 you're > having, the simplest solution may be to use something more mainstream. Yes, I see no benefit in struggling with code that works as promised on a wide range of systems. Wietse
Re: Feature Request: Allow Rejecting UTF BOM in MAIL FROM
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 below that is: >> > > >> > > http://www.postfix.org/postconf.5.html#strict_smtputf8 >> > > >> > > which will do the job. >> > >> > Does it disable the mechanics outlined in "SMTPUTF8 autodetection"[1] ? >> > Or I'm grossly misunderstanding the implications? >> >> As documented, it only affects the processing of the message envelope, >> (in the "MAIL FROM", "RCPT TO" and "VRFY" commands), which will reject >> non-ascii input when SMTPUTF8 is not signalled by the client. > And perhaps surprisingly, that is what the code does. This setting > is used only while parsing SMTP commands, in the SMTP daemon. 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 -- With best regards, Andrey Repin Thursday, February 14, 2019 3:46:45 Sorry for my terrible english...
Re: Feature Request: Allow Rejecting UTF BOM in MAIL FROM
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: http://www.postfix.org/SMTPUTF8_README.html#compatibility in the un-anchored "Pre-existing non-ASCII email flows" section. -- Viktor.
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 switch to something more mainstream like Fedora. Thank you all for your help. ‐‐‐ Original Message ‐‐‐ On Wednesday, February 13, 2019 7:09 PM, Wietse Venema wrote: > 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 you're > > having, the simplest solution may be to use something more mainstream. > > Yes, I see no benefit in struggling with code that works as promised > on a wide range of systems. > > Wietse
Re: Postfix With OpenDKIM: milter: SMFIC_EOH
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-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 switch to something more mainstream like Fedora. Thank you all for your help. ‐‐‐ Original Message ‐‐‐ On Wednesday, February 13, 2019 7:09 PM, Wietse Venema wrote: > 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 you're > > having, the simplest solution may be to use something more mainstream. > > Yes, I see no benefit in struggling with code that works as promised > on a wide range of systems. > > Wietse
Re: Postfix With OpenDKIM: milter: SMFIC_EOH
> 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 likely more current. If the OP was adventurous enough to consider "Void Linux", Fedora is a rather conservative choice by comparison. -- Viktor.
