# Discourse/mail-receiver:release Docker 이미지가 오래된 것으로 보입니다
**URL:** https://meta.discourse.org/t/discourse-mail-receiver-release-docker-image-appears-to-be-outdated/411734
**Category:** Bug
**Tags:** mail-receiver
**Created:** [9월 6, 2026, 4:30오전 UTC](https://meta.discourse.org/t/discourse-mail-receiver-release-docker-image-appears-to-be-outdated/411734 "2026-09-06T04:30:12Z")
**Posts on this page:** 1
**Showing post:** 3
### Author:  [@Ethsim2](https://meta.discourse.org/u/Ethsim2)
#### Post date: [9월 6, 2026, 7:01오전 UTC](https://meta.discourse.org/t/discourse-mail-receiver-release-docker-image-appears-to-be-outdated/411734/3 "2026-09-06T07:01:50Z")
#mail-receiver의 다른 변경 사항에서 오래된 릴리스 이미지를 확인할 수 있습니다.
8월 11일에 병합된 이 PR을 열었습니다:
>
>
> \## What does this change?
>
> Updates mail-receiver to send incoming MIME messages …using the
> \`email\_encoded\` parameter expected by Discourse's \`/admin/email/handle\_mail\`
> endpoint.
>
> The message is encoded with \`Base64.strict\_encode64\` before being added to
> the form data.
>
> This removes use of the deprecated raw \`email\` parameter.
>
> \## Why?
>
> Discourse currently logs a deprecation notice for every incoming email sent
> by mail-receiver:
>
> \> the email parameter is deprecated. all POST requests to this route should
> \> be sent with a base64 strict encoded email\_encoded parameter instead
>
> A freshly rebuilt \`discourse/mail-receiver:release\` still reproduces the
> warning because the current mail-receiver code continues to send \`email\`.
>
> \## Tests
>
> Adds regression coverage which verifies that:
>
> \- the deprecated \`email\` parameter is not sent
> \- \`email\_encoded\` is sent
> \- the encoded value represents the original MIME message
>
> Tested locally with Ruby 3.2.11:
>
> \- \`bundle exec rake test\` — 16 examples, 0 failures
> \- \`bundle exec rubocop\` — no offenses
> \- \`bundle exec stree check ...\` — all files matched expected format
>
> This is related to #13, which proposed the same API migration in 2023.
> This PR refreshes that change against current \`main\` and adds regression
> coverage.
이 PR은 메일 리시버를 다음과 같이 변경합니다:
`post.set_form_data(email: @mail)`
Discourse에서 기대하는 새로운 `email_encoded` 매개변수로 변경됩니다.
PR이 병합된 후 8월 17일에 mail-receiver를 다시 빌드했지만, 새로 빌드된 컨테이너에는 여전히 다음 코드가 포함되어 있었습니다:
`post.set_form_data(email: @mail)`
병합된 PR에 세부 정보를 여기에 추가했습니다:
>
>
> Thanks again for merging this.
>
> I rebuilt \`mail-receiver\` again today (17 August…), but the published
> \`discourse/mail-receiver:release\` image still appears to contain the old
> implementation.
>
> The rebuild reports the \`release\` image as up to date, and checking the
> freshly rebuilt running container gives:
>
> \`\`\`text
> \# docker exec mail-receiver \\
> grep -n -E 'base64|set\_form\_data' \\
> /usr/local/lib/site\_ruby/mail\_receiver/discourse\_mail\_receiver.rb
>
> 40: post.set\_form\_data(email: @mail)
>
>
> \`\`\`
> A newly received email therefore still produces the \`email parameter is
> deprecated\` warning in Discourse.
>
> Since #37 is merged into \`main\`, does the
> \`discourse/mail-receiver:release\` Docker image need to be rebuilt/published
> separately for this change to reach normal self-hosted installations?
8월 22일에 다시 빌드했으며 `./launcher rebuild mail-receiver` 명령은 게시된 릴리스 이미지가 최신 상태라고 보고했고, 다이제스트는 다음과 같았습니다:
`sha256:2a0d45bb92a783c846a821e635413764eeadb3441ef6190085545a4bf054cb1e`
제 설치 환경에서는 수신 메일이 여전히 정상 작동하지만, 수신된 각 메일은 게시된 이미지에 병합된 [#37](https://github.com/discourse/mail-receiver/pull/37) 변경 사항이 포함되어 있지 않기 때문에 Discourse의 다음 경고를 계속 트리거합니다:
`the email parameter is deprecated`
따라서 이는 여러분이 발견한 첫 번째 문제를 독립적으로 확인하는 것으로 보입니다: #mail-receiver 저장소에 병합된 변경 사항이 게시된 `discourse/mail-receiver:release` 이미지에 반영되지 않고 있습니다.
---
_[View the full topic](https://meta.discourse.org/t/discourse-mail-receiver-release-docker-image-appears-to-be-outdated/411734)._