@liorj ,
the answers:
a. which MTA take/update are you using and which blades are currently enabled.
MTA Version => 8030.991002055
blades => ASPAM, AntiBot, URLF, APPLC, AntiVirus, IPS, Firewall, VPN, MOB, HTTPS inspection (no ThreatPrevention, no ThreatEmulation)
b. could you copy paste here the spf configuration you used in $FWDIR/conf/mail_security_config file.
[spf]
enforce=1
action_spam=reject
action_suspected_spam=monitor-only
track_non_spam=log
track_spam=log
track_suspected_spam=log
c. The scenario where emails are being bounced because of SPF check failure shouldn't happen - instead those emails should be dropped. Neither the 'source' field in the log should be 127.0.0.1 as you said. Could you follow sk139892 and enable the debugs with debug toppic 'ALL'. Then send one email for example to replicate the issue and send over the mta debugs(located under $FWDIR/log/mtad.elg*) and files named maillog under '/var/log'.
We had TAC involved and case is open. These debugs are done, I'll PM you the SR number.
d. in addition, if you have a"special "environment or any additional information you can add about your environment(changes you did maybe lately) it would be good to know.
no special configuration there
Wolfgang