Am 28.03.2011 18:30, schrieb Charles Marcus:
>> to specify exactly:
>>
>> "smtpd_sasl_type": smtpd = receive mails, smtp = send mails
>
> Interesting - I never even noticed you can specify a different type for
> each, so I thought the one setting was for both... guess I should have
> checked post
On 2011-03-28 12:12 PM, Reindl Harald wrote:
> Am 28.03.2011 18:01, schrieb Charles Marcus:
>> On 2011-03-25 5:27 PM, Walt Shekrota wrote:
>>> smtpd_sasl_type = dovecot
>> dovecot's sasl implementation doesn't support CLIENT side SASL auth,
>> only server side.
>> If you need client side SASL AUTH
On Mon, Mar 28, 2011 at 12:01:18PM -0400, Charles Marcus wrote:
> On 2011-03-25 5:27 PM, Walt Shekrota wrote:
> > smtpd_sasl_type = dovecot
>
> dovecot's sasl implementation doesn't support CLIENT side SASL auth,
> only server side.
>
> If you need client side SASL AUTH capability, use Cyrus-SAS
Am 28.03.2011 18:01, schrieb Charles Marcus:
> On 2011-03-25 5:27 PM, Walt Shekrota wrote:
>> smtpd_sasl_type = dovecot
>
> dovecot's sasl implementation doesn't support CLIENT side SASL auth,
> only server side.
>
> If you need client side SASL AUTH capability, use Cyrus-SASL...
to specify exa
On 2011-03-25 5:27 PM, Walt Shekrota wrote:
> smtpd_sasl_type = dovecot
dovecot's sasl implementation doesn't support CLIENT side SASL auth,
only server side.
If you need client side SASL AUTH capability, use Cyrus-SASL...
--
Best regards,
Charles
Closed thread I had TLS enabled and SASL was not being called for.
Moral of the story KISS Keep it Simple
And maybe, ONLY read official documents, but that is good advice for anything.
Thanks for those who tried to help.
-Walt
On Sunday 27 March 2011 19:22:42 Wietse Venema wrote:
> I conclude that your syslog service logs all the warnings to a different
> file than normal logging, and therefore you don't see the warning
> message with "warning: TLS has been selected, but TLS support is
> not compiled in".
>
> Wi
Wietse Venema:
> Walt Shekrota:
> > Hi Wietse,
> >
> > I tried the telnet test with a non frontier emailid and it just said ok so
> > that can't be the problem.
> > What returns from a normal send is 554 5.7.1 Error: (I think this is just a
> > catch all that says I do not identify myself)
I'm
Walt Shekrota:
> Hi Wietse,
>
> I tried the telnet test with a non frontier emailid and it just said ok so
> that can't be the problem.
> What returns from a normal send is 554 5.7.1 Error: (I think this is just a
> catch all that says I do not identify myself)
You need to send me (OFF-LIST) a
Hi Wietse,
I tried the telnet test with a non frontier emailid and it just said ok so
that can't be the problem.
What returns from a normal send is 554 5.7.1 Error: (I think this is just a
catch all that says I do not identify myself)
-Walt
Walt Shekrota:
> On Friday 25 March 2011 18:19:32 you wrote:
> > On Fri, Mar 25, 2011 at 6:27 PM, Walt Shekrota
> >
> > wrote:
> > > Mar 25 16:55:39 ubu postfix/qmgr[560]: 3485281365:
> > > from=, size=505, nrcpt=1 (queue active)
> >
> > [..]
> >
> > >
> > > smtp.frontier.com:25 wshekr...@fron
On Friday 25 March 2011 18:19:32 you wrote:
> On Fri, Mar 25, 2011 at 6:27 PM, Walt Shekrota
>
> wrote:
> > Mar 25 16:55:39 ubu postfix/qmgr[560]: 3485281365:
> > from=, size=505, nrcpt=1 (queue active)
>
> [..]
>
> >
> > smtp.frontier.com:25 wshekr...@frontier.com:mypassword
>
> . The sender
Am 26.03.2011 00:32, schrieb Walt Shekrota:
> On Friday 25 March 2011 18:19:32 Reinaldo de Carvalho wrote:
>> On Fri, Mar 25, 2011 at 6:27 PM, Walt Shekrota
>>
>> wrote:
>>> Mar 25 16:55:39 ubu postfix/qmgr[560]: 3485281365:
>>> from=, size=505, nrcpt=1 (queue active)
>>
>> [..]
>>
>>>
>>> smtp
On Friday 25 March 2011 18:19:32 Reinaldo de Carvalho wrote:
> On Fri, Mar 25, 2011 at 6:27 PM, Walt Shekrota
>
> wrote:
> > Mar 25 16:55:39 ubu postfix/qmgr[560]: 3485281365:
> > from=, size=505, nrcpt=1 (queue active)
>
> [..]
>
> >
> > smtp.frontier.com:25 wshekr...@frontier.com:mypassword
On Fri, Mar 25, 2011 at 6:27 PM, Walt Shekrota
wrote:
> Mar 25 16:55:39 ubu postfix/qmgr[560]: 3485281365: from=,
> size=505, nrcpt=1 (queue active)
[..]
>
> smtp.frontier.com:25 wshekr...@frontier.com:mypassword
. The sender (MAIL FROM) is equals to authentication user (AUTH)?
No: wshekr...@fro
On Friday 25 March 2011 14:44:07 Noel Jones wrote:
> If you're having trouble reading the logs, it's possible
> someone here might know what to make of those messages.
>
> If you need help, please see:
> http://www.postfix.org/DEBUG_README.html#mail
>
> In particular, show us "postconf -n" outpu
Walt Shekrota:
> > http://www.postfix.org/SASL_README.html#client_sasl_enable
>
> Trust me I've been through a lot of your documents and some several times.
These are simple instructions to turn on SASL authentication.
Nothing more, nothing less. If the instructions don't work, then
show what yo
On 3/25/2011 1:26 PM, Walt Shekrota wrote:
http://www.postfix.org/SASL_README.html#client_sasl_enable
Trust me I've been through a lot of your documents and some several times.
What does come to mind going through these is ...
1. Somehow I have to convey that I'm coming from a non existan
>
> http://www.postfix.org/SASL_README.html#client_sasl_enable
>
>
Trust me I've been through a lot of your documents and some several times.
What does come to mind going through these is ...
1. Somehow I have to convey that I'm coming from a non existant domain (mine)
and the remote side d
On Friday 25 March 2011 12:34:37 /dev/rob0 wrote:
> 1. Why did you switch from ssmtp? It's possible, even likely, that
>your needs would be better served by a null SMTP client, rather
>than a MTA such as Postfix.
>
Like you said this enables you to use a single client to access your mai
On Fri, Mar 25, 2011 at 11:47:03AM -0400, Walt Shekrota wrote:
> On Friday 25 March 2011 11:32:01 Brian Evans - Postfix List wrote:
> > > smtp.frontier.com wshekro...@frontier.com:x
> > > relayhost = 199.224.64.207
> >
> > smtp.frontier.com != 199.224.64.207
> >
> > As documented, they MU
Walt Shekrota:
> On Friday 25 March 2011 11:32:01 Brian Evans - Postfix List wrote:
> > > smtp.frontier.com wshekro...@frontier.com:x
> > > relayhost = 199.224.64.207
> >
> > smtp.frontier.com != 199.224.64.207
> >
> > As documented, they MUST be equal
>
> yes I read that last night and
On Friday 25 March 2011 11:32:01 Brian Evans - Postfix List wrote:
> > smtp.frontier.com wshekro...@frontier.com:x
> > relayhost = 199.224.64.207
>
> smtp.frontier.com != 199.224.64.207
>
> As documented, they MUST be equal
yes I read that last night and fixed it. Something I alternative
On Friday 25 March 2011 11:28:26 Reinaldo de Carvalho wrote:
> 1. The authentication really happened when postfix/smtp tried deliver?
I used telnet to verify that I truely have THE RIGHT ID AND PW
Now I look in the /etc/postfix/sasl_password I created and see it the same so
I am at a loss undesta
On 3/25/2011 11:12 AM, Walt Shekrota wrote:
> On Friday 25 March 2011 11:01:58 Wietse Venema wrote:
>> You must first fix the problem with SENDING MAIL to the REMOTE SERVER.
>> The REMOTE SERVER is not on localhost port 25.
> ok point taken... the server in that doc is the remote isp then obviousl
On Fri, Mar 25, 2011 at 12:12 PM, Walt Shekrota
wrote:
>
> ok point taken... the server in that doc is the remote isp then obviously I
> picked up a bad idea in some doc. So when I telnet auth with the remote its
> fine.
> 235 2.7.0 Authentication successful
>
> I'm grasping here trying to find wa
On Friday 25 March 2011 11:01:58 Wietse Venema wrote:
> You must first fix the problem with SENDING MAIL to the REMOTE SERVER.
> The REMOTE SERVER is not on localhost port 25.
ok point taken... the server in that doc is the remote isp then obviously I
picked up a bad idea in some doc. So when I
> On Friday 25 March 2011 10:09:23 Wietse Venema wrote:
> > The remote SMTP server rejects mail from your Postfix SMTP client.
> >
> > To configure SASL authentication in your Postfix SMTP client, see
> > http://www.postfix.org/SASL_README.html#client_sasl (Configuring
> > SASL authentication in t
On Friday 25 March 2011 10:09:23 Wietse Venema wrote:
> The remote SMTP server rejects mail from your Postfix SMTP client.
>
> To configure SASL authentication in your Postfix SMTP client, see
> http://www.postfix.org/SASL_README.html#client_sasl (Configuring
> SASL authentication in the Postfix S
Wietse:
> The remote SMTP server rejects mail from your Postfix SMTP client.
> To configure SASL authentication in your Postfix SMTP client, see
> http://www.postfix.org/SASL_README.html#client_sasl (Configuring
> SASL authentication in the Postfix SMTP/LMTP client).
Walt Shekrota:
> Ok yes that i
On Friday 25 March 2011 10:09:23 Wietse Venema wrote:
> Walt Shekrota:
> > > > Mar 24 13:57:27 ubu postfix/smtp[15875]: BAD9F82CB0:
> > > > to=, relay=199.224.64.207[199.224.64.207]:25,
> > > > delay=0.57, delays=0.2/0.03/0.17/0.17, dsn=5.7.1, status=bounced
> > > > (host 199.224.64.207[199.224.64.
On Fri, Mar 25, 2011 at 10:55 AM, Walt Shekrota
wrote:
>
> ok :( then I am at fault in understanding. The outgoing process must then be
> fully contained within postfix and the sasl2-bin. (still?) The above message
> is the ISP saying "you didn't authenticate". Is smtpd then part of postfix or
> a
Walt Shekrota:
> > > Mar 24 13:57:27 ubu postfix/smtp[15875]: BAD9F82CB0:
> > > to=, relay=199.224.64.207[199.224.64.207]:25,
> > > delay=0.57, delays=0.2/0.03/0.17/0.17, dsn=5.7.1, status=bounced (host
> > > 199.224.64.207[199.224.64.207] said: 554 5.7.1 Error: The message could
> > > not be
>
>
On Friday 25 March 2011 09:09:27 Wietse Venema wrote:
> Walt Shekrota:
> > if I telnet localhost smtp I get a lot of seemingly inert debug or trace
> > info in the same log which ultimately gets...
> > SASL: Connect to private/auth failed: connection refused
>
> This means one or more of the follo
Walt Shekrota:
> if I telnet localhost smtp I get a lot of seemingly inert debug or trace info
> in the same log which ultimately gets...
> SASL: Connect to private/auth failed: connection refused
This means one or more of the following:
- The Dovecot authentication server does not listen on the
35 matches
Mail list logo
