• Q: Mail are not sent, why?

    A1: Check if all parameters are correct and check if the smtp works in another program like an email client
    A2: If you are using SSL/TLS you need a PHP with openSSL support, see requirements
    A3: Unblock/open and white list the smtp server port selected
    A4: White list your smtp server url (some hosts have a white list)

    Q: Why I got duplicates of mails? It’s clearly a Cimy Swift SMTP issue!

    A: If the sender and the destination addresses are the same probably you are receiving one mail for the sender and one mail for the destination and you are thinking it’s a duplicate, but it’s not true and it’s not “clearly a Cimy Swift SMTP issue”.
    For example GMail always does like that.

    Q: When feature XYZ will be added?

    A: I don’t know, remember that this is a 100% free project so answer is “When I have time and/or when someone help me with a donation”.

    Q: Can I help with a donation?

    A: Sure, visit the donation page or contact me via e-mail.

    Q1: I have found a bug what can I do?
    Q2: Something does not work as expected, why?

    A: The first thing is to download the latest version of the plug-in and see if you still have the same issue.
    If yes please write me an email or write a comment but give as more details as you can, like:

    • Plug-in version
    • WordPress version
    • MYSQL version
    • PHP version
    • exact error that is returned (if any)

    after describe what you did, what you expected and what instead the plug-in did :)
    Then the MOST important thing is: DO NOT DISAPPEAR!
    A lot of times I cannot reproduce the problem and I need more details, so if you don’t check my answer then 80% of the times bug (if any) will NOT BE FIXED!

220 Responses

  1. Kenichi says:

    I found it in /wp-admin/options-general.php?page=swift_smtp

    1. EDIT: you are right documentation sucks a bit, thanks for your comment.

  2. Mark says:

    Hi Marco,

    First off, thank you for such a useful plugin. However, after installing it, this is what I got back:

    Test result

    Warning: stream_socket_client() [function.stream-socket-client]: unable to connect to ssl://smtp.gmail.com:465 (Connection timed out) in /home/wpcrusad/public_html/wp-content/plugins/cimy-swift-smtp/Swift/lib/classes/Swift/Transport/StreamBuffer.php on line 271
    Connection could not be established with host smtp.gmail.com [Connection timed out #110]

    I confirmed that both POP and IMAP are enabled for this account. Likewise, I confirmed that the server is SSL/TLS enabled.

    Any suggestions would be greatly appreciated!

    Many thanks in advance,


    1. I would try to use TLS and not SSL for gmail, as the plug-in also suggests.

    2. Mark says:

      Quick Update: The above solution only worked for gmail-based email addresses to send the test email to. However, when I used a yahoo address, it still threw the same error.

      So the host provider ultimately whitelisted port 465, as well. Now yahoo does indeed get through.

      Still need to do further tests but so far looks promising.

      Best regards,


      1. Thanks for sharing this.

  3. Mark says:

    Hi Marco,

    I did indeed do both, as well as IMAP; all to no avail. After going several rounds with the host provider, I found out that they needed to whielist smtp.gmail.com on their end.

    Once that happened… Voila! Worked like a champ.

    Hopefully that helps any future users of your fine plugin that run into a similar set of difficulties.

    Best regards,


  4. Mark says:

    Hi Marco,

    I just upgraded to a VPS and had to go through the whole procedure once again. While it’s still fresh on my mind, here is everything the host provider needed to do on their end to get your plugin working smoothly:

    1) Unblock/allow port 465
    2) Whitelist port 465
    3) Whitelist smtp.gmail.com

    Beyond that – it’s a truly excellent plugin – thanks!

    Best regards,


  5. riko ms says:

    hi marco,
    thank you for your nice plugins.

    i have problem with usage on webhost.

    this is the detail:
    cimi swift wmtp version:1.2.3
    wp ver: 2.9.1
    openssl: installed, shown in phpinfo().
    send mode: smtp gmail.

    when cimi installed on localhost,
    Test result:
    TEST EMAIL SENT – Connection Verified.
    If you don’t receive the e-mail check also the spam folder.

    when cimi on webhost,
    Test result:

    and no email sent.

    i’ve read along this FAQ, but no answer found.

    any clue, master?

    1. v1.2.3 of the plug-in is no longer supported, you should update to latest v2.1.0 but yes works only for WordPress 3.0 or higher.
      Maybe webhost is blocking gmail address and/or port chosen, in that case updating won’t help, but if you need further assistance consider updating WP and the plug-in.

  6. Paulo says:

    Hi Marco!

    I found a weird situation when I check the “overwrite sender” option and try to send a test email: the test result comes blank.

    I’m using the lastest version of WordPress and updated the plugin to version 2.1.0.

    If I uncheck the option mentioned above, the test works fine: TEST EMAIL SENT – Connection Verified.

    Do you have any suggestion?

    Thanks in advance!

    1. Paulo says:

      P.S.: when the option is checked, no wordpress message is sent at all.

      1. But did you enter at least a valid email above that checkbox?

  7. Paulo says:

    Hi Marco! Thanks for your attention!

    I’m using a valid email but the problem was that it had been configured to send and receive messages only from an certain domain. Problem solved.

    Congratulations for the great plugin and sorry for bothering you!

  8. Rolf says:

    Hi Marco,

    thank your for that great plugin!
    There is only one major flaw for me:
    E.g. Contact Form 7 provides a customizable From: adress which I don’t want to be overwritten by any other plugin.
    On the other hand, I don’t want comment moderation emails to have that ugly wordpress@my-domain as sender adress for two reasons:
    -this can cause trouble with some mailers or spam filters
    -when a site has several authors, it can be misleading for an author when he gets an email from “WordPress” instead of the blog owner.

    This could be resolved like this:
    Instead of the “Always overwrite the sender” checkbox, provide three (mutually exclusive) radio buttons:
    -Always overwrite the sender with the above adress.”
    -Only overwrite the sender if no From: adress is provided” (So we have a way to provide an own default adress.)
    -Use wordpress@my-domain if no From: adress is provided”

    Afaik, this would be exactly the same functionality as before, but statet clearer and with one more option.

    Could you change it that way?

    1. You are reporting actually a WordPress issue which would find best place in its bug tracker.
      I can do it, but also nice from you to consider a donation.

      thank you

    2. I changed it for v2.1.1 donation very welcome. If you do NOT support plug-in’s developers then you’ll not see improvements anymore.

      Consider a donation now.

      1. Rolf says:

        The source if this issue is certainly wordpress itself, but as I could see in your code, your plugin was copying this behaviour by explicitely generating that wordpress@my-domain adress.
        So reporting a wordpress issue wouldn’t have changed anything about smtp delivery in the first place… until you would have copied that new wordpress behavior;-).

        Anyway – thank your for the change. A donation will be considered.

  9. Hi Marco, I’m rather unexpectedly (i.e. this is new) error reports in the PHP error log, triggered by the Cimy Swift SMTP plugin. I’ve minimally sanitized the log and put it up publicly visible for 1 month on Pastebin here:

    Any idea what’s going on there? Thanks in advance!

    1. As said via email provide full log to me in private.

      1. Thanks Marco, I solved it – by nuking the error message of that sterile “compliance” check on perfectly valid addresses. See also:

        Less is more.

        1. Ugh… Pasted the wrong link but you get the idea.

        2. That doesn’t fix anything is just a workaround, if you have an email address that is not validated by Swift Mailer you should send me via email or to the Swift mailer developer.

          1. The email format that throws the error is as shown in the pastebin – i.e.:

            John Doe

            Not even quotes surrounding the name (even though that is used a lot out there, too)

          2. Look at the source code of my comment – in spite of the advertised support for the “code” tags it ate the “code” tags itself so the example email format shown above doesn’t print as intended.

          3. I already read the email in paste bin
            [14-Jan-2012 21:15:11] PHP Fatal error: Uncaught exception 'Swift_RfcComplianceException' with message 'Address in mailbox given [John Doe <person@example.com>] does not comply with RFC 2822, 3.6.2.' in /path/to/public_html/wp-content/plugins/cimy-swift-smtp/Swift/lib/classes/Swift/Mime/Headers/MailboxHeader.php:308

            but I believe is not the real one you used is it? You changed it and I am asking the _real_ one that caused the issue not an example from you.
            Errors must be reported AS IS not an interpretation of.

            BTW: Code tag works but Akismet antispam clears out email addresses seems so or WordPress has issues with < and > anyway is it my fault?

  10. First, the easy part: I’m not interested in “fault” – life’s too short, seriously – but the fact is that it really says under the comment text area: “You may use these HTML tags and attributes” but what you read is not what you get, really (hint: you can tweak or simply kill the printed allowed tags with comment_notes_after in your theme)

    Then, the really easy part: I’m not inclined to post or email real people’s names and email addresses, period. But there were absolutely no “strange” characters in there, nothing you wouldn’t find in a standard ASCII table, so there’s no character encoding issue in play either. The data in the log was exact analogous to what I typed. Dunno what borked it; it’s not unique though, looking at Google I’ve seen a bunch of reports of “strictness” issues at parsing.

    1. 1. ‘the easy part’: as said the antispam cleared out the email address not the code tag, you can continue blaming whatever you like, but you have to get to reality if you want to really understand how things work.
      Plus with my website I do what I want.

      2. ‘the really easy part’: if I cannot have the exact error what you think I can do? Open a ticket to Swift mailer with random email? Get to reality or stop to speak to me, you are wasting my time.

  11. Jens Holm says:

    Hi there

    There seem to be a problem when using your excellent plugin and Contact form 7.

    Cimy SMTP Plugin: 2.1.2
    Contact form 7: 3.1.1
    Wordpress 3.3.1
    PHP version 5.3

    I am using Google Apps as my email handler, and when I send one mail, it works excellent. When I use the second email option in Contact form 7, it seems like none of the mails are send.

    Kind regards

    1. And why should be my bug?

      1. John Kristiansen says:

        Hi, I just wanted to say that I was thinking about using your plugin but after reading through the comments, I decided against it because of you being a real jerk giving support. You complain about people not telling you details about potential bugs, and when they do that even in the most polite manner, like Jens Holm did, you dismiss them rudely. It must be sad to be like that. I mean if you don’t want to give support that’s fine, just say it and we can all move along using another plugin and both you and us can live happier lives.

        I don’t expect you to approve this comment, but seriously, I hope you try to change your attitude. And an apology in advance for wasting your so very precious time reading/deleting this. Ciao!

        1. I answer politely to polite people. People that are not reading FAQ or documentation on a free product are not polite, are time waster. Period.
          So you’re free to choose any product you like, I am free to be impolite towards impolite people. Or shall I ask you the permission?

  12. Jens Holm says:

    Ahh forget it.. wrong attitude, I’ll find a plugin, that works..


  13. Franco says:

    Ciao Marco, ho provato ad installare il plugin. E’ attivo ma provando a recuperare una password compare la schermata

    Impossibile inviare la mail.
    Possibile motivo: il tuo host potrebbe avere disabilitato la funzione mail()…

    Pensavo bastasse attivare il plugin, quali altre opzioni non ho considerato? Grazie!

    1. Bisogna immettere il proprio server smtp, relativa porta, username e password nel caso sia necessario.

  14. Joshee says:

    Hi Marco, my plugin has always worked fine until it has suddenly started giving the following errors:

    Warning: stream_set_blocking() expects parameter 1 to be resource, null given in /home/mypeel/public_html/mypeel/wp-content/plugins/cimy-swift-smtp/Swift/lib/classes/Swift/Transport/StreamBuffer.php on line 273

    Warning: stream_set_timeout() expects parameter 1 to be resource, null given in /home/mypeel/public_html/mypeel/wp-content/plugins/cimy-swift-smtp/Swift/lib/classes/Swift/Transport/StreamBuffer.php on line 279

    Expected response code 220 but got code “”, with message “”

    What does this mean and how can it be resolved?

    1. Joshee says:

      Okay, I figured out it’s an SMTP issue with my hosts. I will contact them! Thanks for the plug-in though! It’s great!

  15. suleiman says:

    The plugin works fantastically. The only issue? It doesn’t work correctly on a WordPress Multi-Site Installation.

    First, allow me to make my case:

    1) Multi-site admins are always looking for ways to offload server strain. By using an external SMTP solution (such as GMAIL), it allows us to disable the QMAIL or SENDMAIL processes and squeeze out some more RAM / CPU.

    2) This should be a trivial fix. Once activated the plugin loads up the default options page where the settings can be set, but this will not be replicated across all the blogs in a multi-site install. Those subsites will need to individually go in and configure the SMTP settings themselves, which is not really an option.

    The feature that’s needed here is for the Cimy Swift SMTP plugin to only load an options page on the Network Admin section, to apply across all the blogs on the site.

    1. Well debatable, who said that everyone needs the same settings? If I do these changes maybe someone could tell me that preferred the opposite.

  16. Suleiman says:

    The point behind a multi-site install is supposed to be for the site administrators to choose which plugins, themes, and settings should apply across all the blogs on the site.

    Our users aren’t looking for a fully-customizeable installation of wordpress, their looking to be a part of a community where blogging is easy and fun.

    As far as making the changes, it should be easy to provide a hook for the Network Admin page (which only MultiSite admins see) if it finds one on the wordpress install.

  17. Rolf says:

    I don’t fully agree with you, Suleiman. When using wordpress as a CMS for different brands of the same company, each having its own website, you need a different sender name and email address for each instance.

    So a compromise might be to to configure a default in the network admin page, but to still be able to overwrite this default in each instance.

  18. chhayu says:

    First of all thank you for you plug,then i want to give you some suggests.Add some functions ,for example people can change the style of the letter or add some css to to it .Besides i anly want to know how can i use it and also stop it to send the letter?because before you make people change the letter’s style i want to use other plug.
    thank you

    1. No, that is totally out of the plug-in’s scope. This is only a new engine to send email, don’t want to add anything else in it.

  19. JvD says:

    Is it possible to use the plugin to send network-related messages?

    1. This plug-in is a SMTP engine to send emails and overrides default WordPress function. It is nothing more, nothing less. Not sure what you really want to do though.

      1. JvD says:

        I see, by default the plugins is enabled for each site in the WP-network. That’s cool, but it would be a bit more useful when the network-related notifications would be sent by SMTP transport.

  20. Luiz says:

    Hi Marco, I am using your plugin in my site and the test works great, but still can’t receive messages sent via my wordpress theme’s contact page. Any clues? This happened with other themes as well.

    1. How can I possibly understand which is your issue if you do not read the FAQ, provide enough details of your system, theme used, code?

  21. Luiz says:

    Ok, you assume I did not read the FAQ. Thank you.

    1. Actually I did not assume, I *deducted* it, since last FAQ asks you about WordPress version, plug-in’s version exact steps to reproduce the issue, etc.
      You did not provide them, so indeed, you did *not* read the FAQ or you read only partially and you are wasting my time. Cheers.

  22. Nina de Leon says:

    I would like to share how I was able to make my inquiry form mail setup with Cimy Swift and a few other things.

    I’m using Amazon SES, and to be able to use it you need:
    1. Cimy Swift SMTP, set to port 25 and TLS
    2. Configure php.ini to use openssl and Fake Sendmail
    3. Replace the sendmail binary with one that supports SSL.

    I hope that helps.

  23. paul says:

    hi, your Cimy Swift SMTP plugin works fine for smtp with the standard registration on wp 3.6, but i’m using Simplr User Registration Form Plus and with that on a page for registration, i get a blank return page and no email received on registration.

    i can quite understand plugin incompatibility, do you want to investigate, i imagine the simplr uses phpmail, so how would i call your plugin from within simplr, if that needs to be done. i can do php.

    1. Please enable Debug logging and tell me which is the error thrown during registration:

  24. paul says:

    hi, debug now on and see the last error, is it a cimy smmtp prob, or a missing email address from the simplr end causing the fatal error?


    on the homepage
    Notice: Trying to get property of non-object in //wp-content/plugins/simplr-registration-form/simplr_reg_page.php on line 328

    Notice: Trying to get property of non-object in //wp-content/plugins/simplr-registration-form/simplr_reg_page.php on line 609

    Notice: Trying to get property of non-object in //wp-content/plugins/simplr-registration-form/simplr_reg_page.php on line 139

    on reg page
    Notice: Trying to get property of non-object in //wp-content/plugins/simplr-registration-form/simplr_form_functions.php on line 452

    Notice: Trying to get property of non-object in //wp-content/plugins/simplr-registration-form/simplr_form_functions.php on line 457

    Notice: Trying to get property of non-object in //wp-content/plugins/simplr-registration-form/simplr_form_functions.php on line 535

    With debug on wp, registration form..simplr…

    Notice: Trying to get property of non-object in //wp-content/plugins/simplr-registration-form/simplr_form_functions.php on line 401

    Notice: Trying to get property of non-object in //wp-content/plugins/simplr-registration-form/simplr_form_functions.php on line 427

    Notice: Undefined variable: out in /home/artdotgr//plugins/simplr-registration-form/simplr_form_functions.php on line 460

    in the simplr form itself

    Notice: Undefined index: options_array in //wp-content/plugins/simplr-registration-form/simplr_form_functions.php on line 358

    RETURN PAGE ERRORS after clicking register button

    Notice: Trying to get property of non-object in /…/wp-content/plugins/simplr-registration-form/simplr_reg_page.php on line 328

    Notice: registration.php is deprecated since version 3.1 with no alternative available. This file no longer needs to be included. in /…/wp-includes/functions.php on line 2920

    Notice: Trying to get property of non-object in /…/wp-content/plugins/simplr-registration-form/simplr_form_functions.php on line 17

    Notice: Trying to get property of non-object in /…/wp-content/plugins/simplr-registration-form/simplr_form_functions.php on line 179

    Fatal error: Uncaught exception ‘Swift_RfcComplianceException’ with message ‘Address in mailbox given [] does not comply with RFC 2822, 3.6.2.’ in /…/wp-content/plugins/cimy-swift-smtp/Swift/lib/classes/Swift/Mime/Headers/MailboxHeader.php:352 Stack trace: #0 /…/wp-content/plugins/cimy-swift-smtp/Swift/lib/classes/Swift/Mime/Headers/MailboxHeader.php(264): Swift_Mime_Headers_MailboxHeader->_assertValidAddress(”) #1 /…/wp-content/plugins/cimy-swift-smtp/Swift/lib/classes/Swift/Mime/Headers/MailboxHeader.php(108): Swift_Mime_Headers_MailboxHeader->normalizeMailboxes(Array) #2 /…/wp-content/plugins/cimy-swift-smtp/Swift/lib/classes/Swift/Mime/Headers/MailboxHeader.php(65): Swift_Mime_Headers_MailboxHeader->setNameAddresses(Array) #3 /…/wp-content/plugins/cimy-swift-smtp/Swift/lib/classes/ in /…/wp-content/plugins/cimy-swift-smtp/Swift/lib/classes/Swift/Mime/Headers/MailboxHeader.php on line 352

    1. Fatal error: Uncaught exception ‘Swift_RfcComplianceException’ with message ‘Address in mailbox given [] does not comply with RFC 2822, 3.6.2.’ in /…/wp-content/plugins/cimy-swift-smtp/Swift/lib/classes/Swift/Mime/Headers/MailboxHeader.php:352
      It seems to me that there is a missing address indeed.
      Just for the records:
      did you enable overwriting the sender from the Cimy Swift SMTP plugin without specifying the sender’s email?

    2. If you do not specify any “Notification email” then it will try to send an email to an empty email address, that’s why the error from my plug-in.
      I can workaround that bug discarding all emails with empty recipient, but that is really a bug of the Simplr Registration Form plug-in, it shouldn’t do that.
      A workaround is to change your post/page’s tag like this:
      [register notify="name@domain.com"]

  25. paul says:

    hi.. the cimy is set to overwrite the send address always, its a valid address for the domain and it sends an email ok to my own email address using the send test button.

    and cimy sends advice email out by smtp for ordinary wp registration, its just when I use the simplr registration form/page it fails with that fatal msg at the end in debug of return page.

    1. I have to take a look at what the other plugin is sending over. Seems more their issue, so consider a donation for this.

      Thank you

      1. paul says:

        ok..donation.. seems cimy expects the normal from address as string, or comma separated as an array. couldn’t understand it much further.

        cimy smtp seems the only sender plugin that works currently with wp 3.6, which is why i’m using it.

      2. paul says:

        hi.. is there any progress yet on having a look?

        1. I can look at it, but in the spare time. Donation, again, is welcome.

          1. paul says:

            hi..donation made, hope its enough to look at it

  26. walter says:

    Ciao Marco, Complimenti! vado al sodo:
    Hostgator con php 5.3 e wp 3.6 e ultima versione del plugin. risultato: connection refuser.
    se ho capito bene devo chiedere:
    1) Unblock/allow port 465
    2) Whitelist port 465
    3) Whitelist smtp.gmail.com
    uso gmail for App – devo far modificare anche il php.ini? se si cosa devo chiedere?

    1. Non ne ho idea, non conosco Hostgator. Consulta il loro customer support.

  27. Sergio says:

    Hello Marco,
    Just installed your plugin, thank you.
    I noted that after pushing the Send button the message is sent normally but I remain on the contact page and do not get to the thank you page as it is normal. Is there anything you already know about this? Thanks.

    1. Which send button? Can you elaborate more what are you talking about exactly?

Leave a Reply

Your email address will not be published. Required fields are marked *

You may use these HTML tags and attributes: <a href="" title=""> <abbr title=""> <acronym title=""> <b> <blockquote cite=""> <cite> <code> <del datetime=""> <em> <i> <q cite=""> <strike> <strong>