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!
181 Responses
« Previous 1 2 3 4
I found it in /wp-admin/options-general.php?page=swift_smtp
EDIT: you are right documentation sucks a bit, thanks for your comment.
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,
Mark
I would try to use TLS and not SSL for gmail, as the plug-in also suggests.
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,
Mark
Thanks for sharing this.
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,
Mark
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,
Mark
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:
*blank*
and no email sent.
i’ve read along this FAQ, but no answer found.
any clue, master?
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.
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!
P.S.: when the option is checked, no wordpress message is sent at all.
But did you enter at least a valid email above that checkbox?
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!
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?
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
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.
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.
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:
http://pastebin.com/w8gUqNAk
Any idea what’s going on there? Thanks in advance!
As said via email provide full log to me in private.
Thanks Marco, I solved it – by nuking the error message of that sterile “compliance” check on perfectly valid addresses. See also:
http://stackoverflow.com/questions/1490042/swift-mailer-error-swift-rfccomplianceexception-on-an-email-that-actually-work
Less is more.
Ugh… Pasted the wrong link but you get the idea.
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.
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)
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.
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:308but 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?
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. ‘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.
« Previous 1 2 3 4