[ILUG] Sync-ing kmail on desktop and laptop

[Brendan Kehoe]

> As I said in another posting,
> if you could tell me exactly what happens to a single item of email
> in your scenario, I may understand what is meant to happen.

When mail arrives to zen.org (running Debian 3.1 sarge),
   - postfix gets it once it's past the many checks done by the main.cf
entries

    smtpd_client_restrictions = check_client_access hash:/etc/postfix/access
    smtpd_sender_restrictions = check_sender_access
    hash:/etc/postfix/access_sender
    ## Steps from http://www.akadia.com/services/postfix_spamassassin.html
    smtpd_recipient_restrictions = permit_sasl_authenticated,
    permit_mynetworks,
      reject_unauth_destination,
      reject_unauth_pipelining,
      reject_invalid_hostname,
      reject_non_fqdn_hostname,
      reject_non_fqdn_sender,
      reject_non_fqdn_recipient,
      reject_unknown_sender_domain,
      reject_unknown_recipient_domain,
      check_policy_service inet:127.0.0.1:60000,
      permit
    # Steps from http://www.postfix.org/spam.html
    ## and http://www.howtoforge.com/virtual_postfix_antispam
    smtpd_helo_required = yes
    ## And from http://www.unixwiz.net/techtips/postfix-HELO.html we got
    this:
    smtpd_delay_reject = yes
    smtpd_helo_restrictions = permit_mynetworks,
                            regexp:/etc/postfix/helo.regexp,
                            check_helo_access hash:/etc/postfix/access_helo,
                            permit
    ## Steps from http://www.akadia.com/services/postfix_spamassassin.html
    # Take a LONG time:
    #    reject_unknown_sender_domain,
    #    reject_unknown_recipient_domain,
    strict_rfc821_envelopes = yes
    disable_vrfy_command = yes
    ## And from http://www.howtoforge.com/virtual_postfix_antispam
    unknown_address_reject_code  = 554
    unknown_hostname_reject_code = 554
    unknown_client_reject_code   = 554

   - The check_policy_service line is using postgrey as described at

    http://www.debuntu.org/postfix-and-postgrey-a-proactive-approach-to-spam-filtering

     which has drastically reduced our spam traffic.
   - postfix, once it gets the message with actual final delivery, feeds
it into amavisd-new via
      content_filter = amavis:[127.0.0.1]:10024
   in its main.cf and the configuration in /etc/amavis/amavisd.conf
   - if it passes unscathed, postfix drops it in my ~/Maildir as per
        # we need this for courier-imap to do things properly
        home_mailbox = Maildir/
        mailbox_command =
   in its main.cf
  - when I connect to the 'imaps' port 993 with my email client
(thunderbird, mutt, kmail) or if I connect to the 'imap2' port 143 on
127.0.0.1 with either the Roundcube or Horde+IMP webmail interface,
    the courier-imap daemon looks in ~/Maildir because of
        MAILDIRPATH=Maildir
    in /etc/courier/imapd.
  - The list of folders, and messages in the main INBOX folder, goes to
the client.  The mail as I ask for it is transferred, or some clients
may like to cache it locally---it makes no difference to the server.  It
just supplies the message when asked, deletes it when asked, provides
the current list of messages when asked, says if there's new mail when
asked, etc etc.

When I want to look at the mail folders on my desktop at home (running
OpenSUSE 10.2),
  - courier-imap & courer-authlib installed partly based on what's at
        http://www.howtoforge.com/perfect_setup_suse_10.1_p4
  - Mail client (wherever I happen to be) connects to a local
ssh-forwarded port like 127.0.0.1 port 1143, which connects to port 143
of my desktop machine

Feel free to ping for more detail.

Hope this helps,
B