NC 30 - Warning: "itinerary file doesn't exist"

ℹ️ Support
1

I upgraded to NC 30.0.1 and now I see the following warning in my logs

{
  "reqId": "jZT8UZ9deiUgrZsOKegm",
  "level": 2,
  "time": "2024-10-27T08:47:03+00:00",
  "remoteAddr": "",
  "user": "--",
  "app": "mail",
  "method": "",
  "url": "--",
  "message": "itinerary file doesn't exist",
  "userAgent": "--",
  "version": "30.0.1.2",
  "data": {
    "app": "mail"
  },
  "id": "671e0870639db"
}

What does trigger this warning? How to I solve it?

There is only one other thread which mentions this warning. However, the author of that thread had problems to get mail to work at all and the warning was merely a side remark. I have a working mail setup and no other mail-related problems. In my case the warning is the only disturbance.

2

@nagmat84, the mail app is a recommended app and is installed “automatically” upon first start. if it hasn’t been set up correctly this warning appears.

3

Please re-read my post:

I am using the mail app since the beginning and it is set up. It rather seems that something has changed between NC 29 and NC 30 which was not handled by the upgrade itself. So, what has changed and how do I fixed that issue?

4

It seems that this error was related to a wrong values for trusted_domains in config.php. Since I have corrected those, the error hasn’t appeared again.

5

I’m getting the same error in the log but seemingly only after a Mail App update. I had a look in the trusted domains and it looks OK but perhaps not? Here’s a redacted copy of that section:

‘trusted_domains’ =>
array (
0 => ‘localhost’,
1 => ‘nextcloud.example.com’,
2 => ‘1xx.1xx.1xx.xx’,

The little data in there is correct but I notice an URL reference in the full redacted log error message below - perhaps add that??

{
“reqId”: “IQixxxxxxxxxxxxxxxxxxzw”,
“level”: 2,
“time”: “2024-11-30T11:17:50+00:00”,
“remoteAddr”: “2xx.1xx.xx.2xx”,
“user”: “NigelNext”,
“app”: “mail”,
“method”: “GET”,
“url”: “/settings/apps/update/mail”,
“message”: “itinerary file doesn’t exist”,
“userAgent”: “Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:133.0) Gecko/20100101 Firefox/133.0”,
“version”: “30.0.2.2”,
“data”: {
“app”: “mail”
},
“id”: “674xxxxxxx68”
}

6

Fresh-installed Nextcloud 30.0.2.2 with all recommended extensions/apps.

At config/config.php I have:

'mail_smtpmode' => 'smtp',
'mail_smtphost' => 'localhost',
'mail_smtpport' => 25,
'mail_from_address' => 'nextcloud',
'mail_domain' => 'dav.MyDomain.net',

I go to Administration → Basic settings and press on “Send email”.
Inspediately there appears text in red highlight “A problem occurred while sending the email. Please revise your settings. (Error: Email could not be sent. Check your mail server log)”
No e-mail is sent and Log reader says:

  • Level: Warning
  • Application: mail
  • Message: itinerary file doesn’t exist

Mail server log does not contain any try to send an e-mail, then has no record about any sending/warning/error. CLI “mail” command works perfectly from console.

7

I’ve tested by editing file apps/mail/lib/Migration/MakeItineraryExtractorExecutable.php
and replaced line:
$this->logger->warning('itinerary file doesn\'t exist');
by:
$this->logger->warning('itinerary file doesn\'t exist: '.$this->file);

Then Log reader shows a more concrete message:
itinerary file doesn’t exist: /srv/www/dav.MyDomain.net/apps/mail/lib/Migration/…/…/vendor/christophwurst/kitinerary-bin/bin/kitinerary-extractor

I see that referred file really does not exist:
apps/mail/lib/Migration/…/…/vendor/christophwurst/kitinerary-bin/bin/kitinerary-extractor
but a different path yes, that exist located as:
apps/mail/lib/Migration/…/…/vendor/nextcloud/kitinerary-bin/bin/kitinerary-extractor
It seems a bug in “mail” application/extension files definition.

8

Hello @narcisgarcia,

may I ask you to create an issue in the corresponding github repo GitHub - nextcloud/mail: 💌 Mail app for Nextcloud?

I would suggest to reference directly to the maintainer https://github.com/ChristophWurst

Hopefully he can work arround that anoying hardcoded path.

smf

1 Like
9

This topic was automatically closed 90 days after the last reply. New replies are no longer allowed.