# 이메일로 답장 기능이 작동하지 않음 (각 구성 요소가 정상인지 확인했지만...)
**URL:** https://meta.discourse.org/t/reply-by-email-not-working-but-im-able-to-verify-each-component-is-working-as-it-should/177551
**Category:** Support
**Created:** [1월 28, 2021, 2:55오후 UTC](https://meta.discourse.org/t/reply-by-email-not-working-but-im-able-to-verify-each-component-is-working-as-it-should/177551 "2021-01-28T14:55:44Z")
**Posts on this page:** 1
**Page:** 1
### Author:  [@jacklenox](https://meta.discourse.org/u/jacklenox)
#### Post date: [1월 28, 2021, 2:55오후 UTC](https://meta.discourse.org/t/reply-by-email-not-working-but-im-able-to-verify-each-component-is-working-as-it-should/177551/1 "2021-01-28T14:55:44Z")
안녕하세요 여러분, 이 게시판 여기저기 둘러보았지만 저와 같은 문제를 겪고 있는 사람을 찾지 못했습니다. 정말 머리가 지끈거릴 지경입니다.
현재 제 환경은 다음과 같습니다:
- VPS에 Mail-in-a-Box 설치
- 다른 VPS에 Discourse 설치
두 가지는 모두 정상적으로 작동하고 있습니다. **그런데** , 이메일로 답장(reply-by-email) 기능이 어떻게 설정해도 작동하지 않습니다.
POP3 폴링을 사용 중이며, Discourse 로그와 Mail-in-a-Box 로그를 확인해 보니 Discourse가 POP3로 로그인하는 것은 성공적으로 이루어지고 있습니다. 또한 Mail-in-a-Box 자체에 로그인하여 이메일 답장이 Discourse에 의해 수집되기를 기다리고 있는 것을 확인할 수도 있습니다. 하지만 문제는 Discourse가 POP3로 인증을 한 후, 이메일 답장을 감지하지 못하고 바로 로그아웃한다는 점입니다.
제 `reply by email address`는 다음과 같이 설정되어 있습니다: `reply+%{reply_key}@fiftyshadesof.green`
제 `alternative reply by email addresses`는 다음과 같이 설정되어 있습니다: `jack+%{reply_key}@fiftyshadesof.green`
`reply@`를 `jack@`의 별칭(alias)으로 설정해 두었는데, 이메일 헤더를 보니 이메일이 후자(`jack@`)로 처리되는 것 같습니다. 아래는 이메일 헤더입니다:
```plaintext
Return-Path:
Delivered-To: jack+583cabd428af27911245150bb3679039@fiftyshadesof.green
Received: from b ****** h ([127.0.0.1])
by ********** with LMTP id 8L3WEQDCEmAEsAAAOOEQUQ
for ; Thu, 28 Jan 2021 13:54:08 +0000
X-Spam-Checker-Version: SpamAssassin 3.4.2 (2018-09-13) on ******
X-Spam-Level:
X-Spam-Status: No, score=0.6 required=5.0 tests=DKIM_SIGNED,DKIM_VALID,
DKIM_VALID_AU,FREEMAIL_FROM,HTML_IMAGE_ONLY_28,HTML_MESSAGE,
RCVD_IN_DNSWL_NONE,RCVD_IN_MSPIKE_H2,SPF_HELO_NONE autolearn=no
autolearn_force=no version=3.4.2
X-Spam-Report:
* -0.0 RCVD_IN_MSPIKE_H2 RBL: Average reputation (+2)
* [209.85.222.175 listed in wl.mailspike.net]
* 0.0 SPF_HELO_NONE SPF: HELO does not publish an SPF Record
* 0.0 FREEMAIL_FROM Sender email is commonly abused enduser mail
* provider (j **** m)
* 0.7 HTML_IMAGE_ONLY_28 BODY: HTML: images with 2400-2800 bytes of
* words
* 0.0 HTML_MESSAGE BODY: HTML included in message
* 0.1 DKIM_SIGNED Message has a DKIM or DK signature, not necessarily
* valid
* -0.1 DKIM_VALID_AU Message has a valid DKIM or DK signature from
* author's domain
* -0.1 DKIM_VALID Message has at least one valid DKIM or DK signature
* -0.0 RCVD_IN_DNSWL_NONE RBL: Sender listed at
* https://www.dnswl.org/, no trust
* [209.85.222.175 listed in list.dnswl.org]
X-Spam-Score: 0.6
Received: from mail-qk1-f175.google.com (mail-qk1-f175.google.com [209.85.222.175])
(using TLSv1.3 with cipher TLS_AES_128_GCM_SHA256 (128/128 bits))
(No client certificate requested)
by ************ (Postfix) with ESMTPS id 10B91A6ACC
for ; Thu, 28 Jan 2021 13:54:07 +0000 (GMT)
Authentication-Results: ***********; dmarc=pass (p=none dis=none) header.from=****.com
Authentication-Results: *********** ;
dkim=pass (2048-bit key; unprotected) header.d= ****.com header.i=@****.com header.b="aU1Sdycv";
dkim-atps=neutral
Received: by mail-qk1-f175.google.com with SMTP id x81so5267064qkb.0
for ; Thu, 28 Jan 2021 05:54:07 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;
d= ****.com; s=20161025;
h=mime-version:references:in-reply-to:from:date:message-id:subject:to;
bh=illVjQUsMQXKmF7F7Mv1ysXAw5aKA0qiK8o4tLS6BMQ=;
b=aU1SdycvYshTO1kKUFq9r3xR0UJrSOh4Met+wcwqEaK7EWb26bJwbMpa850USAmKjY
CajKe2iyRobMDtYg9I7zQVKh1i3cqnc8ve1/hSFnEPW/Nc6zapWJn72fdhsPQGyiBASq
Y5gAIqL6Sz6SaaPAB2i4zcx5I+6jJq/m/mC8o9IxJ3W0YExxQlHc6l+JZR6EqACPccXi
m53fB9qFCsSU1fmS6VgVE+LegvFozjsMeHjTJ3qzjeHyK82NG3UJSmMzDuyad7yJOBYT
4wa13+2ERPlRdPASY/dmWQB6+nCQTQhRhXCNMpzUdOFZTPnVdauj+QpcPGQnnvYHl90w
bBtg==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;
d=1e100.net; s=20161025;
h=x-gm-message-state:mime-version:references:in-reply-to:from:date
:message-id:subject:to;
bh=illVjQUsMQXKmF7F7Mv1ysXAw5aKA0qiK8o4tLS6BMQ=;
b=udoaf8sLd7IeXLppi0FCOTvqdg8fQkCdLsH4EFwxQSTa9fjax1P1/1yIBexxRHi/zw
dSpY+/8L/v+VHN9RDw4q9jn3Xx6hqxFzfSLJcEXMoQ6eyVzbCYKNVUNcNPAZ2/hqgqu8
8XZ5PpYCVUxcsmqSKYcWcbA0JHqGKcJbvTKCugrqeuqByOESSEBzKQS7+xxpFw02yPA4
1TEyW020NBXVHTVy8eSkGTPpHuK4Q159/ewyXx3aLNDGwCruwXXfh32uO48QA+vsU6m9
c0oXiGgAdsodj3+dOOmxAiSqa+wlei7xV1YFQ79uorjb+kZXlFu5jGUrVq7BlL3PeB+j
hn8g==
X-Gm-Message-State: AOAM5332+AyWKnsgCEaYCAgVNKrukhC2+1N032dkVYgN6xcAuJYYTyyQ
7VWcl/WGEEwNN+BKozjToIRQ+cN836UNAl8TFwDzJpbCOq4=
X-Google-Smtp-Source: ABdhPJwKf65r23SSJmH5DRfIi1VOU4fLExuZ/hO/9EBZMDXrK5m6gYotkBSCDvrI3zTNTumMa6CWFULLQ2eqnIeWDFA=
X-Received: by 2002:a37:4590:: with SMTP id s138mr15675696qka.239.1611842046913;
Thu, 28 Jan 2021 05:54:06 -0800 (PST)
MIME-Version: 1.0
References:
In-Reply-To:
From: Jack Lenox
Date: Thu, 28 Jan 2021 13:53:55 +0000
Message-ID:
Subject: =?UTF-8?Q?Re=3A_=5BFifty_Shades_of_Green_=E2=80=93_Test_Discourse=5D_=5BSamp?=
=?UTF-8?Q?le_Category=5D_I_wonder_if_I=27ll_be_able_to_reply_to_the_emails?=
=?UTF-8?Q?_sent_from_this_one?=
To: =?UTF-8?Q?Fifty_Shades_of_Green_=E2=80=93_Test_Discourse?=
Content-Type: multipart/alternative; boundary="000000000000a3f5e605b9f63853"
```
개인정보 보호를 위해 일부 내용을 마스킹 처리했지만, 현재는 테스트용 서버에 불과합니다.
`find related post with key` 옵션의 체크를 해제해 보았지만, 어느 쪽도 작동하지 않습니다.
도움 주시면 감사하겠습니다!