Headers with my domain and public ip xxx’ed out
Received: from BarracudaMail.xxxxx.com (10.10.1.5) by vpalm.xxxxx.com
(10.10.1.28) with Microsoft SMTP Server (TLS) id 14.3.319.2; Fri, 30 Sep 2016
10:09:50 -0400
X-ASG-Debug-ID: 1475244588-0533950cf60ad10001-zynJku
Received: from mail14.ess.barracuda.com (mail14.ess.barracuda.com
[64.235.154.140]) by BarracudaMail.xxxxx.com with ESMTP id E8jfwoCF2XoMjQti
(version=TLSv1.2 cipher=ECDHE-RSA-AES256-GCM-SHA384 bits=256 verify=NO) for
<gmail-smtp2p...@xxxxx.com>; Fri, 30 Sep 2016 10:09:49 -0400 (EDT)
X-Barracuda-Envelope-From: xxxxxincomm...@gmail.com
X-ASG-Whitelist: Sender
X-Barracuda-RBL-Trusted-Forwarder: 64.235.154.140
Received: from mail-qk0-f171.google.com (mail-qk0-f171.google.com
[209.85.220.171]) by mx1433.ess.rzc.cudaops.com (version=TLSv1.2
cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128 verify=NO); Fri, 30 Sep 2016
14:09:47 +0000
Received: by mail-qk0-f171.google.com with SMTP id z190so107533395qkc.3
for <gmail-smtp2p...@xxxxx.com>; Fri, 30 Sep 2016 07:09:47 -0700 (PDT)
X-Barracuda-Effective-Source-IP: mail-qk0-f171.google.com[209.85.220.171]
X-Barracuda-Apparent-Source-IP: 209.85.220.171
X-Barracuda-RBL-IP: 209.85.220.171
X-Barracuda-BBL-IP: 209.85.220.171
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;
d=gmail.com; s=20120113;
h=date:to:from:subject:message-id;
bh=Y/V7WkIq7e6HtwpR/uDCP0nVn98Kgd6sLnbBUWVbBgo=;
b=lJPLICxj5Utt2m4935dsxEu/VrdSfZ6ucjv69sj4cVc4Fg4Xz7I6xGuodpGKN/4Spu
qWE7F0YTUJBojI+g1qJRzoAcxvG9p8WQm2oqEE+G0jqihEtcAg1BEZWyvK/YNgghATtY
ZdK7qSwcnQgJXUf2idGYdXLyGXxXZdodZCSzwTqTnmgHWAOHmVyD8yfi/Bna81BzSSe+
EuZhFPAHR7AJQ9b1Lus3iKqBbYcJ49182VomKelJ31mNqYofT6FN+7rJHLUpzd9tJOXb
Bpji1Ww/3pEXHgDfkyWxFRTJz0oC9Je+dRRe5uNG3ogzwG/XdZcGvEeZbmGCh9hHua4U
cnVg==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;
d=1e100.net; s=20130820;
h=x-gm-message-state:date:to:from:subject:message-id;
bh=Y/V7WkIq7e6HtwpR/uDCP0nVn98Kgd6sLnbBUWVbBgo=;
b=D2EZ+sZLp0RqSKk1Bm22Z9vQ5fPyDoPXhQvuWT4dXFI+7o3lVvbkGfba3VcdO+flBV
86/6O5pMmdu4zYCPugy7LFuuRlMIfhXSNyQ2tZDnHSS7ssI1SIwJdBdXCOiussxdAjEa
am1mbbeOxw7HViFHCLnvw/X2Rx3SFAXIF5nXfmJFTYXdPYKARBowfhA67s3bseT3x8OH
ALiO5toDEEqlw+YK4h9IqrBLJ4LcIDsMmKzyXV2YFvGjCPh53sjBlzjmdcXzVxtvDvFB
KuRv/fXrxZIc42ZNYjMkhvQuTyp7Xa8BLO1lr94mLiTh/eq3eolJPZ0kec/SzPYkrCen
mdKg==
X-Gm-Message-State:
AA6/9RkfOPOH26MqGzQylc0fHsSxZG8JqpUQY2C0zWsNNuYJj7cOa+HAkMjI9qe8Pnr6bw==
X-Received: by 10.55.157.215 with SMTP id g206mr7691943qke.12.1475244586464;
Fri, 30 Sep 2016 07:09:46 -0700 (PDT)
Received: from VOAK.xxxxx.com (mx1.xxxxx.com. [xxx.xxx.xxx.xxx]) by
smtp.gmail.com with ESMTPSA id u9sm10145590qtb.28.2016.09.30.07.09.45
for <gmail-smtp2p...@xxxxx.com> (version=TLS1 cipher=AES128-SHA
bits=128/128); Fri, 30 Sep 2016 07:09:46 -0700 (PDT)
Date: Fri, 30 Sep 2016 07:09:46 -0700
X-Google-Original-Date: Fri, 30 Sep 2016 14:09:46 GMT
To: <gmail-smtp2p...@xxxxx.com>
From: <xxxxxincomm...@gmail.com>
Subject: SMTP2POP3 1494547720160930
Message-ID: <54013072l.1054038312l1558164...@gmail.com>
X-ASG-Orig-Subj: SMTP2POP3 1494547720160930
X-Sender: SMTP2POP3Com
X-BESS-ID: 1475244586-723108-3463-76134-1
X-BESS-VER: 2016.13-r1609300003
X-BESS-Apparent-Source-IP: 209.85.220.171
X-BESS-BRTS-Status: 1
X-Barracuda-Connect: mail14.ess.barracuda.com[64.235.154.140]
X-Barracuda-Start-Time: 1475244589
X-Barracuda-Encrypted: ECDHE-RSA-AES256-GCM-SHA384
X-Barracuda-URL: https://10.10.1.5:443/cgi-mod/mark.cgi
X-Barracuda-Scan-Msg-Size: 48
X-Virus-Scanned: by bsmtpd at xxxxx.com
MIME-Version: 1.0
Content-Type: text/plain
Return-Path: xxxxxincomm...@gmail.com
X-MS-Exchange-Organization-AuthSource: vPalm.xxxxx.com
X-MS-Exchange-Organization-AuthAs: Anonymous
From: Servers Alive Discussion List [mailto:salive@woodstone.nu] On Behalf Of
Dirk Bulinckx
Sent: Friday, September 30, 2016 10:10 AM
To: Servers Alive Discussion List
Subject: RE: [SA-list] SMTP2POP3 Help
If you set the alert on 1 down, it will give you the requested alert on the 1st
failure, and that can be a send or a receive. And yes in your example it could
lead to an continious up/down situation with a lot of alerts. I don't see
another way to to this.
As for the 2nd issue, can you send the HEADERS of the received mail?
dirk.
--------------------------------------------------------------------------------
From: Servers Alive Discussion List [mailto:salive@woodstone.nu
(mailto:salive@woodstone.nu)] On Behalf Of Chris Coho
Sent: Friday, September 30, 2016 3:55 PM
To: Servers Alive Discussion List
Subject: [SA-list] SMTP2POP3 Help
I’m having some issues getting SMTP2POP3 working how I want it. Maybe
someone can assist. I tried a check sending an email from my mail server to
gmail in operating mode SMTP + POP3. Works, but the problem we just found
was we had an issue related to the mail leaving our facility. I had alerts set
on 2 failures and was never alerted because the send always succeeded, even
though the POP3 check kept failing…. But if I set it to alert on 1
failure in this same scenario I would just keep getting up and down notices
over and over again as the SMTP check was succeeding. Is that accurate and if
so is there a way to solve that?
I also tried setting it up as 2 checks, one dependent on the first. Check one
SMTP and check 2 POP3, with the idea that now I’m only alerted when POP3
fails, and it’ll stay down until it finally gets the email. Problem is
the 2nd check keeps failing saying “messages received but not send by
correct application”, but the only emails in the mailbox were SMTP2POP3
emails. Any way to resolve that?
Thanks!
To unsubscribe send a message with UNSUBSCRIBE in the subject line to
salive@woodstone.nu (mailto:salive@woodstone.nu)
If you use auto-responders (like out-of-the-office messages), make sure that
they are not sent to the list nor to individual members. Doing so will cause
you to be automatically removed from the list.
No virus found in this message.
Checked by AVG - www.avg.com (http://www.avg.com)
Version: 2016.0.7797 / Virus Database: 4656/13118 - Release Date: 09/30/16
To unsubscribe send a message with UNSUBSCRIBE in the subject line to
salive@woodstone.nu (mailto:salive@woodstone.nu)
If you use auto-responders (like out-of-the-office messages), make sure that
they are not sent to the list nor to individual members. Doing so will cause
you to be automatically removed from the list.
To unsubscribe send a message with UNSUBSCRIBE in the subject line to
salive@woodstone.nu
If you use auto-responders (like out-of-the-office messages), make sure that
they are not sent to the list nor to individual members. Doing so will cause
you to be automatically removed from the list.
