Dear Wallace: where's my mail?

Daniel Hoffend dh at dotlan.net
Mon Sep 1 19:36:10 CEST 2014


Hi Nick

>Can you send me a link to the bug report so I can provide additional 
>info?
sorry, forgot to add the link:
https://issues.kolab.org/show_bug.cgi?id=3554

>I have disabled wallace for now (likely don't need it)
That's fine and up to everybody if they need particular features or not.
and documentation ... well it's a community effort but in this case 
wallace
or at least the modules (resources, itip) using it are pretty new.

>I wasn't sure about dropping the mail back in to the postfix queue as 
>the spool
>files aren't in mbox format. I'll try one and see if postfix chokes on 
>it.
It's a guess. Give it a try.

>Also - thank you for Eve maps :)
You're welcome. Fly safe :-)
Daniel


>On September 1, 2014 16:04:53 Daniel Hoffend wrote:
>>  Hi Nick
>>
>>  I'm not a python expert. I've created a bugzilla ticket for you cause
>>  fatal errors are never a good thing. It looks like postfix 
>>successfully
>>  delivered the mail message to wallace:10026 which stored the message
>>  in its spool folder /var/spool/pykolab/wallace/resources/incoming/
>>  under the filename 'tmpy6zUa0'.
>>
>>  It looks like the wallace deamon has a problem with parsing some
>>  expected
>>  mail headers and then fails.
>>
>>  I guess the kolab developer would be happy if you could provide
>>  additional
>>  informations like the mail headers (from the spool file above). Or if
>>  you
>>  could run the wallace daemon manually with debug enabled
>>
>>  service wallace stop
>>  /usr/sbin/wallaced --user kolab -d9
>>
>>  If you don't need wallace (for handling/booking resources, handling 
>>itip
>>  invites, etc)
>>  you can just savely disable wallance in the content-filter of the
>>  smtp:10025
>>  process in postfix's master.conf.
>>
>>  if you want your stuck messages back (after removing wallace atm) you
>>  can move
>>  them manually out of the spool folder into the spool folder of 
>>postfix
>>  and
>>  use postfix flush or something (maybe do some additional readings 
>>before
>>  injecting mails into the postfix queue).
>>
>>  I know this won't fix your problem but maybe with some additional 
>>help
>>  the kolab guys can easily fix it.
>>
>>
>>  --
>>  Regards
>>  Daniel
>>
>>
>>  ------ Originalnachricht ------
>>  Von: "Nick Wiltshire" <nick at customdesigns.ca>
>>  An: users at lists.kolab.org
>>  Gesendet: 01.09.2014 03:59:39
>>  Betreff: Re: Dear Wallace: where's my mail?
>>
>>  >On August 31, 2014 17:30:27 Nick Wiltshire wrote:
>>  >> I wrote to list earlier today regarding mail not showing up in my
>>  >>
>>  >>inbox.
>>  >>
>>  >> Ironically, I didn't see any replies because of the same issue.
>>  >>
>>  >> I have since figured out that wallace was eating my mail. The new 
>>3.3
>>  >> Postfix config has mail delivered to wallaced on port 10026. This 
>>was
>>  >> happening.
>>  >>
>>  >> Wallace is supposed to then re-inject mail back to postfix on port
>>  >>
>>  >>10027.
>>  >>
>>  >> It was not. Still isn't. So while I can now receive mail by 
>>bypassing
>>  >> wallace, I likely have mail stuck in a wallace queue somewhere (or
>>  >>
>>  >>perhaps
>>  >>
>>  >> it is gone?)
>>  >>
>>  >> Since this daemon seems to be the worst documented piece of 
>>software
>>  >>
>>  >>in the
>>  >>
>>  >> history of man kind, can someone give me a hint of where to start
>>  >>
>>  >>looking?
>>  >>
>>  >> Or is all that mail just gone?
>>  >>
>>  >> The sum of documentation for wallace on the entire internet seems 
>>to
>>  >>
>>  >>be
>>  >>
>>  >> this:
>>  >>
>>  >> "Wallace is a modular daemon responsible for filtering the content
>>  >>
>>  >>passing
>>  >>
>>  >> through it as part of the mail flow between recipients and 
>>senders.
>>  >>
>>  >> While it does not perform anti-spam and anti-virus content 
>>filtering,
>>  >>
>>  >>for
>>  >>
>>  >> which Kolab Groupware uses Amavisd, SpamAssassin and ClamAV, mail
>>  >>
>>  >>submitted
>>  >>
>>  >> through Wallace is handled with specific use-cases for particular
>>  >>
>>  >>mail
>>  >>
>>  >> flows in mind."
>>  >>
>>  >> So I know what it doesn't do, and have a vague idea that it does
>>  >>
>>  >>something.
>>  >>
>>  >> I'm guessing it's not supposed to eat my mail.
>>  >
>>  >Some progress. I found some errors in pykolab.log and corrected 
>>them.
>>  >That
>>  >caused some messages to go through. There are still some errors I am
>>  >unable to
>>  >figure out.
>>  >
>>  >Firstly:
>>  >
>>  >pykolab.conf WARNING Option kolab/domain_sync_interval does not 
>>exist
>>  >in config
>>  >file /etc/kolab/kolab.conf, pulling from defaults
>>  >
>>  >
>>  >Yet, here's my config:
>>  >
>>  >[kolab]
>>  >imap_backend = cyrus-imap
>>  >auth_mechanism = ldap
>>  >primary_domain = customdesigns.ca
>>  >default_locale = en_US
>>  >sync_interval = 300
>>  >domain_sync_interval = 600
>>  >
>>  >
>>  >Then there's this:
>>  >
>>  >
>>  >2014-08-31 19:45:43,569 pykolab.wallace ERROR Module
>>  >resources.execute()
>>  >failed on message
>>  >'/var/spool/pykolab/wallace/resources/incoming/tmpy6zUa0'
>>  >
>>  >with error: Traceback (most recent call last):
>>  > File "/usr/lib/python2.6/site-packages/wallace/__init__.py", line 
>>67,
>>  >
>>  >in
>>  >pickup_message
>>  >
>>  > result_filepath = modules.execute(module, filepath)
>>  >
>>  > File "/usr/lib/python2.6/site-packages/wallace/modules.py", line 
>>116,
>>  >
>>  >in
>>  >execute
>>  >
>>  > return modules[name]['function'](*args, **kw)
>>  >
>>  > File 
>>"/usr/lib/python2.6/site-packages/wallace/module_resources.py",
>>  >
>>  >line
>>  >163, in execute
>>  >
>>  > recipients = [address for displayname,address in
>>  >
>>  >getaddresses(message.get_all('X-Kolab-To'))]
>>  >
>>  > File "/usr/lib64/python2.6/email/utils.py", line 105, in 
>>getaddresses
>>  >
>>  > all = COMMASPACE.join(fieldvalues)
>>  >
>>  >TypeError
>>  >
>>  >
>>  >
>>  >Any help is appreciated!
>>  >_______________________________________________
>>  >users mailing list
>>  >users at lists.kolab.org
>>  >https://lists.kolab.org/mailman/listinfo/users
>
>--
>Nick Wiltshire
>Technical Consultant
>Custom Designs Technology Solutions Inc.
>Registered Hosting & Web Services Inc.
>Office: 403-210-1973
-------------- next part --------------
A non-text attachment was scrubbed...
Name: smime.p7s
Type: application/x-pkcs7-signature
Size: 5714 bytes
Desc: not available
URL: <http://lists.kolab.org/pipermail/users/attachments/20140901/76d93ad0/attachment-0001.bin>


More information about the users mailing list