Tom Allison wrote: > Well, I'm back online after tossing dovecot for dbmail. The transition > was much easier than I expected except that I had one stupid setting and > lost a ton of email. I'm still alive so I probably won't miss it that > much -- there's a tarball somewhere. > > After sorting through a lot of notes there are a number of things that I > can't seem to get figured out just yet. > > I'm using postfix + dbmail + postgresql with hopes (tomorrow) of setting > up dspam and clam-av. I have clam-av running now but it's an old > version and might not work. I also was using bogofilter but not anymore. > > > postfix: > local_recipient_maps > I added a pgsql-recipients file with a pointer to the dbmail_aliases table > to do the recipient lookups. This doesn't work very well. > > I changed my email address and mapped an alias in dbmail so now anything > that is delivered to my real name isn't seen as an alias. Only email > that is delivered to an alias is seen. > > And I managed to duplicate the aliases table (/etc/aliases.db) with the > dbmail_alias table and that got things badly fuggered. > > Right now I'm running no local_recipient_maps. All my aliases are done > in /etc/alias. I missed a beat on this configuration or am I expected > to add myself as an alias to myself? Seems strange to me.
actually running with an empty local_recipient_maps makes a lot of sense, if you use lmtp delivery. Postfix will pass along everything to dbmail-lmtpd which will do the address resolving; making postfix do hard bounces (550 reject) is an address is not tied to a local recipient. In that scenario, using /etc/aliases is indeed confusing. If you depend on a lot of recursive delivery resolving - rethink! for example, in aliases: root: myuser postmaster: root will deliver all mails to [EMAIL PROTECTED] to local-user myuser. To do something like that in dbmail, you'd have to add an alias like 'postmaster@' to user 'myuser' - however, dbmail doesn't support such wildcard cross-domain aliases! So, you need to add explicit aliases to all users for each address you which to receive mail on. Or, you need to start working out some funky stuff in the sql maps postfix supports. > > dbmail mailing list -- there's another email address out there > 'tallison' that isn't going to be very useful anymore. If someone could > make it go away I would appreciate it. But I can't seem to send email > from that address just yet. Please send mail to [EMAIL PROTECTED] The folks at IC&S control the mailman installation. > > sieve: I was using something under procmail to eliminate duplicate > emails send to me from mailing lists where I was also a To/CC using: > # remove duplicate emails > :0 Wh: msgid.lock > | formail -D 2048 msgid.cache > > This would keep a list of 2048 records of Message-ID's and remove > anything that appears recently. Very handy. Any sieve equals? None that I know of. > > Can someone point to some sieve sites I can RTFM rather than driving > everyone crazy here? The Sieve RFC: http://www.rfc-editor.org/rfc/rfc3028.txt libsieve (and thus dbmail) supports several extensions. These are described in their respective drafts. http://www.ietf.org/html.charters/sieve-charter.html http://libsieve.sf.net http://sieve.info/ -- ________________________________________________________________ Paul Stevens paul at nfg.nl NET FACILITIES GROUP GPG/PGP: 1024D/11F8CD31 The Netherlands________________________________http://www.nfg.nl
