Arno scribbled something like:
>> Yep, I tried that and it does not go anywhere because the relay wants
>> authentication:
Maybe it has to do with a setting you may have accidentally turned on like I
did once and got that particular error.
File: /etc/courier/esmtpd
##NAME: AUTH_REQUIRED:0
#
#
Michael Heitmeier writes:
Indeed it was. What got me was the following text from
http://www.courier-mta.org/?courier.html in the 'esmtpauthclient' section:
Because this file contains passwords, it must not be world or group
readable, and owned by the user "daemon".
I read that as "it must be
That suggests, that the bug is in esmtpauthclient. Please check that:
1. The permissions of that file are right (600, owned by whatever uid the
courier is running with),
2. That Hostname, username and password in esmtpauthclient are separated by
exactly one whitespace,
3. That it is terminated wit
Hello,
On Wednesday 22 June 2005 21:12, Michael Heitmeier wrote:
> >change your esmtproutes to:
> >t-online.de: authmailonline.kundenserver.de /SECURITY=NONE
>
> Yep, I tried that and it does not go anywhere because the relay wants
> authentication:
Hmm, afaik the /SECURITY-switch in esmtproutes
change your esmtproutes to:
t-online.de: authmailonline.kundenserver.de /SECURITY=NONE
Yep, I tried that and it does not go anywhere because the relay wants
authentication:
2005-06-22 21:04:19.991083 192.168.1.30:3547 > auth.mail.onlinehome.de:smtp
tcp S S:1815791592 A:0 W:57344 (DF)
Hi,
On Wednesday 22 June 2005 11:31, Michael Heitmeier wrote:
> >Are you *sure* this name and password can do authenticated smtp? Have
> >you manually tried to connect to this server and issue an AUTH command
> >to see if it works like you think?
>
> Thanks for the suggestion... I believe it does
Are you *sure* this name and password can do authenticated smtp? Have
you manually tried to connect to this server and issue an AUTH command
to see if it works like you think?
Thanks for the suggestion... I believe it does. I'd be grateful for any
other hints. Since courier goes into STARTTLS
Michael Heitmeier wrote:
> Ok, tried that but still no joy:
>
> # more esmtproutes
> t-online.de: authmailonline.kundenserver.de
>
> # more esmtpauthclient
> authmailonline.kundenserver.de user password
>
> What else should I look at?
Are you *sure* this name and password can do authenticated s
Ok, tried that but still no joy:
# more esmtproutes
t-online.de: authmailonline.kundenserver.de
# more esmtpauthclient
authmailonline.kundenserver.de user password
What else should I look at?
If I understand esmtpauthclient correctly then the server name that comes
back in response to my E
Michael Heitmeier writes:
If I understand esmtpauthclient correctly then the server name that comes
back in response to my EHLO should be used, which in this case is
'mrelayeu.kundenserver.de'.
No.
It's the server name that you're connecting to that must be specified, not
whatever it squawk
All,
There have been some references to the same ISP before but I still cannot
get the relay to work. Looking at the following (IPEX output) it seems a
secure session is being established.
If I understand esmtpauthclient correctly then the server name that comes
back in response to my EHLO s
11 matches
Mail list logo
