Link to home
Start Free TrialLog in
Avatar of David Barman
David BarmanFlag for United States of America

asked on

Scrollout F1 as spam filter rejecting some needed emails

Scrollout F1 is setup as a SPAM inbound gateway to an Exchange server.  We have some senders whos emails won't deliver to the Exchange server.  Thus far the emails have not kicked back.  The remote Exchange server is stating the message delivery has been delayed.  I am assuming Scrollout is terminating the connection from the remote mail server.  I did notice that the remote domain doesn't have an SPF record.  Would that be enough to cause this issue?  What can I do i Scrollout to mitigate the issue so we can receive their emails?  I don't see anything in the logs of the web interface that report any activity for the remote server domain.  Are there other logs on the Scrollout file system that I should be looking at?

Any help would be appreciated
Avatar of Ivan
Ivan
Flag of Serbia image

Hi,

I don't really know Scrollout, but if it is configured to check SPF and sender does not have it, then that may be a reason.
Have you checked SPF settings? It seams it is configured at /etc/postfix-policyd-spf-python/policyd-spf.conf

Regards,
Ivan.
Avatar of David Barman

ASKER

I have not checked.  I can't seem to find any official documentation that lays out everything.  Additionally I would like to see some logs to see why it is rejecting the connection from the remote mail server.
if you have option to whitelist sender domain. That will be your first option to fix it. Next you need to ask sender to fix SPF issue. I personally wouldn't allow such vendor, who doesn't follow basic messaging standards.
I have request them to fix the SPF however, in my experience that is not always an option.  Some don't have qualified people or don't care.  In some cases, their perspective is that they can send to other people but not us, so it must be our problem.

With that in mind, I am looking for a way to mitigate the issue so we can receive their emails.
You can whitelist that domain and let it bypass your filter is the only way, I can see. Yesterday, itself I was dealing with similar issue, so temp I whitelisted, so mails are not rejected.
I have whitelisted the domain but the emails are still rejected. What can be done?
Is there some logs that show why the emails are being rejected?
You need to check the logs on scrollout, how it handles them exactly and what does it require? I would assume it's something to do with domain being not trusted probably.

Can you try and change the domain on Exchange server from Authoritative to Internal relay and check what would happen?
That is part of the inquiry. I can't seem to find where the logs are on the file system to see where the connection is being denied so I can see the exact reason.
ASKER CERTIFIED SOLUTION
Avatar of Mohammed Hamada
Mohammed Hamada
Flag of Portugal image

Link to home
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
Start Free Trial
Thank you.