This obviously don’t happens if i use webmail that send email from expected b.b.b.b IP address causing no errors on SPF matching.The software consists of both client and server components, and at one time also offered a desktop email client, called Zimbra Desktop. but the question is, why SPF policyd check is searching for client-ip address tag instead MTA’ sending IP? I was expecting my client to use MTA IP address (b.b.b.b) instead it connects through my network gateway IP address (a.a.a.a) and SPF doesn’t match DNS records because this ip is not listed (as it should be) and I got a softfail error…. Oct 20 17:10:57 mail postfix/smtps/smtpd: 861C582264C: client=unknown, sasl_method=PLAIN, in mind I’ve configured SMTP to use my MTA hostname ( -> b.b.b.b), nothing strange here, standard SSL connection on 465 tcp port. Oct 20 17:10:57 mail postfix/smtps/smtpd: NOQUEUE: filter: RCPT from unknown: : Sender address triggers FILTER smtp-amavis::10026 from= to= proto=ESMTP helo= Received-SPF: softfail (: Sender is not authorized by default to use in ‘mfrom’ identity, however domain is not currently prepared for false failures (mechanism ‘~all’ matched)) receiver= identity=mailfrom helo=”” client-ip=a.a.a.a I send an email from (always on same Zimbra server and network) to user using a standard IMAP client like thunderbird/outlook and I receive this softfail SPF errorĬBPOLICYD LOG (/opt/zimbra/log/cbpolicyd.log) SPF/DKIM/DMARC for domain / is correctly configured and verified with gLock Apps & MXtoolbox, but when I send email to test it something I can’t understand is goin’ on…
Zimbra 8.0.7 GA Ubuntu 14.04LTS with cbpolicyd 2.1Į SPF public TXT record: v=spf1 mx a ip4:b.b.b.b/32 ~allĮ SPF public TXT record: v=spf1 mx a ip4:b.b.b.b/32 ~all
Host said: 554 5.7.1 : Sender address rejected: Failed SPF check qq.com, Sender is not authorized by default to use in ‘mfrom’ identity, however domain is not currently prepared for fals Jul 13 09:12:24 webmail postfix/postscreen: PASS OLD :52814 Jul 13 09:12:24 webmail postfix/postscreen: CONNECT from :52814 to :25 Jul 13 09:12:24 webmail postfix/smtpd: disconnect from ehlo=1 auth=0/1 commands=1/2 Jul 13 09:12:24 webmail postfix/smtpd: lost connection after AUTH from Jul 13 09:12:24 webmail postfix/smtpd: warning: : SASL LOGIN authentication failed: authentication failure Jul 13 09:12:24 webmail saslauthd: do_auth : auth failure: Jul 13 09:12:24 webmail saslauthd: auth_zimbra: cangcuiman auth failed: authentication failed for Jul 13 09:12:24 webmail postfix/smtpd: disconnect from ehlo=2 starttls=1 mail=1 rcpt=0/1 quit=1 commands=5/6 Jul 13 09:12:24 webmail saslauthd: zmauth: authenticating against elected url ‘’ … Jul 13 09:12:24 webmail postfix/smtpd: NOQUEUE: reject: RCPT from : 554 5.7.1 : Sender address rejected: Failed SPF check qq.com, Sender is not authorized by default to use in ‘mfrom’ identity, however domain is not currently prepared for false failures (mechanism ‘~all’ matched) from= to= proto=ESMTP helo= Jul 13 09:12:24 webmail postfix/smtpd: connect from Spf=pass (: domain of designates 74.299.135.46 as permitted sender) sure if its my SPF setting or IMAP settings # imap user showing correct mail server public IP when sending to gmail # But going to external address like gmail. Received: from DESKTOP4OH085B (. )īasically when I have outlook configured with IMAP, the email going to internal address gets rejected. Received-SPF: fail (: Sender is not authorized by default to use in ‘mfrom’ identity (mechanism ‘-all’ matched)) receiver= identity=mailfrom helo=DESKTOP4OH085B client-ip=75.74.180.166 # imap user showing home comcast IP when sending to another internal user # Here is an example show more information. The IP 96.x.y.z is actually the public IP from where the computer with outlook is sitting. I did not get notification of your comment.
0 kommentar(er)
