I'm adding a new field to the Postfix queue file that says if a
message was forcibly expired. The field is set with the postsuper
command, using syntax that is similar to other postsuper commands.
The new option behaves like 'delete' except of course that it sets
a flag in a file instead of
> You said in your message "lack of MX record", not "nullMX".
Read the entire thread?
>> postfix/smtp[53472]: 47yz7m5Jj2zg4gL: to=, relay=none,
>> delay=0.29, delays=0.06/0/0.22/0, dsn=5.1.0, status=bounced (Domain
>> hotmal.com does not accept mail (nullMX))
IMO a correct nullMX should be:
hotmal.com. 3600IN MX 0 .
--
Sent from: http://postfix.1071664.n5.nabble.com/Postfix-Users-f2.html
Dnia 18.01.2020 o godz. 07:15:23 @lbutlr pisze:
>
> Yes. And? This has what to do with nullMX?
>
> hotmal.com. 3600IN MX 10 .
>
> That is not the same as not having an MX record.
You said in your message "lack of MX record", not "nullMX".
Yes, there are two different
On Thu, 16 Jan 2020, Dominic Raferd wrote:
I recently started using an RBL service where we have a 'private key' and
this operates very simply by prefixing the key to the RBL address. But I
just realised that this appears to mean that for any rejections the whole
address - including the key -
On 17 Jan 2020, at 02:02, Jaroslaw Rafa wrote:
> Dnia 16.01.2020 o godz. 15:46:31 @lbutlr pisze:
>>
>> Recheck? What do you mean> there is no rechecking the VALID domain is looked
>> up, it does not have an MX record, so postfix does not attempt to deliver it
>> and immediately bounces the
