ClearOS Bug Tracker


View Issue Details Jump to Notes ] Issue History ] Print ]
IDProjectCategoryView StatusDate SubmittedLast Update
0002158ClearOSapp-smtp - SMTP Serverpublic2015-01-27 12:412020-11-12 04:46
Reporterbchambers 
Assigned To 
PrioritynormalSeverityminorReproducibilityhave not tried
StatusclosedResolutionsuspended 
PlatformOSOS Version
Product Version 
Target VersionFixed in Version 
Summary0002158: Does local_recipient_maps work with AD connector
DescriptionUsers using Postfix/Cyrus + AD connector first saw 'invalid recipient' with default settings. Prevents mail from being delivered.

Setting local_recipient_maps to nothing allowed (confirm req'd) delivery to occur.

Does Postfix need to talk back to AD?

https://www.howtoforge.com/postfix-dovecot-authentication-against-active-directory-on-centos-5.x [^]

Working AD / ClearOS environment needed
TagsNo tags attached.
Attached Files

- Relationships

-  Notes
(0001349)
user2
2015-01-27 13:28

By default Postfix/IMAP + AD does not quite work in ClearOS. Here are the necessary changes to get it going. In /etc/postfix/main.cf, change the following parameters:

  virtual_alias_maps = $alias_maps, $virtual_maps
  local_recipient_maps = proxy:unix:passwd.byname $alias_maps $virtual_alias_maps

The file should be "chattr-ed" since the ClearOS IMAP server won't like seeing virtual_alias_maps in that state. Normally, that line looks like:

  virtual_alias_maps = $alias_maps, $virtual_maps, ldap:/etc/postfix/imap-aliases.cf, ldap:/etc/postfix/imap-groups.cf

Translation: Postfix is doing direct LDAP lookups for mail aliases and group distribution lists (e.g. sales -> dave, cindy, mike).

Normally, local_recipient_maps looks like:

  local_recipient_maps = $alias_maps $virtual_alias_maps

By adding "proxy:unix:passwd.byname" (the default), Postfix will do a standard Posix/getent lookup, and that's fine in AD mode.
(0015081)
NickH (developer)
2020-11-12 04:46

Migrated to https://gitlab.com/clearos/clearfoundation/app-smtp/-/issues/14 [^]

- Issue History
Date Modified Username Field Change
2015-01-27 12:41 bchambers New Issue
2015-01-27 13:28 user2 Note Added: 0001349
2015-01-27 13:29 user2 Assigned To => user2
2015-01-27 13:29 user2 Status new => confirmed
2018-12-14 12:11 user2 Status confirmed => assigned
2018-12-14 12:11 user2 Assigned To user2 => tracker
2020-11-12 04:46 NickH Note Added: 0015081
2020-11-12 04:46 NickH Status assigned => closed
2020-11-12 04:46 NickH Assigned To tracker =>
2020-11-12 04:46 NickH Resolution open => suspended