Forums & Blog

soz for messing up but should i wait for _domainkeys record to propagate over network. But even if it is like that, i shouldnt have seen `domainkeys=neutral (no sig)' in message header i thnik.

As mentioned in the FAQ, the lack of a signature in outgoing messages will usually be attributed to authentication issues (i.e. either your messages are not using SMTP authentication or else the envelope does not match the content of the message). Setting 'SmarterMailCompatibility=2.x' in dkeyeventsm.ini will often provide a quick fix for these issues.

i made compability mode to "2.x" but still it doesnt work. i see the `exe` it is running with every message but it doesnt work properly. Smarter mail is: SmarterMail Professional Edition Version 4.3.2831.

 what can i do more. why doesnt it write the error to log file.

 

thanks 

Serious errors will be logged to the Windows EventLog. If nothing is logged, then it is likely not an error, but a configuration issue. 

So do u have any suggestion to find out the problem and solve it ? i m trying different  Smartermail configuration .Any dow DKeyEvent operates on 2.x mode. but so far i vent solved it .

 

 Thanks

And i dont need to wait for dns propagation,do i ? immediately i have to see whether it isnt working or not

Any Help ? shall i try old version of DKeyEvent SM ?

It's possible that the reason why DKeyEvent is ignoring your messages is that they are not valid. The headers from the message you quoted, for example, do not have a valid sender address, so such a message would obviously not get signed by DKeyEvent.

thank you for your help but it still doesnt work for me . My sender address is valid domain in my dns server. i checked the header, they seem ok too.DKeyevent doesnt sign my messages.

Hello Again

 When i send an email to `dktest@exhalus.net ` it says neutral (no signature)

When i send email to myself . It was like

 -------------------------------------------------------------------------------------------------------------------

DKIM-Signature: v=1; t=1198500462; a=rsa-sha1; q=dns/txt; s=dkim;
  d=toldns.net; i=gokhan@toldns.net; c=relaxed/relaxed; bh=gqbDjpilsE87b/CZ
  Fii7SsQ41D4=; h=DomainKey-Signature:MIME-Version:Content-Type:Date:
  Subject:From:Reply-To:To:CC:Message-ID; b=QqBR8EH1J3i7XMIRg4wb2cj2WrIOZ39
  I7bqmRba3e23NgS+Kc59Aqb13QdKtH78/RjBktTriVuhpvguFT2wB9WNhj6Cd6bkrjGrSlc+W
  yd8bS7/Mc9ZYGpKdMA5kcVg0bEAMLJofF3yKwpVTSnEyOPl/s6lWqLttrEc+IN1fwnw=
DomainKey-Signature: a=rsa-sha1; q=dns; s=dig; d=toldns.net;
  c=simple; h=Received:MIME-Version:Content-Type:Date:Subject:From:Reply-To
  :To:CC:Message-ID; b=SCFwCuSQpJR6Ae2D58GDnyQm01uQvJx7L0u6PFYjOzNFNuJGIsl0
  e2c/utoXv2uSxLt0HRBZHQWfJkjY8XKU0kfVDYzTlHyboF4oZcW+SYyRO3xB4wwCdny5F4neL
  BlwwdN3crPlBwzjHyOj7uuFeYl7ZGqOpHQK0r0ler6GYjk=;
Received: from [82.108.79.130] by toldns.net via HTTP; Mon, 24 Dec 2007 12:47:25 +0000
MIME-Version: 1.0
Content-Type: multipart/alternative;
 boundary=----_SmarterMail_NextPart_5670225730837085
Date: Mon, 24 Dec 2007 12:47:25 +0000
Subject: asd
From: "Gokhan Karasoglu" <gokhan@toldns.net>
Reply-To: gokhan@toldns.net
To: <gokhan@toldns.net>
CC:
Message-ID: <3fa47f3c61ef44dd93bf8441ed1b0927@toldns.net>

This is a multi-part message in MIME format.

------_SmarterMail_NextPart_5670225730837085
Content-Type: text/plain;
 charset=iso-8859-1
Content-Transfer-Encoding: quoted-printable

=0D=0Aasdasdasd=0D=0A

------_SmarterMail_NextPart_5670225730837085
Content-Type: text/html;
 charset=iso-8859-1
Content-Transfer-Encoding: quoted-printable

<br>asdasdasd<br>

 

 

------_SmarterMail_NextPart_5670225730837085--

 -----------------------------------------------------------------------------------------------------------

 When i send an email to gmail

Delivered-To: karasoglu@gmail.com
Received: by 10.70.30.1 with SMTP id d1cs121289wxd;
        Mon, 24 Dec 2007 04:52:56 -0800 (PST)
Received: by 10.86.76.16 with SMTP id y16mr4450256fga.35.1198500775388;
        Mon, 24 Dec 2007 04:52:55 -0800 (PST)
Return-Path: <gokhan@toldns.net>
Received: from toldns.net ([82.108.79.133])
        by mx.google.com with ESMTP id 3si4744717fge.7.2007.12.24.04.52.54;
        Mon, 24 Dec 2007 04:52:55 -0800 (PST)
Received-SPF: pass (google.com: domain of gokhan@toldns.net designates 82.108.79.133 as permitted sender) client-ip=82.108.79.133;
Authentication-Results: mx.google.com; spf=pass (google.com: domain of gokhan@toldns.net designates 82.108.79.133 as permitted sender) smtp.mail=gokhan@toldns.net
MIME-Version: 1.0
Content-Type: multipart/alternative;
 boundary=----_SmarterMail_NextPart_3240371835215776
Date: Mon, 24 Dec 2007 12:52:32 +0000
Subject: asd
From: "Gokhan Karasoglu" <gokhan@toldns.net>
Reply-To: gokhan@toldns.net
To: <karasoglu@gmail.com>
CC:
Message-ID: <d3ddeea61bd44b9c80dcbb90433e5abb@toldns.net>

This is a multi-part message in MIME format.

------_SmarterMail_NextPart_3240371835215776
Content-Type: text/plain;
 charset=iso-8859-1
Content-Transfer-Encoding: quoted-printable

=0D=0Aasdasdas=0D=0A

------_SmarterMail_NextPart_3240371835215776
Content-Type: text/html;
 charset=iso-8859-1
Content-Transfer-Encoding: quoted-printable

<br>asdasdas<br>

------_SmarterMail_NextPart_3240371835215776--

The destination does not affect the way in which a message is parsed by DKeyEvent.

Hmm

 

But When i send a local domain user , i can see the headers but when i send remote dns users i cant. Maybe it could help to find out the problem.

You are probably sending the messages differently (or at least they are handled differently internally). The headers in the second messages you quoted seem to indicate that the relay was performed due to a whitelisted IP; this can mean that SMTP authentication was either not performed or else ignored, and this would obviously affect DKeyEvent.

DKeyEvent SM 0.3.2 is now available.


changes in this version:
    * added: option to SignOnlyForTheseRecipients

 

notes:

    - This option can be used to restrict signing to certain explicitly specified recipient domains. If any domains are specified using this option, then outgoing messages to other domains (i.e. domains not explicitly specified here) will not get signed. The option is defined separately for DomainKeys and DKIM.

First of all, I'd like to express very sincere thanks for making this plugin available...thank you!

Next, today I began to implement this for some domains on our SM 4 server.

The problem I'm having is that I seem to have it set up correctly, and when I send messages from the various domains for which I'm implemented domainkeys to a test address at Yahoo!, I see that the DomainKeys Authentication shows "pass (ok)".

You would think this would be good, right?

Unfortunately, EVERY message from all 8 of the domains I've tested with so far, even though they all show "pass (ok)", they are STILL delivered to the Spam folder and not the Inbox.

How on earth do we make it so that Yahoo! users actually get messages we send??

GenNS