On May 11, 2014, at 10:37 PM, Rajeev S wrote:
>I doubt the usability of a common option `name`. As per the above snippet,
>you have used a `in-domain` to specify the domain name. There are many such
>instances where you would have to use more than one `name`, for instance
>adding moderators for a
On May 11, 2014, at 10:37 PM, Rajeev S wrote:
>I have modified the CLI to use English like commands and hence will
>use them hereafter.
>
>*list*
>
>The command lists the entities and should be available for users,mailing
>lists and domains.
>
>mmclient list list [[email protected]] [-v for verbose]
Barry Warsaw writes:
> Also as a general rule, I think we want just one level of
> subcommand, so that `mmclient show --list` would be the template.
> (That's open to discussion.)
I wonder about this in the context of argparse and the command line,
because argparse makes a strong distinction (
Hi,
I don't manage to figure out how to keep the same
Content-Transfer-Encoding, while rewriting the content?
msg.set_payload() doesn't seems to trigger any encoding, base64 for
example was set.
not using decode=True, return a base64 bloc… I just want to write it back.
I should be able to k
On 05/12/2014 09:03 AM, Sylvain Viart wrote:
>
> I don't manage to figure out how to keep the same
> Content-Transfer-Encoding, while rewriting the content?
Do you really want that? That's not what your example code does.
> msg.set_payload() doesn't seems to trigger any encoding, base64 for
>
