[Pkg-exim4-users] exim4, gmail and 550-5.7.1

[Robert Steinmetz AIA]

Pretty much, but since I didn't get any responses I thought I'd try again.

Marc Haber wrote:
> Isn't this basically the same message you already sent three days ago?
>
> Greetings
> Marc
>
> On Fri, Dec 18, 2015 at 11:09:28AM -0500, Robert Steinmetz wrote:
>> From: Robert Steinmetz <rob at steinmetznet.com>
>> Subject: Re: [Pkg-exim4-users] exim4, gmail and 550-5.7.1
>> To: pkg-exim4-users at lists.alioth.debian.org
>> Date: Fri, 18 Dec 2015 11:09:28 -0500
>> User-Agent: Mozilla/5.0 (Windows NT 5.1; rv:42.0) Gecko/20100101
>>   Firefox/42.0 SeaMonkey/2.39
>> List-Id: "User-level discussion and support for the Debian packages."
>>   <pkg-exim4-users.lists.alioth.debian.org>
>> X-Spam-Score: (-) -1.9
>> X-Spam-Report: torres.zugschlus.de  Content analysis details:   (-1.9
>>   points, 5.0 required)   pts  rule name              description  ----
>>   ---------------------- ------------------------------------------- -0.0
>>   T_RP_MATCHES_RCVD      Envelope sender domain matches handover relay
>>                               domain -1.9 BAYES_00               BODY: Bayes
>>   spam probability is 0 to 1%                             [score: 0.0000]
>>
>> Based on the link I listed in my first post I have come up with a
>> potential solution:
>>
>> Can anyone comment on whether it should work or not?
>>
>> I propose adding a new files in /etc/exim4/conf.d/main
>>
>> 05_ipv4_force_domains
>>
>> Containing:
>>
>> domainlist ipv4_force_domains = \
>> gmail.com : \
>> googlemail.com : \
>> virgin.net : \
>> linkedin.com : \
>> virginmedia.com
>>
>>
>> Greping router for remote_smtp
>>
>> I get
>>
>> 100_exim4-config_domain_literal: transport = remote_smtp
>> 150_exim4-config_hubbed_hosts: transport = remote_smtp
>> 200_exim4-config_primary: transport = remote_smtp
>> 200_exim4-config_primary: transport = remote_smtp
>> 200_exim4-config_primary: transport = remote_smtp_smarthost
>> 500_exim4-config_hubuser: transport = remote_smtp_smarthost
>>
>>
>> So I propose adding a new file to /etc/exim4/conf.d/router called
>>
>> 050_exim4_config_ipv4_only.
>>
>> Containing
>>
>> ipv4_only:
>> driver = dnslookup
>> domains = +ipv4_force_domains
>> transport = ipv4_smtp
>> ignore_target_hosts = <; 0::0/0|
>>
>> Finally adding a file in /etc/exim4/conf.d/transports
>>
>> 50_exim4_config_ipv4_only_transport:
>>
>> I'm a little puzzled by the one in the example.
>>
>> ipv4_smtp:
>> driver = smtp
>> dkim domain = mydomain.co.uk
>> dkim_selector = x
>> dkim_private_key = /usr/exim/dkim.private.key
>> dkim_canon = relaxed
>> interface = <my.v4.ip.address>|
>>
>> Why can't I simply use the existing smtp remote_smtp transport with
>> the some relatively simple edits? This example contains a directive
>> that limits it to using ipv4 by specifying the interface using an
>> ipv4 address. Seems like somewhere should be a directive like
>> disable_ipv6 = true or dns_ipv4_lookup = *
>>
>> I also wonder if these dkim statements conflict with the rest of the
>> basic debian configuration.
>>
>> _______________________________________________
>> Pkg-exim4-users mailing list
>> Pkg-exim4-users at lists.alioth.debian.org
>> http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-exim4-users