StarKev2525's questions

We are trying to find a good way to disconnect SSH sessions to our servers when users are leaving their SSH sessions connected when they go home for the day. The SSHD timeout settings (ClientAliveInterval 300, ClientAliveCountMax 0) are not disconnecting the users, as the users have set SecureCRT to "Send protocol NO-OP" every 60 seconds. Therefore the ssh server sees the session as not being idle.

Is there any way to get the SSH server to ignore the NO-OP commands, or another way to timeout/end sessions when there has been no other input from the user?

Thanks

We have a service that we offer to one of our clients that sends statements to their clients. Unfortunately, our customer's validation of email addresses isn't always the best, so when they submit a batch to us to send we usually see a lot of emails that fail to send due to misspellings of common domains (ex. gnail.com, htmail.com, etc.). We collect the bounce backs to give to our client to fix their email list, but until that bounce back/NDR occurs, these messages remain in our postfix mailq until they reach the queue expiry time. Retrying to send again and again.

Is there any good way to have postfix send an NDR for these messages immediately on the first failure instead of trying again and again? We only want this to happen to bad domains though, sometimes, we see messages deferred due to greylisting, and they go out on the second attempt.

I have tried out my Google-foo, but it seems to be failing me in this task...