I come back to this post to say that quanah was right. the 8.0.2 upgrade solved the problem for me. I pass the dkim control when i send a mail from my thunderbird on linux.
Thanks a lot quanah for your support, i wish you the best for this new year.
Printable View
I come back to this post to say that quanah was right. the 8.0.2 upgrade solved the problem for me. I pass the dkim control when i send a mail from my thunderbird on linux.
Thanks a lot quanah for your support, i wish you the best for this new year.
Good to hear, I also upgraded to 8.0.2, however I hit the IPv6 problem as found in the bug tracker, therefore mail isnt being signed at the moment. I will post back here when theres a patch for IPv6 support, but I am assuming this issue will be fixed as per houarnet-tech's post.Quote:
Originally Posted by houarnet-tech
Hi, the same here. 8.0.2 is working properly also for me (although I had problems with mails from Thunderbird on Windows).Quote:
Originally Posted by houarnet-tech
I would like to say THANK YOU to all ZCS developers.
I am still having the IPv6 issue Bug 79377 – IPv6 issues with amavis/opendkim/milter/postfix since 8.0.2
Is this supposed to be fixed yet?
I am running OS 8.0.3 GA in Ubuntu 12.10
Ok so I am at 8.0.3, but still having issues with milter/dkim...
I assume this is the cause:
May 8 02:00:07 mx1 postfix/dkimmilter/smtpd[13377]: NOQUEUE: reject: CONNECT from ip6-localhost[::1]: 554 5.7.1 <ip6-localhost[::1]>: Client host rejected: Access denied; proto=SMTP
I have no idea how to fix it, and it seems to have been that way since bug 79337 was fixed (never noticed it was somewhat different until now since the end result is the same as that bug, mail going into deferred).
Any ideas?
It looks like ::1 is not in "mynetworks" for postfix, so it is rejecting it. The rules are:
-o smtpd_recipient_restrictions=permit_mynetworks,rej ect
-o smtpd_client_restrictions=permit_mynetworks,reject
i.e., it allows anything in mynetworks, rejects anything else.
What is the output of
zimbra@zre-ldap002:~$ postconf mynetworks
I have:
mynetworks = 127.0.0.0/8 10.137.242.0/24 [::1]/128 [fc00:10:137:242::]/64 [fe80::]/64
(or as you can see, localhost for both ipv4 and ipv6)
This comes from the server entry:
zimbra@zre-ldap002:~$ zmprov gs zre-ldap002.eng.vmware.com zimbramtamynetworks
# name zre-ldap002.eng.vmware.com
zimbraMtaMyNetworks: 127.0.0.0/8 10.137.242.0/24 [::1]/128 [fc00:10:137:242::]/64 [fe80::]/64
Hi Quanah,
I got the email and was busy replying to that, sorry for the duplication (sticking to forum now).
It appears I only have IPv4 entries in my config, is there a correct way to add the IPv6 ones or can I just add them to zimbramtamynetworks?
zimbra@mx1:/root$ postconf mynetworks
mynetworks = 127.0.0.0/8 46.105.122.0/24
Regards,
Daniel
Hi Daniel,
Just use zmprov to modify the values in zimbramtamynetworks. For your case specifically, you want the [::1]/128 and [fe80::]/64 bits added to your existing value. I'm not sure what your IPv6 host range is based off of your ipv4 46.105.122.0/24 range, but that doesn't matter for this. ;)
Something along the lines of
zmprov ms mx1.yourdomain.com zimbraMtaMyNetworks '127.0.0.0/8 46.105.122.0/24 [::1]/128 [fe80::]/64'
Should do it.
Well I don't get Access denied anymore, but now i get:
May 8 03:30:05 mx1 postfix/dkimmilter/smtpd[16605]: warning: connect to Milter service inet:localhost:8465: Connection refused
EDIT: This was fixed by making changes to /etc/hosts, adding 'localhost' to the entry for ::1.
Thank You Quanah for your prompt help on these issues!Quote:
Originally Posted by Quanah
Relating it to the actual topic: I now have DKIM signed email that validates and does not get held up by IPv6 related issues, so all is working as it should.