Hi, your Postfix logs look normal to my untrained eyes. If it was me i would figure out the best contact email for the ISP and tell them as much detailed info as i could, so it is easy for them to get you the answer to "what happened to X email ?".
Looks like they just need this line : Jun 17 12:03:16 localhost postfix/smtp[8033]: 10C52100049C: to=<cpoll...@embarqmail.com>, orig_to=<root>, relay=smtp.embarqmail.com[206.152.134.66]:25, delay=3.6, delays=0.05/0.01/0.17/3.3, dsn=2.0.0, status=sent (250 SPF validation soft failure) They will then know the : DATE TIME IP address of server that accepted your email Also i think they will want the FQDN and IP address of your server. Good luck -ANGELO FAZZINA ang...@uconn.edu University of Connecticut, ITS, SSG, Server Systems 860-486-9075 -----Original Message----- From: owner-postfix-us...@postfix.org <owner-postfix-us...@postfix.org> On Behalf Of Richard James Salts Sent: Monday, June 17, 2019 11:29 PM To: postfix-users@postfix.org Subject: Re: How to tell my ISP there's a problem On Monday, 17 June 2019 7:48:05 PM AEST Chris Pollock wrote: > Apologies if the subject is vague however I'll attempt to explain > further. I run a cron job once a day that updates my Spamassassin > rules. Up until a couple of weeks ago I would get the output of that > cron job mailed to me. For some reason this is the only cron job output > that's not coming back. I've determined that size it not a factor since > some of my hourly logcheck messages are up to 400k if a restart has > taken place. Below is the output when it was working and the output > since them. I can't see a difference so it has to be something at my > ISP with just this one cron job but I can't see it. > > https://nam01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fpastebin.com%2Fv0rMErQh&data=02%7C01%7Cangelo.fazzina%40uconn.edu%7C442762b0d67a4f43757a08d6f39d536a%7C17f1a87e2a254eaab9df9d439034b080%7C0%7C0%7C636964254387499317&sdata=zUjcikOfrs11SwYzM7o%2Bi6txTfWZeuQkXkqNHxOmT9k%3D&reserved=0 > > Thanks for any suggestions Maybe it's going to a spam folder. I notice that the reply from your isp says 250 SPF validation soft failure in both cases, but if they stopped forwarding "potentially forged" emails that might be a possible cause. It is definitely the behaviour on smtp.embarqmail.com that has changed though, so you need to ask the administrators of that server. Is this direct to MX or is it a fixed relay intended to be a smarthost?
