SMTP server does not support authentication

[rodrigo tavares]

Hello !

I try sent a email via web, come this errors.

I searched for many sites, but i not found

I have postfix, cyrus and LDAP included.

# When sent mail for firefox

Auhentication failure [SMTP: SMTP server does not support authentication
(code: 250, response: def.com PIPELINING SIZE 20971520 VRFY ETRN ENHANCEDS

#Logs Cyrus.

Feb  6 15:41:07 defensoria cyrus/imap[1324]: fetching user_deny.db entry for 'user^jim'
Feb  6 15:41:07 defensoria cyrus/imap[1324]: open: user user^jim opened INBOX
Feb  6 15:41:07 defensoria cyrus/imap[1324]: fetching user_deny.db entry for 'user^jim'
Feb  6 15:41:07 defensoria cyrus/imap[1324]: fetching user_deny.db entry for 'user^jim'
Feb  6 15:41:07 defensoria cyrus/imap[1324]: USAGE user^jim user: 0.000000 sys: 0.000000

Any Idea ?

Rodrigo Tavares

[David Guntner]

Via Google search for "postfix authentication":

http://www.postfix.org/SASL_README.html#server_sasl

--Dave

[Jerry Stuckle]

Your message is telling you the problem. Many servers do not require
(nor allow) authentication when coming from a trusted source, i.e.
localhost.

What are you using to send your webmail?


--
To UNSUBSCRIBE, email to debian-us...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listm...@lists.debian.org
Archive: http://lists.debian.org/51129D4...@attglobal.net

[David Guntner]

No, look again at the messages he's providing. I can't speak for the
cyrus log entries in his syslog, but the 250 response from the MTA
(Postfix) is the telling one - there's no "AUTH" showing up there, which
means it's not configured to accept authentication. Typically, a local
trusted net connection won't *require* auth, but I've yet to see a setup
where it's *prohibited* simply because it's local.

--Dave

[Jerry Stuckle]

What I said was the server doesn't accept authentication. And yes, I
have seen many servers which don't allow it from trusted sources. They
include localhost, but a large number also accept from designated
servers (where authentication has already been done). Often these are
heavily loaded systems.

If the source is trusted, there is no need to authenticate.

--
To UNSUBSCRIBE, email to debian-us...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listm...@lists.debian.org

Archive: http://lists.debian.org/5112B425...@attglobal.net

[David Guntner]

Jerry Stuckle grabbed a keyboard and wrote:
>
> What I said was the server doesn't accept authentication. And yes, I
> have seen many servers which don't allow it from trusted sources. They
> include localhost, but a large number also accept from designated
> servers (where authentication has already been done). Often these are
> heavily loaded systems.
>
> If the source is trusted, there is no need to authenticate.

Agreed, there's no need if on a trusted network. I personally don't see
a need to *prohibit* authentication from a connection on a local network
(and would most likely never set up a system that way), and I haven't
run into one yet. Clearly, you have - so, I stand corrected. :-)

--Dave

[Jerry Stuckle]

Dave,

As I said - typically used on heavily loaded systems. Unnecessary
authentication will add even more to the load. The easiest way to
prevent the extra load is to prohibit it.

Certain parts of the U.S. Government use such a system, as do some large
corporations. I've even seen some larger web hosting companies use it,
where they funnel all their outgoing email through one server.

--
To UNSUBSCRIBE, email to debian-us...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listm...@lists.debian.org

Archive: http://lists.debian.org/5112C8E2...@attglobal.net