also sprach Gunnar Wolf <gw...@gwolf.org> [2010.05.26.1530 +0200]:
> I cannot say this behaviour is wrong. Swaks cannot decide where to
> connect to. Quoting from source (line ~1766):

Huh? I am asking it to connect to port 587-g, which is silly. It
cannot do that. So it should exit with an error, rather than flood
me with errors.

Note that this has nothing to do with stdin, it seems:

  echo -e '1\n2\n3' | swaks -s localhost -p doesnotexist -g
  [… endless errors …]

So I think swaks should output a single error, rather than to enter
an endless loop.

>     # in here, the user has either specified a port, or that they _want_
>     # to, so if it isn't a resolvable port, ,keep prompting for another one

If -p came without an argument, then the user /might/ want to be
prompted, this is what the manpage suggests:

  Specify which TCP port on the target is to be used, or prompt if
  no argument is listed.

In the face of an unusable argument, however, I think swaks is
trying to be a little too smart or forgiving if it then prompts.

Also, given that I passed -g, I told swaks that I want to use stdin
for something else, not the port.

-- 
 .''`.   martin f. krafft <madd...@d.o>      Related projects:
: :'  :  proud Debian developer               http://debiansystem.info
`. `'`   http://people.debian.org/~madduck    http://vcs-pkg.org
  `-  Debian - when you have better things to do than fixing systems
 
one has to multiply thoughts to the point
where there aren't enough policemen to control them.
                                               -- stanislaw jerzey lec

Attachment: digital_signature_gpg.asc
Description: Digital signature (see http://martin-krafft.net/gpg/)

Reply via email to