Brad Riemann:
> Hi Ram,
>
> We are using ZXTM (also known as Stingray), with the built in SMTP
> options from the load balancer (which really isn't much..),
> everything im seeing in the config indicates it should be running
> and processing on the application layer, were there any settings
> on t
Am 2015-01-09 07:27, schrieb m...@ruggedinbox.com:
Hi all, when hardening dovecot against the POODLE vulnerability,
we followed the advise to disable SSL2 and SSL3
but this is giving problems with some email clients (claws-mail).
ssl_protocols = !SSLv2 !SSLv3
results in the following error:
do
On Fri, Jan 09, 2015 at 07:04:13PM +0530, Ram wrote:
> This seems to be a Firewall NAT issue. The Load balancer would add a HOP if
> it is on the application layer.
That's wrong. Layer 4 devices don't add SMTP hops (Received:
headers, ...).
--
Viktor.
Hi Ram,
We are using ZXTM (also known as Stingray), with the built in SMTP options from
the load balancer (which really isn't much..), everything im seeing in the
config indicates it should be running and processing on the application layer,
were there any settings on the F5 you had to adjust t
2015-01-09 11:01 GMT-03:00 Wietse Venema :
> M. Rodrigo Monteiro:
>> >From command line, SASL Auth is working. The auth is from a remote
>> zimbra (imap) server.
>>
>>
>> Init saslauthd
>> /usr/sbin/saslauthd -m /var/run/saslauthd -a rimap -O IP -r -l -n 10
>>
>> # cat /etc/sasl2/smtpd.conf
>
> Ple
M. Rodrigo Monteiro:
> >From command line, SASL Auth is working. The auth is from a remote
> zimbra (imap) server.
>
>
> Init saslauthd
> /usr/sbin/saslauthd -m /var/run/saslauthd -a rimap -O IP -r -l -n 10
>
> # cat /etc/sasl2/smtpd.conf
Please show evidence that libsasl2 actually uses this fi
>From command line, SASL Auth is working. The auth is from a remote
zimbra (imap) server.
Init saslauthd
/usr/sbin/saslauthd -m /var/run/saslauthd -a rimap -O IP -r -l -n 10
# cat /etc/sasl2/smtpd.conf
pwcheck_method: saslauthd
mech_list: plain login
# testsaslauthd -u u...@domain.tld -p 'passw
On 01/07/2015 10:40 PM, Brad Riemann wrote:
Hello!
First time caller, long time listener J.
I’ve been working on a new mail filtering solution for our company
that revolves around the solution receiving inbound mail through a
load balancer.
We have come upon an issue that I am not finding
On Fri, 09 Jan 2015 06:27:44 +, m...@ruggedinbox.com stated:
> Hi all, when hardening dovecot against the POODLE vulnerability,
> we followed the advise to disable SSL2 and SSL3
> but this is giving problems with some email clients (claws-mail).
>
> ssl_protocols = !SSLv2 !SSLv3
>
> results
