Email from in-house copier junked because of SPF

This is a new install. Most of it seems to be working fine, including our SPF.

We have a in-house copier that emails PDF of scanned items to local users. These emails are flagged as spam:

Feb 16 16:13:32 mail postfix/smtpd[19070]: connect from unknown[]
Feb 16 16:13:32 mail postfix/smtpd[19070]: warning: restriction `reject_authenticated_sender_login_mismatch' ignored: no SASL support
Feb 16 16:13:32 mail postgrey[1625]: action=pass, reason=triplet found, client_name=unknown, client_address=,,
Feb 16 16:13:32 mail postfix/smtpd[19070]: 9BD1DA415BB: client=unknown[]
Feb 16 16:13:32 mail postfix/cleanup[20075]: 9BD1DA415BB: message-id=<>
Feb 16 16:13:32 mail opendmarc[1137]: implicit authentication service:
Feb 16 16:13:32 mail opendmarc[1137]: 9BD1DA415BB: SPF(mailfrom): fail
Feb 16 16:13:32 mail opendmarc[1137]: 9BD1DA415BB: fail
Feb 16 16:13:33 mail postfix/qmgr[1753]: 9BD1DA415BB: from=<>, size=934827, nrcpt=1 (queue active)
Feb 16 16:13:33 mail postfix/smtpd[19070]: disconnect from unknown[] helo=1 mail=1 rcpt=1 data=1 quit=1 commands=5
Feb 16 16:13:33 lmtp(20102): Info: Connect from
Feb 16 16:13:33 mail spampd[9620]: processing message <> for <>
Feb 16 16:13:34 mail spampd[9620]: identified spam <> (11.28/5.00) from <> for <> in 1.76s, 935081 bytes.
Feb 16 16:13:35 lmtp( Info: gNCyAY1DLGCGTgAA1nX8CA: sieve: msgid=<>: stored mail into mailbox 'Spam'
Feb 16 16:13:35 lmtp(20102): Info: Disconnect from Successful quit
Feb 16 16:13:35 mail postfix/lmtp[20076]: 9BD1DA415BB: to=<>, relay=[]:10025, delay=2.7, delays=0.4/0/0.01/2.2, dsn=2.0.0, status=sent (250 2.0.0 <> gNCyAY1DLGCGTgAA1nX8CA Saved)
Feb 16 16:13:35 mail postfix/qmgr[1753]: 9BD1DA415BB: removed
mail header
Return-Path: <>
Received: from ([])
	by with LMTP id gNCyAY1DLGCGTgAA1nX8CA
	for <>; Tue, 16 Feb 2021 16:13:33 -0600
X-Spam-Checker-Version: SpamAssassin 3.4.2 (2018-09-13) on
X-Spam-Flag: YES
X-Spam-Level: ***********
X-Spam-Status: Yes, score=11.3 required=5.0 tests=DMARC_FAIL_QUARANTINE,
	autolearn_force=no version=3.4.2
	*  5.0 SPF_FAIL SPF check failed
	*  5.0 DMARC_FAIL_QUARANTINE DMARC check failed (p=quarantine)
	*  0.0 SPF_HELO_NONE SPF: HELO does not publish an SPF Record
	*  1.3 RDNS_NONE Delivered to internal network by a host with no rDNS
	*  0.0 TO_EQ_FM_DOM_SPF_FAIL To domain == From domain and external SPF
	*       failed
X-Spam-Score: 11.3
Received: from (unknown [])
	by (Postfix) with SMTP id 9BD1DA415BB
	for <>; Tue, 16 Feb 2021 16:13:32 -0600 (CST)
Authentication-Results:; dmarc=fail (p=quarantine dis=none)
Authentication-Results:; spf=fail
Authentication-Results:; dkim=none;

First of all, the copier is pretty old. I corrected several issues with the copier configuration but they didn’t fix the issue entirely. Some of the configuration can’t be set the same way I would configure a computer.

SMTP from the copier points to the mail server using port 25, originally without authentication.This worked fine on our old server which ran SpamAssassin, but didn’t have SPF configured. Actually all of our computers were set to use port 25, but that errored out with MaiB. Changing them to port 587 fixed that. I changed the copier to port 587 but there was a note in the config that password encryption wouldn’t work without a certificate installed (???). I tried it anyway and the auth was rejected.

So, two questions: any thoughts on configuring an old copier? It is a Ricoh 400C. Or, how do I go about whitelisting the sucker?


Seems like this might be what you are looking for:

Note that may get overwritten on future updates, but I think that spamassassin will load all of the files in /etc/spamassassin/ so you could add a custom whitelist file, but don’t quote me on that.


I think that the easiest approach is going to be changing your SPF and DMARC records accordingly.

I am still trying to formulate what the correct records would be to accomplish this.

Can you easily enough change the email address of the printer to say, ? You’d want to add that email to MiaB so that the authentication will work, and that the adjustment of the SPF and DMARC records won’t affect your normal domain email.

I am curious as to why you have entered your DNS MX record(s) the way that you have.

1 Like

Yeah, I hadn’t thought about that. The SPF and DMARC records will apply only to their domain or subomain of the record (assuming DMARC isn’t configured to be for all subdomains, IIRC is an option but not used by default MiaB config).

Finally getting back to this. I had to play phone geek instead of mail geek for several days.

@alento: I can change the copier address easily, but I’m a bit fuzzy on the logic. One of the issues is that I can’t authenticate on 587 due to the lack of a certificate on the copier (at least that’s what the copier interface says). If I try it, I get an auth error from MaiB. My only option has been sending on port 25 which, as I understand, ends up being anonymous. Thus MiaB sees it as an external or separate server rather than local and the SPF checks kick in?

I suppose one thing that I should clarify, just in case, is that all emails from the copier remain in-house. Nothing should be going to an external server.

On the MX thing, the two listings are a suggestion I came across to make greylisting a little more user friendly. The first try defers, then the sender tries the next MX which presents as a retry and the email is accepted since it has been seen before. That’s the theory anyway. So far, not really working.

So that it is in the same domain. Currently it is using a subdomain.

Received: from (unknown [])

Yeah, there needs to be a time delay in between. I think MiaB is set at 8 minutes.

Your solution is likely a smtp proxy running locally on your network for the printer/copier to connect to which relays the email to the MiaB server. I linked a post the other day in response to someone else with a similar issue. There are two different local proxy choices out there.