Skip to main content

How to stop bounce-back emails?

Comments

3 comments

  • cPanelMichael
    Hello, cPanel 58 introduces the following option in "WHM >> Server Configuration >> Mailserver Configuration": Disk Quota Delivery Failure Response This option determines how Dovecot will handle delivery to a mailbox that reaches it mailbox quota or when the cPanel account reaches its system disk quota: [LIST]
  • Reject the message permanently. " This setting rejects the message and bounces it back to the sender.
  • Defer delivery temporarily. " This setting allows the user to free disk space or add more disk quota before the system attempts to deliver the message again. This is documented at: 58 Release Notes - Documentation - cPanel Documentation Thank you.
  • 0
  • anton_latvia
    In fact none of these options suit us anymore. Before the change - server would not even accept such emails and would defer them - so we did not have to deal with them in any way. Now they are filling up queues on servers and generate outgoing emails with notification, that recipient's mailbox is full. Such messages contain original email, which in it's turn, contain spam message. I have set all servers to "defer deliver", but still - mail queue is growing and server sends out notifications. I want to stop them and make server act as before. Is it possible?
    0
  • cPanelMichael
    In fact none of these options suit us anymore. Before the change - server would not even accept such emails and would defer them - so we did not have to deal with them in any way. Now they are filling up queues on servers and generate outgoing emails with notification, that recipient's mailbox is full. Such messages contain original email, which in it's turn, contain spam message. I have set all servers to "defer deliver", but still - mail queue is growing and server sends out notifications. I want to stop them and make server act as before. Is it possible?

    Could you verify if the issue persists on cPanel version 58.0.30 or newer? There's a thread here regarding a bug that's now addressed:
    0

Please sign in to leave a comment.