Sending messages via email on the dashboard is not working

[saha23412]

I have a component that is responsible for sending messages via email. At some point, it stopped working. As far as I understand, a too‑long string (the generated URL for the chart) is being passed to the mailto field. Do you have any advice on how to fix this?

file path: superset-frontend\src\dashboard\components\menu\ShareMenuItems\index.tsx

import { RefObject } from 'react';
import copyTextToClipboard from 'src/utils/copy';
import { t, logging } from '@superset-ui/core';
import { Menu } from 'src/components/Menu';
import { getDashboardPermalink } from 'src/utils/urlUtils';
import { MenuKeys, RootState } from 'src/dashboard/types';
import { shallowEqual, useSelector } from 'react-redux';

interface ShareMenuItemProps {
  url?: string;
  copyMenuItemTitle: string;
  emailMenuItemTitle: string;
  emailSubject: string;
  emailBody: string;
  addDangerToast: Function;
  addSuccessToast: Function;
  dashboardId: string | number;
  dashboardComponentId?: string;
  copyMenuItemRef?: RefObject<any>;
  shareByEmailMenuItemRef?: RefObject<any>;
  selectedKeys?: string[];
  setOpenKeys?: Function;
  key?: string;
  title: string;
}

const ShareMenuItems = (props: ShareMenuItemProps) => {
  const {
    copyMenuItemTitle,
    emailMenuItemTitle,
    emailSubject,
    emailBody,
    addDangerToast,
    addSuccessToast,
    dashboardId,
    dashboardComponentId,
    key,
    title,
  } = props;

  const { dataMask, activeTabs } = useSelector(
    (state: RootState) => ({
      dataMask: state.dataMask,
      activeTabs: state.dashboardState.activeTabs,
    }),
    shallowEqual,
  );

  async function generateUrl() {
    return getDashboardPermalink({
      dashboardId,
      dataMask,
      activeTabs,
      anchor: dashboardComponentId,
    });
  }

  async function onCopyLink() {
    try {
      await copyTextToClipboard(generateUrl);
      addSuccessToast(t('Copied to clipboard!'));
    } catch (error) {
      logging.error(error);
      addDangerToast(t('Sorry, something went wrong. Try again later.'));
    }
  }

  async function onShareByEmail() {
    try {
      const encodedBody = encodeURIComponent(
        `${emailBody}${await generateUrl()}`,
      );
      const encodedSubject = encodeURIComponent(emailSubject);
      window.location.href = `mailto:?subject=${encodedSubject}&body=${encodedBody}`;
    } catch (error) {
      logging.error(error);
      addDangerToast(t('Sorry, something went wrong. Try again later.'));
    }
  }

  return (
    <Menu.SubMenu title={title} key={key}>
      <Menu.Item key={MenuKeys.CopyLink} onClick={() => onCopyLink()}>
        {copyMenuItemTitle}
      </Menu.Item>
      <Menu.Item key={MenuKeys.ShareByEmail} onClick={() => onShareByEmail()}>
        {emailMenuItemTitle}
      </Menu.Item>
    </Menu.SubMenu>
  );
};

export default ShareMenuItems;

[kgeminicdev]

The URL length probably isn't the problem. generateUrl() doesn't put the dashboard state in the link. It POSTs the filters and tabs to /api/v1/dashboard/<id>/permalink, the backend stores them, and you get back a short URL like https://host/superset/dashboard/p/<key>/. The full mailto: is usually well under 200 characters, so you're nowhere near the ~2000-character limits some clients have.

Things that actually break this:

1. No mail handler. Setting window.location.href = 'mailto:...' never throws. If the OS or browser has no default mail app, nothing happens and you get no error. Paste mailto:test@example.com into the address bar to check.
2. Superset running in an iframe. A sandboxed or cross-origin iframe can block the mailto: navigation. Chrome logs Not allowed to launch 'mailto:...' in the console. If that's you, the embedding iframe needs allow-top-navigation-by-user-activation (or allow-popups, if you switch to window.open).
3. The permalink request fails. You'd see the "Sorry, something went wrong" toast. Look at the POST /api/v1/dashboard/<id>/permalink request in the Network tab for a 403 or 400 (share permission, CSRF, and so on).
4. Custom copy of the component. On recent master, getDashboardPermalink resolves to { key, url } instead of a string. If you upgraded Superset but kept the old generateUrl, the email body will contain [object Object]. Use (await getDashboardPermalink(...)).url.

If your screenshot really does show a huge URL in the body, the link isn't coming from the permalink API, and something in your fork is building it.

[FrancescoCastaldi]

In superset-frontend/src/dashboard/components/menu/ShareMenuItems/index.tsx, the failure of the Share by Email action typically boils down to two specific causes:

1. The getDashboardPermalink Return Value Type

In earlier Superset versions, getDashboardPermalink returned a Promise resolving to a string URL. In recent versions, getDashboardPermalink resolves to an object: { key: string, url: string }.
When your code executes:

const encodedBody = encodeURIComponent(
  `${emailBody}${await generateUrl()}`,
);

If generateUrl() returns { key, url }, string interpolation produces [object Object] or causes the URL calculation to break.

Fix: Destructure the url property explicitly:

async function generateUrl() {
  const result = await getDashboardPermalink({
    dashboardId,
    dataMask,
    activeTabs,
    anchor: dashboardComponentId,
  });
  return typeof result === 'string' ? result : result.url;
}

2. Permalink REST API Permissions and Failures

The function getDashboardPermalink sends a POST request to /api/v1/dashboard/{id}/permalink.
If that request fails (for instance with HTTP 401, 403, or 500), execution immediately enters the catch block and displays the error toast.

• Verify in your browser's Developer Tools (Network tab) whether the POST request to /api/v1/dashboard/{id}/permalink succeeds.
• If it returns 403 Forbidden, ensure that the user's role has the required permission:
  can write on DashboardPermalinkRestApi (or all_datasource_access).

3. OS Mailto Handler Protocol

Setting window.location.href = mailto:... relies on the operating system having a registered default email client (such as Outlook, Thunderbird, or a configured webmail handler in Chrome). If no default client is registered, the browser silently ignores the navigation without throwing a JavaScript error. Testing window.open(mailtoUrl, '_blank') or verifying system mail associations confirms whether the client environment is intercepting the scheme.