Get answers quicker by searching

Howdy, Stranger!

It looks like you're new here. If you want to get involved, click one of these buttons!

In this Discussion

Mail ending up in junk mail
  • Vote Up0Vote Down catalogcatalog
    Posts: 3Sendy user

    Hi, I have just completed the set up of sendy and conducted a test sending an HTML email to 3 of my own email addresses. All three ended up in my gmail junk folder. I repeated the process with my old email solution using the same content and addresses but sending it from a gmail address and all three arrived in my mail box. Any ideas why it should consider this header junk? The message is the same so it seems fair to rule that out of the equation.

    Delivered-To: peterr@removed for security.co.uk Received: by 10.49.116.5 with SMTP id js5csp158875qeb; Tue, 5 Feb 2013 04:51:28 -0800 (PST) Received: from a8-34.smtp-out.amazonses.com (a8-34.smtp-out.amazonses.com. [54.240.8.34]) by mx.google.com with ESMTP id q13si18766482vcw.36.2013.02.05.04.51.27; Tue, 05 Feb 2013 04:51:27 -0800 (PST) X-Received: by 10.52.16.40 with SMTP id c8mr10609501vdd.99.1360068688099; Tue, 05 Feb 2013 04:51:28 -0800 (PST) Return-Path: 0000013caa6931e1-67e4d04d-6c8b-40d6-820e-b22da7fbd899-000000@amazonses.com Return-Path: 0000013caa6931e1-67e4d04d-6c8b-40d6-820e-b22da7fbd899-000000@amazonses.com Received-Spf: pass (google.com: domain of 0000013caa6931e1-67e4d04d-6c8b-40d6-820e-b22da7fbd899-000000@amazonses.com designates 54.240.8.34 as permitted sender) client-ip=54.240.8.34; Authentication-Results: mx.google.com; spf=pass (google.com: domain of 0000013caa6931e1-67e4d04d-6c8b-40d6-820e-b22da7fbd899-000000@amazonses.com designates 54.240.8.34 as permitted sender) smtp.mail=0000013caa6931e1-67e4d04d-6c8b-40d6-820e-b22da7fbd899-000000@amazonses.com Message-Id: 0000013caa6931e1-67e4d04d-6c8b-40d6-820e-b22da7fbd899-000000@email.amazonses.com X-Priority: 3 X-Mailer: PHPMailer 5.1 (phpmailer.sourceforge.net) Mime-Version: 1.0 Content-Type: multipart/alternative; boundary="b1_2c874fa4927afa767386e1ebff0bc3d0" X-Ses-Outgoing: 54.240.8.34 Natural Rankings

    Peter

  • 4 Comments
  • Vote Up0Vote Down BenBen
    Posts: 3,489Sendy support

    Hi Peter,

    Your emails probably didn't get pass Gmail's junk filter.

    Please see this existing thread http://sendy.co/discussion/594/sometimes-marked-as-spam#Item_13

    Also, you may want to find more information about your emails getting sent to spam on Amazon SES's forum https://forums.aws.amazon.com/forum.jspa?forumID=90

    Thanks.

    Ben

  • Vote Up0Vote Down catalogcatalog
    Posts: 3Sendy user

    Thanks Ben I read that one and have also read the Amazon one. I used my existing emailer software with SMTP2Go and they didn't go to junk. Tried everything and can only get them to go into junk using SES. Very depressing as I had set my heart on it. It's all so clean, productive and usable.

  • Vote Up0Vote Down catalogcatalog
    Posts: 3Sendy user

    On further comparison the headers in sendy junked mail are quite different from those in our current mail manager received message. Is this a configurable option in sendy?

    Received: from st11p00mm-smtpin003.mac.com ([17.172.83.252]) by ms01551.mac.com (Oracle Communications Messaging Server 7u4-26.01 (7.0.4.26.0) 64bit (built Jul 13 2012)) with ESMTP id 0MHR00K6WGX10CK0@ms01551.mac.com for somename@me.com; Tue, 05 Feb 2013 19:03:01 +0000 (GMT) Received: from smtp2go.com ([207.58.142.213]) by st11p00mm-smtpin003.mac.com (Oracle Communications Messaging Server 7u4-26.01(7.0.4.26.0) 64bit (built Jul 13 2012)) with ESMTP id 0MHR000J6GX01LV0@st11p00mm-smtpin003.mac.com for somename@me.com (ORCPT somename@me.com); Tue, 05 Feb 2013 19:03:01 +0000 (GMT) Original-Recipient: rfc822;somename@me.com X-Proofpoint-Virus-Version: vendor=fsecure engine=2.50.10432:5.9.8327,1.0.431,0.0.0000 definitions=2013-02-05_05:2013-02-04,2013-02-05,1970-01-01 signatures=0 X-Proofpoint-Spam-Details: rule=notspam policy=default score=1 spamscore=1 ipscore=0 suspectscore=89 phishscore=0 bulkscore=100 adultscore=2 classifier=spam adjust=0 reason=mlx scancount=1 engine=6.0.2-1212290000 definitions=main-1302050138 Message-Id: Tw7WhBiFSQypAbYp5c9fhwqdnu26AMP02H3A7l0G1PFK@lockside.co.uk Mime-Version: 1.0

  • Vote Up0Vote Down BenBen
    Posts: 3,489Sendy support

    Hi @catalog,

    The headers you've provided are generated by the email provider themselves, eg. Gmail, iCloud etc and cannot be changed.

    What's passed as headers to Amazon SES (as specified in their API docs) looks something like these:

    Date: Wed, 17 Aug 2011 00:21:38 GMT
    Host: email.us-east-1.amazonaws.com
    Content-Type: application/x-www-form-urlencoded
    X-Amzn-Authorization: AWS3 AWSAccessKeyId=AKIAIOSFODNN7EXAMPLE,
     Signature=uN0lHIf14tmMBzwnkHzaWBLrBFvJAvyXCsfSYAvwLuc=,
     Algorithm=HmacSHA256, SignedHeaders=Date;Host
    Content-Length: 230

    Basically it contains the date, AWS access key ID and secret. There is nothing to change here to make your email go to the inbox.

    It will help if you post this question on Amazon SES forum, they will be better able to help you better in this aspect.

    Thanks.

    Ben

This discussion has been closed.
All Discussions