Username:
TITLE
auto-reply in dovecot & horde based webmail not working properly
PRODUCT, VERSION, OPERATING SYSTEM, ARCHITECTURE
Plesk 18.0.50 #1, AlmaLinux 8.7 latest updates
PROBLEM DESCRIPTION
When auto-reply / vacation filter is turned on in webmail, the auto-reply mail is generated and sent in such a way that some receiving servers refuse the auto-reply mail. See details under additional info below.
STEPS TO REPRODUCE
set up email account and webmail. Choose either Dovecot or Horde. Set up an auto-reply / vacation response and have it active. Send a mail from a gmail (or yahoo) address to the account that has the auto-response active.
ACTUAL RESULT
No auto-reply mail is received on the gmail or yahoo account.
EXPECTED RESULT
Auto-reply is received.
ANY ADDITIONAL INFORMATION
- SPF, DMARC, DKIM all set up perfectly for the domain
- If auto-reply is set up in the domains control panel, it works flawless. So is limited to webmail only.
- We use PES on all server. May or may not play a role.
- Have tested it across three servers. All servers exhibit same behaviour.
Incoming Mails from other Plesk servers do get auto replies. Mails originating from a different domain on the same Plesk server also get an auto response. Mail from an outlook.com address get the auto-reply.
But incoming mails from gmail or yahoo for example do not get the auto-reply.
The attempted auto-reply to the yahoo email address produced an error:
23E0743443: to=<[email protected]>, relay=mta5.am0.yahoodns.net[67.195.228.109]:25, delay=3.1, delays=0.53/0.02/1.4/1.2, dsn=5.7.9, status=bounced (host mta5.am0.yahoodns.net[67.195.228.109] said: 554 5.7.9 Message not accepted for policy reasons. See https://postmaster.yahooinc.com/error-codes (in reply to end of DATA command))
As the auto reply when set up in the control panel works perfect, but the one in webmail does not (to certain servers) it appears/indicates that the one generated (and/or sent) from webmail does not use some or all of the security measures available and is thus blocked.
YOUR EXPECTATIONS FROM PLESK SERVICE TEAM
Confirm bug
TITLE
auto-reply in dovecot & horde based webmail not working properly
PRODUCT, VERSION, OPERATING SYSTEM, ARCHITECTURE
Plesk 18.0.50 #1, AlmaLinux 8.7 latest updates
PROBLEM DESCRIPTION
When auto-reply / vacation filter is turned on in webmail, the auto-reply mail is generated and sent in such a way that some receiving servers refuse the auto-reply mail. See details under additional info below.
STEPS TO REPRODUCE
set up email account and webmail. Choose either Dovecot or Horde. Set up an auto-reply / vacation response and have it active. Send a mail from a gmail (or yahoo) address to the account that has the auto-response active.
ACTUAL RESULT
No auto-reply mail is received on the gmail or yahoo account.
EXPECTED RESULT
Auto-reply is received.
ANY ADDITIONAL INFORMATION
- SPF, DMARC, DKIM all set up perfectly for the domain
- If auto-reply is set up in the domains control panel, it works flawless. So is limited to webmail only.
- We use PES on all server. May or may not play a role.
- Have tested it across three servers. All servers exhibit same behaviour.
Incoming Mails from other Plesk servers do get auto replies. Mails originating from a different domain on the same Plesk server also get an auto response. Mail from an outlook.com address get the auto-reply.
But incoming mails from gmail or yahoo for example do not get the auto-reply.
The attempted auto-reply to the yahoo email address produced an error:
23E0743443: to=<[email protected]>, relay=mta5.am0.yahoodns.net[67.195.228.109]:25, delay=3.1, delays=0.53/0.02/1.4/1.2, dsn=5.7.9, status=bounced (host mta5.am0.yahoodns.net[67.195.228.109] said: 554 5.7.9 Message not accepted for policy reasons. See https://postmaster.yahooinc.com/error-codes (in reply to end of DATA command))
As the auto reply when set up in the control panel works perfect, but the one in webmail does not (to certain servers) it appears/indicates that the one generated (and/or sent) from webmail does not use some or all of the security measures available and is thus blocked.
YOUR EXPECTATIONS FROM PLESK SERVICE TEAM
Confirm bug