public inbox for cygwin@cygwin.com
 help / color / mirror / Atom feed
From: Brian Inglis <Brian.Inglis@SystematicSw.ab.ca>
To: cygwin@cygwin.com
Cc: Priyanka Joshi <Priyanka.Joshi@bhnetwork.com>
Subject: Re: Issue with email -a (Zip files)
Date: Thu, 30 Jan 2020 21:56:00 -0000	[thread overview]
Message-ID: <c95bb418-bf80-1768-3732-82aa75a1a03b@SystematicSw.ab.ca> (raw)
In-Reply-To: <BN8PR18MB2673C215B777949D20B633258F040@BN8PR18MB2673.namprd18.prod.outlook.com>

On 2020-01-30 02:21, Priyanka Joshi wrote:
> I am facing issue when I am trying to send zip file as attachment, same 
> command works fine for xml file.
> 
> PFB commands for reference:
> 
> Below command worked fine and sent testng.xml as attachment
> email -s "BHN Test Automation Report" -a testng.xml priyanka.joshi@bhnetwork.com
> 
> email -s "BHN Test Automation Report" -a allure-report.zip priyanka.joshi@bhnetwork.com
> ==> Not triggering any email and not throwing any error.
>
> Please let us know how to debug and fix the zip attachment issue.

Cygwin email requires -b option flag, body text on stdin, or invokes your editor
for body text entry to send emails.
First, check location, version, and test:

	$ which email
	/usr/bin/email
	$ email --version
	email - By Dean Jones; Version 3.2.3-git
	$ email -b -s "Test zip send" -a Downloads/....zip above-email-address

worked for me, with a random downloaded small zip file, also worked whether I
echoed or redirected text into stdin, or did neither and typed body text into
the editor window opened on a tmp file.

Corporate networks often have filters and strict rules about what may be
included in a zip file, may be both outgoing and incoming; they could even have
Outlook, other email client, or generic email filters on your desktop system.
Talk to your IT mail and security admins to find out what is filtered where.
Try renaming the zip file as if xml or something safe, and see if that works,
and if not, try putting your xml in a zip file, and see if that works.

-- 
Take care. Thanks, Brian Inglis, Calgary, Alberta, Canada

This email may be disturbing to some readers as it contains
too much technical detail. Reader discretion is advised.

--
Problem reports:       http://cygwin.com/problems.html
FAQ:                   http://cygwin.com/faq/
Documentation:         http://cygwin.com/docs.html
Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple

  reply	other threads:[~2020-01-30 21:56 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-01-30  9:21 Priyanka Joshi
2020-01-30 21:56 ` Brian Inglis [this message]
2020-01-31  6:40   ` Priyanka Joshi
2020-01-31 13:55     ` Brian Inglis

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=c95bb418-bf80-1768-3732-82aa75a1a03b@SystematicSw.ab.ca \
    --to=brian.inglis@systematicsw.ab.ca \
    --cc=Priyanka.Joshi@bhnetwork.com \
    --cc=cygwin@cygwin.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).