Response$\N} } \
{ match {$h_Subject:} {\N^ezmlm warning$\N} } \
{ match {$h_X-FC-MachineGenerated:} {true} } \
{ match {$h_X-Spam-Flag:} {\N^yes\N} } \
{ match {$message_body} {\N^Your \"cron\" job on\N} } \
{ match {$h_Subject:} {\N^Out of Office\N} } \
{ match {$h_Subject:
My experience shows that when things go wrong there is usually an amplified
feedback loop between your mail server and the remote, so ensure that any
header you set is one that you drop too.
This is also why the mighty no-reply@ was thought up, which simply drops
all mail. It might be crude, but i
On 4/11/2014 2:16 AM, Tei wrote:
So
Suppose I configure my email to send a "Thanks, we have received your
email, we will reply shortly in office hours.". Whats the Holy Headers
so even poorly configured servers don't cause a AutoReply Storm?
Googling, I found "Precedence", "X-Auto-Response-S
So
Suppose I configure my email to send a "Thanks, we have received your
email, we will reply shortly in office hours.". Whats the Holy Headers
so even poorly configured servers don't cause a AutoReply Storm?
Googling, I found "Precedence", "X-Auto-Response-Suppress",..? For
something like
solution is the complete
eradication of the software (a lot of which makes mistakes that have
been well-known as mistakes for decades) and thus the entire practice
of setting up "out of office" messages.
[relevant discussion]
But I think by now everyone who is capable of being educated has b
I am out of the office until 30.11.2009.
Na Vas e-mail odpovim co nejdrive. V pripade urgentnich problemu prosim
kontaktujte helpdesk.
I will answer your e-mail as soon as possible. Your e-mail will not be
forwarded. Please contact helpdesk for urgent issues.
Dekuji za pochopení
Lumir Srch ml.
I will be out of the office from May 31 - June 4 attending the
NANOG conference in NYC with limited access to email. For urgent
issues, please contact Dwight Ernest ([EMAIL PROTECTED]).
7 matches
Mail list logo
