Greetings, Noel Jones! Thank you for the reply, Noel. I'm not seeing my own message sent to the list, is this normal?
>> At this moment, I have a working prototype of our organization's mail server, >> but I'm lacking some final touches on it, and would like to have some advice. >> >> The server suite consists of >> >> postfix >> dovecot >> PAM auth >> OpenLDAP backend behind that one. >> amavisd-new with it's own suite of troubles >> >> The server is supposed to host 3 mail domains (one internal, two real >> internet >> domains) for the same set of users. (Means, users have same mailboxes in both >> internet domains and should be able to receive internal mail as well.) >> >> So far, the simple functionality is in place, but I'm lacking some precise >> features that I've been so far unable to implement. >> >> The most important feature is a blind carbon copying of all incoming and >> outgoing mail into separate mailboxes (incoming - to archive-in, outgoing - >> to >> archive-out). I've tried to use BCC mappings, but they are too selective for >> the task at hands, and are processed too late in the chain, as I've realized. >> It is somewhat sufficient for outgoing mail, but by no means enough for >> incoming. Could probably utilize amavis for this task, since it is the first >> to process all incoming mail, but the amavis-users list is dead and doesn't >> help. > amavis-new is the right tool for archiving, since it has that > built-in. Maybe as easy as uncommenting the $clean_archive_method > setting, but see the amavis-users list for details. > Are you using the right mail list amavis-us...@amavis.org? It's > pretty active. Yes, I suppose. I see your empty message arrived not long ago. > There may be some other dead lists floating around that were > associated with long-dead projects with similar names. >> The other feature is the so-called common mailboxes, such as info@ or sales@. >> I would like to have different delivery lists for same named common mailbox >> in >> each of the two internet domains. I've found vague reference to the >> possibility of utilizing LDAP directly to this extent, and I'm reading >> http://www.postfix.org/LDAP_README.html to see if I can get it working, but >> any quick hints are greatly appreciated. > Look at the dovecot shared mailbox feature. Um. I'll see about it, but from the name of it, this doesn't sound like the feature I need. I don't need a _shared_ mailbox (else I could just connect the specified mailbox to users' clients. Trivial task considering IMAP usage). >> The last, but not least feature I'm struggling to implement is the dealing >> with retired employees. >> When an employee retire, if their account was part of the common business >> process (managers commonly fall into this category), their account is not >> immediately retired, but password-locked and any mail coming to it needs to >> be >> auto-replied with redirection statement for a period of time, before all >> access to the specified account is forever restricted. >> I could easily hack together an auto-reply bot, but I seems to be unable to >> prevent delivery to the existing mailboxes of disabled users. > The postfix "relocated" feature is specifically for this. > http://www.postfix.org/postconf.5.html#relocated_maps It seems it may help me with mail redirection, but doesn't answer the question of delivery prevention. Quick search of the list turned up a suggestion that I could somehow use dovecot to check if the user is available for delivery, but I've found no further information on that yet. The task is to prevent the use of retired addresses without constant change of postfix configuration. Not to keep them in use. -- WBR, Andrey Repin (anrdae...@freemail.ru) 14.03.2014, <01:35> Sorry for my terrible english...
