[Scheduled] 2026/8/12 PORTERS 1.2.3 Release Notes

*This page was machine-translated from Japanese and may contain inaccuracies.

We will perform maintenance in connection with a release of PORTERS HAISHIN.
Details of the maintenance and the changes are as follows.

■ Release Work Schedule

2026/8/12 (Wed)　14:00 – 14:30　Japan Time

*Time is shown in 24-hour format.
*The maintenance window is subject to change.

■ Impact During the Maintenance Window

The service will remain available during the above time period.
 

■ Fix Details

Until now, the delivery count shown in the email delivery results list for job proposals, Candidates, and HR Contacts included the number of undelivered emails.

We are changing this so that the count excludes bounces and drops※.

• After email sending is complete for a single email delivery setting, bounces and drops are detected sequentially and reflected in the count with a short delay (typically a few minutes).
  ※ Bounces detected after a significant delay are also reflected in the count as soon as they are detected, so the delivery count may end up lower than the number initially displayed.
• The daily sending limit is also calculated after excluding bounced and dropped emails.
  ※ If a bounce is detected after the sending limit has already been reached, the sent count may fall back below the limit.

In addition, for hard bounces (excluding soft bounces [temporary bounces] and drops), a Bounce Management screen — scheduled for release soon — will let you view a list of bounces and release them.

*Definitions of Bounce (Hard, Soft) and Drop

Bounce

This is a status, based on RFC 3463, indicating that the recipient's mail server "could not receive" or "did not receive" the email — in other words, a case where the email is rejected by the recipient's server after sending.

Reference site: RFC 3463 - Enhanced Mail System Status Codes(Official IETF site)

•  Hard Bounce
  A permanent failure, such as a nonexistent recipient address (corresponding to RFC 3463 status "5.x.x (Permanent Failure)").
  Email addresses that result in a hard bounce will be excluded from future deliveries before sending.
   
•  Soft Bounce
  A temporary failure, such as a full mailbox or a temporary server issue (corresponding to RFC 3463 status "4.x.x (Temporary Failure)").
  If a soft bounce occurs, a retry (resend) will be attempted.
   

Drop

This refers to cases where, based on the definition used by the email delivery system that HAISHIN uses, sending is canceled before an attempt is even made to send the email.
When a Drop occurs, a retry (resending) will be attempted. (However, this does not apply to addresses that have previously bounced and are on the suppression list — these will not be retried.)
 

■ Hard Bounce — Permanent Failure (5.x.x)

■ Soft Bounce — Temporary Failure (4.x.x)

■ List of Drop Reasons

■ Affected Areas

• Email sending module
  An email identifier is added at the time of sending, in order to identify the events received when a bounce or drop occurs.
  In addition, addresses that have previously bounced are excluded before sending.
• The delivery count in the email delivery results list for job proposals, Candidates, and HR Contacts

■ Version Information

PORTERS HAISHIN 1.2.3