search for: submission_backend_capabilities

...t the documentation says, dovecot don't try to connect to the backend until the user is properly logged. In my raw log I show that after I logged in dovecot-submission, the later open a connection to the backend and send a X-CLIENT command. Now, if I try to force the capabilities by using: submission_backend_capabilities = VRFY 8BITMIME DSN dovecot properly reports all SMTP capabilities in the first EHLO response, but it completely stops emitting X-CLIENT command to the backend and try to simply forward the command without authentication, which result in postfix rejecting the command with an unauthorized user err...

...the backend until the user is properly logged. >> >> In my raw log I show that after I logged in dovecot-submission, the later open a connection to the backend and send a X-CLIENT command. >> >> >> Now, if I try to force the capabilities by using: >> >> submission_backend_capabilities = VRFY 8BITMIME DSN >> >> dovecot properly reports all SMTP capabilities in the first EHLO response, but it completely stops emitting X-CLIENT command to the backend >> and try to simply forward the command without authentication, which result in postfix rejecting the command wit...

...ar *hostname; const char *login_greeting; const char *login_trusted_networks; /* submission: */ size_t submission_max_mail_size; unsigned int submission_max_recipients; const char *submission_client_workarounds; const char *submission_logout_format; /* submission backend: */ const char *submission_backend_capabilities; /* submission relay: */ const char *submission_relay_host; in_port_t submission_relay_port; bool submission_relay_trusted; const char *submission_relay_user; const char *submission_relay_master_user; const char *submission_relay_password; const char *submission_relay_ssl; bool submissi...

...cot don't try to connect to the backend until the user is properly logged. > > In my raw log I show that after I logged in dovecot-submission, the later open a connection to the backend and send a X-CLIENT command. > > > Now, if I try to force the capabilities by using: > > submission_backend_capabilities = VRFY 8BITMIME DSN > > dovecot properly reports all SMTP capabilities in the first EHLO response, but it completely stops emitting X-CLIENT command to the backend > and try to simply forward the command without authentication, which result in postfix rejecting the command with an unauthor...

...rly logged. Oh, then we need to adjust the documentation. This is normal behavior. > In my raw log I show that after I logged in dovecot-submission, the later open a connection to the backend and send a X-CLIENT command. > > > Now, if I try to force the capabilities by using: > > submission_backend_capabilities = VRFY 8BITMIME DSN > > dovecot properly reports all SMTP capabilities in the first EHLO response, but it completely stops emitting X-CLIENT command to the backend > and try to simply forward the command without authentication, which result in postfix rejecting the command with an unauthor...

Hello all, I'm attempting to implement a submission server with questions in regards to how Dovecot handles the backend hosts capabilities. To my understanding, Dovecot will connect to the host specified in either submission_host or submission_relay_host, and gather a list of capabilities. Once gathered, after the client sends the EHLO greeting Dovecot will respond back with capabilities

Looking further into this segfault at settings-parser.c:setting_copy():1519 *dest_size = *src_size; *src_size points to type size_t (typedef unsigned long), a 4-byte aligned value consistent with a 32-bit build. This is mismatched with declared type (gdb) whatis src_size type = const uoff_t * (gdb) whatis uoff_t type = unsigned long long (gdb) p sizeof(uoff_t) $1 = 8 resulting

...logged. >>> >>> In my raw log I show that after I logged in dovecot-submission, the >>> later open a connection to the backend and send a X-CLIENT command. >>> >>> >>> Now, if I try to force the capabilities by using: >>> >>> submission_backend_capabilities = VRFY 8BITMIME DSN >>> >>> dovecot properly reports all SMTP capabilities in the first EHLO >>> response, but it completely stops emitting X-CLIENT command to the >>> backend >>> and try to simply forward the command without authentication, which &gt...

...to work correctly on 32-bit ? systems. - submission: Trusted connections crashed in second connection's EHLO ? if submission-login { service_count } is something else than 1 (which ? is the default). - submission: XCLIENT command was never used in the protocol exchange ? with the relay MTA when submission_backend_capabilities is configured, ? even when the relay MTA was properly configured to accept the XCLIENT ? command. -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 488 bytes Desc: OpenPGP digital signature URL: <https://dove...

...to work correctly on 32-bit ? systems. - submission: Trusted connections crashed in second connection's EHLO ? if submission-login { service_count } is something else than 1 (which ? is the default). - submission: XCLIENT command was never used in the protocol exchange ? with the relay MTA when submission_backend_capabilities is configured, ? even when the relay MTA was properly configured to accept the XCLIENT ? command. -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 488 bytes Desc: OpenPGP digital signature URL: <https://dove...

Hopefully, there is some fix for issue 3 which is beyond my skill to fix. Issue 1) Need recent gcc version Building Dovecot versions <=2.2.x using gcc 3.4.4 worked, but this gcc version fails to build 2.3.x properly: symptoms include compile failures and executable crashes that depended on the amount of optimization used, which is usually a sign of compiler bugs. (It could also be