On 16 Jan 2020, at 00:02, azu...@pobox.sk wrote:
> Citát "@lbutlr" <krem...@kreme.com>:
>
>> On 15 Jan 2020, at 15:12, Noel Jones <njo...@megan.vbhcs.org> wrote:
>>> We've had problems with users mistyping domain names, such as hotmal.com or
>>> aoil.com. And they ignore the delay warning message because they still
>>> don't notice their typo.
>>
>> Then they get the bounce when the max queue expires.
>>
>> The messages in the queue are not hurting anything and unless there are
>> millions and millions of them, they are not worth manually handling (nor
>> adding custom transport maps to “fix” user’s tyops).
>
>
> I don't agree with this. Yes, technically it isn't a problem but we (and for
> sure not alone) are using message queue size as a sign of a problem - if
> there are much more messages then usual, our monitoring software is notifying
> us. In most cases it is a sign of hacked account which is spamming - in about
> 50% of such cases, spammers are sending spam very slowly, so you cannot
> simply note it, that's why we monitor it. And that's why it is a problem when
> there are lots of messages which you cannot get rid of by any means.
If you have that many users sending mail to typed domains that you mistake it
as a server issue then you have far more serious user issues than most people.
And chances are whatever you do the user is going to continue to be confused
and require personalized handholding “Yes, we know you’re just sending the mail
from your address book/contacts list, but you are not checking that the email
address is actually correct, are you? Oh, see, your MUA — er, mail program
thingy, isn’t even SHOWING the email address you are sending to.”
Anyway, as Viktor pointed out, this is a coding nightmare because you have to
account to the multi-recipient mail.
This is not a technical problem requiring a technical solution, this is a user
problem requiring a user solution. If your users are ignoring delay messages,
that is a user problem.
You can certainly write a script fairly easily to parse the mailq, find the
messages that you consider problematic, delete them, and then generate a mail
from the system (that your user will evidently ignore) saying "these were not
delivered, they appear to have invalid email addresses" and then list the
messages.
Isn’t this a much better solution than trying to write some bounce processing
ability into postsuper?
Also, when I try to send an email to hotmal.com I get the following:
postfix/smtp[53472]: 47yz7m5Jj2zg4gL: to=<kr...@hotmal.com>, 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))
So, there is nothing in the mailq and the message bounces immediately:
> This is the mail system at host mail.covisp.net.
>
> I'm sorry to have to inform you that your message could not
> be delivered to one or more recipients. It's attached below.
>
> For further assistance, please send mail to postmaster.
>
> If you do so, please include this problem report. You can
> delete your own text from the attached returned message.
>
> The mail system
>
> <kr...@hotmal.com>: Domain hotmal.com does not accept mail (nullMX)
So perhaps THIS is the issue on your server, you are not respecting nullMX
replies?
--
A is for AMY who fell down the stairs B is for BASIL assaulted by
bears
