Re: [Fetchmail-users] message size error in fetchmail :SOLVED

[Matthias A. <mat...@gm...>]

Am 31.10.2017 um 18:42 schrieb Chuck Campbell:
> On 10/31/2017 11:58 AM, Chuck Campbell wrote:
>> I couldn't find a pre-built rpm for Centos 6 for any newer version.
>>
>> I built fetchmail-6.3.26 from sources, but must have done something
>> wrong, because it doesn't appear to do anything, and issues no info,
>> even when invoked with -vvvvv
>>
>> It appears as a running process, but I get no outputs at all. That is
>> an a different issue.
>>
>> I have a great deal of space available, but I'll have to remember how
>> to check available inodes. Curiously, using mpop with procmail, I can
>> get the mail just fine, so I have to believe there is no inode issue
>> (delivery to the same disk/ user).
>>
>> This may well be a sendmail (local) issue. I thought it was too much
>> work to replace it with qmail or postfix, until I know for sure it
>> isn't a fetchmail problem.
>>

At least CentOS/RHEL are more responsive distros, they should have fixed
security issues in 6.3.17 since, I hope they've also fixed
fetchmail-EN-2010-03 (a severe SASL auth bug).

> First, it turns out NOT to be a fetchmail problem, sorry for the
> noise. Now, in case anyone else comes looking for this, here is my
> solution:
>
> Thanks for the suggestion to look into the maillog. It turns out that
> opendkim was trying to create a temp file, and selinux was not
> allowing it. I tried to use audit2allow to build a module to fix this,
> but that failed. I ended up doing this:
>
> semanage permissive -a dkim_milter_t
>
> All is working again. If there is a better way, I'd be happy to hear it.

I'm not using DKIM locally; regarding choice of alternative MTAs I
consider qmail bitrotten beyond recognition, and it's "accept then
bounce" default policy of qmail-smtpd is unacceptable by today's
standards. I have very few Exim installations (notably I've run it for a
few years on a Windows laptop in Cygwin so I had local logs of outbound
mail), but I normally install Postfix, fetchmail just doesn't react all
too well to Postfix's smtpd_delay_reject feature, it expects instant
rejects...

Good that you've solved the issue.