Skip to content

Single-message Mbox files ignored based on filename extension. #499

@jfarwer

Description

@jfarwer

During import, ePADD ignores files that it detects as an Mbox containing exactly one email when the filename has certain extensions (e.g., .html, .jpg, .doc).

However, filename extensions are ignored when the file is detected as an Mbox containing more than one email.

This leads to inconsistent behaviour:

Mbox files with multiple emails are imported regardless of filename extension.

Mbox files with exactly one email may be ignored if the filename extension matches certain types, such as .html, .jpg, or .doc.

This behaviour is currently undocumented and may be confusing for users.

In practice, a non-Mbox file should already be excluded during import unless it contains a valid Mbox message delimiter (a leading line starting with 'From ' or a blank line followed by 'From ' anywhere in the file).

Suggestion

Consider removing the exclusion based on filename extensions and relying just on the Mbox structure detection.

Metadata

Metadata

Assignees

No one assigned

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions