DomainKeys + DKIM Issue

[rmmoore80]

Yes, it is sent using PHPNuke which is a web app built on PHP. Right now the ONLY filter I run is DKeyEvent. Once I get this ironed out I will reimplement the SWSoft Mail filter (AV, spamassassin, etc) as necessary.

 

[globalmcs]

After breaking down both of your headers, in the Fail one the only thing that doesn’t look right is the ****Return-Path:**** can you change the script that is creating the e-mail so it doesn’t include the Return-Path?

 

[rmmoore80]

I'll see if I can find that portion in the code and post my results.

That's the same conclusion I came to. It's the only difference I can see.

Does having my headers up there pose any major risk? Should I clear them out now that we looked at them?

 

[globalmcs]

Yeah, SPAM!
Let me know I'll edit the post and remove your header info.

 

[rmmoore80]

Yes if you could please.

 

[rmmoore80]

I was unable to find any reference to Return-Path in any of the coding. I am unfamiliar with the PHP Core or PHPNuke, so I'm not sure where it would be performing these actions. I'll continue looking.

 

[rmmoore80]

I setup a relay to go to two DomainKey tests using the same coding/technique that I a having issues with. Here are the results:



SENDMAIL:

Authentication System: DomainKeys Identified Mail
Result: DKIM signature confirmed GOOD
Description: Signature verified, message arrived intact
Reporting host: sendmail.net
More information: http://mipassoc.org/dkim/
Sendmail milter: https://sourceforge.net/projects/dkim-milter/

Authentication System: Domain Keys
Result: DK signature confirmed BAD
Description: Signature verification failed, message may have been tampered with or corrupted
Reporting host: sendmail.net
More information: http://antispam.yahoo.com/domainkeys
Sendmail milter: https://sourceforge.net/projects/domainkeys-milter/


EXHALUS.NET:


Authentication Results:


.mechanism DomainKeys
information: http://antispam.yahoo.com/domainkeys
reflector spec: rfc4870
auth result: pass


.mechanism DomainKeys Identified Mail
information: http://dkim.org
reflector spec: rfc4871
draft-allman-dkim-ssp-01
auth result: pass

 

[epicweb]

Was anyone able to get the _domainkey added to Plesk DNS? This is the roadblock for me.

 

[epicweb]

Can anyone help on this issue?

Originally posted by epicweb
Was anyone able to get the _domainkey added to Plesk DNS? This is the roadblock for me.

 

[rmmoore80]

Not yet. I've tried over and over again. No luck yet.

 

[LeaUK]

Snap, can't add an underscore with Plesk 8.1.1

started another thread here: http://forum.swsoft.com/showthread.php?s=&postid=179708#post179708 by accident!

4PSA DNS management also fails to allow this.

I too am keen to implement domainkeys but am stuck!

BTW - I too implement my DNS mail server/clients in the same manor. Good to hear others carrying out the same

Some further info from the SmarterMail filter developer can be found in this thread: http://forums.smartertools.com/forums/1/34987/ShowThread.aspx

Looking forward to another Plesk update

Lea

 

[epicweb]

I also wish Plesk BIND dns would support underscores. I have not been able to get an answer from anyone about it.

 

[rmmoore80]

I ALMOST got this working by manually editing the PSA database, but I never did quite get it right.

 

[LeaUK]

If one doesn't have a support contract do Plesk actually charge the $75 for this type of question as it's not technically a 'support' questions is it?

I might simply fire it to them anyway...

 

[LeaUK]

anyone dared to install Plesk 8.2 yet and checked for '_' acceptance?

 

[epicweb]

LOL - nope not yet... waiting to see how others do.

Originally posted by LeaUK
anyone dared to install Plesk 8.2 yet and checked for '_' acceptance?

 

[LeaUK]

ROFL, me too!

New features look exciting in terms of DotNetNuke etc, but I simply want Autoresponders to function, work with Smarter Mail 4.2 (for significantly increased mail password security) and for '_' in the DNS manager!

But daren't update for a couple of months...

Ho hum...
Lea

 

[epicweb]

Whats wrong you dont want to be on the bleeding edge? j/k

 

[sergius]

Gentlemen,

Thank you for request. This feature is scheduled for the next Plesk version.

 

[LeaUK]

Many thanks, looking forward to the new features already

Cheers
Lea