Posts

Showing posts from February, 2020

Use the blkid command to find the UUID of the device

$ sudo blkid /dev/nvme0n1p1: LABEL="/" UUID="55da5202-8008-43e8-8ade-2572319d9185" TYPE="xfs" PARTLABEL="Linux" PARTUUID="591e81f0-99a2-498d-93ec-c9ec776ecf42" /dev/nvme1n1: UUID="7c4d5e8c-5f26-475f-b985-5a1411359058" TYPE="ext2" /dev/nvme0n1: PTUUID="83181c97-6d5e-43c9-9ede-e2f50ead5338" PTTYPE="gpt" /dev/nvme0n1p128: PARTLABEL="BIOS Boot Partition" PARTUUID="4908ae49-9d5b-423e-a23c-a507a47bacf5" /dev/nvme2n1: PTUUID="5a72544b-a4e2-4bbe-aed0-04f727374581" PTTYPE="gpt" /dev/nvme2n1p1: LABEL="/" UUID="577849ee-6d06-4473-9eec-074495a45d70" TYPE="xfs" PARTLABEL="Linux" PARTUUID="7ba2672d-1d11-4f12-9358-2edd6b813413" /dev/nvme2n1p128: PARTLABEL="BIOS Boot Partition" PARTUUID="5a9fc16d-ac21-49f8-8880-28c8f8d2e8bf"

Emails bounces are categorised into two types

A hard/permanent bounce: This indicates that there exists a permanent reason for the email not to get delivered. These are valid bounces, and can be due to the non-existence of the email address, an invalid domain name (DNS lookup failure), or the email provider blacklisting the sender/recipient email address.A soft/temporary bounce: This can occur due to various reasons at the sender or recipient level. It can evolve due to a network failure, the recipient mailbox being full (quota-exceeded), the recipient having turned on a vacation reply, the local Message Transfer Agent (MTA) not responding or being badly configured, and a whole lot of other reasons. Such bounces cannot be used to determine the status of a failing recipient, and therefore need to be sorted out effectively from our bounce processing.