Re: transport_maps how to match mx's

2 msg	Postfix SASL Help
6 msg	Slowing down postfix
2 msg	need help deciphering a line
4 msg	Postfix SMTP server: errors from something.net[...
4 msg	2.5.0-RC and 2.6 should recognize FreeBSD 8
9 msg	Postfix not following my access file.
3 msg	postfix logs delay, delays, dsn
3 msg	Best way to shutdown postfix prior to servicing...
1 msg	the bounce process hangs a mail (?)
3 msg	messages destined for content_filter stuck in d...
2 msg	Domain in username
5 msg	missing authentication on recipient
5 msg	postfixadmin
5 msg	check_policy_service before reject_rbl_client
9 msg	MXBackup via LDAP
5 msg	header and body check exemptions
5 msg	Relay recipient maps and relocated users
4 msg	mail forwarding loop :: SPAM

transport_maps how to match mx's
\ Ruben Gonzalez Arnau (21 Jan 2008)
. \ (Wietse Venema) (21 Jan 2008)
. . \ Ruben Gonzalez Arnau (21 Jan 2008)

2 msg	Where/when to insert a missing Message-ID

Subject:	Re: transport_maps how to match mx's
Group:	Postfix-users
From:	Ruben Gonzalez Arnau
Date:	21 Jan 2008

Wietse Venema wrote:
> Ruben Gonzalez Arnau:
>
> Checking application/pgp-signature: FAILURE
> -- Start of PGP signed section.
> [ Charset ISO-8859-1 unsupported, converting... ]
>> Hello,
>>
>> I have a problem sending mail on gmail accounts since I am marked as
>> spammer (junk folder), in this case, using transport_maps file with my
>> ISP fixes my problem
>>
>> transport:
>> gmail.com smtp:[isp_ip]
>>
>> But for example, lots of domains uses 'google apps' and I still have the
>> same problem.
>>
>> example:
>> dig -t mx domainusinggoogleapps.com
>> aspmx1.googlemail.com
>> aspmx2.googlemail.com
>> aspmx3.googlemail.com
>>
>> etc
>>
>> It uses the same 'spam filters' as gmail does, so my emails goes to junk
>> too.
>>
>> So, it is possible to use transport_maps using something like this
>> (regular expression) to catch mx?
>>
>> (catching mx instead)
>> /.*googlemail\.com/ smtp:[isp_ip]
>
> No, because transport map lookups happen BEFORE mail is given to
> delivery agents, and because MX lookups happen in the SMTP delivery
> agent.
>
> Substitution of MX hosts names or IP addresses would have to be
> implemented by the SMTP client itself. Such code currently does
> not exist, but would be relatively easy to add.
>
> Why not use the ISP's host? You can spend the rest of your life
> discovering which mail servers don't like direct mail from end-user
> IP addresses.
>
> Wietse
Ok, so at moment it is not possibe. The problem is ... that my ISP host
is blacklisted by others :)

Thank you Wietse.