Messages getting though Postini OK but then end up in spam

[jimbo09990]

Hi,

We have recently upgraded to the prem editions.
All was working fine.

We now have a problem that ALL new messages are being delivered to the
users spam box within gmail. They are passing though Postini without
getting flagged, its when they are delivered to the users that they
are not going to the inbox. This is even happening to emails from our
own domain!

Any ideas?

Regards

James

[Surmed]

white-list Postini IPs in the email server settings in ur apps

[jimbo09990]

Surely not! There must be loads of Postini servers.
I'm sure other Admins would have complained of this by now if you had
to do that.

Any other ideas?

Regards

James

[FrankM - Power Poster]

I'll assume your MX records are correct and only pointing Postini?


Frank

> > > James- Hide quoted text -
>
> - Show quoted text -

[jimbo09990]

Hi Frank,

Yes, the MX look fine to me
Name: cougar-it.co.uk
Address: 146.101.123.4
cougar-it.co.uk
origin = ns1.cougar-it.net
mail addr = info.cougar-it.co.uk
serial = 2009011916
refresh = 86400
retry = 7200
expire = 3600000
minimum = 86400
cougar-it.co.uk mail exchanger = 10 cougar-it.co.uk.s7a1.psmtp.com.
cougar-it.co.uk mail exchanger = 20 cougar-it.co.uk.s7a2.psmtp.com.
cougar-it.co.uk mail exchanger = 30 cougar-it.co.uk.s7b1.psmtp.com.
cougar-it.co.uk mail exchanger = 40 cougar-it.co.uk.s7b2.psmtp.com.
cougar-it.co.uk nameserver = ns1.cougar-it.net.
cougar-it.co.uk nameserver = ns2.cougar-it.net.

Authoritative answers can be found from:
cougar-it.co.uk nameserver = ns1.cougar-it.net.
cougar-it.co.uk nameserver = ns2.cougar-it.net.
ns2.cougar-it.net internet address = 146.101.123.101
ns1.cougar-it.net internet address = 146.101.123.3

The message headers show they have been sent though the Postini
service.

Regards

James

[FrankM - Power Poster]

What are your category spam settings on Postini? Make sure your domain
is not listed as an approved sender in Postini, and make sure no user
adds their own account or domain as an approved sender.

I would also suggest using an SPF record in DNS and lock down Gmail to
only accept messages from Postini. To lock down your Gmail server to
Postini; go to your Google APPS mail dashboard -> Service Settings ->
Email; add this IP to your inbound gateway setting, 64.18.0.0/20 and
check the box; "Only let my users receive email from the email
gateways listed above. All other mail will be rejected".

In your SPF record make sure you add the following for Postini as an
authoritative sender, spf.postini.com.



FrankM

> > > - Show quoted text -- Hide quoted text -

[jimbo09990]

Hi - thanks for the reply.

The spam filters are as default. The mail is getting though postini
without being marked as spam. I also checked the headers though the
checker.
I have checked and made sure our domain is not listed.

I think the problem may have been down to the SPF. We did not have
one set, but have no and it looks like mail is getting though and been
delivered to the inbox as it should be.
I checked the domain control panel. The mail is not locked down as
you have suggested it should be. I'll look at doing that tonight.

Many thanks for your help.

Regards

James

[Surmed]

Hello James
Whitelisting Postini in Apps and setting the SPF records are
recommended settings. there are two sets of CIDR depending on your
system.

You should always set your SPF, Postini or no Postini ;)

Cheers
Surmed

[Maserati]

On Feb 5, 10:34 am, FrankM - Power Poster <Frank.M...@gmail.com>
wrote:

> I would also suggest using an SPF record in DNS and lock down Gmail to
> only accept messages from Postini. To lock down your Gmail server to
> Postini; go to your Google APPS mail dashboard -> Service Settings ->
> Email; add this IP to your inbound gateway setting, 64.18.0.0/20 and
> check the box; "Only let my users receive email from the email
> gateways listed above. All other mail will be rejected".
>

Frank,

If you're going to suggest locking down your inbound gateways (and
this IS good practice) then you'd better include Postini's secondary
network range, 207.126.144.0/20. I've had Gmail decide we were being
spamflooded. From a server Google owns.

[FrankM]

Never had that problem, but that's were good SPF records come into
play. Usually when I have a client that inter-mixes mail servers and
also has end-users using third party POP3 fetch and send, I'll suggest
adding both Postini and Google SPF info as an included domain.

spf.postini.com =
v=spf1 ip4:64.18.0.0/20 ip4:207.126.144.0/20 ip4:204.14.232.0/22
ip4:63.146.199.13/32 ip4:63.146.199.14/32 ip4:68.123.185.46/32
ip4:67.114.133.222/32 ip4:63.71.11.123/32 ip4:63.71.11.124/32
ip4:208.111.151.5/32 ip4:208.74.204.5/32 -all"

_spf.google.com =
"v=spf1 ip4:216.239.32.0/19 ip4:64.233.160.0/19 ip4:66.249.80.0/20
ip4:72.14.192.0/18 ip4:209.85.128.0/17 ip4:66.102.0.0/20
ip4:74.125.0.0/16 ip4:64.18.0.0/20 ip4:207.126.144.0/20 ?all"


Example used in an SPF record; v=spf1 mx include:spf.postini.com
include:_spf.google.com ~all


FrankM