From db8567e5035978dc16fd5bbac9aecb73b600d41e Mon Sep 17 00:00:00 2001 From: "Kali Kaneko (leap communications)" Date: Fri, 21 Oct 2016 17:10:49 -0400 Subject: [bug] capture the exception value properly this looks like a careless migration to twisted failures. who knows how long this was like this, this should be covered by tests. --- src/leap/bitmask/mail/outgoing/service.py | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) (limited to 'src/leap/bitmask/mail/outgoing') diff --git a/src/leap/bitmask/mail/outgoing/service.py b/src/leap/bitmask/mail/outgoing/service.py index accb9e5d..416b8bfe 100644 --- a/src/leap/bitmask/mail/outgoing/service.py +++ b/src/leap/bitmask/mail/outgoing/service.py @@ -194,10 +194,10 @@ class OutgoingMail(object): if self._bouncer: self._bouncer.bounce_message( - err.message, to=self._from_address, + failure.getErrorMessage(), to=self._from_address, orig=origmsg) else: - raise err + failure.raiseException() def _route_msg(self, encrypt_and_sign_result, raw): """ -- cgit v1.2.3