Re: [fpc-pascal] Dependency of OpenSSL 1.0.2 still in FPC 3.2.0 on some platforms?
On Sat, 15 May 2021 18:11:22 +0200 (CEST), Michael Van Canneyt via fpc-pascal wrote: >Welcome to the world of mailing. >I wish I could say it gets better, but it does not. > >> >> The body of the message is fixed at the moment, I could add a timestamp >> string >> to it but not much more to make it "new" every time. >> ... :( > >It might be better not to mail this, but to upload results to a server using >http, which puts everything in a database, and make a small frontend for your >database. Well, then we would have to supply a website too... -- Bo Berglund Developer in Sweden ___ fpc-pascal maillist - fpc-pascal@lists.freepascal.org https://lists.freepascal.org/cgi-bin/mailman/listinfo/fpc-pascal
Re: [fpc-pascal] Dependency of OpenSSL 1.0.2 still in FPC 3.2.0 on some platforms?
On Sat, 15 May 2021, Bo Berglund via fpc-pascal wrote: On Sat, 15 May 2021 09:00:08 +0200 (CEST), Michael Van Canneyt via fpc-pascal wrote: Glad you got it working. I worked for some time for a mass mailing company. From that experience I assure you that delivering mail is NOT easy. Meanwhile, there are a lot of safety mechanisms installed on all "big" mail platforms, and getting a mail delivered becomes more and more difficult. Well, after a few more tests two of my test recipients again did not receive the emails. Both are handled by GMail (of course). Now the reason is that GMail determined that the recipient had gotten too many "similar" emails so it stopped accepting them. And I also saw that it is getting suspicious of the "non-validated" sender... All of this is a PITA since I am working on porting an automatic environment monitoring system from Delphi to FreePascal and Linux. Here the results will be emailed packaged in a zipfile several times a day to a few recipients and it is not acceptable that the recipient's mail server blocks these emails. Welcome to the world of mailing. I wish I could say it gets better, but it does not. The body of the message is fixed at the moment, I could add a timestamp string to it but not much more to make it "new" every time. ... :( It might be better not to mail this, but to upload results to a server using http, which puts everything in a database, and make a small frontend for your database. Michael. ___ fpc-pascal maillist - fpc-pascal@lists.freepascal.org https://lists.freepascal.org/cgi-bin/mailman/listinfo/fpc-pascal
Re: [fpc-pascal] Dependency of OpenSSL 1.0.2 still in FPC 3.2.0 on some platforms?
On Sat, 15 May 2021 09:00:08 +0200 (CEST), Michael Van Canneyt via fpc-pascal wrote: >Glad you got it working. > >I worked for some time for a mass mailing company. >From that experience I assure you that delivering mail is NOT easy. > >Meanwhile, there are a lot of safety mechanisms installed on all "big" mail >platforms, and getting a mail delivered becomes more and more difficult. Well, after a few more tests two of my test recipients again did not receive the emails. Both are handled by GMail (of course). Now the reason is that GMail determined that the recipient had gotten too many "similar" emails so it stopped accepting them. And I also saw that it is getting suspicious of the "non-validated" sender... All of this is a PITA since I am working on porting an automatic environment monitoring system from Delphi to FreePascal and Linux. Here the results will be emailed packaged in a zipfile several times a day to a few recipients and it is not acceptable that the recipient's mail server blocks these emails. The body of the message is fixed at the moment, I could add a timestamp string to it but not much more to make it "new" every time. ... :( -- Bo Berglund Developer in Sweden ___ fpc-pascal maillist - fpc-pascal@lists.freepascal.org https://lists.freepascal.org/cgi-bin/mailman/listinfo/fpc-pascal
Re: [fpc-pascal] Dependency of OpenSSL 1.0.2 still in FPC 3.2.0 on some platforms?
On Sat, 15 May 2021, Bo Berglund via fpc-pascal wrote: It is not a size problem, the test mail contains just a very small zipfile sample (5 kb in size). And the mail is not in the spam folder either, it is simply silently rejected by GMail... No error message. It turns out that GMail inspects the *content* of the zipfile and if it discovers "dangerous" constituent files it blocks delivery altogether. https://support.google.com/mail/answer/6590?hl=en#zippy=%2Cmessages-that-have-attachments%2Cmessages-that-dont-have-attachments In my case there is a small text file inside named .cmd which is NOT a Windows command file (similar to a batch file) but a file with a set of equipment commands and geometry information So I tested by changing the extension from .cmd to ,cmd.txt and then delivery started working... So now I have to modify the automatic server so it will rename this particular file using a different extension. But that is easier than dealing with the OpenSSL incompatibility of Indy10 in any case. Glad you got it working. I worked for some time for a mass mailing company. From that experience I assure you that delivering mail is NOT easy. Meanwhile, there are a lot of safety mechanisms installed on all "big" mail platforms, and getting a mail delivered becomes more and more difficult. Michael. ___ fpc-pascal maillist - fpc-pascal@lists.freepascal.org https://lists.freepascal.org/cgi-bin/mailman/listinfo/fpc-pascal
Re: [fpc-pascal] Dependency of OpenSSL 1.0.2 still in FPC 3.2.0 on some platforms?
On Sat, 15 May 2021 01:11:07 +0200, Tomas Hajny via fpc-pascal wrote: >> Is there some kind of blocking for emails with zip attachments which >> stops them >> from being delivered to GMail accounts? >> >> If so, is there some other type of compressed format I can use which >> is allowed >> by GMail? > >Probably a silly question, but have you checked the Spam folder in >GMail? In general, you can certainly send ZIP files to GMail. Also, what >was the size of those attachments? The e-mail used as sender address >didn't get any SMTP error message, did it? Personally, I'd guess for >some other difference in your sending apart from the attachment type. It is not a size problem, the test mail contains just a very small zipfile sample (5 kb in size). And the mail is not in the spam folder either, it is simply silently rejected by GMail... No error message. It turns out that GMail inspects the *content* of the zipfile and if it discovers "dangerous" constituent files it blocks delivery altogether. https://support.google.com/mail/answer/6590?hl=en#zippy=%2Cmessages-that-have-attachments%2Cmessages-that-dont-have-attachments In my case there is a small text file inside named .cmd which is NOT a Windows command file (similar to a batch file) but a file with a set of equipment commands and geometry information So I tested by changing the extension from .cmd to ,cmd.txt and then delivery started working... So now I have to modify the automatic server so it will rename this particular file using a different extension. But that is easier than dealing with the OpenSSL incompatibility of Indy10 in any case. -- Bo Berglund Developer in Sweden ___ fpc-pascal maillist - fpc-pascal@lists.freepascal.org https://lists.freepascal.org/cgi-bin/mailman/listinfo/fpc-pascal
