mouss a écrit : > Jose Ildefonso Camargo Tolosa a écrit : >> On Fri, Dec 19, 2008 at 7:19 AM, Jorey Bump <l...@joreybump.com> wrote: >>> Jose Ildefonso Camargo Tolosa wrote, at 12/18/2008 06:28 AM: >>> >>>> I think you should send more info on your config, for example: >>>> >>>> MX record for your domain. >>>> myhostname entry from main.cf >>>> >>>> these two should match. >>> There is no requirement that these match. They are completely unrelated. >> I said: should. > > No, they are unrelated, so there is no need for them to match. Sites with >
my mouse likes eating some lines ;-p I was saying: sites with multiple servers, ones for MX and others for outbound relay will have mismatching inbound and outbound names. >> There are some spam filters which uses the hostname >> provided by the server and make several verifications like: >> >> + Is the hostname listed as a MX for the domain? > > They may use this for whitelisiting, not blacklisting. similar to SPF. > but they should not consider a mismatch as an anomaly. > >> + Does the hostname *forward* resolve to the IP I'm being contacted from? > > I guess you use the term "hostname" for the HELO argument. > Some people do this, but: > - it will cause FPs > - The RFC recommends against it > >> + Does the IP *reverse* resolve to the hostname? > > if the hostname is the HELO argument, then no. there were some borked > filters that do this, but this is borked... > > what is done is: > - resolve the client IP. get the first returned PTR > - resolve this PTR and check that the original IP is returned by this > resolution. > > note that the PTR and the hostname are two different terms (even if they > may be set to the same value in many cases). > >>> The OP needs to describe the problem more accurately. In general, no >>> special configuration is required to send mail to any domain. >> Correct, as long as there are no spam filters around. >> > > OP problem has nothing to do with filters. he is trying to submit mail > to gmail. for that, he needs smtp TLS (without a certificate) and smtp > SASL and submit to [smtp.gmail.com]:587. > > of course, if he has an firewall/proxy/anti-virus/... that interferes > with the communication (some don't allow TLS because they can't filter > the content. some don't support ESMTP, ... etc), he needs to disable this.
