2009/6/30 Ralf Hildebrandt :
> That would make sense. Some decision process in that stage to find out
> if the mail needs to be signed...
>
> Maybe that kind of lookup is slow?
It certainly looks like it.
> I set it up according to the readme:
>
> dkim_key('charite.de', 'default', '/etc/ssl/priv
* Guy :
> But wouldn't the options set for submission in master.cf be checked
> after RCPT TO? So if dkimproxy is just slow to accept a connection
> (could have something to do with trying to run it for 130+ domains)
> would that interfere at the RCPT TO stage?
That would make sense. Some decisio
Hi Ralf,
2009/6/30 Ralf Hildebrandt :
> DNS seems to be slow. Check the chroot, check the resolv.conf
I've got a DNS server on the LAN doing caching. Local domains return a
response within 15msec for a first request and 1msec or lower after
that (tested with dig).
Neither bind nor Postfix are ch
* Guy :
> Hi,
>
> I recently tried adding DKIM/DomainKeys to postfix using DKIMproxy. It
> signs things just fine, but connections were slowed down to the point
> that I've had to remove it.
> When telnetting to port 587 (25 is only used for incoming mail) with
> it enabled the response to the RCP
Hi,
I recently tried adding DKIM/DomainKeys to postfix using DKIMproxy. It
signs things just fine, but connections were slowed down to the point
that I've had to remove it.
When telnetting to port 587 (25 is only used for incoming mail) with
it enabled the response to the RCPT TO: command takes 30
