Email is delivered with a delay

Follow

Comments

4 comments

  • Avatar
    b_p

    As it seems, greylisting also happens for mails submitted internally or sent (authenticated) via Ports 587 / 465. This should not be the case?

    0
    Comment actions Permalink
  • Avatar
    Mikhail Shport

    Hi b_p,

    By default, it is no matter which port is used. Greylisting checks received messages despite the way they were delivered. It can filter emails sent internally or via 587/465 ports.

    Emails are processed during the SMTP session and there is checked whether the client has previously connected recently.

    0
    Comment actions Permalink
  • Avatar
    b_p

    Hi Mikhail Shport the problem is: it also happens when you have forwarding mail addresses (e.g. you can an external mail (after the greylisting timeout) and this should now automatically be forwarded to another address. As the original sending client already has passed the greylisting barrier, checking this again does not make sense.

    In addition, if greylisting would be properly implemented (e.g. using postgrey), it is clearly possible (https://rimuhosting.com/knowledgebase/linux/mail/greylisting%20with%20postgrey) and desired that authenticated users (who connect through whichever port but DO authenticate) are excluded from greylisting. Not trusting your own users when they try to send (authenticated) mails, is not the proper way...

    0
    Comment actions Permalink
  • Avatar
    Mikhail Shport

    Hi b_p,

    If one of the mailboxes is compromised or there is malware on the server it is a good idea to check local messages as well.

    Emails are processed by greylisting over SMTP connections. When a mail address forwards a message it creates a new connection because the sender changes.

    If it seems greylisting works improperly on the server I suggest you submit a request to the support in order to check it further.

    0
    Comment actions Permalink

Please sign in to leave a comment.

Have more questions? Submit a request