On Sun, Dec 07, 2014 at 10:56:17PM -0700, Steffan A. Cline wrote:
> Looking earlier on the thread, Jan suggested that it was dovecot that had
> the issue and may be related.
>
> My issue seems to be a connection issue postfix and my webapp. Viktor
> suggested it could be an issue with my OpenSSL
On December 7, 2014 12:28:12 PM EST, John wrote:
>Are SPF DNS records deprecated. i was checking my setup using MXTools
>and it comes back with a warning then SPF records are no longer
>"supported".
>When I look for docs on the internet, I get two answers( 3 actually)
>a) no they are current,
>b
Looking earlier on the thread, Jan suggested that it was dovecot that had
the issue and may be related.
My issue seems to be a connection issue postfix and my webapp. Viktor
suggested it could be an issue with my OpenSSL implementation. The dev
webapp is running on MacOS X 10.10 which should have
John skrev den 2014-12-07 18:28:
And just to make life a little more interesting, the Bind9 log show
an entry "general: warning: zone klam.ca/IN/external: 'klam.ca' found
SPF/TXT record but no SPF/SPF record found, add matching type SPF
recor..."!
what spf client software are you using ?
atle
Are SPF DNS records deprecated. i was checking my setup using MXTools
and it comes back with a warning then SPF records are no longer
"supported".
When I look for docs on the internet, I get two answers( 3 actually)
a) no they are current,
b) they have been dropped,
c) articals that only discuss
On Sun, Dec 07, 2014 at 06:02:23PM +0100, Jan Kowalski wrote:
> In my case it is caused by my dovecot configuration, namely:
>
> ssl_protocols = !SSLv2 !SSLv3
> ssl_cipher_list = HIGH:!LOW:!SSLv2:!SSLv3:!EXP:!aNULL
This configuration is incorrect. The majority of TLSv1.2 cipher
suites were defi
Am 07.12.2014 um 18:16 schrieb Whit Blauvelt:
On Sat, Dec 06, 2014 at 04:48:31PM -0500, Wietse Venema wrote:
Looks like some proxy is plugged in the wrong way (waiting for the
client to speak first). With SMTP the server speaks first.
Given zero details on Postfix configuration, I won't waste
Am 07.12.2014 um 18:02 schrieb Jan Kowalski:
Dnia , o godz.
"Steffan A. Cline" napisał(a):
have you resolved this problem yet?
I reproduce it when I connect via either imap or smtp from claws-mail
linked against gnutls 3.3.10-1 to a postfix server with dovecot sasl
enabled.
In my case it is
Whit Blauvelt:
> Given that it's not the well-known TCP window scaling problem, and that it
> is a problem specific to just the one ISP's routers, what is the list of how
> they can have those configured wrong? SYN flood protection? Anything else? I
> have Postfix servers on other ISPs too, all con
On Sat, Dec 06, 2014 at 04:48:31PM -0500, Wietse Venema wrote:
> Looks like some proxy is plugged in the wrong way (waiting for the
> client to speak first). With SMTP the server speaks first.
>
> Given zero details on Postfix configuration, I won't waste time
> with random guesses.
Much as I lo
Jan,
No, I have not.
Viktor suggested my webapp was at fault. I submitted a bug to the
middleware provider to see if they can isolate it but if there are other
apps with the same issue, it makes me wonder if there's something we can
change server side (postfix) to fix it.
You've renewed my inter
Dnia , o godz.
"Steffan A. Cline" napisał(a):
Hi,
have you resolved this problem yet?
I reproduce it when I connect via either imap or smtp from claws-mail
linked against gnutls 3.3.10-1 to a postfix server with dovecot sasl
enabled.
In my case it is caused by my dovecot configuration, namely
Whit Blauvelt:
> In telnetting to the two IPs, with the one that works the 220 line comes up
> right away. On the bad line, the "Connect to" and "Escape character is '^]'"
> lines come right up, but not the 220. If I then hit Enter the 220 line comes
> right up, but not without that.
Turn off the
13 matches
Mail list logo
