Mailman and Spamassassin

Greetings again,
My mail configuration is humming along nicely, but there is a small matter which irks me somewhat. We run a mailing list for our company so that any mail our customers send to our main e-mail address gets bounced to all our personal accounts.
Since out e-mail address is advertised on our website, spam-blocking is a big consideration, so we've set up set of Spamassassin/Bayes rules which greatly cut down on Spam. Naturally, we've also assembled a comprehensive "whitelist_sender" hash file to make sure nothing from our clients ever gets blocked.
When spam does get through, it gets marked in the subject "<Junk> <Junk>". This dual-marking puzzled me at first, but I realized that mail gets scanned once it arrives on our server and then again as the server delivers it to each e-mail on the mailman list. The problem is, I've occasionally seen list e-mails with the spam marking "<junk>" only appear one in the subject line. To further confuse matters, I've seen them appear on e-mails from people who are whitelisted. Why would a different set of rules apply for the mailing list delivery?
A mailing list mails are from "[email protected]". Does Amavis scan the the "From:" field of the e-mail or the "FROM" envelope header? I've considered adding "localhost" to the whitelist_sender file, but I fear that all e-mails would then go unscanned.
Have other people encountered this situation? Any simple solutions?

Depending on the usage of your server....
You could have amavis discard or bounce the messages before they hit Mailman (if you don't mind the same for your non-mailman mail).
If you look in /etc/amavisd.conf, you'll find a kill_level (default of 22), you can set this to a lower number. Some sites, which prefer aggressive anti-spam protection, will set this to the same level as tag2 (also in the config file).
In this way, no spam which hits the threshold is delivered.
Make sure to configure finalspamdestiny to your preference.
Again, this would effect your non-mailman users- so whether this is viable for you- I don't know.
Jeff

Similar Messages

  • Mailman and jes

    i have installed mailman and jes on solaris 10.it's include identity server and communication server.i have created test10 maillist and sent a message to maillist because mail is not delivery.I checked pipe queue.i saw this error "Failed to create shell input (Permission denied)
    ^A^ABoundary_(ID_Aivo6PXmS+eY4mCQSs4+CQ)" . i added mailmanwrapper in program list.How could i solve this problem...
    thanks..
    regards...

    "I used communication express". I have no idea what this might mean, nor how it affects "mailman", "mailmanwrapper" or such.
    Mailman is something you're trying to integrate into the MTA, right? Communi8cation Express is a mail client. Ther'es really no relationship.
    If you're getting errors about permissions, then you need to examine the error carefully, and see what file or directory has wrong ownership or permissions.

  • Group Mail, Mailman and archives

    Im confused. I have a mailman list I want to migrate to Leopard Server. Id like to let the listers have a wiki. Ive set up the group, and the wiki and I see it. (i have other problems with that but ignoring them for the minute)
    Will poste to my mailman list be the mail archive?
    If so can I migrate my old archive somewhere to make sure the old data is still searchable.
    Or, is a mailman list completely separate from a group mailing list.
    Like I said. Im confused.
    If this is all explained somewhere please point me. Ive looked for doc and searched - probably not enough.
    thanks
    Angus

    Hi
    "It seems that group mail introduced in previous Snow Leopard Server, it's gone. There is mailman, but I don't need a mailing list , just a simple mail grooup functionality. It's impossible to do in Lion Server?"
    Actually Group e-mailing was available in previous versions of the Server. It's not impossible to do in Lion Server either. It's just not obvious if you want to use the interface. There's not much documentation regarding this either.
    These two threads (you could have searched this for yourself) should have the information you need:
    https://discussions.apple.com/thread/3518290?start=0&tstart=0
    https://discussions.apple.com/thread/3229060?start=0&tstart=0
    There's also a way of doing this using WorkGroup Manager's Info Tab.
    You should get into the habit of using the command line on OS X Server - the Terminal application in /Applications/Utilities - as this is the most effective way for you to get what you want, especially with the Mail Service.
    The other Server Administration applications (which you may not be aware of?) are available for free download here:
    http://support.apple.com/kb/DL1488
    You will need Server Admin to initially configure the Mail Service properly. As ever remember to set up DNS Services correctly as everything you want or may want will depend on it.
    HTH?
    Tony

  • Another Mailman and virtual domains problem... mailbox does not exist

    Hi,
    this is yet another thread about virtual domain mailinglist with mailman.
    To sum up:
    - OpenDirectory account "[email protected]" -> mail delivered
    - Deleting this account and creating a mailing-list "test11", opening the admin interface to change the host "server.domain.com" (which is the primary host of the machine, so each mailinglist is created with this host) and replacing it with "virtualdomain.com"
    - sending an email to "[email protected]" -> following error:
    Jan 18 14:12:23 server postfix/qmgr[74872]: 698E5BF735: from=<[email protected]>, size=691, nrcpt=1 (queue active)
    Jan 18 14:12:23 server postfix/pipe[74882]: 698E5BF735: to=<[email protected]>, orig_to=<[email protected]>, relay=cyrus, delay=0.28, delays=0.14/0.01/0/0.13, dsn=5.6.0, status=bounced (data format error. Command output: test11: Mailbox does not exist )
    - adding back the OD account "[email protected]" -> mail delivered to inbox (not to mailing-list recipients)
    - now if i delete the mailinglist in Server Admin then send an email to "[email protected]" -> following error (seems obvious):
    Jan 18 13:18:49 server postfix/lmtp[74275]: A9B7CBF45F: to=<[email protected]>, relay=server.domain.com[/var/imap/socket/lmtp], delay=0.16, delays=0.13/0/0/0.03, dsn=5.1.1, status=bounced (host server.domain.com[/var/imap/socket/lmtp] said: 550-Mailbox unknown. Either there is no mailbox associated with this 550-name or you do not have authorization to see it. 550 5.1.1 User unknown (in reply to RCPT TO command))
    IOW, it looks like somehow the mailinglist aliases are being lost somewhere.
    Postfix forgets to delivers the incomming mails to Mailman, doesn't it? According to lots of forum searchs it could be forced by using one of those two commands:
    sudo /usr/sbin/postalias
    sudo /usr/sbin/postmap
    Unfortunately I dont know how they work precisely and can't find X.5 accurate information so I hope you can guide me through this step.
    Also I don't know how to track the incomming mails at the moment they are dispatched to either an OD account (so it's delivered or generates the 550 error) or a Mailman list (so it's looking for aliases and so on).
    Any help will be appreciated.
    Config:
    - in /etc/postfix/main.cf
    virtual_transport = lmtp:unix:/var/imap/socket/lmtp
    virtualmailboxdomains = hash:/etc/postfix/virtual_domains
    alias_maps = hash:/etc/aliases,hash:/var/mailman/data/virtual-mailman
    virtualaliasmaps = hash:/etc/aliases,hash:/var/mailman/data/virtual-mailman
    - in /etc/postfix/virtual_domains
    virtualdomain.com allow
    - in /var/mailman/data/virtual-mailman
    # LOOP ADDRESSES START
    [email protected] mailman-loop
    # LOOP ADDRESSES END
    # STANZA START: test11
    # CREATED: Sun Jan 18 13:55:03 2009
    [email protected] test11
    [email protected] test11-admin
    [email protected] test11-bounces
    [email protected] test11-confirm
    [email protected] test11-join
    [email protected] test11-leave
    [email protected] test11-owner
    [email protected] test11-request
    [email protected] test11-subscribe
    [email protected] test11-unsubscribe
    # STANZA END: test11
    - in /var/mailman/data/aliases
    # The ultimate loop stopper address
    mailman-loop: /private/var/mailman/data/owner-bounces.mbox
    # STANZA START: mailman
    # CREATED: Sun Jan 18 14:11:53 2009
    mailman: "|/usr/share/mailman/mail/mailman post mailman"
    mailman-admin: "|/usr/share/mailman/mail/mailman admin mailman"
    mailman-bounces: "|/usr/share/mailman/mail/mailman bounces mailman"
    mailman-confirm: "|/usr/share/mailman/mail/mailman confirm mailman"
    mailman-join: "|/usr/share/mailman/mail/mailman join mailman"
    mailman-leave: "|/usr/share/mailman/mail/mailman leave mailman"
    mailman-owner: "|/usr/share/mailman/mail/mailman owner mailman"
    mailman-request: "|/usr/share/mailman/mail/mailman request mailman"
    mailman-subscribe: "|/usr/share/mailman/mail/mailman subscribe mailman"
    mailman-unsubscribe: "|/usr/share/mailman/mail/mailman unsubscribe mailman"
    # STANZA END: mailman
    # STANZA START: test11
    # CREATED: Sun Jan 18 14:11:53 2009
    test11: "|/usr/share/mailman/mail/mailman post test11"
    test11-admin: "|/usr/share/mailman/mail/mailman admin test11"
    test11-bounces: "|/usr/share/mailman/mail/mailman bounces test11"
    test11-confirm: "|/usr/share/mailman/mail/mailman confirm test11"
    test11-join: "|/usr/share/mailman/mail/mailman join test11"
    test11-leave: "|/usr/share/mailman/mail/mailman leave test11"
    test11-owner: "|/usr/share/mailman/mail/mailman owner test11"
    test11-request: "|/usr/share/mailman/mail/mailman request test11"
    test11-subscribe: "|/usr/share/mailman/mail/mailman subscribe test11"
    test11-unsubscribe: "|/usr/share/mailman/mail/mailman unsubscribe test11"
    # STANZA END: test11
    - in /usr/share/mailman/Mailman/mm_cfg.py
    MTA = 'Postfix'
    POSTFIXSTYLE_VIRTUALDOMAINS = ['virtualdomain.com','mail.virtualdomain.com']
    add_virtualhost('virtualdomain.com', 'mail.virtualdomain.com')

    I've finaly solved the problem by myself, mixing postfix-style aliases.
    Since it's quite long I wrote a tutorial, it's here:
    http://spip.ashorlivs.net/notepad/os-x/article/virtual-host-mailman-w-os-x-serve r
    Hope it can help someone else.
    Regards,
    g.
    Message was edited by: ashorlivs

  • Setup mailinglist for virtual domain with postfix, mailman and Server Admin

    Hello everybody!
    we have set up a working mailman/postfix configuration for mailing list purposes only on a Tiger Server. What we wanted to do now is to enable another mailinglist for a virtual domain which is hosted (the website) on another Tiger Server in our domain. But everything we tried up to now did lead to a solution. When I send an email to [email protected], the MX of our domain hands the email over to the mailing list server, who seems not to be aware of his obligation to handle that mail. The mailing list server then forwards the mail again to the original MX and so on... It seems like we missed something simple to do in the postfix config.
    Things we tried:
    * hints from http://www.freebsddiary.org/mailman-virtual-domains.php -- no effect
    * hints from http://discussions.apple.com/thread.jspa;jsessionid=aOuiMaZMLAq_Mfqf9S?messageID =1566428 -- no mailing list working anymore
    Any hints would be dearly appreciated!
    Cheers,
    Florian Schneider

    I solved the problem myself after getting a better understanding of the postfix documentation on postfix.org.
    In detail, I added
    to /etc/postfix/virtual:
    [email protected] [email protected]
    to /etc/postfix/main.cf:
    virtualaliasdomains = virtualdomain.com
    virtualaliasmaps = hash:/etc/postfix/virtual
    then I did
    sudo postmap /etc/postfix/virtual
    sudo postfix reload
    and everything worked fine.
    iBook G3   Mac OS X (10.4.6)  

  • SpamAssassin and too much CPU load

    I have been testing my messaging server and SpamAssassin integration. Everything seems fine except too much CPU load coming from spamd (SpamAssassin's daemon). I am testing them on a UltraSparcII-i, 256MB, Solaris 10 box. When I loaded it with 4msg/min containing 50K ascii text each on the receiving side, the spamd process went up to 90% of CPU load, and then just died silently. My questions;
    1) Is there any performance tuning that I should do to avoid that much CPU load? Or is this just normal?
    2) I have heard of another anti-spam product called dspam. How can I integrate dspam with the Java Messaging Server?
    Thanks!

    Installation of JES Messaging Server by itself suggests 1.2 gig of RAM. SpamAssassin adds to that suggestion.
    You have less than 1/4 of the suggested RAM. You're 'way short.
    SpamAssassin will use cpu. I found that nx x86 box was far less expensive to feed, and works extremely well for Messaging and SpamAssassin. 1 gig or ram for my PC costs about $75. Adding ram to your Sparc will cost mor than a PC complete.
    4 messages/min isn't much, but. . .
    You're likely swapping pretty hard. Check for "I/O wait". I often use "top" for a quick look at such.
    When I switched from an "ultra-5" with 384 megs ram, to an AMD 1200+ with 1 gig of ram, my system went from feeling totally buried to feeling mostly un-used. I'm currently able to handle far more than 4 message/minute, with no overload or swapping.

  • 10.5.8 SpamAssassin and FH_DATE_PAST_20XX

    The 10.5.8 standard SpamAssassin is pretty old. It also has a rule (FHDATE_PAST20XX) that tags everything with a date after Jan 1 2010 as 'suspiciously in the future'. First, I tried to change the .cf files that contained this, but that did not work. Then I followed instructions found on the net about updating SpamAssassin on Leopard Server with CPAN, which made a mess of things (parts were installed in /usr/local, parts in /Library/Perl) and SpamAssassin stopped working altogether. Luckily I have a decent CrashPlan backup, so I am now back at square one.
    Question: is there a failsafe way, not using CPAN (I have been burned by CPAN every time I tried to use it) to either update SpamAssassin on Leopard Server to something up to date and working and if not, how do I fix this?
    Thanks,

    This should help:
    http://osx.topicdesk.com/content/view/61/62/
    If you want to bypass installation of dependencies via CPAN, simply download the needed modules and build them the same way SpamAssassin is built in above tutorial.
    HTH,
    Alex

  • Mailman + Postfix - User unknown

    Hi all, I'm having some trouble installing mailman (who doesn't?) right now.
    I tried everything. I followed EXACTLY what is said on our wiki (https://wiki.archlinux.org/index.php/Mailman) but still it's not working.
    Actually the only thing that is not working is 'sending an email to the mailing list'. And this is quite important for a mailing list, I guess.
    After spending hours trying, here is my current status:
    I created a mailing list called pynochio, with [email protected] as the mailing list address.
    Postfix reads my /var/lib/mailman/data/virtual-mailman file and applies the mapping. I'm sure about that because I changed the content of virtual-mailman (and then hashed it using postmap command) and the email postfix was trying to authenticate changed. (so there is no permission issue from this side)
    But then postfix concludes that the user doesn't exist. Here are fresh logs from journalctl, just for you:
    Mar 20 19:59:53 ks3100290 postfix/qmgr[26527]: 128382077C: from=<[email protected]>, size=1775, nrcpt=2 (queue active)
    Mar 20 19:59:53 ks3100290 postfix/trivial-rewrite[26562]: warning: do not list domain too.gy in BOTH mydestination and virtual_mailbox_domains
    Mar 20 19:59:53 ks3100290 postfix/trivial-rewrite[26562]: warning: do not list domain too.gy in BOTH mydestination and virtual_mailbox_domains
    Mar 20 19:59:53 ks3100290 postfix/virtual[26567]: 128382077C: to=<[email protected]>, relay=virtual, delay=0.74, delays=0.65/0.03/0/0.07, dsn=5.1.1, status=bounced (unknown user: "[email protected]")
    Mar 20 19:59:53 ks3100290 postfix/virtual[26567]: 128382077C: to=<[email protected]>, relay=virtual, delay=0.78, delays=0.65/0.03/0/0.1, dsn=2.0.0, status=sent (delivered to maildir)
    This warning appears because in the tutorial we are said to put `too.gy` (our domain) in mydestination and because in my postfix database inside the `domain` table, `too.gy` is said to be virtual (transport=virtual). I don't know if it should be that way.
    My problem is that I don't really know how postfix and mailman are supposed to communicate. Postfix is supposed to let mailman handle things since [email protected] is a list address but it doesn't.
    I read some tutorials (on other distribs) and they are using lists.too.gy domain for their lists address (it seems easier) but it looks like there's a better way to do it and in the archlinux mailman documentation, we are not using such subdomain for our lists. So I want to do it the right, archlinux way.
    There is `postfix_to_mailman.py` transport script thing but I read it's a bad practice...
    Here is the output of `postconf -n` (which respects the mailman tutorial, once again):
    alias_database = $alias_maps
    alias_maps = hash:/etc/postfix/aliases, hash:/var/lib/mailman/data/aliases
    broken_sasl_auth_clients = yes
    command_directory = /usr/bin
    config_directory = /etc/postfix
    daemon_directory = /usr/lib/postfix
    data_directory = /var/lib/postfix
    debug_peer_level = 2
    debugger_command = PATH=/bin:/usr/bin:/usr/local/bin:/usr/X11R6/bin ddd $daemon_directory/$process_name $process_id & sleep 5
    html_directory = no
    inet_protocols = ipv4
    local_recipient_maps = $alias_maps
    local_transport = virtual
    mail_owner = postfix
    mailq_path = /usr/bin/mailq
    manpage_directory = /usr/share/man
    mydestination = localhost, too.gy
    mydomain = too.gy
    myhostname = mail.too.gy
    mynetworks_style = host
    myorigin = $mydomain
    newaliases_path = /usr/bin/newaliases
    queue_directory = /var/spool/postfix
    readme_directory = /usr/share/doc/postfix
    recipient_delimiter = +
    relay_recipient_maps = hash:/var/lib/mailman/data/virtual-mailman
    sample_directory = /etc/postfix/sample
    sendmail_path = /usr/bin/sendmail
    setgid_group = postdrop
    smtpd_recipient_restrictions = permit_mynetworks, permit_sasl_authenticated, reject_unauth_destination
    smtpd_relay_restrictions = permit_mynetworks, permit_sasl_authenticated, reject_unauth_destination
    smtpd_sasl_auth_enable = yes
    smtpd_sasl_local_domain = $mydomain
    smtpd_sasl_path = /var/run/dovecot/auth-client
    smtpd_sasl_security_options = noanonymous
    smtpd_sasl_tls_security_options = $smtpd_sasl_security_options
    smtpd_sasl_type = dovecot
    smtpd_tls_auth_only = yes
    smtpd_tls_cert_file = /etc/ssl/private/server.crt
    smtpd_tls_key_file = /etc/ssl/private/server.key
    smtpd_tls_loglevel = 1
    transport_maps = hash:/etc/postfix/transport
    unknown_local_recipient_reject_code = 550
    virtual_alias_maps = hash:/etc/postfix/virtual, proxy:mysql:/etc/postfix/virtual_alias_maps.cf, hash:/var/lib/mailman/data/virtual-mailman
    virtual_gid_maps = static:5000
    virtual_mailbox_base = /home/vmail
    virtual_mailbox_domains = proxy:mysql:/etc/postfix/virtual_domains_maps.cf
    virtual_mailbox_limit = 512000000
    virtual_mailbox_maps = proxy:mysql:/etc/postfix/virtual_mailbox_maps.cf
    virtual_minimum_uid = 5000
    virtual_transport = virtual
    virtual_uid_maps = static:5000
    Any help appreciated. I'm on it since 10 hours, I don't want to kill myself.
    EDIT: Forgot my `/etc/mailman/mm_cfg.py` >
    # -*- python -*-
    from Defaults import *
    DEFAULT_URL_HOST = 'lists.too.gy'
    DEFAULT_EMAIL_HOST = 'too.gy'
    MTA = 'Postfix'
    VIRTUAL_HOSTS.clear()
    add_virtualhost(DEFAULT_URL_HOST, DEFAULT_EMAIL_HOST)
    POSTFIX_STYLE_VIRTUAL_DOMAINS = ['too.gy']
    DEFAULT_URL_PATTERN = 'http://%s/'
    PUBLIC_ARCHIVE_URL = 'http://%(hostname)s/archives/%(listname)s'
    MAILMAN_SITE_LIST = 'mailman'
    Last edited by toogy (2014-03-20 19:23:23)

    AlanNYC wrote:
    If I turn off local recipient checking, will I actually get my mail?
    Yes, all email properly addressed should be delivered to you without problems.
    The line only affects improperly addressed email, in this case allowing them to be accepted instead of rejected.
    Since you are running Spamassassin and an IMAP server, I suggest also using the line
    luser=[email protected]
    which will send all improperly addressed mail to the address specified by "[email protected]". This is what I meant by "catch-all" address.
    If you find postfix giving you problems after adding the lines, simply delete them or comment them out by adding a hash mark to the front of the line, e.g.
    #localrecipientmaps =
    Alternatively, you can simply make no changes and allow the log messages to accumulate. The messages mean that postfix is doing its job by rejecting email addressed to users that don't exist. The above steps allow you to receive mail addressed to [email protected], where "anything" is any string allowed in an email address.
    I assume you're testing your changes using a separate email account, but in case you're not: sign up for a free email account with any of a number of free email services (Gmail, Yahoo) and test your postfix install as you make changes using the free account.

  • Spamassassin questions

    Now that I have the mail server up and running with mailman and squirrelmail working (mostly) I'm trying SpamAssassin and reading everything I can. One question: I keep seeing reference to the path for SpamAssassin to be in /etc/mail.
    However, when I tried to install it today, my SpamAssassin installed ended up in:
    /users/admin/.cpan/build/Mail-SpamAssassin-3.1.8
    Should I move it? Will it cause a problem?
    Also, I have not installed ClamAV or Amavsid yet, will Spamtrainer still work?
    I want to go slow so I don't muck up the server....
    Thanks.

    I am on 10.3.9.
    I followed the instructions I found on Apple's web site. There was a link on the SpamAssassin Downloads page that pointed to an Apple ADC page.
    I do not have a SpamAssassin folder in /usr/bin, and there is no /usr/local/bin folder.
    However....
    It does seem to be working. I set up the two mailboxes (IMAP) and I've been putting spam into the junkmail account, and when I run spamtrainer on the server, this is the output:
    sudo: /bin/launchctl: command not found
    Learning SPAM...
    su: unknown login: clamav
    su: unknown login: clamav
    su: unknown login: clamav
    su: unknown login: clamav
    su: unknown login: clamav
    su: unknown login: clamav
    su: unknown login: clamav
    su: unknown login: clamav
    su: unknown login: clamav
    su: unknown login: clamav
    su: unknown login: clamav
    su: unknown login: clamav
    su: unknown login: clamav
    su: unknown login: clamav
    su: unknown login: clamav
    su: unknown login: clamav
    su: unknown login: clamav
    su: unknown login: clamav
    su: unknown login: clamav
    su: unknown login: clamav
    su: unknown login: clamav
    su: unknown login: clamav
    su: unknown login: clamav
    su: unknown login: clamav
    su: unknown login: clamav
    su: unknown login: clamav
    Learned new SPAM (junk mail)
    Learning HAM...
    Learned new HAM (not junk mail)
    Syncing SpamAssassin Database
    su: unknown login: clamav
    Displaying SpamAssassin Database Stats
    su: unknown login: clamav
    Done!
    Output produced by spamtrainer Version 1.6.1
    That's why I asked about clamav...
    Any other suggestions - is my install totally FUBARed?
    Thanks.....

  • How do I get new SpamAssassin cf files?

    When spamtrainer runs, I get the following message:
    config: configuration file "//usr/share/spamassassin/20bodytests.cf" requires version 3.000001 of SpamAssassin, but this is code version 3.001005. Maybe you need to use the -C switch, or remove the old config files? Skipping this file at /Library/Perl/5.8.6/Mail/SpamAssassin/Conf/Parser.pm line 344.
    How do I get the new cf files? I never updated SA manually, so all mail service related files should have been updated by SoftwareUpdate. Is it just that the newer version of SA doesn't look in the /usr/share/spamassassin directory anymore?

    Hi Alex,
    I went through my upgrade notes and found an entry back in 2004. I apparently ran the CPAN command for Mail::SpamAssassin on this server by mistake and SpamAssassin was overwritten with v.3.1.5. *spamassassin -V* confirmed it. I wonder why spamtrainer decided to tell me now all of a sudden.
    Anyway, I thought this would be a good time as any to update SpamAssassin... and because of the Perl modules, Amavis. Your notes on Topicdesk was a big help.
    One thing I don't like about the newest Amavis is that the start/stop/reload command is a hassle to type during the install and debug process (I made shortcut executables in ~/bin). I guess now that it's installed and working, I would never have to type those commands again.
    Thanks for your help!

  • Question to Exim mantainer and Exim users

    Good day
    Question to mantainer:
    Now, in 'current' Exim compiled without mysql and postgresql support. And have version 4.64, while current version of Exim is 4.66
    Quite often Exim is used with some database and SpamAssassin uses database for AWL and Bayes, and pop3/imap-server (Dovecot in 'testing' built with database support) uses same as Exim, plus SquirrelMail
    It's not hard to rebuild Exim with abs, but maybe it will useful to have in 'current' Exim with database support?
    And there are libmysqlclient and postgresql-libs alreade present in 'current'.
    Question to Exim users:
    Did you use rebuit Exim with database support or use dbm/passwd?
    If you rebuid Exim with ABS, how you avoid replacing it with new version from repo? Change package name on something like 'exim-custom'?

    Tomk wrote:
    > ..Any optional dependencies that aren't needed to run the package or have it generally function shouldn't be included..
    Full text is:
    > Any optional dependencies that aren't needed to run the package or have it generally function shouldn't be included, but a warning message inside the .install file should echo something like: "To enable SMB support, download the Samba package."
    Maybe I misunderstood term "optional dependencies" due to my lack of english )
    > I'd recommend using IgnorePkg in /etc/pacman.conf - see man pacman for details.
    Thanks for advice!
    P.S.
    It seems that with all this PKGBUILDs i will soon need to maintain my tiny repo
    [/quote]

  • Mailman in OS X Server (10.8)?

    What happened to Mailman and how can I get it's functionality back into OS X Server?

    Mailman has been removed, but it's possible to get it back. Check out this guide:
    http://www.livetime.com/mountain-lion-mailman-mailing-list/

  • Mailman problem

    hello
    recently i am getting an error on my web page as following
    Bug in Mailman version 2.1.5
    We're sorry, we hit a bug!
    If you would like to help us identify the problem, please email a copy of this page to the webmaster for this site with a description of what happened. Thanks!
    Traceback:
    Traceback (most recent call last):
    File "/usr/share/mailman/scripts/driver", line 68, in run_main
    immediate=1)
    File "/usr/share/mailman/Mailman/Logging/StampedLogger.py", line 52, in _init_
    Logger._init_(self, category, nofail, immediate)
    File "/usr/share/mailman/Mailman/Logging/Logger.py", line 49, in _init_
    self._getf()
    File "/usr/share/mailman/Mailman/Logging/Logger.py", line 67, in _getf
    1)
    File "/System/Library/Frameworks/Python.framework/Versions/2.3/lib/python2.3/codecs. py", line 566, in open
    IOError: [Errno 13] Permission denied: '/private/var/mailman/logs/error'
    Can any1 please help me with this..
    Thankyou

    Hmm. This mail seems to be coming from the cron daemon. It tries to "fire up" gate_news which for some reason fails. gate_news is part of mailman and is used to gateway NNTP (news servers) to mailing lists.
    You probably tried to change some configuration options for mailman (through it's webinterface) and activated gate_news. If so, reverse what you did. If not try to remember what you did before the problem started.
    Alex

  • Duplicate Mailman postings, mailman unpickling error in some conditions

    After applying the most recent Security Update to our Mac OS X Server 10.4.10 installation, we are encountering the following two problems:
    1) Each message sent to any of our Mailman-based e-mail lists appears to be sent in duplicate to each member of the list
    2) Under some conditions we encounter an "unpickling error" that from Googling around would appear to be a python error, as follows:
    Aug 03 01:22:25 2007 (7442) Uncaught runner exception: invalid load key, 'm'.
    Aug 03 01:22:25 2007 (7442) Traceback (most recent call last):
    File "/usr/share/mailman/Mailman/Queue/Runner.py", line 111, in _oneloop
    self._onefile(msg, msgdata)
    File "/usr/share/mailman/Mailman/Queue/Runner.py", line 167, in _onefile
    keepqueued = self._dispose(mlist, msg, msgdata)
    File "/usr/share/mailman/Mailman/Queue/IncomingRunner.py", line 130, in _dispose
    more = self._dopipeline(mlist, msg, msgdata, pipeline)
    File "/usr/share/mailman/Mailman/Queue/IncomingRunner.py", line 153, in _dopipeline
    sys.modules[modname].process(mlist, msg, msgdata)
    File "/usr/share/mailman/Mailman/Handlers/Moderate.py", line 109, in process
    Hold.holdforapproval(mlist, msg, msgdata, Hold.NonMemberPost)
    File "/usr/share/mailman/Mailman/Handlers/Hold.py", line 214, in holdforapproval
    id = mlist.HoldMessage(msg, reason, msgdata)
    File "/usr/share/mailman/Mailman/ListAdmin.py", line 178, in HoldMessage
    self.__opendb()
    File "/usr/share/mailman/Mailman/ListAdmin.py", line 80, in __opendb
    self.__db = cPickle.load(fp)
    UnpicklingError: invalid load key, 'm'.
    Aug 03 01:22:25 2007 (7442) SHUNTING: 1186122145.370055+f2ab5fac4a7b2dc159498a36ed5c91b5de42f490
    The condition that produced this particular error involved sending a message to the mailman list on our server.
    Any advice from anyone on either of these two problems? Is it possible that the security update left an old copy of mailman around with a different python, or is this a bug in the copy of mailman that we have in effect after the update?
    We have tried disabling and re-enabling the mailing lists under Server Admin, stopping and starting the Mail service entirely, rebooting, stopping and starting mailman using mailmanctl from the command line, stopping mailman and running the check_db and check-perms commands and then re-enabling it, all to no avail. Help would be much appreciated.

    Are you adding the list via SA or the web interface?

  • Mailman vs Launchd

    I've built and installed Mailman 2.12 from current source code and have it running just fine under OS X Server 10.5.7, with on exception…
    If I start Mailman from the CLI, using +/usr/share/mailman/bin/mailmanctl -s start+, all is well.
    If I allow launchd to start it using the following Launch Daemon…
    +<?xml version="1.0" encoding="UTF-8"?>+
    +<!DOCTYPE plist PUBLIC "-//Apple//DTD PLIST 1.0//EN" "http://www.apple.com/DTDs/PropertyList-1.0.dtd">+
    +<plist version="1.0">+
    <dict>
    + <key>Label</key>+
    + <string>org.list.mailmanctl</string>+
    + <key>OnDemand</key>+
    + <false/>+
    + <key>Program</key>+
    + <string>/usr/share/mailman/bin/mailmanctl</string>+
    + <key>ProgramArguments</key>+
    + <array>+
    + <string>mailmanctl</string>+
    + <string>-s</string>+
    + <string>start</string>+
    + </array>+
    + <key>ServiceIPC</key>+
    + <false/>+
    </dict>
    </plist>
    …I get an endless succession of…
    +Jun 18 16:50:26 org.list.mailmanctl[1697]: Starting Mailman's master qrunner.+
    +Jun 18 16:50:26 com.apple.launchd[1] (org.list.mailmanctl[1697]): Stray process with PGID equal to this dead job: PID 1698 PPID 1 Python+
    +Jun 18 16:50:26 com.apple.launchd[1] (org.list.mailmanctl): Throttling respawn: Will start in 9 seconds+
    …complete with dawn-of-the-dead respawning processes.
    I configured Mailman to replicate OSXS's default locations, and it runs fine. It doesn't even break Server Admin, aside from my use of virtual domains which ServerAdmin of course can't handle.
    The only difference between my org.list.mailmanctl.plist and Apple's is my verb start, as opposed to Apple's startf. I'm baffled by startf, which is not supported by mailman and does nothing, either in the CLI or in org.list.mailmanctl.plist.
    Obviously this isn't fatal and there are even other ways to insure an automatic startup, but I use launchd for such things, Apple more or less deprecates other approaches, and it drives me nuts not to understand what's going on.
    Speak, oh voices of wisdom!
    -Bryan

    +something in the newer version that you absolutely had to have, feature-wise+
    Let's just I have control issues. In general, I find Apple's builds to be lackluster and poorly documented (PHP without GED? What planet are they on? LOL). In this case, I was unable to implement mailman virtual domains with the installed binary.
    +That error sounds like you didn't unload the plist before editing it+
    Thanks for the suggestion, but the problem has survived more loads, unloads, and restarts than I can count.
    Apple's undocumented use of startf apparently works only with Apple's binary. It's not in mailman's usual lexicon, and has no effect on other builds.
    Regards,
    Bryan

Maybe you are looking for