Problems on mailman3 installation via mailman-bundler
I've been struggling for couple of days to get mailman3 up and running on my Debian Jessie -host. So far I'm in the situation that everything should (more or less) work, I can create lists and receive confirmation emails etc.
However, every post I send to the testing-list I created end up in shunting, from log file I get this:
Sep 29 00:59:34 2015 (21017) Traceback (most recent call last): File "/home/mailman/mailman-bundler/venv-3.4/lib/python3.4/site-packages/mailman/core/runner.py", line 165, in _one_iteration self._process_one_file(msg, msgdata) File "/home/mailman/mailman-bundler/venv-3.4/lib/python3.4/site-packages/mailman/core/runner.py", line 258, in _process_one_file keepqueued = self._dispose(mlist, msg, msgdata) File "/home/mailman/mailman-bundler/venv-3.4/lib/python3.4/site-packages/mailman/runners/incoming.py", line 63, in _dispose process(mlist, msg, msgdata, start_chain) File "/home/mailman/mailman-bundler/venv-3.4/lib/python3.4/site-packages/mailman/core/chains.py", line 86, in process link.function(mlist, msg, msgdata) File "/home/mailman/mailman-bundler/venv-3.4/lib/python3.4/site-packages/mailman/chains/hold.py", line 182, in _process autorespond_to_sender(mlist, msg.sender, language)): File "/home/mailman/mailman-bundler/venv-3.4/lib/python3.4/site-packages/mailman/chains/hold.py", line 83, in autorespond_to_sender address = user_manager.create_address(sender) File "/home/mailman/mailman-bundler/venv-3.4/lib/python3.4/site-packages/mailman/database/transaction.py", line 92, in wrapper return function(args[0], config.db.store, *args[1:], **kws) File "/home/mailman/mailman-bundler/venv-3.4/lib/python3.4/site-packages/mailman/model/usermanager.py", line 110, in create_address address = Address(email, display_name) File "<string>", line 4, in __init__ File "/home/mailman/mailman-bundler/venv-3.4/lib/python3.4/site-packages/sqlalchemy/orm/state.py", line 306, in _initialize_instance manager.dispatch.init_failure(self, args, kwargs) File "/home/mailman/mailman-bundler/venv-3.4/lib/python3.4/site-packages/sqlalchemy/util/langhelpers.py", line 60, in __exit__ compat.reraise(exc_type, exc_value, exc_tb) File "/home/mailman/mailman-bundler/venv-3.4/lib/python3.4/site-packages/sqlalchemy/util/compat.py", line 182, in reraise raise value File "/home/mailman/mailman-bundler/venv-3.4/lib/python3.4/site-packages/sqlalchemy/orm/state.py", line 303, in _initialize_instance return manager.original_init(*mixed[1:], **kwargs) File "/home/mailman/mailman-bundler/venv-3.4/lib/python3.4/site-packages/mailman/model/address.py", line 59, in __init__ getUtility(IEmailValidator).validate(email) File "/home/mailman/mailman-bundler/venv-3.4/lib/python3.4/site-packages/mailman/email/validate.py", line 64, in validate raise InvalidEmailAddressError(email) mailman.interfaces.address.InvalidEmailAddressError
So, apparently something is wrong with member addresses? Since I'm dealing with fresh installation there's only two of my own addresses, both valid (checked via bin/mailman members mylist@example.com)
Additionally, for some reason my debug.log is empty. I couldn't find any reference from documentation nor from sample configuration files on how to switch debugging on, is there documentation about mailman.cfg and options I can (or should) have there?
-- Take
On 09/28/2015 03:31 PM, Take wrote:
I've been struggling for couple of days to get mailman3 up and running on my Debian Jessie -host. So far I'm in the situation that everything should (more or less) work, I can create lists and receive confirmation emails etc.
However, every post I send to the testing-list I created end up in shunting, from log file I get this:
Sep 29 00:59:34 2015 (21017) Traceback (most recent call last): File "/home/mailman/mailman-bundler/venv-3.4/lib/python3.4/site-packages/mailman/core/runner.py", line 165, in _one_iteration self._process_one_file(msg, msgdata) File "/home/mailman/mailman-bundler/venv-3.4/lib/python3.4/site-packages/mailman/core/runner.py", line 258, in _process_one_file keepqueued = self._dispose(mlist, msg, msgdata) File "/home/mailman/mailman-bundler/venv-3.4/lib/python3.4/site-packages/mailman/runners/incoming.py", line 63, in _dispose process(mlist, msg, msgdata, start_chain) File "/home/mailman/mailman-bundler/venv-3.4/lib/python3.4/site-packages/mailman/core/chains.py", line 86, in process link.function(mlist, msg, msgdata) File "/home/mailman/mailman-bundler/venv-3.4/lib/python3.4/site-packages/mailman/chains/hold.py", line 182, in _process autorespond_to_sender(mlist, msg.sender, language)): File "/home/mailman/mailman-bundler/venv-3.4/lib/python3.4/site-packages/mailman/chains/hold.py", line 83, in autorespond_to_sender address = user_manager.create_address(sender) ... File "/home/mailman/mailman-bundler/venv-3.4/lib/python3.4/site-packages/mailman/email/validate.py", line 64, in validate raise InvalidEmailAddressError(email) mailman.interfaces.address.InvalidEmailAddressError
So, apparently something is wrong with member addresses? Since I'm dealing with fresh installation there's only two of my own addresses, both valid (checked via bin/mailman members mylist@example.com)
No. The address which is the problem is the sender address of the post that is being held. Mailman is attempting to notify the poster that her post is being held for moderation and the poster's address appears to be invalid. This is normally the address in the From: header of the post, but can be another address depending on the message itself and the [mailman] -> sender_headers configuration.
Additionally, for some reason my debug.log is empty. I couldn't find any reference from documentation nor from sample configuration files on how to switch debugging on, is there documentation about mailman.cfg and options I can (or should) have there?
The debug information is the traceback from the 'error' log which you post above. I'm not completely sure about MM 3, but in MM 2.1 in order to write anything to a debug log, you actually have to insert the logging calls in the code.
Questions about Mailman 3 are better posted to the mailman-developers@python.org list <http://mail.python.org/mailman/listinfo/mailman-developers>. Please join that list if you are not already a member and post there.
-- Mark Sapiro <mark@msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan
On 09/29/2015 08:28 PM, Mark Sapiro wrote:
No. The address which is the problem is the sender address of the post that is being held. Mailman is attempting to notify the poster that her post is being held for moderation and the poster's address appears to be invalid. This is normally the address in the From: header of the post, but can be another address depending on the message itself and the [mailman] -> sender_headers configuration.
I'll verify this again, however I'm suspecting that this is a some sort of bug in mailman configuration, since the domain I'm using for testing is dedicated to mailman and (as far as I can understand) mailman should take care of it's own email addresses automatically.
I tried to browse trough the code, but I'm not that competent with python that I could see any problems immediately. However I'll try to debug this problem further now since I have atleast some clue about where to look from.
The debug information is the traceback from the 'error' log which you post above. I'm not completely sure about MM 3, but in MM 2.1 in order to write anything to a debug log, you actually have to insert the logging calls in the code.
As I browsed trough the code I saw calls to function log.debug(), which suggested to me that there should be atleast something on the debug log, but since the documentation (atleast the ones I have found) for mailman3 are shallow at best I couldn't confirm if there's any configuration options to specifically enable debugging.
Questions about Mailman 3 are better posted to the mailman-developers@python.org list <http://mail.python.org/mailman/listinfo/mailman-developers>. Please join that list if you are not already a member and post there.
I assumed that user-list is for stable releases, which mailman3 has been for couple of months now, but I'll subscribe to developers list as well and post results from my debugging to there. Thank you for your time, I really appreciate it.
-- Take
On 10/01/2015 11:39 AM, Take wrote:
On 09/29/2015 08:28 PM, Mark Sapiro wrote:
No. The address which is the problem is the sender address of the post that is being held. Mailman is attempting to notify the poster that her post is being held for moderation and the poster's address appears to be invalid. This is normally the address in the From: header of the post, but can be another address depending on the message itself and the [mailman] -> sender_headers configuration.
I'll verify this again, however I'm suspecting that this is a some sort of bug in mailman configuration, since the domain I'm using for testing is dedicated to mailman and (as far as I can understand) mailman should take care of it's own email addresses automatically.
The email address of the sender of the post doesn't pass the test in mailman/email/validate.py. This means it contains a space or begins with a '-' or contains or a non-printable ascii character or an ascii printable character in the set
][()<>|;^,
It also must be a fully qualified address with at least one '.' in the domain.
As I browsed trough the code I saw calls to function log.debug(), which suggested to me that there should be atleast something on the debug log, but since the documentation (atleast the ones I have found) for mailman3 are shallow at best I couldn't confirm if there's any configuration options to specifically enable debugging.
log.debug() will write a 'debug' level log message to the log file which is defined in the 'log' instance.
For example, just to pick one, the module mailman/mta/connection.py contains
log = logging.getLogger('mailman.smtp')
and a few calls to log.debug(). In this case, all those calls will write to the 'smtp' log with level = debug
Questions about Mailman 3 are better posted to the mailman-developers@python.org list <http://mail.python.org/mailman/listinfo/mailman-developers>. Please join that list if you are not already a member and post there.
I assumed that user-list is for stable releases, which mailman3 has been for couple of months now, but I'll subscribe to developers list as well and post results from my debugging to there. Thank you for your time, I really appreciate it.
We are trying to get there. We will have a mailman3-users@mailman3.org list running under Mailman 3, but we're not quite there yet. In the mean time mailman-developers@python.org is the best place for Mailman 3 issues.
-- Mark Sapiro <mark@msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan
On 10/01/2015 10:22 PM, Mark Sapiro wrote:
The email address of the sender of the post doesn't pass the test in mailman/email/validate.py. This means it contains a space or begins with a '-' or contains or a non-printable ascii character or an ascii printable character in the set
][()<>|;^,
It also must be a fully qualified address with at least one '.' in the domain.
I added some logging (and posted details to dev-list) as well, apparently the part raising exception is:
if not self.is_valid(email): raise InvalidEmailAddressError(email)
However, the variable 'email' is empty, which obviously doesn't qualify as an valid email address. I haven't yet got further about why the variable doesn't contain anything.
-- Take
participants (2)
-
Mark Sapiro -
Take