On 26/08/11 22:16, lance raymond wrote: > > My transport file looks like this; (one example) > members...@domain.com <mailto:members...@domain.com> > smtp:[ASPMX.L.GOOGLE.COM <http://ASPMX.L.GOOGLE.COM>]:25 > > When postfix was started and happy, an example looked like this; > > pwsdata postfix/smtp[840]: A0FAD7E22C: to=<members...@domain.com > <mailto:members...@domain.com>>, relay=ASPMX.L.GOOGLE.COM > <http://ASPMX.L.GOOGLE.COM>[74.125.113.27]:25, delay=1.5, > delays=0.07/0.01/0.14/1.3, dsn=2.0.0, status=sent (250 2.0.0 OK > 1313600883 s8si3016648vdh.46) > > I got a call saying mail hasn't been recieved to support or membership > which is odd, and when I look I see the following; > > 12:20:30 pwsdata postfix/pipe[31348]: E57127E232: > to=<members...@domain.com <mailto:members...@domain.com>>, > relay=dovecot, delay=0.27, delays=0.17/0.01/0/0.1, dsn=2.0.0, > status=sent (delivered via dovecot service) >
The message that goes to the google transport enters postfix via smtp, the failing one via pipe (i.e. sendmail(1) command line util on the host). My crystal ball says that your transport map is only applied to smtp traffic, but since you forgot to include postconf -n, we can only guess. ow, and please lose the html mail. -- Tom
