On Tue, 14 Jan 2020 at 12:53, Scott Kitterman <[email protected]> wrote:
> On Tuesday, January 14, 2020 7:39:05 AM EST Emanuel wrote: > > Hello everyone.! > > > > I see this error in the postfix logs: > > > > said: 550 Blocked by SPF () (in reply to MAIL FROM command)) > > > > Jan 14 09:31:46 antartida postfix/smtpd[16086]: 9248680010: > > client=a48-146.smtp-out.amazonses.com[54.240.48.146] > > Jan 14 09:31:46 antartida postfix/cleanup[16162]: 9248680010: > > > message-id=<0100016fa4095ae5-d7ad3acb-ae83-4ec5-98b7-2caf1aa89dda-000000@ema > > il.amazonses.com> Jan 14 09:31:47 antartida postfix/qmgr[16065]: > 9248680010: > > > from=<0100016fa4095ae5-d7ad3acb-ae83-4ec5-98b7-2caf1aa89dda-000000@amazonses > > .com>, size=18774, nrcpt=1 (queue active) > > Jan 14 09:31:47 antartida postfix/smtp[16067]: 9248680010: > > to=<[email protected]>, > > relay=mail.aylendepartamentos.com.ar[200.58.120.110]:25, delay=1.8, > > delays=1.6/0/0.17/0, dsn=4.0.0, status=SOFTBOUNCE (host > > mail.aylendepartamentos.com.ar[200.58.120.110] said: 550 Blocked by SPF > > () (in reply to MAIL FROM command)) > > > > Postifix does not use any spf policy, the configuration is here: > > > > https://pastebin.com/kK6yCnFM > > > > any ideas? I'm losing emails because of this > > > > Regards, > > The error message comes from the remote server. Based on a quick Google > Search, it's hmailserver [1], nothing to do with Postfix. Since it's SPF > specific, the spf-help mailing list [2] would be a good place to ask for > help. > > Scott K > > [1] https://www.hmailserver.com/ > [2] https://spf.topicbox.com/groups/spf-help/subscription As Scott has written, the blockage is being done by the onward server ( mail.aylendepartamentos.com.ar) not by your postfix (clue: the message is logged by 'smtp' not by 'smtpd'). They seem to be applying the SPF rule from amazonses.com which includes '-all'. It is an unwise policy on their part as SPF is broken by relaying such as you are doing. If you have to relay in this way to this server, and you can't persuade them to change their policy, consider encapsulating such mails (i.e. sending on as attachments).
