[sylpheed:36824] Re: Windows - associate sylpheed to right click menu "send to mail recipient"

Joe joe.on.list at gmail.com
Thu Jun 6 03:57:22 JST 2019


Well, the issue is really trivial...
If you want to send a file as attachment, you can do in two ways:

- first way
open your mail client, write your message, set recipient  and subject,
click on attach button, browse your file system untill you have found
the file to attach, and finally send the mail message...

-  second way
open folder that contain file you want to send, right click on it,
select "sen to" and choose mail recipient, this open your mail client
"compose" window with the file you clicked already loaded as
attachment. You have just to complete the blank parts of the message
and then send.

For some people this second way could be simpler than the one...
On my windows seven system it doesn't work:
when I choose send to and then "mail recipient" it says there isn't
any mail program to use, install one mail program or check if your
client is right set at predefined programs system options etc...

Teorically Sylpheed should be in compliance with windows system
mechanisms, and should be recognized as a regular mail client to
choose as your predefined program also for "send to" feature (included
in explorer I think).
But in practice on my system (brand new, re-installed from scratch
just two week ago...) it doesn't seem so recognized for what concern
this "send to" feature.

Did you remember if on your old w7 system the second way attachment
approach worked properly?

On Wed, Jun 5, 2019 at 7:48 PM Gene Goldenfeld <genegold at fastmail.com> wrote:
>
> Perhaps I din’t understand your glitch, but it’s strange that I never encountered this problem in my years with Win 7, which with my laptop only ended a few months ago. Please let us know if you find a solution.
>
> Gene
>
> --
>
>
>
> On Wed, Jun 5, 2019, at 11:34 AM, Joe wrote:
> > I tried, but it doesn't work:
> >
> > -------------
> > Set WshShell = WScript.CreateObject("WScript.Shell")
> > runCmd = "c:\program files (x86)\sylpheed\sylpheed.exe --attach " &
> > WScript.Arguments(0)
> > 'WshShell.Run "cmd /c " & runCmd, 0, True
> > wscript.echo "cmd /c " & runcmd, 0, True
> > ---------------
> >
> > I tired to edit it just to obtain some more debug infos, the final
> > command returns what the script get as argument and how use... it
> > seems ok but sylpheed doesn't appears.
> > I actually save the script directly in "save to" directory... may be
> > that is the problem...
> >
> > Anyway thanks a lot for your hint!
> > Hope with a bit of tries I/we cant solve this issue. Thanks again! :)
> >
> > On Wed, Jun 5, 2019 at 7:03 PM Michael Weiner <spam at cogit.net> wrote:
> > >
> > > OK, that is the key info we needed.
> > >
> > > You can simply insert into the SendTo directory a link to a VBS
> > > file containing the following three lines.
> > >
> > > Set WshShell = WScript.CreateObject("WScript.Shell")
> > > runCmd = "[pathToSylpheed]\sylpheed.exe --attach " & WScript.Arguments(0)
> > > WshShell.Run "cmd /c " & runCmd, 0, True
> > >
> > > In the last line, "0" means hide the command window, and "True" means
> > > that any error codes will be returned.
> > >
> > > This works for just a single attachment, since WScript.Arguments(0) refers
> > > to the first command-line argument.
> > >
> > > Mike
> > >
> > > ________________________________
> > >
> > > On Wed, 5 Jun 2019 18:10:38 +0200, Joe <joe.on.list at gmail.com> wrote:
> > > > On Wed, Jun 5, 2019 at 4:04 PM Michael Weiner <spam at cogit.net> wrote:
> > > > >
> > > > > I believe that the issue is "Send to"-- from the Windows Explorer
> > > > > context menu-- rather than "mailto:". "Mailto:" is easy to fix.
> > > > > "Send to" appears more difficult. I have not found a fix yet.
> > > > > Although one can insert a Windows file shortcut to Sylpheed into
> > > > > the "Send to" directory, sending a file to that shortcut does not
> > > > > attach it to a new message in a composition window. Instead, the
> > > > > Sylpheed viewer window attempts to display the file.
> > > > >
> > > > > The "Send to" directory is listed below.
> > > > >
> > > > > C:\Users\[username]\AppData\Roaming\Microsoft\Windows\SendTo\
> > > >
> > > > Exactly, that is the matter...
> > > >
> > > > I'm a bit surprised nobody of you users tested this problem.Likely
> > > > this list and more in general sylpheed client is not so used by
> > > > windows users... :)
> > > >
> > > > Anyway a quick solution i found is to write a little batch file (.bat
> > > > dos/win script) that call the command:
> > > >
> > > > sylpheed --attach %1
> > > >
> > > > %1 -stand for the first argument the script was passed by explorer
> > > > (when you right-click a file and choose send-to, and then
> > > > mail-recipient, that file is passed to the mail compose program as
> > > > "the first argument").
> > > >
> > > > I experienced that the above script has to be placed in the sylpheed
> > > > install directory:
> > > >
> > > > c:\program files (x86)\sylpeed\batch-file.bat
> > > >
> > > > And then a new link has to be created under "send to" dir:
> > > >
> > > > C:\Users\[username]\AppData\Roaming\Microsoft\Windows\SendTo
> > > > \link-to-batch-file.lnk
> > > >
> > > > I don't know why but it doesn't work if you create a symlink from
> > > > windows shellprompt, you have to open that dir, right click in it,
> > > > and then create new link, choose sylpheed batch file.
> > > > We can also name it as similar to "Mail Recipient" or so on...
> > > >
> > > > Now, if I right click a file (or even more files at once) and choose
> > > >
> > > > "send to" > "Mail Recipient"...
> > > >
> > > > Here we go, sylpheed opens-up its compose window, selected files
> > > > appear attachedto the new message. We can edit recipient, subject
> > > > body an finally send.
> > > >
> > > > Anyway I noticed one other problem linked to this particular solution.
> > > > batch script use to run in a dos window...
> > > > Also in this case, when sylpheed opens up, also a black dos windows
> > > > appears, and persists open. It is not a very clean behavior and I'd
> > > > like to find a work around.
> > > >
> > > > Seems a way could be to write a VB script that call our batch script
> > > > that recallsylpheed command. May be we just need a vbs file only,
> > > > the runs sylpheed commandand pass to it the first argument explorer
> > > > give to it when right click the file to attach.
> > > >
> > > > Is there anybody out there able to write down a VB solution as
> > > > explained? If thanks to my poor english I wasn't clear enough, let me
> > > > know, I'll try to repeat again.
> > > >
> > > > As recap:
> > > > - visual basic script that
> > > > - get the first argument passed by explorer
> > > > - and send this argument (fil we want to attach) to sylpheed command:
> > > >
> > > > c\program files (x86)\sylpheed\sylpheed --attach "$ARGUMENT"
> > > >
> > > >
> > > > I'm a linux user and don't know visual basic at all. I tried to copy
> > > > some example but they didn't work...
> > > >
> > > > I tried to install sylpheed on a pc at office, it is used by some
> > > > windows 7 users (really basic users!).
> > > >
> > > > Anyway, thanks for your replies! :)
> > > > Bye!
> >


More information about the Sylpheed mailing list