On 01/05/2018 02:38 PM, Ruben Safir wrote:
> not what mailman does with the SMTPHost, and that is my point. It
> should be documented clearer (or fixed?).
I think MX record is documented fairly clearly on e.g. wikipedia. The
rest of it spelled out in Defaults.py in my installation:
- "delivery
On 01/05/2018 03:32 PM, Dimitri Maziuk wrote:
> On 01/05/2018 02:13 PM, Ruben Safir wrote:
>
>> That is not a true statement. When you are looking for a MAIL host, it
>> is logical to ask for it with an MX record.
> Fine. Dig for an MX record for your defined SMTPHost and see what you get.
not
On 01/05/2018 02:13 PM, Ruben Safir wrote:
> That is not a true statement. When you are looking for a MAIL host, it
> is logical to ask for it with an MX record.
Fine. Dig for an MX record for your defined SMTPHost and see what you get.
--
Dimitri Maziuk
Programmer/sysadmin
BioMagResBank, UW-M
On 01/05/2018 02:56 PM, Dimitri Maziuk wrote:
> I think you are confused: I am not talking about what you get back, I am
> talking about what you ask *for*.
>I think you are confused: I am not talking about what you get back, I
> am
> talking about what you ask *for*.
That is just not logical.
On 01/05/2018 01:34 PM, Ruben Safir wrote:
> On 01/05/2018 01:41 PM, Dimitri Maziuk wrote:
>> On 01/05/2018 11:49 AM, Ruben Safir wrote:
>>
>>> SMTPHost seems to do a non-mx record lookup for the value ... which is a
>>> little strange.
>> When you look up
>> an MX, you can look up an MX for a *do
On 01/05/2018 01:41 PM, Dimitri Maziuk wrote:
> On 01/05/2018 11:49 AM, Ruben Safir wrote:
>
>> SMTPHost seems to do a non-mx record lookup for the value ... which is a
>> little strange.
> When you look up a *host*, you look for A/PTR or CNAME.
No, all dns look ups are for hosts. Since this is
On 01/05/2018 11:49 AM, Ruben Safir wrote:
> SMTPHost seems to do a non-mx record lookup for the value ... which is a
> little strange.
When you look up a *host*, you look for A/PTR or CNAME. When you look up
an MX, you can look up an MX for a *domain*, *or* you could look up an
MX for a *host*.
On 01/05/2018 12:17 PM, Ruben Safir wrote:
> But I don't see why it does this. It doesn't seem to be dns confusion
> because that works correctly for the mx records. It seems to be
> confusion restricted to mailman
OK - I found the problem
SMTPHost should be documented to need the FQDN of the h
On 01/05/2018 09:59 AM, Ruben Safir wrote:
> I have a custom archive system that I have used for decades and I lost
> the ability to send mail through the mailing list to its user account.
>
> Jan 05 01:13:13 2018 (3042) delivery to arch...@xxx.com failed the code
> 550: 5.1.1 : Recipient address
I have a custom archive system that I have used for decades and I lost
the ability to send mail through the mailing list to its user account.
Jan 05 01:13:13 2018 (3042) delivery to arch...@xxx.com failed the code
550: 5.1.1 : Recipient address rejected: User unknown
in local recipient table
I am
10 matches
Mail list logo
