[Cialug] Logwatch not sending email to my Gmail account

Sat Aug 16 09:25:32 CDT 2014

At least they made it to your SPAM folder. That's an easy fix. If Google
was completely dropping them it would be a bit more difficult to fix.

On Sat, Aug 16, 2014 at 9:21 AM, Rob Cook <rdjcook at gmail.com> wrote:

> Sonofa... Thank you for pointing out the obvious, I have my GMail web
> interface setup so that the Spam folder is hidden. They were all there and
> are now marked not spam. Yeah, well I need more coffee before I work on
> stuff in the morning.
>
>
> On Sat, Aug 16, 2014 at 9:18 AM, Rob Cook <rdjcook at gmail.com> wrote:
>
> > So it's possible that GMail is simply listing my logwatch as spam, crap.
> > Well I'll look and see if I can whitelist my servers.
> >
> >
> > On Sat, Aug 16, 2014 at 9:16 AM, kristau <kristau at gmail.com> wrote:
> >
> >> Not sure on the maillog issue, but that status in the log you presented
> >> tells me that gmail-smtp-in.l.google.com accepted the message for
> >> delivery.
> >> Many spam filters accept all messages these days and apply the filtering
> >> after acceptance. This is to help avoid spammers trying to discover
> valid
> >> and invalid recipients, domains, etc.
> >>
> >>
> >> On Sat, Aug 16, 2014 at 9:04 AM, Rob Cook <rdjcook at gmail.com> wrote:
> >>
> >> > I can't say I knew I was using IPv6 honestly, though looking at it
> that
> >> > would appear to be an IPv6 address.
> >> >
> >> > *admitting ignorance here* I never see the successful test emails in
> the
> >> > /var/log/maillog, where should I be looking for them? If Google did
> >> start
> >> > blocking invalid TLDs then this is quite the timing coincidence. I'll
> >> see
> >> > if changing the hostname does anything.
> >> >
> >> >
> >> >
> >> >
> >> > On Sat, Aug 16, 2014 at 9:00 AM, kristau <kristau at gmail.com> wrote:
> >> >
> >> > > It looks like the gmail host resolved to an IPV6 address at first,
> but
> >> > then
> >> > > it appears that the process re-resolved using IPV4 and sent
> >> successfully.
> >> > > Reference the code 200 and OK in the following section:
> >> > >
> >> > > <http://gmail-smtp-in.l.google.com>[74.125.193.27]:25, delay=1.8,
> >> > > > delays=0.96/0.02/0.45/0.34, dsn=2.0.0, *status=sent (250 2.0.0 OK*
> >> > > 1408195625
> >> > > > dt9si16457433icc.99 - gsmtp)*
> >> > >
> >> > > When you successfully send your test message, is the sender domain
> >> > > gmail.com,
> >> > > or is it cookfam.lan? They may have started blocking all invalid
> >> TLDs. .
> >> > .
> >> > >
> >> > >
> >> > >
> >> > > On Sat, Aug 16, 2014 at 8:47 AM, Jim Shanks <jim at cybershanks.com>
> >> wrote:
> >> > >
> >> > > > Have you tried it over IPv4?
> >> > > >
> >> > > > On Aug 16, 2014, at 8:36 AM, Rob Cook <rdjcook at gmail.com> wrote:
> >> > > >
> >> > > > > Recently, in the last week, I've stopped getting logwatch emails
> >> from
> >> > > my
> >> > > > > home machines to my gmail account, I'm still getting denyhost
> >> > > > notification
> >> > > > > emails (damn chinese bots!) and I can send an email to my gmail
> >> > account
> >> > > > > using  *mail -s "Testing" rdjcook at gmail.com <rdjcook at gmail.com>
> >> *but
> >> > > > > logwatch gives the following:
> >> > > > >
> >> > > > > *Aug 16 08:27:17 backup postfix/pickup[7688]: D581D400EB: uid=0
> >> > > > from=<root>*
> >> > > > > *Aug 16 08:27:17 backup postfix/cleanup[8480]: D581D400EB:
> >> > > > > message-id=<20140816132717.D581D400EB at backup.cookfam.lan>*
> >> > > > > *Aug 16 08:27:17 backup postfix/qmgr[7673]: D581D400EB:
> >> > > > > from=<root at backup.cookfam.lan>, size=2265, nrcpt=1 (queue
> >> active)*
> >> > > > > *Aug 16 08:27:18 backup postfix/smtp[8482]: connect to
> >> > > > > gmail-smtp-in.l.google.com
> >> > > > > <http://gmail-smtp-in.l.google.com>[2607:f8b0:4001:c05::1a]:25:
> >> > > Network
> >> > > > is
> >> > > > > unreachable*
> >> > > > > *Aug 16 08:27:18 backup postfix/smtp[8482]: D581D400EB:
> >> > > > > to=<rdjcook at gmail.com <rdjcook at gmail.com>>,
> >> > > > > relay=gmail-smtp-in.l.google.com
> >> > > > > <http://gmail-smtp-in.l.google.com>[74.125.193.27]:25,
> delay=1.8,
> >> > > > > delays=0.96/0.02/0.45/0.34, dsn=2.0.0, status=sent (250 2.0.0 OK
> >> > > > 1408195625
> >> > > > > dt9si16457433icc.99 - gsmtp)*
> >> > > > > *Aug 16 08:27:18 backup postfix/qmgr[7673]: D581D400EB: removed*
> >> > > > >
> >> > > > > Specifically the 'Network is unreachable' is the obvious issue
> but
> >> > I'm
> >> > > > > stumped as to why I can email without problem but
> >> logwatch/postfix is
> >> > > > > unable to do so. I have not made any changes that I know of,
> this
> >> > seems
> >> > > > to
> >> > > > > have happened of it's own accord.
> >> > > > >
> >> > > > > If there are conf files I can post please let me know,
> >> > > > >
> >> > > > > Thanks for the help,
> >> > > > > Rob
> >> > > > > _______________________________________________
> >> > > > > Cialug mailing list
> >> > > > > Cialug at cialug.org
> >> > > > > http://cialug.org/mailman/listinfo/cialug
> >> > > >
> >> > > > _______________________________________________
> >> > > > Cialug mailing list
> >> > > > Cialug at cialug.org
> >> > > > http://cialug.org/mailman/listinfo/cialug
> >> > > >
> >> > >
> >> > >
> >> > >
> >> > > --
> >> > > Tired programmer
> >> > > Coding late into the night
> >> > > The core dump follows
> >> > > _______________________________________________
> >> > > Cialug mailing list
> >> > > Cialug at cialug.org
> >> > > http://cialug.org/mailman/listinfo/cialug
> >> > >
> >> > _______________________________________________
> >> > Cialug mailing list
> >> > Cialug at cialug.org
> >> > http://cialug.org/mailman/listinfo/cialug
> >> >
> >>
> >>
> >>
> >> --
> >> Tired programmer
> >> Coding late into the night
> >> The core dump follows
> >> _______________________________________________
> >> Cialug mailing list
> >> Cialug at cialug.org
> >> http://cialug.org/mailman/listinfo/cialug
> >>
> >
> >
> _______________________________________________
> Cialug mailing list
> Cialug at cialug.org
> http://cialug.org/mailman/listinfo/cialug
>

-- 
Tired programmer
Coding late into the night
The core dump follows