wwIPstuff - Ionos not accepting Date: header value

[GriffMG]

I have a customer who uses West Wind utilities to send out emails to suppliers for prices.

Two suppliers have ceased receiving their emails, both are using Ionos to handle their emails and I think
they are being rejected because of the Date: header is not acceptable.

Has anyone else come across this?

 

[GriffMG]

It's all to do with the clocks going back in the UK on 26 Oct.

Ionos like the zone offset to be presented as either +0000 or -0000 for
the West Wind components I'm using send 0000.

Off to Chilkat

 

[Chris Miller]

Are you talking about the mails and their composition or the autheniotcation process towards Ionos Mailservers?

Anyway, it seems you figure it out, but only knowing you have some problem with Ionos is not enough to help, sorry.

 

[GriffMG]

Hi Chriss

Originally I thought maybe someone else had experienced something - messages being accepted by their servers but never
reaching the client, the mails seemed good, all with spf, DKIM and DMARC... no bounce from Ionos. I spotted that the date:
being passed was different, and was hoping that another VFPer had found a work around.

Meanwhile I'm swapping the mail component out for chilkat, it does it right but it's a body of work to implement
in place of the WW utilities - but so is upgrading those.

 

[Chris Miller]

>it's a body of work to implementin place of the WW utilities - but so is upgrading those.

If it's a time issue then it should be fixed by servers or clients adjust their time correctly, shouldn't it? But what if replacing wwipstuff with chilkat doesn't help and the problem is really something with accounts, port changes, whatever else?

Is this happening since October 26 at all? Or don't you know? Does wwipstuff allow logging all the communication happening from your app to the mailservers? If sending mails works, then what goes wrong with the delivery to the recipient is not in your hands, is it? Usually, if there is a recipient not found or rejecting mails you get a maildemon response mail, usually telling some mail address does not exist, but also with other problems. If you send mails from mail accounts that are not looked into or are even noreply addresses that don't exist, You get nothing back telling what's not working. That won't change using chilkat. All you can be sure modernizing with current chilkat modules should get this going in principle, but then again if it all just fails because of changes of recipient mail addresses or any othe problems on the recipient side, you still won't know.

 

[vaxman9]

I have been using WWIPStuff for a while - you might want to make sure the clients have the latest release. I had some issues with it a couple years ago with HELO/EHLO. I Mr. Strahl pointed out to me that I had a very old version of the tools. Once I upgraded, the issue was resolved.
Not sure if your problem is version related, but it might be worth a look before making the change.

FWIW, I have been using the West Wind tools for years and have found them rock solid.

msc

 

[Tore Bleken]

Why isn't this question posted on West-Wind's message board where it belongs?