Add Envelope-to Header line ?

[Melibokus73]

Hi.

is it possible to get a "Envelope-To:" header line added at any incoming Mail ?

At the Moment I get some Mails (mostly SPAM) where I could not see in the header to whom they are originally send.

But in future this would be nice to know anyway at all mails.

Is there any option /script or so to do this

[^DooM^]

http://www.hmailserver.com/documentatio ... otocolsmtp

Add Delivered-To header

If this option is selected, hMailServer will add a Delivered-To header to all email messages. This header will contain the recipient address as given in the SMTP envelope during SMTP communication.

[Melibokus73]

http://www.hmailserver.com/documentatio ... otocolsmtp

Add Delivered-To header

If this option is selected, hMailServer will add a Delivered-To header to all email messages. This header will contain the recipient address as given in the SMTP envelope during SMTP communication.

Thanks ... that seams to be what I'm looking for.

I did test it and it works

but one little question/Issue I found about it.

I did send a mail:
TO: user1@mydomain.com
BCC: user2@mydomain.com; not_a_user@mydomain.com

Both users got the Mail, also the catchall User (=>not_a_user)
All 3 copys of the Mail have the correct "Delivered-To:" line

Code: Select all

Delivered-To: User1@mydomain.com
...
Delivered-To: User2@mydomain.com
...
Delivered-To: not_a_user@mydomain.com
...

But I also have a Mirror User:
there I saw the Mail 3 times. but all 3 have the same line

Code: Select all

Delivered-To: Mirror@mydomain.com

I did expect 3 differnt ones like in the Mails in the User and catch all accounts.

Am I wrong ?

[^DooM^]

You know as much as I do now. As far as i was concerned it showed which email address it was sent to so it should only have a single email address showing.

[Melibokus73]

You know as much as I do now. As far as i was concerned it showed which email address it was sent to so it should only have a single email address showing.

What I'm confused about is that the Mail is 3 times in the Mirror account, but 3 times with the same Delivered-To. of the Mirror Account.

yes, you are right => they are copied there. but I don't think that matters anybody on the Mirror Account.

In the catch-All account there it is like it should be. The MSG hast the right (original) Delivered-To header, but the Mail anyway got copied to this catch all Account . There the diliverd to header is not changed.

Would it be possible to do it this way for the Mirror Account, too? Or is there a Reason why this is not done ??

I only aks first before I insert a feature request

[^DooM^]

You know as much as I do now.

[Melibokus73]

You know as much as I do now.

and now ??

Is there a Workaround for this ?

Is it like it should be or an Error ?

(and no, I don't ask you ( doom ) if you don't know it )

Martin

[martin]

Well, that's kind of unspecified... The actual recipient of the mirror message is the address specified in the administration gui, so in one way it would make sense that the Delivered-To header contains that address. On the other hand, I understand if it's not the expected..

I've reported it here:
http://www.hmailserver.com/devnet/?page ... ssueid=248

[Melibokus73]

Well, that's kind of unspecified... The actual recipient of the mirror message is the address specified in the administration gui, so in one way it would make sense that the Delivered-To header contains that address. On the other hand, I understand if it's not the expected..

I've reported it here:
http://www.hmailserver.com/devnet/?page ... ssueid=248

Is this Issue still on a todo list


Would be really great ...

TIA

PS: NO .. I do not Push

[martin]

Yes, it's planned to be fixed in 5.4.

[Melibokus73]

Yes, it's planned to be fixed in 5.4.

is it already fixed? in a 5.4 beta ? the newest Beta and Daily build are still both Beta 5.31 build 1680 and 1702

only 'cause it is now been marked as "Status = Resolved " in the Issue List.

[^DooM^]

Probably an early alpha build that is not available to us mortals yet.

[martin]

The bug has been fixed but it's not included in any public builds yet. The fix will be included in 5.4.

[Melibokus73]

The bug has been fixed but it's not included in any public builds yet. The fix will be included in 5.4.

Oh .. thanks. Nice to hear this

So about when do you plan to release 5.4 / beta ?

[Melibokus73]

The bug has been fixed but it's not included in any public builds yet. The fix will be included in 5.4.

Is 5.4 still only in unpublic test

BTW: Is there a roadmap of other planed 5.4 changes ?

[Melibokus73]

The bug has been fixed but it's not included in any public builds yet. The fix will be included in 5.4.

Is 5.4 still only in unpublic test

BTW: Is there a roadmap of other planed 5.4 changes ?

[martin]

5.4 is not public until it's up on the download page.

It will include mostly bug fixes, performance enhancements and some architectural changes to make it a bit more stable. A few new minor features will be added as well.

[Melibokus73]

5.4 is not public until it's up on the download page.

It will include mostly bug fixes, performance enhancements and some architectural changes to make it a bit more stable. A few new minor features will be added as well.

Many thanks

Will 5.4 be the next public Beta? or are first still any 5.3.x Betas in the pipeline?

[sheffters]

http://www.hmailserver.com/index.php?page=download

theres a 5.3.2 beta ... but unless your really after testing on a seperate machine then I'd wait till they went production.

S.

[martin]

I have no idea whether 5.4 will be the next build. It depends on what issues are found by users using previous versions. Also, I don't see how its relevant whether 5.3.2 or 5.4 is the next version released.

[Melibokus73]

Also, I don't see how its relevant whether 5.3.2 or 5.4 is the next version released.

For ME it is

this Issue is very relevant to me and my possibility to go on with test/debug and switch to produktion----

I have no idea whether 5.4 will be the next build. It depends on what issues are found by users using previous versions.

So, how full is the Issue List now ? would it be possible to switch over to 5.4 now ???

*please*please*please*

[martin]

Also, I don't see how its relevant whether 5.3.2 or 5.4 is the next version released.

The change you're requesting is in 5.4. The release date of 5.3.2 or 5.3.x won't affect the release date of 5.4.

So, how full is the Issue List now ?

There's still several features which are going to be added.

would it be possible to switch over to 5.4 now ???

No, because there is no 5.4 version yet...

[Melibokus73]

5.4 is not public until it's up on the download page.

It will include mostly bug fixes, performance enhancements and some architectural changes to make it a bit more stable. A few new minor features will be added as well.

Hi Martin,

do you know if 5.4 (beta) now get in sight anyhow