From: David Hill (davidhwmis.net)
Date: Mon Jan 03 2005 - 12:19:25 CST

• Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]

On Mon, Jan 03, 2005 at 07:11:54PM +0100, Magnus Bäck wrote:
> On Monday, January 03, 2005 at 17:47 CET,
> David Hill <davidhwmis.net> wrote:
>
> > We currently use the Postini filtering service.
> >
> > If a user has requested to use the service, we alias the email address
> > so it forwards to postini servers.
> >
> > For example
> > virtual_alias_maps
> > ---------
> > daviddomain.com davidpostini.domain.com
> >
> > host -t mx postini.domain.com resolves to 4 postini MX's.
> >
> > That works fine.
> >
> > I tried to get rid of the alias_maps and just change to per-user transports
> >
> > transport_maps
> > daviddomain.com smtp:postini.domain.com
> >
> > Postini accepts it, but bounces it saying 554 Too many hops.
> >
> > Any idea what is going on? I setup a test to forward the email to
> > another server here, and it shows the correct number of Hops (source,
> > our mail server, transport)
> >
> > Why is it too many hops?
>
> Because your configuration causes the message to loop; the two servers
> will send the message to each other and none will consider itself to be
> the final destination. Your logs will give clues about the reason for
> the loop.
>
> What does Postini do with scanned messages? Send them back to Postfix?
>
> --
> Magnus Bäck
> magnusdsek.lth.se
>

Issue solved. One of our servers wasn't accepting email for domain.com, just postini.domain.com.

• Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]