Hi,
I’m afraid you’re going to have to do some of your own work here. You’ve got another router that looks at that file. I don’t know the intended purpose of either router. You may also have other systems looking at that file.
Remember, we’re all volunteers here!
You’re not going to break your configuration by removing the file. But somebody once thought it was a good idea to create it. If you want certainty, you’ll have to find out what that reason was. You won’t find it on this list.
> On 14 Dec 2015, at 15:37, Jaime Stuardo <jstuardo@???> wrote:
>
> Hello,
>
> I browsed /opt/exim/valiases folder, and I saw a file called desytec.com with this content:
>
> *: :blackhole:
>
> I think I am near to find the solution to this. So, can you tell me if I can safely remove that file to solve the problem? I want to avoid to do "trial and error", so I prefer you confirm this.
>
> Thanks
> Jaime
>
> -----Mensaje original-----
> De: Ian Eiloart [mailto:iane@sussex.ac.uk]
> Enviado el: lunes, 14 de diciembre de 2015 10:48
> Para: Jaime Stuardo <jstuardo@???>
> CC: Exim Users <exim-users@???>
> Asunto: Re: [exim] Mails are not sent
>
>
>> On 11 Dec 2015, at 20:53, Jaime Stuardo <jstuardo@???> wrote:
>>
>> I am attaching my exim configuration file.
>>
>> There is a line that shows:
>>
>> domainlist relay_domains = lsearch;/opt/exim/localdomains :
>> lsearch;/opt/exim/secondarymx
>>
>> I am wondering if this is the file that affects this behavior. When I
>> saw /opt/exim/localdomains file, this is listed:
>>
>>
>> vps-1128921-x.dattaweb.com
>> gestionproyectos.cl
>> v-track.cl
>> vtrack.cl
>> dias.cl
>> gestionx.cl
>> marvas.cl
>> commerce.gestionx.cl
>> depasa.cl
>> desytec.cl
>> desytec.cn
>> desytec.com.cn
>> desytec.com
>>
>> As you read in my original mail, the address that is blackholed,
>> belongs to desytec.com domain. Can I safely remove "desytec.com" line
>> in above file to solve this problem?
>
> the list local_domains isn’t used in the router virtual_aliases, but there is a test that searches that file. So, it would help. Whether it does any harm elsewhere depends on whether the list, or the file, is consulted for any other purpose. Removing it could, for example, prevent local submission.
>
> virtual_aliases:
> driver = redirect
> allow_defer
> allow_fail
> data = ${if exists{/opt/exim/valiases/$domain}{${lookup{*}lsearch{/opt/exim/valiases/$domain}}}}
> file_transport = address_file
> group = exim
> pipe_transport = virtual_address_pipe
> domains = lsearch;/opt/exim/localdomains
> retry_use_local_part
>
>
> --
> Ian Eiloart
> Postmaster, University of Sussex
> +44 (0) 1273 87-3148
>
>
--
Ian Eiloart
Postmaster, University of Sussex
+44 (0) 1273 87-3148
