Since upgrade to V 10 my message rules no longer sort incoming mail into folders. I adjusted order of rules to see if that helps - moved spam rule down in the list of rules.Do i need to delete and re-enter rules? Or is this a glitch related to “Primary” “Other” sorting?
Also we can no longer send emails through our local Exchange server. We get the following SMTP error:
“[SMTP] SMTP server didn’t like our greetings and replied with: 5.5.4 Invalid Address”
We have local POP emails that go to an address “xxxx.local”
This address no longer functions on outgoing mail only with V 10.
Incoming still works fine.
Same problem with rules after upgrade to v10. Re-entering the rules does not help.
The rules work if they are started manually. (Right-klick on folder inbox, rules …) So it seems that the option “start rule when receiving mail” does not work …
I have this issue as well. Sometimes the messages do get moved, sometimes they do not. Applying the filter manually does work and they always worked in version 9.
English:
Have the same problem. Rules does not apply when receiving mail. Have apply manually.
French:
J’ai le même problème . Les règles ne s’appliquent pas automatiquement lors de la réception des messages. Je dois appliquer les règles manuellement.
Since upgrade to V 10 my message rules no longer sort incoming mail into folders. I adjusted order of rules to see if that helps - moved spam rule down in the list of rules.Do i need to delete and re-enter rules? Or is this a glitch related to “Primary” “Other” sorting?
There is other reports in various threads of move to folder rules no longer automatically working on startup in V10 and only working either “after the program is open” or if you manually run them.
So sounds like an update to eM Client is needed. So if you haven’t already try the latest V10.0.3351 from the release history page or otherwise you might need to wait for the new update which hopefully won’t be far away.
If the current update doesn’t fix it, then you could eg: Try disabling Categories completely and see if your move to folder rules on startup work again. But I personally don’t think it’s anything to do with the new V10 Categories and more of a bug.
However if your automatic move to folder rules “then do work on startup without Categories enabled”, then update this thread.
We can no longer send emails through our local Exchange server. We get the following SMTP error:
“[SMTP] SMTP server didn’t like our greetings and replied with: 5.5.4 Invalid Address
That’s usually something either “in the sending email header” or “sender name” etc within the email and the SMTP server then rejects it.
So If this is happening with every sent email via your exchange server “and the SMTP server settings are the same as you had in eM Client V9”, then I would contact your SMTP server technical support and let them know your sent emails are being rejected with that specific error message.
You might then need to send them an example email that was rejected via webmail so they can determine why it’s getting rejected.
We see similar messages on the server if the Emclient tries to establish an SMTP connection.
But why should the server configuration be changed if the Emclient V10 is no longer able to register properly with the server?
All other mail clients do not make bitches.
EM Client V9 in the identical environment and with identical account data and settings do not cause any problems.
I can add this from the Postfix Log as follows:
Aug 5 11:12:07 {mailserver} postfix/smtpd[11353]: > {client_hostname}[{IPv4}]: 220 {mailserver} ESMTP Postfix
Aug 5 11:12:07 {mailserver} postfix/smtpd[11353]: watchdog_pat: 0x557267352590
Aug 5 11:12:07 {mailserver} postfix/smtpd[11353]: vstream_fflush_some: fd 23 flush 35
Aug 5 11:12:07 {mailserver} postfix/smtpd[11353]: vstream_buf_get_ready: fd 23 got 11
Aug 5 11:12:07 {mailserver} postfix/smtpd[11353]: < {client_hostname}[{IPv4}]: A1 LOGOUT
Aug 5 11:12:07 {mailserver} postfix/smtpd[11353]: match_string: A1 ~? CONNECT
Aug 5 11:12:07 {mailserver} postfix/smtpd[11353]: match_string: A1 ~? GET
Aug 5 11:12:07 {mailserver} postfix/smtpd[11353]: match_string: A1 ~? POST
Aug 5 11:12:07 {mailserver} postfix/smtpd[11353]: match_list_match: A1: no match
Aug 5 11:12:07 {mailserver} postfix/smtpd[11353]: report unknown command to all milters
Aug 5 11:12:07 {mailserver} postfix/smtpd[11353]: milter8_unknown_event: milter unix:/var/run/opendkim/milter: unknown command: A1
Aug 5 11:12:07 {mailserver} postfix/smtpd[11353]: event: SMFIC_UNKNOWN; macros: (none)
Aug 5 11:12:07 {mailserver} postfix/smtpd[11353]: skipping event SMFIC_UNKNOWN for milter unix:/var/run/opendkim/milter
Aug 5 11:12:07 {mailserver} postfix/smtpd[11353]: > {client_hostname}[{IPv4}]: 502 5.5.2 Error: command not recognized
Aug 5 11:12:07 {mailserver} postfix/smtpd[11353]: watchdog_pat: 0x557267352590
Aug 5 11:12:07 {mailserver} postfix/smtpd[11353]: vstream_fflush_some: fd 23 flush 41
Aug 5 11:12:08 {mailserver} postfix/smtpd[11353]: smtp_get: EOF
Aug 5 11:12:13 {mailserver} postfix/smtpd[11349]: warning: {client_hostname}[{IPv4}]: SASL GSSAPI authentication failed:
Aug 5 11:12:13 {mailserver} postfix/smtpd[11350]: warning: {client_hostname}[{IPv4}]: SASL GSSAPI authentication failed:
Aug 5 11:12:20 {mailserver} postfix/smtpd[9637]: warning: problem talking to server private/anvil: Success
Aug 5 11:12:27 {mailserver} dovecot: lmtp(11407): Connect from local