Digital Marketing

Loading...

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.

Comments

Post a Comment

Popular posts from this blog

Fixed WSL sshd: no hostkeys available -- exiting

Encountered:  $  sudo service ssh --full-restart  * Stopping OpenBSD Secure Shell server sshd                                                                     [ OK ]  * Starting OpenBSD Secure Shell server sshd                                                                            sshd: no hostkeys available -- exiting. Run ssh-keygen -A In the /etc/ssh/ folder, and then restart the server by: $  sudo service ssh --full-restart  * Stopping OpenBSD Secure Shell server sshd                                                                     [ OK ]  * Starting OpenBSD Secure Shell server sshd                                                                     [ OK ]
Read more

PowerMTA pmta command

Usage: pmta [options] command where 'options' are:     --help                display this message     --xml                 display result in XML     --dom                 display result as DOM-like "variables" and where 'command' is one of:     clear dnscache domainname     check mfrom [--tcp] [--dumppackets] mfrom ip     check spf [--tcp] [--dumppackets] ip heloDomain [mailFrom]     delete [--dsn] [--queue=domain[/vmta]] [--orig=addr] [--rcpt=addr] [--jobId=id] [--envId=id] [--older-than=time-interval] [--no-accounting]     deregister [--user=name] [--local-only] [--retain-unloaded]     disable source [--reenable-after=interval] ip domain[/vmta]     enable source ip domain[/vmta]     list [--queue=domain[/vmta]] [--orig=addr] [--rcpt=addr] [--jobId=id] [--envId=id] [--maxitems=n] [--older-than=time-interval] [--pause] [--priority] [--schedule]     pause queue domain[/vmta]     pause job jobid     register [--user=name] [--label=name] [--webmon-ip=ip] [--webm
Read more

How to fix: mv: failed to preserve ownership

mv  is the wrong tool for this job; you want  cp  and then  rm . Since you're moving the file to another filesystem this is exactly what  mv  is doing behind the scenes anyway, except that  mv  is also trying to preserve file permission bits and owner/group information. This is because  mv  would preserve that information if it were moving a file within the same filesystem and  mv  tries to behave the same way in both situations. Since you don't care about the preservation of file permission bits and owner/group information, don't use that tool. Use  cp --no-preserve=mode  and  rm  instead. But if you don't care about the warning, mv actually does move the files before complaining  ownership problem.
Read more