Last modified: 2014-05-13 16:06:41 UTC

Wikimedia Bugzilla is closed!

Wikimedia migrated from Bugzilla to Phabricator. Bug reports are handled in Wikimedia Phabricator.
This static website is read-only and for historical purposes. It is not possible to log in and except for displaying bug reports and their history, links might be broken. See T65702, the corresponding Phabricator task for complete and up-to-date bug report information.
Bug 63702 - jmail bounces with 4.4.7 Message delayed
jmail bounces with 4.4.7 Message delayed
Status: RESOLVED FIXED
Product: Wikimedia Labs
Classification: Unclassified
tools (Other open bugs)
unspecified
All All
: Unprioritized major
: ---
Assigned To: Tim Landscheidt
:
Depends on:
Blocks: 58796
  Show dependency treegraph
 
Reported: 2014-04-08 21:24 UTC by Tim Landscheidt
Modified: 2014-05-13 16:06 UTC (History)
11 users (show)

See Also:
Web browser: ---
Mobile Platform: ---
Assignee Huggle Beta Tester: ---


Attachments

Description Tim Landscheidt 2014-04-08 21:24:32 UTC
+++ This bug was initially created as a clone of bug #58796, comment #14 +++

(In reply to Marc A. Pelletier from bug #58796, comment #13)
> This is now working, as documented at:
> 
> https://wikitech.wikimedia.org/wiki/Nova_Resource:Tools/Help#Email

It tried it yesterday by setting up ~/.forward.subster containing:
|jmail cat > ~/data/subster/mail_inbox_test

This does not seam to work - if I try to send a mail to drtrigonbot.subster@tools.wmflabs.org I do not receive the mail but it bounces with following error:
Diagnostic-Code: smtp;400 4.4.7 Message delayed

Is the mail server running? What am I doing wrong?
Comment 1 DrTrigon 2014-04-09 20:37:35 UTC
The same for drtrigonbot.maintainers@tools.wmflabs.org which should work out of the box, right?
Comment 2 jeremyb 2014-04-12 15:55:56 UTC
reverted your priority/severity fields.

AFAICT, no other user has said it also doesn't work for them.

Given the recent comment bug 58796 comment #18, it does work for someone.

(In reply to Tim Landscheidt from bug 58796 comment #18)
> But despite (!) this, using "|jmail cat > /data/project/wikilint/mailbox" as

Should be >>? (append)
Comment 3 DrTrigon 2014-04-13 18:02:57 UTC
(In reply to jeremyb from comment #2)
> reverted your priority/severity fields.
> 
> AFAICT, no other user has said it also doesn't work for them.

Just because nobody else is using this feature like me does not mean it's ok. Especially as it is supposed to be a replacement for toolserver - and there it works perfectly (and even simpler).

> Given the recent comment bug 58796 comment #18, it does work for someone.
> 
> (In reply to Tim Landscheidt from bug 58796 comment #18)
> > But despite (!) this, using "|jmail cat > /data/project/wikilint/mailbox" as
> 
> Should be >>? (append)

Might be, but is not the crucial point here at the moment - I would be very happy if at least something would arrive. But I assume (I don't know) it fails already before...

Tim: What does work for you? Could you describe your setting and use case to me, please?
Comment 4 Tim Landscheidt 2014-04-13 18:19:10 UTC
(In reply to DrTrigon from comment #3)
> [...]

> Tim: What does work for you? Could you describe your setting and use case to
> me, please?

What I wrote in bug #58796, comment #18:

| [...]                 using "|jmail cat > /data/project/wikilint/mailbox" as
| /data/project/wikilint/.forward.subster perfectly stores incoming mail to
| wikilint.subster@tools.wmflabs.org at the specified location [...]
Comment 5 Tim Landscheidt 2014-04-13 18:20:34 UTC
I don't see any jobs for the mailq queue for tools.drtrigonbot in /var/lib/gridengine/default/common/accounting, but for tools.wikilint, so apparently the job doesn't get launched in the first place.
Comment 6 Tim Landscheidt 2014-04-13 18:30:30 UTC
/var/log/exim4/rejectlog on tools-mail contained:

| 2014-04-13 18:22:00 H=mo4-p00-ob.smtp.rzone.de [81.169.146.162] F=<tim@tim-landscheidt.de> temporarily rejected RCPT <drtrigonbot.subster@tools.wmflabs.org>: failed to open /data/project/drtrigonbot/.forward.subster: Permission denied (euid=107 egid=110)

So I "chmod o+r ~tools.drtrigonbot/.forward.subster", and my next test mail was correctly written to ~tools.drtrigonbot/data/subster/mail_inbox_test.

I documented that at https://wikitech.wikimedia.org/w/index.php?title=Nova_Resource:Tools/Help&diff=109536&oldid=108815.
Comment 7 DrTrigon 2014-04-13 19:48:28 UTC
(In reply to Tim Landscheidt from comment #6)
> /var/log/exim4/rejectlog on tools-mail contained:
> 
> | 2014-04-13 18:22:00 H=mo4-p00-ob.smtp.rzone.de [81.169.146.162]
> F=<tim@tim-landscheidt.de> temporarily rejected RCPT
> <drtrigonbot.subster@tools.wmflabs.org>: failed to open
> /data/project/drtrigonbot/.forward.subster: Permission denied (euid=107
> egid=110)
> 
> So I "chmod o+r ~tools.drtrigonbot/.forward.subster", and my next test mail
> was correctly written to ~tools.drtrigonbot/data/subster/mail_inbox_test.

Aaaahh I see, now that makes sense to me - was what I somewhat initially assumed to be the problem... its always about the permissions...! :)) Thanks a lot!!! :)

The strange thing now is why it was NOT deliverd to the mail address specified in '~/.forward'? And also not bunced with an error message? But instead was not able to be delivered and ended up being delayed? The same for drtrigonbot.maintainers@tools.wmflabs.org mentioned in comment 1.
Comment 8 Tim Landscheidt 2014-05-12 22:00:12 UTC
(In reply to DrTrigon from comment #7)
> [...]

> The strange thing now is why it was NOT deliverd to the mail address
> specified in '~/.forward'? And also not bunced with an error message? But
> instead was not able to be delivered and ended up being delayed? The same
> for drtrigonbot.maintainers@tools.wmflabs.org mentioned in comment 1.

The same thing (mail being stuck in the queue) happened previously when ~/.forward had wrong permissions and is thus apparently a design choice by the Exim developers.  It makes some sense because otherwise mail to a user with an improper ~/.forward would be misrouted to for example local storage with no indication to the user about that, while the "we'll keep trying" approach shows up at least in the mail queue and thus potentially in the admins' eyes.

Note You need to log in before you can comment on or make changes to this bug.


Navigation
Links