Note that there are some explanatory texts on larger screens.

plurals
  1. PO
    primarykey
    data
    text
    <h2>Email doesn't arrive</h2> <p>First at all, <strong>you cannot really rely on mail</strong>. Never. Because <a href="http://www.codinghorror.com/blog/2010/04/so-youd-like-to-send-some-email-through-code.html" rel="nofollow noreferrer">you can't even know if it was received</a> or read. A mail may be blocked as spam on server side, can be filtered on client side, or can just be lost or ignored.</p> <p>There may be plenty of causes. For example, you may use <strong>e-mail authentication</strong> mechanisms. You may also start to check if there is <strong>reverse DNS</strong> for your domain.</p> <p>Further, you may want to <strong>read some documentation and books</strong> to know how spam filters work. It will show you some obvious methods to reduce filtering of your mails, like sending mails in plain text instead of full-HTML, but also less obvious stuff like the words to use, etc.</p> <p>If you have no choice and you must send mail, probably the most easy solution to prevent spam filtering would be to <strong>ask the users to add your domain to the list of safe senders</strong>. In practice, nobody will do it for you.</p> <h2>Activation through MD5</h2> <p>There is obviously a better way, since the one you implemented does not provide anything. If the activation is a hash from user name, you can as well just tell the users to calculate the hash themselves (thus avoiding all the problems with mails filtered as spam).</p> <p>Normally, <strong>the users may not know what their activation code would be</strong>. It means that the activation code must be random or difficult to guess.</p> <p><strong>Generate a set of random characters</strong>, save them to database and send the code by mail. Then you would just need to validate the code against the one you keep in your database.</p>
    singulars
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    plurals
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. VO
      singulars
      1. This table or related slice is empty.
    2. VO
      singulars
      1. This table or related slice is empty.
    3. VO
      singulars
      1. This table or related slice is empty.
    1. This table or related slice is empty.
 

Querying!

 
Guidance

SQuiL has stopped working due to an internal error.

If you are curious you may find further information in the browser console, which is accessible through the devtools (F12).

Reload