CiviCRM Community Forums (archive)

*

News:

Have a question about CiviCRM?
Get it answered quickly at the new
CiviCRM Stack Exchange Q+A site

This forum was archived on 25 November 2017. Learn more.
How to get involved.
What to do if you think you've found a bug.



  • CiviCRM Community Forums (archive) »
  • Old sections (read-only, deprecated) »
  • Support »
  • Using CiviCRM »
  • Using CiviMail »
  • Using CiviSMTP (Moderator: shane) »
  • Does CiviSMTP require a name?
Pages: [1]

Author Topic: Does CiviSMTP require a name?  (Read 1060 times)

adixon

  • I post frequently
  • ***
  • Posts: 314
  • Karma: 19
    • Blackfly Solutions
Does CiviSMTP require a name?
February 12, 2010, 07:07:22 am
A client just sent out a message to 42 recipients, and 3 went through, with the rest (39) getting bounced for reasons unknown. The 39 bounces were a collection of emails I had just imported, that didn't have a corresponding name. Is that why they bounced? If not, any ideas? Here is the report (time is EST).


Intended Recipients   42
Succesful Deliveries   3 (7.14%)
Spooled Mails   0
Tracked Opens   2
Click-throughs   0
Forwards   0
Replies   0
Bounces   39 (92.86%)
Unsubscribe Requests   0 (0.00%)
Scheduled Date   February 10th, 2010 1:54 PM
Status   Complete
Start Date   February 10th, 2010 1:56 PM
End Date   February 10th, 2010 1:56 PM

adixon

  • I post frequently
  • ***
  • Posts: 314
  • Karma: 19
    • Blackfly Solutions
Re: Does CiviSMTP require a name?
February 12, 2010, 07:56:22 am
i just got some help from lobo here:

http://fisheye2.atlassian.com/changelog/~br=v3.0/CiviCRM/

apply patches 26097 26098

trying it out now...

adixon

  • I post frequently
  • ***
  • Posts: 314
  • Karma: 19
    • Blackfly Solutions
Re: Does CiviSMTP require a name?
February 12, 2010, 08:34:10 am
Yes, that worked - thanks lobo!

Further notes:

1. i think this is only applicable to 3.0.4, and the problem is not universal

2. the origin is in the complication of how to deal with non-ascii characters in the mail headers - there have been multiple patches on patches to try and get this to work, and in my case, there was no "to" name, so that's how/why it failed. There are probably other edge cases that will fail as well. The above patches boil down to editing/replacing two lines in CRM/Mailing/BAO/Job.php - you can do it by hand pretty easily in a pinch. The comment is:

"make $recipient actually be the *encoded* header, so as not to baffle Mail_RFC822, CRM-5743"

Pages: [1]
  • CiviCRM Community Forums (archive) »
  • Old sections (read-only, deprecated) »
  • Support »
  • Using CiviCRM »
  • Using CiviMail »
  • Using CiviSMTP (Moderator: shane) »
  • Does CiviSMTP require a name?

This forum was archived on 2017-11-26.