Bug 16108 - Message reply considered unsolicited bulk e-mail
Summary: Message reply considered unsolicited bulk e-mail
Status: RESOLVED FIXED
Alias: None
Product: Infrastructure
Classification: Unclassified
Component: Others (show other bugs)
Version: unspecified
Hardware: All Linux
Priority: Normal normal
Target Milestone: ---
Assignee: Sysadmin Team
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2015-06-11 12:54 CEST by Bit Twister
Modified: 2016-07-06 22:34 CEST (History)
1 user (show)

See Also:
Source RPM:
CVE:
Status comment:


Attachments

Description Bit Twister 2015-06-11 12:54:42 CEST
A message from <bittwister>
to: qa-discuss@ml.mageia.org
was considered unsolicited bulk e-mail (UBE).

Our internal reference code for your message is 01275-02/Ts1ymv3w+18k


Reporting-MTA: dns; alamut.mageia.org
Received-From-MTA: smtp; alamut.mageia.org ([127.0.0.1])
Arrival-Date: Wed, 10 Jun 2015 16:43:57 +0200 (CEST)

Original-Recipient: rfc822;qa-discuss@ml.mageia.org
Final-Recipient: rfc822;qa-discuss@ml.mageia.org
Action: failed
Status: 5.7.0
Diagnostic-Code: smtp; 554 5.7.0 Reject, id=01275-02 - SPAM
Last-Attempt-Date: Wed, 10 Jun 2015 16:43:57 +0200 (CEST)
Final-Log-ID: 01275-02/Ts1ymv3w+18k
----------------------------------------------------------------------

Above From: email address was shortened just to hide it from general view.

I change ISP anytime I can get a good deal on an Internet package. As a result I have to keep changing my email name because I can not use the old email name when I go back to a previous ISP. 

I use fetchmail to pull down any email from bugzilla, forum, mailing lists, ...

In order to get the reply address correct in any email, I have the generic table/file, via postfix, convert my bittwister@home.test, $ hostname --ip-address
192.168.11.132
to my external account not at my ISP.
Comment 1 Bit Twister 2016-07-06 22:34:24 CEST
Converted to using thunderbird instead of using local postfix.

Status: NEW => RESOLVED
Resolution: (none) => FIXED


Note You need to log in before you can comment on or make changes to this bug.