Email with secure links bounced by AOL

  • Profile Image
    Asked on January 31, 2014 at 01:35 PM

    Hi, I have read all of the questions about how autoreponders do not come to aol addresses.  I followed all of the instructions on your site and even signed up for a mandrill account allow me to send the emails using my own domain. 

    I finally narrowed down what was preventing the emails from arriving at aol and that was I was including the secure jotform link to my form.  Once I changed this to the non secure link the email finally goes through.  I did try a different secure link (not jotform) and that went through also.

    So AOL must have a filter in place that prevents emails with jotform secure links in it.

    This is an example of the secure link.  If it is in the body of an email, it will not arrive at aol.

    Here is the bounce message:


    Delivery to the following recipient failed permanently:

    Technical details of permanent failure:
    Google tried to deliver your message, but it was rejected by the server for the recipient domain by [].

    The error that the other server returned was:
    521 5.2.1 :  (HVU:B2)

    ----- Original message -----

    X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;
  ; s=20130820;
    X-Gm-Message-State: ALoCoQnI1lidZStECXTAiwvRB9eQaG4DflwBqku2qAHOHgArpIY3a3fx6WP6qKX37vd2GRzP7/8s
    X-Received: by with SMTP id yn3mr2298198lbb.45.1391193185469;
     Fri, 31 Jan 2014 10:33:05 -0800 (PST)
    MIME-Version: 1.0
    Received: by with HTTP; Fri, 31 Jan 2014 10:32:45 -0800 (PST)
    From: Dan <>
    Date: Fri, 31 Jan 2014 13:32:45 -0500
    Subject: Hello!
    Content-Type: multipart/alternative; boundary=001a11c33530a25a4104f1486721


    To bad JotForm and AOL do not play nice.

    Just thought you all should know this.

    It would be nice to use the secure form though.  Please advise if there will ever be a fix for this.

    Thanks, Dan

  • Profile Image
    Answered on January 31, 2014 at 05:00 PM

    JotForm, being a free service, is prone to abuses by spammers, phishers and the likes, so we understand how it can be hard to make it work with other web services. We are definitely trying to reduce that impact, though.

    Anyway, have you tried using instead of https// ?

    If it still does not work, try using a URL shortening service such as and

    Hope this helps.