issues with MTA's timestamp

classic Classic list List threaded Threaded
2 messages Options
Reply | Threaded
Open this post in threaded view
|

issues with MTA's timestamp

Wesley Peng-4
Hello,

I found if peer MTA's timestamp is too much different from my end, the
messages may not be displayed.

for example, when you try to sign up to apache projects' mailing list,
like one of this page:

https://flink.apache.org/community.html

The response message's (for user to confirm) timestamp is 12 hours ahead
of me.

Thus some email servers won't display the response messages correctly
(even no response messages appear in the inbox).

At least GMX's mail servers have this issue, as well as web.de. anyone
can test for it.

Can you give some suggestion?

Thanks.:)
Reply | Threaded
Open this post in threaded view
|

Re: issues with MTA's timestamp

Matus UHLAR - fantomas
On 06.09.19 16:56, Wesley Peng wrote:
>I found if peer MTA's timestamp is too much different from my end, the
>messages may not be displayed.

displayed where? postfix is a mail transfer agent, not mail user agent/

>for example, when you try to sign up to apache projects' mailing list,
>like one of this page:
>
>https://flink.apache.org/community.html
>
>The response message's (for user to confirm) timestamp is 12 hours
>ahead of me.

can you show us?
Are you sure4 you didn't forget to compare timezones?

>Thus some email servers won't display the response messages correctly

correctly?

>(even no response messages appear in the inbox).

that may be a spam filter, messages too ahead get some score.
But that's outside of postfix scope.

--
Matus UHLAR - fantomas, [hidden email] ; http://www.fantomas.sk/
Warning: I wish NOT to receive e-mail advertising to this address.
Varovanie: na tuto adresu chcem NEDOSTAVAT akukolvek reklamnu postu.
I'm not interested in your website anymore.
If you need cookies, bake them yourself.