Amazons AWS is definitely not ideal for hosting Smartermail. Because the internal IP can change at any given point it will most certainly always lead to a failure.

 

Please check you IP addresses and Bindings within Smartermail's setup.

I won't argue the merits of AWS except it has served us well since 2011.  Over the last 3 years the private IP address has changed twice and "Bindings --> IP Addresses" was the first thing checked and changed (otherwise no mail flow at all). 

 

Since Amazon changes your IP address, it probably doesn't match tour rDNS any linger, and youll5have to update your rDNS to remap the FQDN of your server to the new IP address.

 

As was mentioned above, Amazon will randomly change IP addresses with the kind of virtualized service you are running, and you should consider a new virtualized environment with dedicated, static IP addresses. If you don't, you'll fond a lot of rejected email.

Are you using your own DNS servers?

 

Oh come on, knock it off with arguing if Amazon is good or bad, none of that matters to me.  My whole mail system is hosted on Amazon (2 MX and the Mail server) and as I said before, it has served me well these past 3 years. There have been a grand total of two internal IP address changes, one a surprise the other expected.  Both handled within minutes with very little disruption in service as a result.

 

This is all academic because it doesn't answer the question of why the spam filter SPF suddenly spiked...

 

Can anyone shed some light on that?

 

(BTW  Steve Reid, we are using Google public DNS.)

 

We have DNS running on the server however...  (Bruce how are you inserting those screen shots?)

the IP of Primary and Secondary DNS in General Settings is set to:  8.8.8.8 and 8.8.4.4 respectively.

It has been set up this way for as long as I can remember.

 

Which log?  Delivery?

 

 

Ok I may have stumbled across the problem.  Staring at Bruce's screen shot above I started going down the list of domains checking that Outbound IPv4 was in fact configured correctly.  I thought once it was done in "General Settings" that it would propagate down through the domains.  However, I discovered many (not all) were either left "Unassigned" or still listed with the previous IP address!

 

I have worked through all 81 domains and set everyone to the proper IP and I will be watching the SPF test over the weekend (it is enabled but set to add 0 points) and see if the count drops.

 

Have a great Labor Day weekend one and all, and Thank you for your assistance Bruce and Steve!

 

 

 

Good catch, Dan.

 

The IP ADDRESS assigned as the SMTP OUT IP ADDRESS does not auto-propagate.  It must be manually assigned to each domain.