On 21 Feb 2013, at 17:13, Chris Knadle chris.kna...@coredump.us wrote:
On Thursday, February 21, 2013 10:30:10, Todd Lyons wro
I pulled the Exim master and found reference to the expired draft PRDR spec
in
/doc/doc-txt/experimental-spec.txt:
On 21 Feb 2013, at 18:42, Todd Lyons tly...@ivenue.com
wrote:
On Thu, Feb 21, 2013 at 10:17 AM, Todd Lyons tly...@ivenue.com wrote:
example) recipients before the DATA phase and you issue a 2XX response
after the DATA phase, you MUST deliver the email for all 5 or a DSN
for those you didn't
HI All,
Has anyone noticed a problem with exim-4.80.01+OpenSSL 1.0.1e
(installed from FreeBSD ports) and it delivering to remote hosts using
TLS?
Some remote hosts do work. Debugging shows that SSL negotiation
finished successfully but straight after that it is logged that the
remote closed the
W dniu 22.02.2013 14:29, Warren Baker pisze:
HI All,
Has anyone noticed a problem with exim-4.80.01+OpenSSL 1.0.1e
(installed from FreeBSD ports) and it delivering to remote hosts using
TLS?
Hi!
I've got simillar problem with openssl-1.0.1c. Exim couldn't deliver
email usint TLS to
I have a trusted domain we relay to that is not responding to exim
recipient checks. Is there something I can add to the following that
will allow that domain to be whitelisted from checks?
dropmessage = REJECTED - Recipient Verification Failed - User
Not Found
domains
On Friday 22 February 2013 15:29:56 Warren Baker wrote:
HI All,
Has anyone noticed a problem with exim-4.80.01+OpenSSL 1.0.1e
(installed from FreeBSD ports) and it delivering to remote hosts using
TLS?
Some remote hosts do work. Debugging shows that SSL negotiation
finished successfully
On Fri, Feb 22, 2013 at 7:27 PM, Alan Hicks ahi...@p-o.co.uk wrote:
This may be a cipher issue as they are different in your two examples.
Non Working
14:28:59 95534 Cipher: TLSv1:DES-CBC3-SHA:168
Working
Cipher: TLSv1:RC4-MD5:128
You could try the tls_require_ciphers option as per
I have a few google domains being rejected with the following error:
Technical details of permanent failure:
Google tried to deliver your message, but it was rejected by the server
for the recipient domain domain.com http://nls.k12.mn.us by
relay-2domain.com http://relay-2.lctn.org [public
| One could argue that domains that don't publish SPF records don't
| care about sender address forgery, and therefore don't care about
| backscatter. So, perhaps it's OK to send DSNs into domains without SPF
| records. And perhaps it's OK when the result is NEUTRAL (no policy).
This assumption
On 2013-02-22 at 15:29 +0200, Warren Baker wrote:
Disabling TLS fixes the problem or reverting to OpenSSL 0.9.8q (part
of base in FreeBSD 8.2) fixes the problem.
Anyone have suggestions on the best way to debug this to determine if
its a OpenSSL or a Exim problem ?
It looks like TLS
10 matches
Mail list logo