-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On Wed, 25 Feb 2015, Luca Bertoncello wrote:
Currently I use Dovecot 1.2.9 from Ubuntu repositories.
I'll try to upgrade Dovecot (to 2.2.15), compiling from sources. It seems not
too difficult... :)
Well, I see, that I have to recreate the configur
Hi all!
Currently I use Dovecot 1.2.9 from Ubuntu repositories.
I'll try to upgrade Dovecot (to 2.2.15), compiling from sources. It seems not
too difficult... :)
Well, I see, that I have to recreate the configuration, since the old one
can not be used with Dovecot2, OK, not a problem.
Now: is th
Hi list,
is there a reason why nobody answers an my topics?
Greetings
Christian
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On Tue, 24 Feb 2015, Luciano Mannucci wrote:
On Tue, 24 Feb 2015 18:56:03 +0100
Reindl Harald wrote:
* if you cahnge the pwd SASL auth is taken away
True.
But this way the user will be unable to read his/her mail, including
my message saying "Hey
Am 24.02.2015 um 19:48 schrieb Adrian Minta:
On 24.02.2015 20:40, Reindl Harald wrote:
Am 24.02.2015 um 19:37 schrieb Adrian Minta:
On 24.02.2015 20:29, Reindl Harald wrote:
don't allow senders which you would not receive mail for - period
Seems interesting, at least until the bots adap
On 24.02.2015 20:40, Reindl Harald wrote:
Am 24.02.2015 um 19:37 schrieb Adrian Minta:
On 24.02.2015 20:29, Reindl Harald wrote:
don't allow senders which you would not receive mail for - period
Seems interesting, at least until the bots adapt to this.
Any idea how could this be implemente
Am 24.02.2015 um 19:37 schrieb Adrian Minta:
On 24.02.2015 20:29, Reindl Harald wrote:
don't allow senders which you would not receive mail for - period
Seems interesting, at least until the bots adapt to this.
Any idea how could this be implemented?
with the configuration i have posted i
On 24.02.2015 20:29, Reindl Harald wrote:
don't allow senders which you would not receive mail for - period
Seems interesting, at least until the bots adapt to this.
Any idea how could this be implemented ?
--
Best regards,
Adrian Minta
Am 24.02.2015 um 19:20 schrieb Luciano Mannucci:
On Tue, 24 Feb 2015 19:00:32 +0100
Reindl Harald wrote:
so you allow random envelope senders on your servers?
why?
I know it is not necessarily a good idea... :)
It is basicaly to allow fake home addresses from the office for some
managers.
On Tue, 24 Feb 2015 19:00:32 +0100
Reindl Harald wrote:
> so you allow random envelope senders on your servers?
> why?
I know it is not necessarily a good idea... :)
It is basicaly to allow fake home addresses from the office for some
managers.
Thanks for the smtpd_recipient_restrictions list, i
On Tue, 24 Feb 2015 19:00:09 +0100
Benny Pedersen wrote:
> no, when this happend disable smtp auth, but not login, then send a mail
> why smtp auth is disabled
This way, I'll block everybody, not only the troyan victims.
luciano.
--
/"\ /Via A. Salaino, 7 - 20144 Milan
Am 24.02.2015 um 19:04 schrieb Luciano Mannucci:
On Tue, 24 Feb 2015 18:56:03 +0100
Reindl Harald wrote:
* if you cahnge the pwd SASL auth is taken away
True.
But this way the user will be unable to read his/her mail, including
my message saying "Hey, you've got a new virus!"
if the accoun
On Tue, 24 Feb 2015 18:56:03 +0100
Reindl Harald wrote:
> * if you cahnge the pwd SASL auth is taken away
True.
But this way the user will be unable to read his/her mail, including
my message saying "Hey, you've got a new virus!".
Thanks anyway,
luciano.
--
/"\ /Via A.
Hello,
take a look at postfwd, especially "rate limit examples":
http://postfwd.org/
--
Best regards,
Adrian Minta
Am 24.02.2015 um 18:28 schrieb Luciano Mannucci:
for the virus doesn't necessarily use the e-mail of the
user as its from, just the user and password for the
authentication phase
so you allow random envelope senders on your servers?
why?
smtpd_recipient_restrictions = permit_mynetworks
rejec
On February 24, 2015 6:30:53 PM Luciano Mannucci
wrote:
Is it feasible?
no, when this happend disable smtp auth, but not login, then send a mail
why smtp auth is disabled
The things that occur to me are
1) Ensure that the sender domain is authorized by doing a rule in
main.cf for send_restrictions. Then at least they won't be sending
things with faked from=.
2) Do some work with rate limiting.
http://steam.io/2013/04/01/postfix-rate-limiting/
3) Look at some
Am 24.02.2015 um 18:28 schrieb Luciano Mannucci:
I have a few users that are often hit by a trojan virus that steals
e-mail user and password. Having a very little (if not null) power on
their machines, I need to be able to block the outgoing mail wich is
handled by postfix via dovecot SASL.
Blo
Hello,
I have a few users that are often hit by a trojan virus that steals
e-mail user and password. Having a very little (if not null) power on
their machines, I need to be able to block the outgoing mail wich is
handled by postfix via dovecot SASL.
Blocking it at dovecot level would be optimal,
Hi,
I have been trying to get FTS to work with dovecot.
When I search from my client (roundcube webmail) I am able to get
results for From, To and Subject fields expect Body on my Apache Solr
engine.
Could this be a schema related problem?
This is output for the Subject:
8025 [main] INFO org.ec
Hello,
I am trying to migrate emails
from: Mountain Lion OSX 10.8.5 (dovecot: 2.0.19apple1)
to: RHEL 7.0 (dovecot: 2.2.10)
Using command: dsync -m
/Library/Server/Mail/Data/mail/XYZWXYZW-XYZW-XYZW-XYW-XYZXYZXYZXYZ/ -u
giedriust mirror giedri...@192.168.xx.xx
r...@192.168.xx.xx's password:
dsyn
On Tuesday 24 February 2015 10:51:44 David Scheele wrote:
> Hmm...
>
> *ldapsearch -x cn=admin* gives me:
> | # A bunch of information not really interesting
> | # search result
> | search: 2
> | result: 32 No such object
> |
> | numResponses: 1
>
> *ldapsearch -x cn=admin* gives the same.
> Did
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On Tue, 24 Feb 2015, David Scheele wrote:
Ok I completed the dn as thus:
*dn = cn=admin,dc=luenenet,dc=de*
And now wehn i try* a login Username Password *over *telnet localhost 143* I
get
*a NO [AUTHENTICATIONFAILED] Authentication failed.*
Did you
Ok I completed the dn as thus:
*dn = cn=admin,dc=luenenet,dc=de*
And now wehn i try* a login Username Password *over *telnet localhost 143* I
get
*a NO [AUTHENTICATIONFAILED] Authentication failed.*
I confirmed that the user password is correct.
by the way,* ldapsearch -x -D 'cn=admin,dc=[domainn
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On Tue, 24 Feb 2015, David Scheele wrote:
*ldapsearch -x cn=admin* gives me:
| # A bunch of information not really interesting
| # search result
| search: 2
| result: 32 No such object
|
| numResponses: 1
*ldapsearch -x cn=admin* gives the same.
Hmm...
*ldapsearch -x cn=admin* gives me:
| # A bunch of information not really interesting
| # search result
| search: 2
| result: 32 No such object
|
| numResponses: 1
*ldapsearch -x cn=admin* gives the same.
Did i configure the ldap wrong?
2015-02-24 10:42 GMT+01:00 Steffen Kaiser :
>
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On Tue, 24 Feb 2015, David Scheele wrote:
The ldap-utils were already installed.
I did the ldapsearch you gave me, but after inputting my admin password it
gives me
*ldap_bind: Invalid credentials (49)*
I logged into the ldap server with my admin c
On Tuesday 24 February 2015 10:23:14 David Scheele wrote:
> The ldap-utils were already installed.
> I did the ldapsearch you gave me, but after inputting my admin password it
> gives me
> *ldap_bind: Invalid credentials (49)*
> I logged into the ldap server with my admin credentials (which worked
The ldap-utils were already installed.
I did the ldapsearch you gave me, but after inputting my admin password it
gives me
*ldap_bind: Invalid credentials (49)*
I logged into the ldap server with my admin credentials (which worked fine)
and changed my password to '12345', Trying that, still *Invali
Hi all
Version: 2.2.15
OS: SLES11 SP3 x86_64
Problem with replication for some users:
Log Server 1:
Feb 24 09:29:42 v063ik dovecot: dsync-local(u...@domain.com): Error:
read(v063il.pnet.ch) failed:
Log Server 2:
Feb 24 09:29:42 v063il dovecot: dsync-server(u...@domain.com): Panic: file
../..
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On Tue, 24 Feb 2015, David Scheele wrote:
2015-02-24 8:05 GMT+01:00 Steffen Kaiser :
On Mon, 23 Feb 2015, David Scheele wrote:
So, I set up the Server, installed and configured postfix, ldap and
dovecot
(in that order) and now simply try to log i
@Steffen Kaiser:
Sorry I wrote that wrong. I did indeed *grep -v '^ *\(#.*\)\?$'
dovecot-ldap.conf.ext* to get those results.
@Bob Miller:
And how would that look like? I added a auth_bind_userdn looking like this:
*auth_bind_userdn = uid=%u,dc=[hostname],o=de*
And restartet dovecot, no use.
Any
32 matches
Mail list logo
