<html>
<head>
<meta http-equiv="Content-Type" content="text/html; charset=utf-8">
</head>
<body text="#000000" bgcolor="#FFFFFF">
Em 06/07/2018 00:10, ellie timoney escreveu:<br>
<blockquote type="cite"
cite="mid:1530846648.828222.1431613808.54159959@webmail.messagingengine.com">
<meta http-equiv="content-type" content="text/html; charset=utf-8">
<title></title>
<style type="text/css">p.MsoNormal,p.MsoNoSpacing{margin:0}</style>
<div>Hi,<br>
</div>
<div><br>
</div>
<div>The "defaultdomain" is the domain that's assumed by Cyrus for
users that are uid only. Any other domain needs to be
explicitly specified in the user (this applies to login,
delivery, etc). So, if you have:<br>
</div>
<div><br>
</div>
<div> defaultdomain: foo.com<br>
</div>
<div><br>
</div>
<div>then "user" and "<a href="mailto:user@foo.com"
moz-do-not-send="true">user@foo.com</a>" are the same account
(and can login using either variation), but "<a
href="mailto:user@bar.com" moz-do-not-send="true">user@bar.com</a>"
is some other account and can only login as "<a
href="mailto:user@bar.com" moz-do-not-send="true">user@bar.com</a>".<br>
</div>
<div><br>
</div>
<div>It's not clear to me how you wish to use the extra domains.
Do you want your existing users to be able to send/receive from
multiple different domains? (e.g. user "anne" has both email
addresses "<a href="mailto:anne@foo.com" moz-do-not-send="true">anne@foo.com</a>",
"<a href="mailto:anne@bar.com" moz-do-not-send="true">anne@bar.com</a>").<br>
</div>
</blockquote>
<br>
We used to have some domains that represented the same mailbox. Like
@cinbesa.com.br being the same as @belem.pa.gov.br.. but now we want
to create some other domains (while *maintaining* those we already
had), which will point to totally different mailboxes, like
@semad.belem.pa.gov.br and @sesma.belem.pa.gov.br :)<br>
<br>
<br>
<blockquote type="cite"
cite="mid:1530846648.828222.1431613808.54159959@webmail.messagingengine.com">
<div><br>
</div>
<div>Or do you want accounts in different domains to be not
related to each other? (e.g. "<a href="mailto:anne@foo.com"
moz-do-not-send="true">anne@foo.com</a>" and "<a
href="mailto:anne@bar.com" moz-do-not-send="true">anne@bar.com</a>"
are <br>
</div>
<div>two totally different accounts)<br>
</div>
<div><br>
</div>
<div>In either case, I would think about having one LDAP attribute
(single-value, unique) to represent a user's "primary" email
address, and a separate LDAP attribute (multi-value, unique) to
represent their "aliases". You would set up Cyrus to only
consider the "primary" attribute, and then set up your SMTP
server to deliver email destined for "alias" addresses to the
"primary" address for the matching account. I believe this is a
common enough configuration that it shouldn't be hard to find
information online. I have managed (non-Cyrus) systems that
worked like this in the past, but it was a long time ago so I
can't offer much specific help.<br>
</div>
</blockquote>
<br>
humm. so the existing "mail" field on ldap would always contain the
@defaultdomain (as setup on cyrus), but another field for aliases
where Postfix would look up?!<br>
<br>
<blockquote type="cite"
cite="mid:1530846648.828222.1431613808.54159959@webmail.messagingengine.com">
<div><br>
</div>
<div>As for autocreate, it is not compiled in by default, it needs
to be turned on at build time with the --enable-autocreate
argument to configure. If you installed Cyrus from a
distribution, your distribution may have done this for you.<br>
</div>
<div><br>
</div>
<div>If you don't want to recompile to remove the feature, you can
control it using the autocreate_* options in imapd.conf (see man
imapd.conf.5). For example you should be able to use
"autocreate_users" to limit it only to certain LDAP groups
rather than every valid login (if that is useful to you).<br>
</div>
<div><br>
</div>
<div>But if you set up your LDAP directory and Cyrus such that
each user only has a single "primary" email address that they
can use in Cyrus, and map delivery to aliases outside of Cyrus,
then people won't be able to login with the "wrong" alias, and
therefore autocreate won't accidentally make new accounts for
them. :)<br>
</div>
<br>
</blockquote>
Right now I think they can login with the "uid" only OR with the
complete mail ("mail" field)<br>
<pre class="moz-signature" cols="72">--
Atenciosamente,
Heiler Bensimon Bemerguy - CINBESA
Analista de Redes, Wi-Fi,
Virtualização e Serviços Internet
(55) 91 98151-4894</pre>
</body>
</html>