infantex Posted July 14, 2022 Author Posted July 14, 2022 Thanks for your answer, Krydos. I changed the SPF record to: v=spf1 ip4:65.19.141.77 include:_spf.google.com ~all But still it didn't work. I tried to send a couple of mails from the contact form, one about 15 minutes after the other, and I didn't receive them. I just changed the SPF record to: v=spf1 include:_spf.google.com include:tommy2.heliohost.org ~all Waited about 5-10 minutes and tried again to send mail with the contact form. After about ten minutes, I have not received any mail. I was sure the contact form was working when the site was hosted in the VPS and I don't remember having included its IP in the SPF record, so I did another test. I edited my hosts files to point infantex.com.mx to the VPS (vps40): 65.19.141.197 infantex.com.mx Opened an incognito window, and tried the contact form again. It worked! Almost immediately I received the email, I mean, it ended up in spam, but I got it. Even though the VPS was not included in the SPF record. Here's the received mail, I don't know if it is of use to you: Delivered-To: info@infantex.com.mx Received: by 2002:a50:6cc4:0:0:0:0:0 with SMTP id b4csp836145ece; Wed, 13 Jul 2022 22:32:47 -0700 (PDT) X-Google-Smtp-Source: AGRyM1tTMobWUdr4Z6lM2UuH42VuZMVpGdWkhT1rGt5U/xj33ApBd+noF+GxdPBBE5bcc5Hfd/SB X-Received: by 2002:a17:903:1109:b0:16c:b5e7:652f with SMTP id n9-20020a170903110900b0016cb5e7652fmr109501plh.142.1657776766987; Wed, 13 Jul 2022 22:32:46 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1657776766; cv=none; d=google.com; s=arc-20160816; b=oFF20xpyb+g2P4g5qmwAVp6BXH9nn1iRY2U4Gi5UNmGeazMXRU0ul7CXptPLfw1Hdf UwI3FiUBiSX74Ywhzil6635zR3HSdu9vj5/H3qKc5hVU+LkOkOOeY/xIy1lkMZ56KSQf gpF44971hqlC1rUtc4RyKBzieMMTvnRujpuK73qctZwlQhrCmMRotUi+Y24/bFCrsME8 oyHUAvjcZ0wNLoq+3FTNMOI+eg+X9vUjQ0Q1hyQQS48430rOtd3Sxmwj1CzPW0pw5HE1 6PL7gxLjUrpGoutEFaljVEasHJaJKfM8PIxa5cHExH3JS5/UN5blU22j8jP0ZCOBvw9E gGCQ== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=mime-version:message-id:from:date:subject:to; bh=MxznMP1KYHp55PZLe4yzJaeZ8nDHEFFfvOMBHSCgTFg=; b=EAtXaGffaimkKuuKd4JidlXebmp7ay0lWIbscw3MNocfSckhmTNP3NVY7FmzNQx1Ez XBcwvOu8OOsvMKUvx4iP+eT7SZRezXdX9kNW0wOAy5hpPs73x0OKTNTIiaYSQqR7T33b Ki3KWOAGwo5QUa083Z4drieXPpBBhnGXu2rBAr2q+eg5opYaPXczs714cxhnuV+3K2G9 eu9hnNbF6YwdiMfvQ3yCkgFEeqd8g+YSmlq9IgxLCqp0RT5ohAU12Ux8v3TY7FpbxzMD jfl5w88G3wCDD1Uch+35WpmbfGk0udxkoK/ITtsTbvZSIBVYoaEi2B3zNCq2kgOYVn8e d4tw== ARC-Authentication-Results: i=1; mx.google.com; spf=permerror (google.com: permanent error in processing during lookup of admin@infantex.com.mx: tommy2.heliohost.org not found) smtp.mailfrom=admin@infantex.com.mx; dmarc=fail (p=NONE sp=QUARANTINE dis=NONE) header.from=gmail.com Return-Path: <admin@infantex.com.mx> Received: from vps40.heliohost.us (vps40.heliohost.us. [65.19.141.197]) by mx.google.com with ESMTPS id d21-20020a056a00199500b00528a45a239fsi1397826pfl.273.2022.07.13.22.32.46 for <info@infantex.com.mx> (version=TLS1_3 cipher=TLS_AES_256_GCM_SHA384 bits=256/256); Wed, 13 Jul 2022 22:32:46 -0700 (PDT) Received-SPF: permerror (google.com: permanent error in processing during lookup of admin@infantex.com.mx: tommy2.heliohost.org not found) client-ip=65.19.141.197; Authentication-Results: mx.google.com; spf=permerror (google.com: permanent error in processing during lookup of admin@infantex.com.mx: tommy2.heliohost.org not found) smtp.mailfrom=admin@infantex.com.mx; dmarc=fail (p=NONE sp=QUARANTINE dis=NONE) header.from=gmail.com Received: from infantx by vps40.heliohost.us with local (Exim 4.93) (envelope-from <admin@infantex.com.mx>) id 1oBrSu-004zny-C1 for info@infantex.com.mx; Thu, 14 Jul 2022 05:32:44 +0000 To: info@infantex.com.mx Subject: Solicitud de contacto Infantex X-PHP-Originating-Script: 1003:class.phpmailer.php Date: Thu, 14 Jul 2022 05:32:44 +0000 From: "Jorge Zaldívar" <jorge.zaldivar@gmail.com> Message-ID: <2240dbc8f5054ece003748ac1c38dc64@infantex.com.mx> X-Priority: 3 X-Mailer: PHPMailer [version 1.73] MIME-Version: 1.0 Content-Type: multipart/alternative; boundary="b1_2240dbc8f5054ece003748ac1c38dc64" --b1_2240dbc8f5054ece003748ac1c38dc64 Content-Type: text/plain; charset = "UTF-8" Content-Transfer-Encoding: 8bit Solicitud de contacto Infantex --b1_2240dbc8f5054ece003748ac1c38dc64 Content-Type: text/html; charset = "UTF-8" Content-Transfer-Encoding: 8bit <table width="560" border="0" cellspacing="0" cellpadding="0" style="font-family:Arial, Helvetica, sans-serif; font-size:11px; color:#333; text-align:justify; border:1px solid #E4E4E4" align="center"><tr><td style="padding:5px; color:#4E4F51" align="right"><strong>Fecha: </strong>14/07/2022</td></tr><tr><td style="padding:5px; color:#4E4F51" align="left">Este email es una notificación de que alguien ha enviado una solicitud de contacto a través del sitio web de Infantex con la siguiente información:</td></tr><tr><td style="padding:5px; font-size:16px; color:#4E4F51" align="left"><strong>Información general</strong></td></tr><tr><td style="padding:5px;" align="left"><table width="485" border="0" cellspacing="0" cellpadding="0" style="font-family:Arial, Helvetica, sans-serif; font-size:11px; color:#333; text-align:left"><tr><td width="100" style="font-family:Arial, Helvetica, sans-serif; font-size:11px; padding:3px; color:#4E4F51" align="left" valign="top"><strong>Nombre: </b></td><td width="385" style="font-family:Arial, Helvetica, sans-serif; font-size:11px; padding:3px; color:#333;" align="left" valign="top">Jorge Zaldívar</td></tr><tr><td style="font-family:Arial, Helvetica, sans-serif; font-size:11px; padding:3px; color:#4E4F51" align="left" valign="top"><b>Correo: </b></td><td style="font-family:Arial, Helvetica, sans-serif; font-size:11px; padding:3px; color:#333;" align="left" valign="top">jorge.zaldivar@gmail.com</td></tr><tr><td style="font-family:Arial, Helvetica, sans-serif; font-size:11px; padding:3px; color:#4E4F51" align="left" valign="top"><b style="font-family:Arial, Helvetica, sans-serif; font-size:11px; color:#4E4F51">Comentarios: </b></td><td style="font-family:Arial, Helvetica, sans-serif; font-size:11px; padding:3px; color:#333;" align="left" valign="top">Prueba de contacto cambiando hosts a VPS40.</td></tr></table></td></tr><tr><td> </td></tr><tr><td style="padding:5px; color:#333333" align="center" bgcolor="#FFFFFF" height="30" valign="middle"><b>Infantex - 2022</b></td></tr></table> --b1_2240dbc8f5054ece003748ac1c38dc64-- I went ahead and added the VPS's IP to the SPF record and made another test. Again, I received the email instantly, also in spam because "it resembled another email identified as spam previously". SPF was a pass now, though, but DMARC failed. Here's the email: Delivered-To: info@infantex.com.mx Received: by 2002:a50:6cc4:0:0:0:0:0 with SMTP id b4csp840573ece; Wed, 13 Jul 2022 22:46:59 -0700 (PDT) X-Google-Smtp-Source: AGRyM1veHGGEqtLZLYBFMJVC4Dhl6Da5B+oZT2CH3XhmNV1dKemUpztE23VzkX00t8aND5ql0s1H X-Received: by 2002:a05:6a00:3498:b0:52a:f8f4:ca7c with SMTP id cp24-20020a056a00349800b0052af8f4ca7cmr6813096pfb.5.1657777619676; Wed, 13 Jul 2022 22:46:59 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1657777619; cv=none; d=google.com; s=arc-20160816; b=Kl13HTxFQq+rTqAgFT5b+854cB0ft7wchKvaXQSHAuBNRrNQLblcDu0Dr1igShcsbF sVKZ9YhSZHsXZoGIN/NKxffUBfPzyg4jkFy1wPtuGBFfpAcA6dRRJMsYI3x4/kD5VR9Q VSj6Vm4zHcDPmZolND2all3mE/p+0/E3jt/9FODb7IjjpKyqHSYUb9iT2LzAtHUEMYtE aBj7CugixWuk4SfxNib0JMwCjYOeqSi8p15fOuKtTaSku/jTB9sWGZp/9TobVG1QK/wo OFO/mXK1/SEq+msEH2rxsQSAkTStLbEG1azfERNt2QAPx3cDp70iBt4X4MChYtILCdau gDlA== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=mime-version:message-id:from:date:subject:to; bh=wvwKBNyg+mWJQfJHGgp48ln0+DPQFGmG/rP+SThP4Ds=; b=MZydM209rqItLAetKnXc2biim8mjw7z8VvttTBFbWI7BWfuVlq9ope34k7A3ZI0ukh ULuFSfYMZERDUJw8HFPrcu+reNhJ7RZAZlzoBm1ZkZ9G/0uIe2tbuhjUVm/MmhyLU4MA CwR6Vl78VcppvHgzAUNLa4s3geWBXqFkpgYolmkuvONhTlIiPydaJyON6HJtkM6y0A2O OdGus70P9DCIu8LmAxrhSiY7WvOXg1X6gtwHUcUwbfPYiv31Vtb7rYiHUBsnmZv0oXPd qhWPGFPloiQLgxB4ABJ1Oe5fGJ4eOZ8wmPimii0CTs5F2V6z1Bd91XpI8BuZJuALjsQv yD/w== ARC-Authentication-Results: i=1; mx.google.com; spf=pass (google.com: domain of admin@infantex.com.mx designates 65.19.141.197 as permitted sender) smtp.mailfrom=admin@infantex.com.mx; dmarc=fail (p=NONE sp=QUARANTINE dis=NONE) header.from=gmail.com Return-Path: <admin@infantex.com.mx> Received: from vps40.heliohost.us (vps40.heliohost.us. [65.19.141.197]) by mx.google.com with ESMTPS id u185-20020a6385c2000000b0040d40aa9820si810470pgd.195.2022.07.13.22.46.59 for <info@infantex.com.mx> (version=TLS1_3 cipher=TLS_AES_256_GCM_SHA384 bits=256/256); Wed, 13 Jul 2022 22:46:59 -0700 (PDT) Received-SPF: pass (google.com: domain of admin@infantex.com.mx designates 65.19.141.197 as permitted sender) client-ip=65.19.141.197; Authentication-Results: mx.google.com; spf=pass (google.com: domain of admin@infantex.com.mx designates 65.19.141.197 as permitted sender) smtp.mailfrom=admin@infantex.com.mx; dmarc=fail (p=NONE sp=QUARANTINE dis=NONE) header.from=gmail.com Received: from infantx by vps40.heliohost.us with local (Exim 4.93) (envelope-from <admin@infantex.com.mx>) id 1oBrgf-0050Fu-4T for info@infantex.com.mx; Thu, 14 Jul 2022 05:46:57 +0000 To: info@infantex.com.mx Subject: Solicitud de contacto Infantex X-PHP-Originating-Script: 1003:class.phpmailer.php Date: Thu, 14 Jul 2022 05:46:57 +0000 From: "Jorge Zaldívar" <jorge.zaldivar@gmail.com> Message-ID: <8337c4ae5dff02fee86c6e7dfbc54195@infantex.com.mx> X-Priority: 3 X-Mailer: PHPMailer [version 1.73] MIME-Version: 1.0 Content-Type: multipart/alternative; boundary="b1_8337c4ae5dff02fee86c6e7dfbc54195" --b1_8337c4ae5dff02fee86c6e7dfbc54195 Content-Type: text/plain; charset = "UTF-8" Content-Transfer-Encoding: 8bit Solicitud de contacto Infantex --b1_8337c4ae5dff02fee86c6e7dfbc54195 Content-Type: text/html; charset = "UTF-8" Content-Transfer-Encoding: 8bit <table width="560" border="0" cellspacing="0" cellpadding="0" style="font-family:Arial, Helvetica, sans-serif; font-size:11px; color:#333; text-align:justify; border:1px solid #E4E4E4" align="center"><tr><td style="padding:5px; color:#4E4F51" align="right"><strong>Fecha: </strong>14/07/2022</td></tr><tr><td style="padding:5px; color:#4E4F51" align="left">Este email es una notificación de que alguien ha enviado una solicitud de contacto a través del sitio web de Infantex con la siguiente información:</td></tr><tr><td style="padding:5px; font-size:16px; color:#4E4F51" align="left"><strong>Información general</strong></td></tr><tr><td style="padding:5px;" align="left"><table width="485" border="0" cellspacing="0" cellpadding="0" style="font-family:Arial, Helvetica, sans-serif; font-size:11px; color:#333; text-align:left"><tr><td width="100" style="font-family:Arial, Helvetica, sans-serif; font-size:11px; padding:3px; color:#4E4F51" align="left" valign="top"><strong>Nombre: </b></td><td width="385" style="font-family:Arial, Helvetica, sans-serif; font-size:11px; padding:3px; color:#333;" align="left" valign="top">Jorge Zaldívar</td></tr><tr><td style="font-family:Arial, Helvetica, sans-serif; font-size:11px; padding:3px; color:#4E4F51" align="left" valign="top"><b>Correo: </b></td><td style="font-family:Arial, Helvetica, sans-serif; font-size:11px; padding:3px; color:#333;" align="left" valign="top">jorge.zaldivar@gmail.com</td></tr><tr><td style="font-family:Arial, Helvetica, sans-serif; font-size:11px; padding:3px; color:#4E4F51" align="left" valign="top"><b style="font-family:Arial, Helvetica, sans-serif; font-size:11px; color:#4E4F51">Comentarios: </b></td><td style="font-family:Arial, Helvetica, sans-serif; font-size:11px; padding:3px; color:#333;" align="left" valign="top">New test for contact form from VPS. Now VPS's IP is included in SPF record.</td></tr></table></td></tr><tr><td> </td></tr><tr><td style="padding:5px; color:#333333" align="center" bgcolor="#FFFFFF" height="30" valign="middle"><b>Infantex - 2022</b></td></tr></table> --b1_8337c4ae5dff02fee86c6e7dfbc54195-- Can you gather something from this results? Regards,
infantex Posted July 14, 2022 Author Posted July 14, 2022 More info that may be relevant. I checked the "spamness" of the newly configured mail from zaldivar.mx and, although it received good marks, one failing result mentioned that reverse DNS was not properly configured for Tommy. Reference: https://app.mailgenius.com/spam-test/55a617 This may be relevant because the mail from the contact form is also being sent by Tommy, isn't it? Regards,
Krydos Posted July 14, 2022 Posted July 14, 2022 Reverse DNS is set up correctly for Tommy2 for both IPv4 and IPv6 root@cody [/home/krydos]# dig +noall +answer -x 65.19.141.77 77.141.19.65.in-addr.arpa. 4798 IN CNAME 77.subnet72.141.19.65.in-addr.arpa. 77.subnet72.141.19.65.in-addr.arpa. 4835 IN PTR tommy2.heliohost.org. root@cody [/home/krydos]# dig +noall +answer -x 2001:470:1:1ee::2002 2.0.0.2.0.0.0.0.0.0.0.0.0.0.0.0.e.e.1.0.1.0.0.0.0.7.4.0.1.0.0.2.ip6.arpa. 14400 IN PTR tommy2.heliohost.org. Here's your error log now Jul 14 19:54:21 tommy2 plesk-sendmail[2071]: S2070: py-limit-out: stderr: INFO:__main__:Setting 'X-PPP-Vhost' header to 'infantex.com.mx' Jul 14 19:54:21 tommy2 plesk-sendmail[2071]: S2070: py-limit-out: stderr: PASS Jul 14 19:54:21 tommy2 plesk-sendmail[2071]: S2070: check-quota: stderr: SKIP Jul 14 19:54:21 tommy2 postfix/pickup[128820]: B25E940B7FF6: uid=10183 from=<infantx@infantex.com.mx> Jul 14 19:54:21 tommy2 postfix/smtpd[1676]: warning: hostname net6-ip230.linkbg.com does not resolve to address 87.246.7.230: Name or service not known Jul 14 19:54:21 tommy2 postfix/smtpd[1676]: connect from unknown[87.246.7.230] Jul 14 19:54:21 tommy2 postfix/cleanup[128127]: B25E940B7FF6: message-id=<cb96865d9dfaa51f3a09c30ba074aa45@infantex.com.mx> Jul 14 19:54:21 tommy2 postfix/qmgr[15698]: B25E940B7FF6: from=<infantx@infantex.com.mx>, size=2984, nrcpt=1 (queue active) Jul 14 19:54:21 tommy2 postfix-local[2090]: B25E940B7FF6: from=<infantx@infantex.com.mx>, to=<infantx@infantex.com.mx>, dirname=/var/qmail/mailnames Jul 14 19:54:21 tommy2 spamd[32163]: spamd: connection from localhost.localdomain [::1]:40084 to port 783, fd 6 Jul 14 19:54:21 tommy2 spamd[32163]: spamd: using default config for infantx@infantex.com.mx: /var/qmail/mailnames/infantex.com.mx/infantx/.spamassassin/user_prefs Jul 14 19:54:21 tommy2 spamd[32163]: spamd: processing message <cb96865d9dfaa51f3a09c30ba074aa45@infantex.com.mx> for infantx@infantex.com.mx:30 Jul 14 19:54:22 tommy2 spamd[32163]: spamd: clean message (0.2/7.0) for infantx@infantex.com.mx:30 in 0.4 seconds, 3063 bytes. Jul 14 19:54:22 tommy2 spamd[32163]: spamd: result: . 0 - HEADER_FROM_DIFFERENT_DOMAINS,HTML_MESSAGE,NO_RELAYS,T_SCC_BODY_TEXT_LINE scantime=0.4,size=3063,user=infantx@infantex.com.mx,uid=30,required_score=7.0,rhost=localhost.localdomain,raddr=::1,rport=40084,mid=<cb96865d9dfaa51f3a09c30ba074aa45@infantex.com.mx>,autolearn=no autolearn_force=no Jul 14 19:54:22 tommy2 postfix-local[2090]: B25E940B7FF6: spam: stderr: PASS Jul 14 19:54:22 tommy2 dk_check[2095]: B25E940B7FF6: DKIM Feed: No signature Jul 14 19:54:22 tommy2 postfix-local[2090]: B25E940B7FF6: dk_check: stderr: PASS Jul 14 19:54:22 tommy2 dmarc[2096]: B25E940B7FF6: SPF record was not found in Authentication-Results Jul 14 19:54:22 tommy2 spamd[84024]: prefork: child states: II Jul 14 19:54:22 tommy2 dmarc[2096]: B25E940B7FF6: DMARC: smtpdomain=infantex.com.mx maildomain=thankyou.com mailfrom=no@thankyou.com stamp=1657828462 ip=unknown adkim=relaxed aspf=relaxed p=REJECT sp=UNSPECIFIED pct=100 align_dkim=fail align_spf=fail spfres=unknown dkimres=unknown dmarccheck=DMARC_POLICY_REJECT dmarcstatus=STOP Jul 14 19:54:22 tommy2 postfix-local[2090]: B25E940B7FF6: dmarc: stderr: STOP Jul 14 19:54:22 tommy2 postfix-local[2090]: message discarded by a mail handler Jul 14 19:54:22 tommy2 postfix/pipe[2089]: B25E940B7FF6: to=<infantx@infantex.com.mx>, orig_to=<info@infantex.com.mx>, relay=plesk_virtual, delay=0.7, delays=0.06/0.04/0/0.61, dsn=2.0.0, status=sent (delivered via plesk_virtual service) Jul 14 19:54:22 tommy2 postfix/qmgr[15698]: B25E940B7FF6: removed Try using this as your SPF "v=spf1 ip4:65.19.141.197 +ip4:65.19.141.77 include:_spf.google.com ~all" The other issue I see is you don't have DKIM set up. In Plesk mail section enable DKIM and then copy/paste the TXT records they give you into Cloudlfare.
infantex Posted July 15, 2022 Author Posted July 15, 2022 4 hours ago, Krydos said: Reverse DNS is set up correctly for Tommy2 for both IPv4 and IPv6 OK. I was just reporting what MailGenius found. Guess they're wrong then. 4 hours ago, Krydos said: Try using this as your SPF "v=spf1 ip4:65.19.141.197 +ip4:65.19.141.77 include:_spf.google.com ~all" OK. I set the SPF as advised. Then tried to send an email with the contact form but, still, after about half an hour, nothing received. 😞 4 hours ago, Krydos said: The other issue I see is you don't have DKIM set up. I do have DKIM set up. As can be seen here: and here: Should I set a second DKIM record? Maybe tommy._domainkey. Or should it be default._domainkey as Plesk advises? Regards,
Krydos Posted July 15, 2022 Posted July 15, 2022 Yeah, copy/paste the Plesk data in. You can have multiple TXT records for DKIM if you send from your VPS, Google, and Plesk, etc. Each source needs it's own unique DKIM. 16 minutes ago, infantex said: OK. I was just reporting what MailGenius found. Guess they're wrong then. I have no idea why MailGenius is saying that. I even looked at the report you linked and their own report shows the reverse DNS for tommy2.heliohost.org correctly.
infantex Posted July 15, 2022 Author Posted July 15, 2022 1 hour ago, Krydos said: Yeah, copy/paste the Plesk data in. Done. Created the DKIM record (named it tommy._domainkey). I also created another TXT record named _domainkey with the value "o=-", as per Plesk instructions (previously, I didn't have such record). Now to try the contact form again... No good, no email received. Changed the name of the new record to default._domainkey and tried again... Still nothing. 😞 What else can we try?
Krydos Posted July 15, 2022 Posted July 15, 2022 I still see this "Jul 15 05:06:11 tommy2 dmarc[87197]: 5E302402C20C: SPF record was not found in Authentication-Results". It doesn't like your SPF record. Maybe try setting your SPF to "v=spf1 ip4:65.19.141.197 +ip4:65.19.141.77 +ip6:2001:470:1:1ee::2002 include:_spf.google.com ~all"
infantex Posted July 15, 2022 Author Posted July 15, 2022 6 minutes ago, Krydos said: Maybe try setting your SPF to "v=spf1 ip4:65.19.141.197 +ip4:65.19.141.77 +ip6:2001:470:1:1ee::2002 include:_spf.google.com ~all" Done. Tested the contact form. Fingers crossed and... Failed!
Krydos Posted July 15, 2022 Posted July 15, 2022 No, you're making progress. Check out the log now. Jul 15 05:16:38 tommy2 postfix-local[101248]: C09F3402A61D: dmarc: stderr: PASS Jul 15 05:16:38 tommy2 postfix-local[101248]: cannot chdir to mailname dir jazc: No such file or directory Jul 15 05:16:38 tommy2 postfix-local[101248]: C09F3402A61D: Unknown user: jazc@infantex.com.mx Jul 15 05:16:38 tommy2 postfix/pipe[101242]: C09F3402A61D: to=<jazc@infantex.com.mx>, orig_to=<info@infantex.com.mx>, relay=plesk_virtual, delay=0.58, delays=0.2/0.17/0/0.21, dsn=2.0.0, status=sent (delivered via plesk_virtual service) Jul 15 05:16:38 tommy2 postfix/qmgr[121784]: C09F3402A61D: removed That email address it's trying to deliver to doesn't exist in Plesk. Try creating it.
infantex Posted July 15, 2022 Author Posted July 15, 2022 12 hours ago, Krydos said: That email address it's trying to deliver to doesn't exist in Plesk. Try creating it. Oh!, both email addresses (jazc and info) do exist... but in G Suite Legacy (which manages infantex.com.mx mail). It seems that, since the destination email is in the same domain as the web page, Plesk is trying to "shortcut" the sending of the mail, writing it directly to a specific directory instead of actually sending it as mail. Am I correct in interpreting the losgs this way? If that's the case, how can I prevent this "shortcutting"? Do I need to deactivate the mail service for this domain in Plesk? Would in that case the contact form still be able to send mail? Thanks a lot for your help and encouragment, Krydos!
Krydos Posted July 15, 2022 Posted July 15, 2022 Yes, if the domain is hosted on the server Plesk doesn't even bother looking at the MX records or anything and just sends it internally. You would have to make a temporary email address on a domain that isn't hosted on Plesk to make the email leave the server, and then you could forward from the temporary email back to an infantex.com.mx address. Couldn't you create the email address on Plesk and then have your gsuite log in to Plesk and download the emails? That seems easier.
infantex Posted July 16, 2022 Author Posted July 16, 2022 You know what? Now that zaldivar.mx's mail service is properly configured, I'll go ahead and move infantex.com.mx's mail service to Plesk as well, and stop using Google´s G Suite. I intended to do that, anyway, now that they've discontinued their free service. I'll let you know when it's done and tested. From what yoy say, it should then work. However, I do think that there must be a way to avoid Plesk "shortcutting" these emails. I mean, with cPanel the setup was the same: web site serviced by cPanel (under several servers: Johny, Stevie, Ricky, Tommy, don't really remember which ones or in what order) and email serviced by Google. Also with the VPN: It hosted the website but mail was handled by Google. And the contact form worked and sent the emails through the "proper channels", so to speak. In the end, for me, everything will be OK because I'll move everything to Plesk, but there might be someone in my position not willing or able to consolidate how their several services are hosted. Regards,
infantex Posted July 16, 2022 Author Posted July 16, 2022 13 minutes ago, infantex said: However, I do think that there must be a way to avoid Plesk "shortcutting" these emails. There IS a way. I deactivated the email service on the domain in Plesk and, voila! It worked. Just second after pressing the Send button on the contact form, I received the email in the proper mailbox. Don't know how this will reflect in the logs. Anyway, G Suite must go, but now, it's not that urgent. 🙂 Have a great weekend!
infantex Posted July 21, 2022 Author Posted July 21, 2022 (edited) I just finished moving the mail service for infantex.com.mx to Plesk (Tommy). Everything seems to be working fine. I sent a test email to mail-tester.com and the results were fine (https://www.mail-tester.com/test-kd5aj8l8n). I changed the SPF policy to p=none (from p=reject),and will be monitoring no valid emails fail before changing it back to a more strict setting. There are just four issues remaining: Where do I turn off Plesk trying to issue Let's Encrypt certificate. I keep getting the "Could not issue/renew Let's Encrypt certificates for infantx" emails. I get mine from Cloudflare. Could my login ID be changed from infantx to infantex? At some point, when the server my account was hosted on failed, I had to use another user name to install my site on another of your servers. zaldivar.mx is an addon domain. With cPanel, addon domains were "like" subdomains, i.e., I currently have a zaldivar.infantex.com.mx domain that I really don't need (the "Could not issue Let's Encrypt" emails mentioned above reminded me of its existence). Does Plesk also need this subdomain or can I delete it without loosing zaldivar.mx? This last one is related to the VPS and not Plesk. One thing I could not set up correctrly in the VPS was www redirection. If I browsed "infantex.com.mx" I got to the correct, secure (https) website, but if I browsed "www.infantex.com.mx" I landed in a default page (I think, HestiaCP-provided). I tried setting this right through DNS records but gor circular-reference errors (too many redirects). Wasn't able to configure this correctly. Now, with Plesk, it works fine without me doing anything (as did, previously, with cPanel). Any ideas on how to fix that, if I decided to move back to the VPS? Regards, Edit: This is the thread that describes what I tried to do to correct the www-redirecting issue mentioned in point (4): Edited July 21, 2022 by infantex Added link to www-redirecting thread
Recommended Posts
Create an account or sign in to comment
You need to be a member in order to leave a comment
Create an account
Sign up for a new account in our community. It's easy!
Register a new accountSign in
Already have an account? Sign in here.
Sign In Now