Can't get forwarded mail from gmail

maybl8

This is from my rspamd screen.
This email should be fine. If I send directly from the gmx server I get the mail but if it comes from the forward at gmail I don’t get it.
`0BAFA45B-9B4B-45EE-999B-3BFABE1D877F@edison.tech 209.85.214.180 [dcihon@gmail.com] dcihon@gmx.com [danc@dccathome.com] dcihon@gmail.com Test no 3 reject 40.13 / 15 8.92 KiB 1.973 9/20/2024, 2:37:32 PM unknown
[Envelope To] To/Cc/Bcc [danc@dccathome.com] dcihon@gmail.com
Symbols

Sort by:
FREEMAIL_POLICY_FAILURE (16)
R_DKIM_REJECT (8) [gmx.com:s=s31663417]
DMARC_POLICY_QUARANTINE (8) [gmx.com : SPF not aligned (relaxed),quarantine]
FORGED_W_BAD_POLICY (3)
BAD_REP_POLICIES (2)
BAYES_SPAM (1.69996) [88.54%]
IP_REPUTATION_SPAM (1.638178) [asn: 15169(0.40), country: US(0.01), ip: 209.85.214.180(0.00)]
RWL_MAILSPIKE_GOOD (-0.1) [209.85.214.180:from]
MIME_GOOD (-0.1) [multipart/alternative,text/plain]
RCVD_IN_DNSWL_LOW (-0.1) [212.227.17.22:received]
ARC_REJECT (0.1) [signature check failed: fail, {[1] = sig:google.com:reject}]
MX_GOOD (-0.01) []
ASN (0) [asn:15169, ipnet:209.85.128.0/17, country:US]
MISSING_XM_UA (0)
RCVD_TLS_LAST (0)
RCVD_VIA_SMTP_AUTH (0)
TO_DN_ALL (0)
BCC (0)
FORGED_SENDER_FORWARDING (0)
MAILCOW_WHITE_EXCLUDE (0)
FWD_GOOGLE (0) [dcihon@gmail.com]
RCPT_COUNT_ONE (0) [1]
ARC_SIGNED (0) [dccathome.com:s=dkim:i=3]
RCVD_COUNT_THREE (0) [4]
FREEMAIL_ENVFROM (0) [gmail.com]
DKIM_TRACE (0) [gmx.com:-]
R_SPF_ALLOW (0) [+ip4:209.85.128.0/17:c]
FORGED_SENDER (0) [dcihon@gmx.com,dcihon@gmail.com]
FROM_HAS_DN (0)
MIME_TRACE (0) [0:+,1:+,2:~]
TAGGED_FROM (0) [caf_=danc=dccathomecom]
RCVD_IN_DNSWL_NONE (0) [209.85.214.180:from]
RCPT_MAILCOW_DOMAIN (0) [dccathome.com]
FROM_NEQ_ENVFROM (0) [dcihon@gmx.com,dcihon@gmail.com]
RECEIVED_SPAMHAUS_PBL (0) [97.106.130.170:received]
FREEMAIL_TO (0) [gmail.com]`

Here is what I see in postfix:
postfix-mailcow-1 | Sep 20 14:37:31 b1cad95c9193 postfix/postscreen[5258]: CONNECT from [209.85.214.180]:58501 to [172.22.1.253]:25 postfix-mailcow-1 | Sep 20 14:37:31 b1cad95c9193 postfix/postscreen[5258]: ALLOWLISTED [209.85.214.180]:58501 postfix-mailcow-1 | Sep 20 14:37:31 b1cad95c9193 postfix/smtpd[5261]: connect from mail-pl1-f180.google.com[209.85.214.180] postfix-mailcow-1 | Sep 20 14:37:31 b1cad95c9193 postfix/smtpd[5261]: Anonymous TLS connection established from mail-pl1-f180.google.com[209.85.214.180] to mail.dccathome.com: TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (4096 bits) server-digest SHA256 postfix-mailcow-1 | Sep 20 14:37:32 b1cad95c9193 postfix/smtpd[5261]: 2BF09204121: client=mail-pl1-f180.google.com[209.85.214.180] postfix-mailcow-1 | Sep 20 14:37:32 b1cad95c9193 postfix/cleanup[5263]: 2BF09204121: message-id=<0BAFA45B-9B4B-45EE-999B-3BFABE1D877F@edison.tech> postfix-mailcow-1 | Sep 20 14:37:32 b1cad95c9193 postfix/cleanup[5263]: 2BF09204121: prepend: header Content-Transfer-Encoding: quoted-printable from mail-pl1-f180.google.com[209.85.214.180]; from=<dcihon+caf_=danc=dccathome.com@gmail.com> to=<danc@dccathome.com> proto=ESMTP helo=<mail-pl1-f180.google.com>: List-Unsubscribe: mailto:<contact@mydomain.com>?subject=unsubscribe>" postfix-mailcow-1 | Sep 20 14:37:32 b1cad95c9193 postfix/cleanup[5263]: 2BF09204121: prepend: header Content-Transfer-Encoding: quoted-printable from mail-pl1-f180.google.com[209.85.214.180]; from=<dcihon+caf_=danc=dccathome.com@gmail.com> to=<danc@dccathome.com> proto=ESMTP helo=<mail-pl1-f180.google.com>: List-Unsubscribe: mailto:<contact@mydomain.com>?subject=unsubscribe>" postfix-mailcow-1 | Sep 20 14:37:34 b1cad95c9193 postfix/cleanup[5263]: 2BF09204121: milter-reject: END-OF-MESSAGE from mail-pl1-f180.google.com[209.85.214.180]: 5.7.1 This message does not meet our delivery requirements; from=<dcihon+caf_=danc=dccathome.com@gmail.com> to=<danc@dccathome.com> proto=ESMTP helo=<mail-pl1-f180.google.com> postfix-mailcow-1 | Sep 20 14:37:34 b1cad95c9193 postfix/smtpd[5261]: disconnect from mail-pl1-f180.google.com[209.85.214.180] ehlo=2 starttls=1 mail=1 rcpt=1 data=0/1 quit=1 commands=6/7

esackbauer

maybl8 if it comes from the forward at gmail I don’t get it.

Forwarding is your issue here. Gmail is not entitled per SPF record to forward mails from non-gmail domains.
Forwarding is in general bad practice.
In SOGo I would configure your gmail mailbox as additional source under settings - imap accounts, or configure gmail account in your desktop/Mobile mail client additionally.

maybl8

How can I get some help with this? Seems like no one wants to touch this.

maybl8

I’ve determined that I have to find out what emails are failing to this and whitelist them.
Problem is it won’t give me details except in gmail if I am watching it happen at the time.
I wish there was an easier way to do this.

maybl8

esackbauer
I don’t have it in Sogo but I do have it in a phone client and in Thunderbird on my pc.
Why I wanted to forward was my gmail is running out of space and I wanted to start forward and delete gmail account. I guess I could just move all the mail to Sogo and delete gmail manually.
Thanks

esackbauer

Use Imapsync for that to get all your gmail into mailcow.
https://docs.mailcow.email/post_installation/firststeps-sync_jobs_migration/

maybl8

esackbauer
Ok will it create folders for the gmail making it separate from my existing domain mail?
Will it create the gmail folders that already exist in gmail?
Will it bring sent items also?
Will it bring attachments over that are in the emails?
Thanks

esackbauer

maybl8 Ok will it create folders for the gmail making it separate from my existing domain mail?

If you define a folder in the imapsync job, yes

maybl8 Will it create the gmail folders that already exist in gmail?

Yes, under the folder you defined in the job.

maybl8 Will it bring sent items also?

yes

maybl8 Will it bring attachments over that are in the emails?

of course.

maybl8

esackbauer
Is there something else I need to do for gmail?
No matter what I try it gives me this error.
I KNOW the password is correct!

Docker context detected with the file /.dockerenv
No log by default in Docker context. Use --log to trigger logging to the logfile.
Changing current directory to /var/tmp/uid_65534
Here is imapsync 2.178 on host fda4a321b2ab, a linux system with 15.2/31.2 free GiB of RAM
with Perl 5.38.2 and Mail::IMAPClient 3.43
Transfer started at Saturday  5 October 2024-10-05 09:24:05 -0400 EDT
PID is 426476 my PPID is 426458
No log file because of option --nolog
Load is 1.91 1.08 0.97 4/1528 on 2 cores
Current directory is /var/tmp/uid_65534
Real user id is nobody (uid 65534)
Effective user id is nobody (euid 65534)
$RCSfile: imapsync,v $ $Revision: 2.178 $ $Date: 2022/01/12 21:28:37 $ 
Command line used, run by perl:
/usr/local/bin/imapsync --tmpdir /tmp --nofoldersizes --addheader --exclude (?i)spam|(?i)junk --subfolder2 Gmail --delete2duplicates --subscribeall --automap --ssl1 --host1 imap.gmail.com --user1 dcihon@gmail.com --passfile1 /tmp/imapsync.UOEq187 --port1 993 --host2 localhost --user2 danc@dccathome.com*r2s8jgoobzwz45jx@mailcow.local --passfile2 /tmp/imapsync.y_lZ9hy --no-modulesversion --noreleasecheck
Temp directory is /tmp ( to change it use --tmpdir dirpath )
Under docker context so installing only signals to exit
kill -INT 426476 # special behavior: call to sub catch_exit
kill -QUIT 426476 # special behavior: call to sub catch_exit
kill -TERM 426476 # special behavior: call to sub catch_exit
No variable pid_filename
PID file is unset ( to set it, use --pidfile filepath ; to avoid it use --pidfile "" )
Info: will resync flags for already transferred messages. Use --noresyncflags to not resync flags.
Host2: probing ssl on port 993 ( use --nosslcheck to avoid this ssl probe ) 
Host2: sslcheck detected open ssl port 993 so turning ssl on (use --nossl2 --notls2 to turn off SSL and TLS wizardry)
SSL debug mode level is --debugssl 1 (can be set from 0 meaning no debug to 4 meaning max debug)
Host1: SSL default mode is like --sslargs1 "SSL_verify_mode=0", meaning for host1 SSL_VERIFY_NONE, ie, do not check the certificate server.
Host1: Use --sslargs1 SSL_verify_mode=1 to have SSL_VERIFY_PEER, ie, check the certificate server of host1
Host2: SSL default mode is like --sslargs2 "SSL_verify_mode=0", meaning for host2 SSL_VERIFY_NONE, ie, do not check the certificate server.
Host2: Use --sslargs2 SSL_verify_mode=1 to have SSL_VERIFY_PEER, ie, check the certificate server of host2
Info: will act as --uidexpunge2
Info: turned ON syncinternaldates, will set the internal dates (arrival dates) on host2 same as host1.
Host1: will try to use LOGIN authentication on host1
Host2: will try to use LOGIN authentication on host2
Host1: imap connection timeout is 120 seconds
Host2: imap connection timeout is 120 seconds
Host1: imap connection keepalive is on on host1. Use --nokeepalive1 to disable it.
Host2: imap connection keepalive is on on host2. Use --nokeepalive2 to disable it.
Host1: IMAP server [imap.gmail.com] port [993] user [dcihon@gmail.com]
Host2: IMAP server [localhost] port [993] user [danc@dccathome.com*r2s8jgoobzwz45jx@mailcow.local]
Host1: connecting and login on host1 [imap.gmail.com] port [993] with user [dcihon@gmail.com]
Host1 IP address: 74.125.139.108
Host1 banner: * OK Gimap ready for requests from 97.106.130.170 m16mb71852825vsg
Host1 capability before authentication: IMAP4rev1 UNSELECT IDLE NAMESPACE QUOTA ID XLIST CHILDREN X-GM-EXT-1 XYZZY SASL-IR AUTH=XOAUTH2 AUTH=PLAIN AUTH=PLAIN-CLIENTTOKEN AUTH=OAUTHBEARER AUTH
Host1 info: authmech [LOGIN] user [dcihon@gmail.com] authuser [] IsUnconnected []
Host1 failure: Error login on [imap.gmail.com] with user [dcihon@gmail.com] auth [LOGIN]: 2 NO [AUTHENTICATIONFAILED] Invalid credentials (Failure)
Host1: failed login on [imap.gmail.com] with user [dcihon@gmail.com] auth [LOGIN]
Host2: connecting and login on host2 [localhost] port [993] with user [danc@dccathome.com*r2s8jgoobzwz45jx@mailcow.local]
Host2 IP address: ::1
Host2 banner: * OK [CAPABILITY IMAP4rev1 SASL-IR LOGIN-REFERRALS ID ENABLE IDLE LITERAL+ AUTH=PLAIN AUTH=LOGIN] Dovecot ready.
Host2 capability before authentication: IMAP4rev1 SASL-IR LOGIN-REFERRALS ID ENABLE IDLE LITERAL+ AUTH=PLAIN AUTH=LOGIN AUTH
Host2: localhost says it has CAPABILITY for AUTHENTICATE LOGIN
Host2: success login on [localhost] with user [danc@dccathome.com*r2s8jgoobzwz45jx@mailcow.local] auth [LOGIN] or [LOGIN]
++++ Listing 1 errors encountered during the sync ( avoid this listing with --noerrorsdump ).
Err 1/1: Host1 failure: Error login on [imap.gmail.com] with user [dcihon@gmail.com] auth [LOGIN]: 2 NO [AUTHENTICATIONFAILED] Invalid credentials (Failure)
The most frequent error is ERR_AUTHENTICATION_FAILURE_USER1. Check the credentials for dcihon@gmail.com.
Exiting with return value 161 (EXIT_AUTHENTICATION_FAILURE_USER1) 1/50 nb_errors/max_errors PID 426476
Disconnecting from host2 localhost user2 danc@dccathome.com*r2s8jgoobzwz45jx@mailcow.local
No log file because of option --nolog

esackbauer

That is normal behaviour.
According to this you must use an app password and 2FA for your gmail account, or use xoauth2

maybl8

esackbauer
I didn’t have to do any of this with my Thunderbird or phone email clients.
I don’t use 2 Factor on gmail account and I believe thunderbird uses the xoauth2 but I didn’t do anything to make it work.

esackbauer

maybl8 I didn’t have to do any of this with my Thunderbird or phone email clients.

Why don’t you move/copy all mails with Thunderbird then?