That fixed it!
Thanks so much for your help Wietse.
-- Always glad to help,
--Jay Bendon - Bendon Consults
On Fri, Feb 12, 2010 at 8:09 PM, Wietse Venema wrote:
> Jay Bendon:
>> -- listing of /usr/lib64/sasl2 --
>> total 2748
>> drwxr-xr-x 2 root root 4096 Feb 10 19:51 .
>> drwxr-xr-x 28
Jay Bendon:
> -- listing of /usr/lib64/sasl2 --
> total 2748
> drwxr-xr-x 2 root root 4096 Feb 10 19:51 .
> drwxr-xr-x 28 root root 20480 Feb 10 21:31 ..
> -rwxr-xr-x 1 root root890 Sep 3 19:04 libanonymous.la
> -rwxr-xr-x 1 root root 15880 Sep 3 19:05 libanonymous.so
> -rwxr-xr-x 1 r
saslfinger - postfix Cyrus sasl configuration Fri Feb 12 19:51:42 CST 2010
version: 1.0.2
mode: client-side SMTP AUTH
-- basics --
Postfix: 2.3.3
System: CentOS release 5.4 (Final)
-- smtp is linked to --
libsasl2.so.2 => /usr/lib64/libsasl2.so.2 (0x2b16ec84f000)
-- active SMTP AUTH
> relayhost = [smtp.gmail.com]:587
This host supports no SASL authentication BEFORE STARTLS:
% telnet smtp.gmail.com 587
...
220 mx.google.com ESMTP 42sm38391439vws.8
ehlo hostname.porcupine.org
250-mx.google.com at your service, [my.ip.addr]
250-SIZE 35651584
250-8BITMIME
250-STARTTLS
250-ENHANC
the only changes tested were:
smtp_sasl_security_options = noanonymous, noplaintext
smtp_sasl_tls_security_options = noanonymous
and
smtp_sasl_security_options = noplaintext
smtp_sasl_tls_security_options = noplaintext
My origional configuration was the recommended:
smtp_sasl_security_options
> On Thu, Feb 11, 2010 at 7:57 PM, Wietse Venema wrote:
> > Postfix also logged this message, amidst your verbose logging.
> >
> > ? ? Feb 11 18:23:18 nagios postfix/smtp[22560]: warning: SASL
> > authentication failure: No worthy mechs found
> >
> > For a remedy, see http://www.postfix.org/SASL_
Thanks Wietse,
I used what was recommended by the readme and that resulted in the
same error. I also tried a few other settings in there and no better
results.
-- Always glad to help,
--Jay Bendon - Bendon Consults
-Senior Engineer
+1-402-321-7388
On Thu, Feb 11, 2010 at 7:57 PM, Wietse Ven
Postfix also logged this message, amidst your verbose logging.
Feb 11 18:23:18 nagios postfix/smtp[22560]: warning: SASL authentication
failure: No worthy mechs found
For a remedy, see http://www.postfix.org/SASL_README.html
Wietse
Thanks Sahil,
I actually had that attached but was getting bounced for too long of
an email to the mailing list.
I ran "saslfinger -c" and did not receive any errors. The man pages
indicated that it should also tell what type of connections the smtp
server should accept however this did not seem
On Thu, 11 Feb 2010, Jay Bendon wrote:
> Feb 11 18:23:18 nagios postfix/smtp[22559]: 261085EEB34:
> to=, relay=smtp.gmail.com[74.125.47.109]:587,
> delay=1040, delays=1039/0.03/0.57/0, dsn=4.7.0, status=deferred (SASL
> authentication failed; cannot authenticate to server
> smtp.gmail.com[74.125.4
Jay Bendon:
> I think i mis-spoke
>
> i set:
>
> debug_peer_level = 3
> and
> debug_peer_list = smtp.gmail.com
>
> prior to setting that all i was getting was this error in the log:
>
> Feb 11 18:23:18 nagios postfix/smtp[22559]: 261085EEB34:
> to=, relay=smtp.gmail.com[74.125.47.109]:587,
> de
I think i mis-spoke
i set:
debug_peer_level = 3
and
debug_peer_list = smtp.gmail.com
prior to setting that all i was getting was this error in the log:
Feb 11 18:23:18 nagios postfix/smtp[22559]: 261085EEB34:
to=, relay=smtp.gmail.com[74.125.47.109]:587,
delay=1040, delays=1039/0.03/0.57/0, dsn
Jay Bendon:
> I setup a nagios system and i'm trying to use postfix to relay the
> notifications through our google apps setup to our group.
> I have turned debugging 3 on but i'm still not quite sure what to make
> of the results:
Don't do that. Run Postfix in NORMAL MODE and look for the warning
I setup a nagios system and i'm trying to use postfix to relay the
notifications through our google apps setup to our group.
I have turned debugging 3 on but i'm still not quite sure what to make
of the results:
>> Feb 11 18:23:18 nagios postfix/smtp[22559]: flush_add: site powerdnn.com id
>> 261
14 matches
Mail list logo
