Jeroen Geilman wrote:
On 12/28/10 7:58 AM, Alexander Moisseev wrote:
m...@domain.tld has an alias al...@domain.tld and mail sent to alias.
X-Original-To: al...@domain.tld prepends to the message. It's OK.
If the before-queue content filter enabled as shown below then
X-Original-To: is m
=
-o mynetworks=127.0.0.0/8
-o receive_override_options=no_unknown_recipient_checks
--
Thanks in advance,
Alexander Moisseev
mouss wrote:
if you are talking about your own mail (not customer mail), then
differentiate between outbound (submitted) mail and inbound mail. for
example, use port 587 for outbound mail (ideally enforce SASL/TLS here).
Then for such mail, simply remove all received headers:
/^Received:/
of the yandex servers
--
Alexander Moisseev
ts-dump.cap
Description: Binary data
ya-dump.cap
Description: Binary data
Did you try... oh, I dunno, *asking* yandex ?
They have logs that can tell you what happens; you don't.
Yes, I did.
ya-dump.cap was captured by yandex support. They told to me that have conversation
with mx.tehstroi.ru[81.25.172.91] timed out while sending message body errors. Also
they
