Lighthouse has a new layout. Prefer the old one? Return to the old layout, and switch back any time from the link at the top of each page.

From field from emate

#786

I'm trying to use the command line tool to set up some default emails (I'd like to use different Alfred keywords to create new emails pre-populated in different ways).

The -f "from" flag is giving me trouble. I get a new mail window pre-populated with the desired address in the From menu, but then when I hit send, MailMate tries to send it based on SMTP settings of what it seems would have been the default address if I'd created the new email window manually.

I've tried to test some different options and I believe the following description should be reproducible. If the details turn out to be inaccurate, the simplest way I can express the problem is that the -f flag from the command line doesn't seem to change the SMTP settings for a new message the same way selecting a new From address in the new message window would.

I have 6 email accounts set up, but I'll just use a Gmail account, an iCloud account, and a Fastmail account for demonstration.

So, for example, if I'm viewing the inbox for a Gmail account I'm using, and trigger a new mail with -f set to my Fastmail account, I can send the email, its headers will show "From: ", but it seems it will appear in my Sent folder for the Gmail account, not the Fastmail account. Similarly, if I'm viewing the inbox for my iCloud account and try to trigger an email sent from my Gmail account to my Fastmail account, I get this error:

Unexpected return code 550 (expected 250):
“5.7.0 From address is not one of your addresses.”.

Presumably the SMTP settings on iCloud are more strict than for Gmail…

(I started with AppleScript and had the same problem using the from= parameter on the mailto: URL from AppleScript.)

Reported by Brian Jones · May 22nd, 2014 @ 01:39 PM

State: fixreleased
Milestone: none
Assigned to: benny benny

Activity

  1. benny
    benny
    • State changed from new to fixcommitted

    Thanks, I wasn't aware of this bug. I believe I've fixed it now and it'll be part of the next update.

    May 23rd, 2014 @ 01:53 PM

  2. benny
    benny

    You can test the fix with this version of MailMate: http://updates.mailmate-app.com/archives/MailMate_r4249.tbz

    Note that this version might be unstable for other reasons (some major changes to other parts of the code only tested by myself).

    May 23rd, 2014 @ 08:25 PM

  3. Des Dougan
    Des Dougan

    I hit the same problem today - the most recent build works fine. I did find a couple of things that you may want to be aware of.

    Firstly, when I ran emate from the command line I got a python error - it turned out I had installed MacPorts years ago, and it had updated my .bash_profile, causing emate to fail, as the python version wasn’t 2.7. Editing the profile file resolved that.

    The second is that running emate leaves a copy of the message in the Drafts folder - not sure if that's a bug or a feature?

    Regards,

    Des

    July 20th, 2014 @ 01:05 AM

  4. benny
    benny

    @Des: Thanks, I've hardcoded the script to use /usr/bin/python2.7 now. I don't seem to be able to reproduce the duplicate-issue. It's not a feature. Are you sure this is related to emate and not a general problem of the account?

    Make sure you do not use the directly linked version above. Instead hold down ⌥ when clicking “Check Now” in the Software Update preferences pane (if you haven't already done so).

    July 30th, 2014 @ 09:50 AM

  5. benny
    benny
    • State changed from fixcommitted to fixreleased

    October 15th, 2014 @ 03:32 PM

  6. benny
    benny

    December 25th, 2024 @ 04:11 PM

Please Sign in or create a free account to add a new ticket.

With your very own profile, you can contribute to projects, track your activity, watch tickets, receive and update tickets through your email and much more.