bhay3s
If you want answers like that, then it would help to answer my earlier questions.
ie
Please confirm exactly what/where/which whitelists you are adding entries to, is it a contrib you have installed, if so which one ? Please describe fully.
Also your dedicated sme mail server, is it a gateway server configuration ? Please describe fully the network layout and where this machine is connected etc and what other servers are in the "mix" ? Thanks
Refer below:
qpsmtpd whitelisthosts:
67.220.101.207 <- the ip of the smtp relay that metalplate uses
qpsmtpd whitelisthelo:
metalplate.com
mtarbox@metalplate.com
qpsmtpd whitelistsenders:
@metalplate.com
spamassassin whitelist_from:
@metalplate.com
mtarbox@metalplate.com
There is redundancy as you will notice throughout the whitelist. Before somebody makes an obvious comment that you didn't need to do both the @domain and the actual email address, yes of course I realize that. I tried both just because.
bhay3s
If you want answers like that, then it would help to answer my earlier questions.
ie
Please confirm exactly what/where/which whitelists you are adding entries to, is it a contrib you have installed, if so which one ? Please describe fully.
Also your dedicated sme mail server, is it a gateway server configuration ? Please describe fully the network layout and where this machine is connected etc and what other servers are in the "mix" ? Thanks
The server is not a gateway server. Just a standalone email server.
ip:
192.168.1.7
255.255.255.0
192.168.1.254
the router config the server sits behind:
WAN IP: 69.69.69.x (for ex.) The public ip is routed via the Wan->Lan policy as you can see below.
Firewall settings:
WAN -> LAN POLICY:
pop3s Allow Any 69.69.69.x TCP 0 -> 995
smtpin Allow Any 69.69.69.x smtp-in
SMTPS Allow Any 69.69.69.x TCP 0 -> 465
I have 5 other servers that are standalone servers, 2 more SME boxes, 1 proxy box, 2 win term servers. How does a network layout affect spamassassin btw? Just curious.
Yesterday I called the client to discuss this issue further and this is what I found out. They basically scan the invoices in batch during the day and at night around 7:00PM its automated to send the invoices via email. This would be the reason for the DATE_IN_PAST_03_06 failure I would believe. Plus this is the body of the email:
THIS EMAIL IS AUTOMATICALLY GENERATED AND IS UNABLE TO ACCOMODATE REPLIES.
PLEASE CONTACT METALPLATE AT YOUR NEAREST LOCATION IF YOU HAVE ANY
QUESTIONS. AS ALWAYS, THANK YOU FOR YOUR BUSINESS!
TERMS AND CONDITIONS: WWW.METALPLATE.COM/PAPERLESS.PHP
* Notice the email is all uppercase which is responsible for another failure in regards to spamassassin.