Messages still in queue even after 5xx reply

Hi. In my postfix queue I can see messages with return code 5xx which are still in queue for delivery. I find this strange, as the RFC 2821 states that codes starting with 5xx is a permanent failure, and "The SMTP client is discouraged from repeating the exact request". Is this default behavior

Re: Messages still in queue even after 5xx reply

Am 16.11.2013 11:21, schrieb Erik Grøtnes: > Hi. > > In my postfix queue I can see messages with return code 5xx which are > still in queue for delivery. > > I find this strange, as the RFC 2821 states that codes starting with 5xx > is a permanent failure, and “The SMTP client is discouraged from

Re: Messages still in queue even after 5xx reply

Erik Gr?tnes: > Why is postfix still trying to deliver these messages? Can this > behavior be changed by configuration? The default behavior is to bounce. You changed it. $ grep soft_bounce /etc/postfix/* Wietse

Re: Changing the outgoing hostname in message headers

Paul C: > Simon is correct, you must use multi instances, they are pretty simple to > deal with, you run a few commands to create the instances, each one will > have its own config directory with main.cf and master.cf, you can direct > mail based on the incoming ip used to connect, inet_interfaces,

reject_sender_login_mismatch problem

Hi all :-) I configurated postfix to check if a client is within the smtpd_sender_login_maps = hash:/etc/postfix/smtpd_sender_login_maps with sasl sender authentication, and: smtpd_recipient_restrictions = permit_mynetworks, permit_inet_interfaces, reject_sender_login_mis

Re: reject_sender_login_mismatch problem

Am 16.11.2013 19:44, schrieb Pol Hallen: > Hi all :-) I configurated postfix to check if a client is within the > > smtpd_sender_login_maps = hash:/etc/postfix/smtpd_sender_login_maps > > with sasl sender authentication, and: > > smtpd_recipient_restrictions = > permit_mynetworks, >

Re: reject_sender_login_mismatch problem

alias_database = hash:/etc/aliases alias_maps = hash:/etc/aliases anvil_rate_time_unit = 10s anvil_status_update_time = 120s append_dot_mydomain = no biff = no broken_sasl_auth_clients = yes config_directory = /etc/postfix delay_warning_time = 10m disable_vrfy_command = yes helpful_warnings = yes h

Re: reject_sender_login_mismatch problem

and where is the complete log of the message you are speaking about in your initial post? you are long enough here to know how debugging works and how it can't work > mydestination = fuckaround what's that? this is not a domain Am 16.11.2013 19:54, schrieb Pol Hallen: > alias_database = hash:/et

Re: reject_sender_login_mismatch problem

On 11/16/2013 12:44 PM, Pol Hallen wrote: > Hi all :-) I configurated postfix to check if a client is within the > > smtpd_sender_login_maps = hash:/etc/postfix/smtpd_sender_login_maps > > with sasl sender authentication, and: > > smtpd_recipient_restrictions = > permit_mynetworks, >

Re: reject_sender_login_mismatch problem

> Perhaps you can use reject_authenticated_sender_login_mismatch instead. > http://www.postfix.org/postconf.5.html#reject_authenticated_sender_login_mismatch Yeah! Thanks Jones :-) Solved! Pol

RE: Changing the outgoing hostname in message headers

Thank you, men. I confess that my Postfix skills weren't up to handling multiple instances or master.cf hacking, but we did have another domain sitting idle which now serves as the bland mailserver hostname. Its presence in the mail headers won't cause problems for any of the three companies.