Jim Garrison:
> On 6/6/2022 3:13 AM, Jaroslaw Rafa wrote:
> > Dnia 5.06.2022 o godz. 23:29:05 julio covolato pisze:
> >>
> >> I would like to know why these messages appear in the mail.log,
> >> I know that "UGFzc3dvcmQ6" is base64 encoded for "Password:".
> >> Is this some misconfigured internet
On 6/6/2022 3:13 AM, Jaroslaw Rafa wrote:
Dnia 5.06.2022 o godz. 23:29:05 julio covolato pisze:
I would like to know why these messages appear in the mail.log,
I know that "UGFzc3dvcmQ6" is base64 encoded for "Password:".
Is this some misconfigured internet mail server system (Windows)?
Rath
Dnia 5.06.2022 o godz. 23:29:05 julio covolato pisze:
>
> I would like to know why these messages appear in the mail.log,
> I know that "UGFzc3dvcmQ6" is base64 encoded for "Password:".
> Is this some misconfigured internet mail server system (Windows)?
Rather not a misconfigured server, but som
ix/smtps/smtpd[11831]: warning:
unknown[178xxx.xxx.58]: SASL LOGIN authentication failed: UGFzc3dvcmQ6
Jun 5 23:25:08 saturn postfix/smtps/smtpd[11831]: lost connection after
AUTH from unknown[178.88.160.58]
Jun 5 23:25:08 saturn postfix/smtps/smtpd[11831]: disconnect from
unknown[178.xxx.xxx
stomer.com[62.141.41.104]: SASL LOGIN
authentication failed: UGFzc3dvcmQ6
$ printf "%s\n" $(printf "%s\n" UGFzc3dvcmQ6 | openssl base64 -d)
Password:
So, is that what the morons tried to login with (I have a few others
that using your snippet decode to "Username:" (VXNlcm5
08:43:43 ns1 postfix/smtpd[8800]: warning:
unknown[46.148.27.71]: SASL LOGIN authentication failed: UGFzc3dvcmQ6
May 13 08:44:28 ns1 postfix/smtpd[6191]: warning:
unknown[185.234.217.61]: SASL LOGIN authentication failed: UGFzc3dvcmQ6
May 13 08:44:52 ns1 postfix/smtpd[11760]: warning:
unknown
:43 ns1 postfix/smtpd[8800]: warning:
> unknown[46.148.27.71]: SASL LOGIN authentication failed: UGFzc3dvcmQ6
> May 13 08:44:28 ns1 postfix/smtpd[6191]: warning:
> unknown[185.234.217.61]: SASL LOGIN authentication failed: UGFzc3dvcmQ6
> May 13 08:44:52 ns1 postfix/smtpd[11760]: warning
authentication failed: UGFzc3dvcmQ6
May 13 08:44:28 ns1 postfix/smtpd[6191]: warning:
unknown[185.234.217.61]: SASL LOGIN authentication failed: UGFzc3dvcmQ6
May 13 08:44:52 ns1 postfix/smtpd[11760]: warning:
unknown[181.214.206.20]: SASL LOGIN authentication failed: UGFzc3dvcmQ6
May 13 08:45:17 ns1
Wonderful words to reflect on.. on a Sunday.
You too will get old. And when you do you'll fantasize that when you
were young prices where reasonable, politicians were noble, and children
respected their elders. Respect your elders.
Rgds/DP
9849111010
Sent from my iPhone. Pls excuse brevity and
On 2018-05-12 (23:01 MDT), Viktor Dukhovni wrote:
>
>> On May 13, 2018, at 12:42 AM, @lbutlr wrote:
>>
>> In these log lines, what is "UGFzc3dvcmQ6"?
>>
>> May 12 07:52:07 mail submit-tls/smtpd[32670]: warning:
>> vps1590651.vs.
> On May 13, 2018, at 12:42 AM, @lbutlr wrote:
>
> In these log lines, what is "UGFzc3dvcmQ6"?
>
> May 12 07:52:07 mail submit-tls/smtpd[32670]: warning:
> vps1590651.vs.webtropia-customer.com[62.141.41.104]: SASL LOGIN
> authentication failed: UGFzc3dvcmQ6
In these log lines, what is "UGFzc3dvcmQ6"?
May 12 07:52:07 mail submit-tls/smtpd[32670]: warning:
vps1590651.vs.webtropia-customer.com[62.141.41.104]: SASL LOGIN authentication
failed: UGFzc3dvcmQ6
May 12 17:05:14 mail submit-tls/smtpd[87898]: warning:
ma350.mars.fastwe
Hi Viktor,
I switched to dovecot and the email went through fine this time! You rock!
Thanks so much for the help!
Viktor Dukhovni wrote:
On Thu, Feb 09, 2017 at 04:05:25PM +, Viktor Dukhovni wrote:
On Thu, Feb 09, 2017 at 12:45:44PM -0300, Nick wrote:
I have just tried adding
On Thu, Feb 09, 2017 at 04:05:25PM +, Viktor Dukhovni wrote:
> On Thu, Feb 09, 2017 at 12:45:44PM -0300, Nick wrote:
>
> > I have just tried adding multiple symlinks, restarted postfix and saslauthd
> > but the same error persists,
>
> Time to configure "debug_peer_list" to include the IP ad
On Thu, Feb 09, 2017 at 12:45:44PM -0300, Nick wrote:
> I have just tried adding multiple symlinks, restarted postfix and saslauthd
> but the same error persists,
Time to configure "debug_peer_list" to include the IP address of
the client that is triggering the errors. More may become apparent
f
Hi Viktor,
Thanks for the help!
Postfix is from Ubuntu apt official repo, version is 2.11.
# postconf -d | grep mail_version
mail_version = 2.11.0
I have just tried adding multiple symlinks, restarted postfix and
saslauthd but the same error persists,
# ls -lah /usr/lib/sasl2/smtpd.conf
lrw
Hi chaouche,
I appreciate the quick help, I provided the config files on my very
first email, below is the smtpd.conf file, let me know if you want me to
paste all the config files again,
# cat /etc/postfix/sasl/smtpd.conf
pwcheck_method: saslauthd
mech_list: plain login
auxprop_plugin: rimap
On Thu, Feb 09, 2017 at 12:05:08PM -0300, Nick wrote:
> Hi Chris,
>
> Thank you for the prompt reply, package its already installed.
What Postfix version? Is Postfix from the Debian package, or
your own build?
Upthread you mention /etc/postfix/sasl/smtpd.conf, that would not
be used if your Po
Hi Nick,
I'm curious to know what's inside your /etc/postfix/sasl/smtpd.conf file ?
Hi Chris,
Thank you for the prompt reply, package its already installed.
root@server:~# dpkg --get-selections | grep -i sasl2
libsasl2-2:amd64install
libsasl2-modules:amd64install
libsasl2-modules-db:amd64install
sasl2-bininstall
r
On 2017-02-09 09:09, Nick - ServerBuddies Support wrote:
Hello guys,
For some reason Im unable to send any email from this postfix server,
Im getting the following error:
Feb 9 03:00:35 buf postfix/smtpd[6424]: warning: SASL PLAIN
authentication failed: no mechanism available
For debian in
Hello guys,
For some reason Im unable to send any email from this postfix server, Im
getting the following error:
Feb 9 03:00:35 buf postfix/smtpd[6424]: warning: SASL PLAIN
authentication failed: no mechanism available
No more errors than the one below appears on logs.
Im using rimap for
On 2013-06-10 5:25 PM, Charles Marcus wrote:
On 2013-06-10 4:57 PM, Bogdan Enache wrote:
Hi.
On 09.06.2013 18:12, Charles Marcus wrote:
On 2013-06-09 10:34 AM, Zhang Huangbin
wrote:
On Sunday, June 9, 2013 at 10:09 PM, Charles Marcus wrote:
Dovecot uses login_log_format_elements to determ
On 2013-06-10 4:57 PM, Bogdan Enache wrote:
Hi.
On 09.06.2013 18:12, Charles Marcus wrote:
On 2013-06-09 10:34 AM, Zhang Huangbin wrote:
On Sunday, June 9, 2013 at 10:09 PM, Charles Marcus wrote:
Dovecot uses login_log_format_elements to determine what it logs for
login attempts... you'll f
Hi.
On 09.06.2013 18:12, Charles Marcus wrote:
> On 2013-06-09 10:34 AM, Zhang Huangbin wrote:
>> On Sunday, June 9, 2013 at 10:09 PM, Charles Marcus wrote:
>>> Dovecot uses login_log_format_elements to determine what it logs for
>>> login attempts... you'll find the variables it supports here:
>
On 2013-06-09 10:34 AM, Zhang Huangbin wrote:
On Sunday, June 9, 2013 at 10:09 PM, Charles Marcus wrote:
Dovecot uses login_log_format_elements to determine what it logs for
login attempts... you'll find the variables it supports here:
http://wiki2.dovecot.org/Variables?highlight=%28login_log_
On Sun, 09 Jun 2013 16:44:13 +0300
Bogdan Enache articulated:
> Unfortunately if I try lowering it from 10 to 3 I will receive like 20
> phone calls a day about users that don't know how to check when CAPS
> LOCK is on or off.
20 calls from 20,000 users would be insignificant. From 100 users, a
t
On Sunday, June 9, 2013 at 10:09 PM, Charles Marcus wrote:
>
> Dovecot uses login_log_format_elements to determine what it logs for
> login attempts... you'll find the variables it supports here:
>
> http://wiki2.dovecot.org/Variables?highlight=%28login_log_format_elements%29
>
> Mine (which
On 2013-06-08 6:09 AM, Bogdan Enache wrote:
But how can I also show the username that was tried in the logs? I want
to see:
1. Which user keeps entering the wrong password.
2. What user is someone else trying to hijack.
Since you left out the critical fact that you are using dovecot sasl, I
d
Hi list.
On 09.06.2013 03:35, LuKreme wrote:
> On 08 Jun 2013, at 04:09 , Bogdan Enache wrote:
>
>> But how can I also show the username that was tried in the logs? I want
>> to see:
>> 1. Which user keeps entering the wrong password.
>> 2. What user is someone else trying to hijack.
> Are you us
Benny Pedersen:
> Bogdan Enache skrev den 2013-06-08 12:09:
>
> > mx1 postfix/smtpd[1069]: warning: unknown[89.xx.xx.xx]: SASL LOGIN
> > authentication failed: UGFzc3dvcmQ6
> > Which is perfectly normal.
>
> normal in what way ?
>
> i have seen this here aswe
Bogdan Enache skrev den 2013-06-08 12:09:
mx1 postfix/smtpd[1069]: warning: unknown[89.xx.xx.xx]: SASL LOGIN
authentication failed: UGFzc3dvcmQ6
Which is perfectly normal.
normal in what way ?
i have seen this here aswell with that user
But how can I also show the username that was tried in
On 08 Jun 2013, at 04:09 , Bogdan Enache wrote:
> But how can I also show the username that was tried in the logs? I want
> to see:
> 1. Which user keeps entering the wrong password.
> 2. What user is someone else trying to hijack.
Are you using courier authlib?
It has a DEBUG_LOGIN setting wh
Bogdan Enache:
> Hi.
> When an user inputs an incorrect password, I have the following message
> in the logs:
> mx1 postfix/smtpd[1069]: warning: unknown[89.xx.xx.xx]: SASL LOGIN
> authentication failed: UGFzc3dvcmQ6
> Which is perfectly normal.
'UGFzc3dvcmQ6' deco
Hi.
When an user inputs an incorrect password, I have the following message
in the logs:
mx1 postfix/smtpd[1069]: warning: unknown[89.xx.xx.xx]: SASL LOGIN
authentication failed: UGFzc3dvcmQ6
Which is perfectly normal.
But how can I also show the username that was tried in the logs? I want
to see
On Fri, Aug 17, 2012 at 04:20:38PM -0400, Wietse Venema wrote:
> l...@airstreamcomm.net:
> > I am trying to get SASL (with dovecot) setup on postfix 2.6.6
> > and receiving this warning:
> >
> > ?warning: domain.tld[ip.add.re.ss]: SASL LOGIN authentication
> >
On 8/17/12 3:17 PM, Patrick Ben Koetter wrote:
* l...@airstreamcomm.net :
I am trying to get SASL (with dovecot) setup on postfix 2.6.6 and
receiving this warning:
warning: domain.tld[ip.add.re.ss]: SASL LOGIN authentication failed:
Invalid authentication mechanism
The client attempts to use
l...@airstreamcomm.net:
> I am trying to get SASL (with dovecot) setup on postfix 2.6.6 and
> receiving this warning:
>
> ?warning: domain.tld[ip.add.re.ss]: SASL LOGIN authentication failed:
This means that the client sent an "AUTH LOGIN" command, i.e.
a re
* l...@airstreamcomm.net :
> I am trying to get SASL (with dovecot) setup on postfix 2.6.6 and
> receiving this warning:
>
> warning: domain.tld[ip.add.re.ss]: SASL LOGIN authentication failed:
> Invalid authentication mechanism
The client attempts to use a mechanism Postfix
I am trying to get SASL (with dovecot) setup on postfix 2.6.6 and
receiving this warning:
warning: domain.tld[ip.add.re.ss]: SASL LOGIN authentication failed:
Invalid authentication mechanism
There are a number of successful SASL attempts, but a large number of
these warnings are occurring
oded response:
> x postfix/smtpd[1475]: warning: SASL authentication failure:
> All-whitespace username.
> xxxxx postfix/smtpd[1475]: warning: localhost[127.0.0.1]: SASL LOGIN
> authentication failed: generic failure
> x postfix/smtpd[1475]: > localhost[127.0.0.1]: 53
.
x postfix/smtpd[1475]: warning: localhost[127.0.0.1]: SASL LOGIN
authentication failed: generic failure
x postfix/smtpd[1475]: > localhost[127.0.0.1]: 535.5.7.8 Error:
authentication failed: generic failure.
on doing a testsaslauthd :
#testsaslauthd -u mkk@mydomain -p password -f
/
42 matches
Mail list logo
