To extend my previous message :
I added the option '-o lmtp_destination_recipient_limit=1' to Postfix
and try again to send a message to someone outside my domains, but
adding two people in CC.
It seems that Dovecot is still handling the delivery incorrectly. Here
is the transcript of what
Hi,
I'm wondering what is the correct architecture and configuration to
setup a multilayer mail handling? What I have in mind is something
more like what we can found in Web platform architectures.
1. First layer does first checks: user authentication and SSL
offloading. If all checks are OK
Le 26 mai 2014 à 10:01, Stanislas SABATIER a écrit :
To extend my previous message :
I added the option '-o lmtp_destination_recipient_limit=1' to Postfix
and try again to send a message to someone outside my domains, but
adding two people in CC.
It seems that Dovecot is still handling
You're right, Postfix is still passing the two CC recipients in one
LMTP process. I didn't find how to force Postfix to send emails one by
one… Still digging…
Anyway, I believe the way Dovecot is handling this case is not the
right way.
Le Mon May 26 10:48:32 2014, Axel Luttgens a écrit :
Le
Am 26.05.2014 10:54, schrieb Stanislas SABATIER:
You're right, Postfix is still passing the two CC recipients in one
LMTP process. I didn't find how to force Postfix to send emails one by
one
lmtp_destination_recipient_limit = 1
lmtp_destination_concurrency_limit = 1
signature.asc
Le 26 mai 2014 à 10:54, Stanislas SABATIER a écrit :
You're right, Postfix is still passing the two CC recipients in one
LMTP process. I didn't find how to force Postfix to send emails one by
one… Still digging…
Anyway, I believe the way Dovecot is handling this case is not the
right way.
On -10.01.-28163 20:59, Reindl Harald wrote:
Am 25.05.2014 01:18, schrieb Jochen Bern:
Legal requirements like, for example, these German ones:
http://www.recht-im-internet.de/themen/archivierung.htm
Note that the legalese addresses users acting in the name of a company,
Am 26.05.2014 13:01, schrieb Jochen Bern:
On -10.01.-28163 20:59, Reindl Harald wrote:
Am 25.05.2014 01:18, schrieb Jochen Bern:
Legal requirements like, for example, these German ones:
http://www.recht-im-internet.de/themen/archivierung.htm
Note that the legalese addresses users acting
Le 26/05/2014 12:29, Reindl Harald a écrit :
lmtp_destination_recipient_limit = 1
lmtp_destination_concurrency_limit = 1
I tried to put both settings to main.cf and within master.cf under my
'dovecotfeed' service, but Postfix is still using one process to CC the
email to my recipients… Even
Am 26.05.2014 13:53, schrieb Stanislas SABATIER:
Le 26/05/2014 12:29, Reindl Harald a écrit :
lmtp_destination_recipient_limit = 1
lmtp_destination_concurrency_limit = 1
I tried to put both settings to main.cf and within master.cf under my
'dovecotfeed' service, but Postfix is still using
Le 26/05/2014 12:19, Axel Luttgens a écrit :
Now, from you Postfix setup description, you define dovecotfeed as a
unix service:
dovecotfeed unix - - n - 2 lmtp
-o lmtp_send_xforward_command=yes
-o lmtp_tls_security_level=may
but the virtual_transport seems
Hello,
I have all userdata in a ldapserver. Every user has the right to use pop3.
There is no explicit attribute allowing that. It's simply possible.
Now I like to add imap. For a starting period I like to restrict, who
may use imap.
http://wiki2.dovecot.org/Authentication/RestrictAccess
Am Montag, 26. Mai 2014, 13:24:35 schrieben Sie:
Hello,
I have all userdata in a ldapserver. Every user has the right to use pop3.
There is no explicit attribute allowing that. It's simply possible.
Now I like to add imap. For a starting period I like to restrict, who
may use imap.
Am Dienstag, 20. Mai 2014, 14:00:11 schrieben Sie:
Hi,
since migration to Dovecot 2.2 I have troubles with lazy_expunge as soon
as a user shares a folder. The user the folder is shared to cannot login
anymore, dovecot logs Fatal: lazy_expunge: Unknown namespace:
'.EXPUNGED/'
- When no
On 5/24/2014 8:00 AM, Subscriptions llsub...@zudiewiener.com wrote:
Made the changes, so entries in 10-master.conf are now:
--
service auth {
unix_listener auth-userdb {
#mode = 0666
#user =
#group =
}
# Postfix smtp-auth
unix_listener
Florian:
Why not add the attribute to all your users?
yeah, that would be really the simplest solution. Unfortunately the world
is sometimes more complex. That's why I search for other ways...
- multiple dovecot installations
- different ldap filters based on imap or pop3
- other magic
On 2014-05-26 16:39, Andreas Schulze wrote:
Florian:
Why not add the attribute to all your users?
yeah, that would be really the simplest solution. Unfortunately the
world
is sometimes more complex. That's why I search for other ways...
- multiple dovecot installations
- different ldap
Hi,
We have just recently switched from Courier to Dovecot for both IMAAP
and POP access for our shared hosting platform, and while the issues we
have been seeing with Courier have gone away a new one has popped up.
Unfortunately googling for an answer is difficult as it falls into the
We recently upgraded from Dovecot 1.2.15 (on Debian squeeze) to Dovecot
2.1.7 (on Debian wheezy/stable).
For now, we continue to use FTS with Squat indexes. We'd like to
eventually switch to Lucene but it's not yet supported in Debian stable.
Since upgrading to 2.1.7, we've seen some problems
On 5/26/14, 6:06 PM, dclist.h...@hook.net.nz wrote:
It would be great if someone can give us some hints where the problem
maybe as this has us stumped.
Have you tried stat dovecot-uidlist after it's changed to look at all
three times of the file?
The Change time is probably more interesting
Hi,
in my current setup, LDAP authentication + userdb works fine.
I'd like to integrate Dovecot with Shibboleth. I have a custom module at
the IdP (*) that inserts short-time tokens to an SQL table at user
authentication, and I want Dovecot to use the token table for passdb but
keep LDAP for
21 matches
Mail list logo
