Bánhalmi Csaba skrev den 2014-04-12 18:34:
Can you guys help me?
change to use saslauthd with rimap solves it
dont continue with pop-before-smtp since it does NOT take into account
users is mostly using NAT, that means if just one user send a mail via
your server then other users can in sam
On Sat, Apr 12, 2014 at 07:39:22PM -0400, Rick Zeman wrote:
> Apr 11 22:10:15 miniserv.private postfix/smtpd[90054]: SSL_accept
> error from unknown[93.157.46.40]: 0
> Apr 11 22:10:15 miniserv.private postfix/smtpd[90054]: warning: TLS
> library problem: 90054:error:14094416:SSL
> routines:SSL3_RE
On 4/12/2014 11:35 AM, Bánhalmi Csaba wrote:
> Hi All,
>
> I am using pop-before-smtp with postfix 2.9 to authenticate my users
> for years. Now I updated postfix to 2.11 (then I tried with 2.10)
> and pop-before-smtp is not working. Also tried with different
> pop-before-smtp script, but it seems
I'm guessing since I've received a bunch of these over the past few
days that these are Heartbleed scrape attempts, especially since these
IPs belongs to our friends in the former Soviet Union. Agreed? (It's
an Apple server so it uses its own "goto fail" TLS library, and only
has an older version
Viktor:
I re-compiled without TLS:
make makefiles
make
make upgrade
Restarted postfix and send/receive restored (without TLS)
When I use the following command to compile TLS into my postfix build:
make makefiles CCARGS="-DUSE_SASL_AUTH -DUSE_CYRUS_SASL -DUSE_TLS
-I/usr/local/include/sasl -I/u
On Sat, Apr 12, 2014 at 02:39:15PM -0700, Edward Ray wrote:
> Apr 12 14:33:02 portus postfix/smtpd[10743]: initializing the
> server-side TLS engine
> Apr 12 14:33:02 portus postfix/master[10667]: warning: process
> /usr/libexec/postfix/smtpd pid 10743 killed by signal 11
Download and re-install
using this account because my postfix gateway can no longer send or receive
mail.
upgraded from v2.10.1 to v2.10.3 this morning.
Since that time, unable to send or receive mail. If anyone can help me debug
this issue, much appreciated.
Errors seen:
Apr 12 14:33:02 portus postfix/smtpd[10743]:
Am 12.04.2014 22:03, schrieb li...@rhsoft.net:
>
> Am 12.04.2014 21:53, schrieb Robert Schetterer:
>> thx for your info, i was contacted from sombody who is in big trouble by
>> results of this list using a corect but differnt helo then ptr , and
>> warned getting banned from his ip/net by third p
Am 12.04.2014 21:53, schrieb Robert Schetterer:
> thx for your info, i was contacted from sombody who is in big trouble by
> results of this list using a corect but differnt helo then ptr , and
> warned getting banned from his ip/net by third party ignorants
in principals agreed that it is too mu
Am 12.04.2014 21:19, schrieb Bill Cole:
> On 11 Apr 2014, at 11:07, Robert Schetterer wrote:
>
>> Hi , anyone knows this rbl ?
>>
>> http://v4bl.org/about.html
>
> I've had reason to glance at them a few times in the past year but have
> never seen justification to pay ongoing attention...
>
> h
On 11 Apr 2014, at 11:07, Robert Schetterer wrote:
Hi , anyone knows this rbl ?
http://v4bl.org/about.html
I've had reason to glance at them a few times in the past year but have
never seen justification to pay ongoing attention...
http://v4bl.org/results.html was a bit startling when I fi
o...@field.hu:
> I totally agree with you guys, SASL auth is already implemented, BUT...
> there are a couple thousand mailboxes and part of them have weak
> password as it turned out. Spam bots finds out the password and spam the
> world from my server. It never happened with pop-before-smtp (i
Am 12.04.2014 19:44, schrieb o...@field.hu:
> I totally agree with you guys, SASL auth is already implemented, BUT... there
> are a couple thousand mailboxes and
> part of them have weak password as it turned out. Spam bots finds out the
> password and spam the world from my
> server. It never
I totally agree with you guys, SASL auth is already implemented, BUT...
there are a couple thousand mailboxes and part of them have weak
password as it turned out. Spam bots finds out the password and spam the
world from my server. It never happened with pop-before-smtp (imap is
also working wi
Am 12.04.2014 18:34, schrieb Bánhalmi Csaba:
> Hi All,
>
> I am using pop-before-smtp with postfix 2.9 to authenticate my users for
> years. Now I updated postfix to 2.11 (then I tried with 2.10) and
> pop-before-smtp is not working. Also tried with different
> pop-before-smtp script, but it seems
On Sat, Apr 12, 2014 at 06:34:34PM +0200, Bánhalmi Csaba wrote:
> I am using pop-before-smtp with postfix 2.9 to authenticate my
> users for years. Now I updated postfix to 2.11 (then I tried with
> 2.10) and pop-before-smtp is not working. Also tried with different
I am in complete agreement wi
Am 12.04.2014 18:34, schrieb Bánhalmi Csaba:
> I am using pop-before-smtp with postfix 2.9 to authenticate my users for
> years. Now I updated postfix to 2.11 (then
> I tried with 2.10) and pop-before-smtp is not working. Also tried with
> different pop-before-smtp script, but it
> seems postfi
Hi All,
I am using pop-before-smtp with postfix 2.9 to authenticate my users for
years. Now I updated postfix to 2.11 (then I tried with 2.10) and
pop-before-smtp is not working. Also tried with different
pop-before-smtp script, but it seems postfix doesn't take into account
the fact that the
Hi All,
I am using pop-before-smtp with postfix 2.9 to authenticate my users for
years. Now I updated postfix to 2.11 (then I tried with 2.10) and
pop-before-smtp is not working. Also tried with different
pop-before-smtp script, but it seems postfix doesn't take into account
the fact that the
19 matches
Mail list logo