Different retry times for smtp delivery [90%]

Use this forum if you want to suggest a new feature to hMailServer. Before posting, please search the forum to confirm that it has not already been suggested.
Post Reply

I require this feature as well

yes
62
100%
no
0
No votes
 
Total votes: 62

andyp
Normal user
Normal user
Posts: 191
Joined: 2008-01-18 21:00

Different retry times for smtp delivery [90%]

Post by andyp » 2008-03-20 10:47

In detail you can configure the smtp delivery service trying to deliver the message
- the first 30 minutes every 2 minutes
- from that on to 2 hours every 10 minutes
- from that on to 24 hours every hour
or somethine like this, values configuable of course.

Would guarantee the message will be quickly delivered in case of greylisting, short shutdown or connection problems of the corresponding mailserver and would reduce the performance weight on the own server in case the corresponding server is longer down etc.


MOD EDIT: Mostly done in 5.4 with something like this in hmailserver.ini:
(Still needs to be added to GUI admin & perhaps further settings such as a multiplier)

Code: Select all

[Options]
QuickRetries=3
QuickRetriesMinutes=7 
(See posts below for details)

^DooM^
Site Admin
Posts: 13861
Joined: 2005-07-29 16:18
Location: UK

Post by ^DooM^ » 2008-03-20 12:26

This has been mentioned before but I couldn't find a feature request for it. I like it.

redrummy
Senior user
Senior user
Posts: 370
Joined: 2007-06-21 06:52
Location: Alaska

Post by redrummy » 2008-03-20 17:01

I almost requested this before "SMTP retry back-off", but guess I figured I didn't need it that badly. But yes, I woud like it. Simpler implementation might be:

SMTP Retry intervals (in min): [user-defined fields]
1st retry: [2]
2nd retry: [5]
3rd retry: [15]
Subsequent retries: [30]
Expiration (failure/NDR): [1440]

Dan
Normal user
Normal user
Posts: 75
Joined: 2008-02-02 19:40

Re: Different retry times for smtp delivery

Post by Dan » 2008-06-06 19:21

This is a very nice feature :-)

Also very usable for routes on a MX backup server.

westdam
Senior user
Senior user
Posts: 728
Joined: 2006-08-01 21:24
Location: Padova, Italy
Contact:

Re: Different retry times for smtp delivery

Post by westdam » 2008-12-23 02:38

i've create a topic for this but it was old so martin puts mine on archived..

i'll write here to move up this feature.
has my vote.

User avatar
martin
Developer
Developer
Posts: 6834
Joined: 2003-11-21 01:09
Location: Sweden
Contact:

Re: Different retry times for smtp delivery

Post by martin » 2008-12-23 10:01

> i've create a topic for this but it was old so martin puts mine on archived..

No, I moved your topic to the archive because you had requested a feature which had already been requested.

User avatar
weinberk
Normal user
Normal user
Posts: 95
Joined: 2009-01-24 00:17

Re: Different retry times for smtp delivery

Post by weinberk » 2009-01-24 03:41

This would absolutely help us.

I'm just getting started with hMailServer, but so far, I absolutely love it! Thanks for the hard work and for making this freely available. It's going to help a of the non-profits that I help out.

I think it might be a good idea to be able to have different retry intervals.

Something like this would be very helpful, especially with so many servers greylisting these days.

1st retry: x minutes after initial try
2nd retry: y minues after 1st try
3rd retry: z minnutes after 3rd try
4th and subsequent retries: w minutes

This would let us set the 1st retry for 5 miunute (good for most greylists) and the 2nd for 10 minutes (which would be 10 minutes after the first retry).

I hope I'm making sense - it's been one of those really long days.

sheck
New user
New user
Posts: 5
Joined: 2008-04-14 02:14

Re: Different retry times for smtp delivery

Post by sheck » 2009-01-29 20:38

I would join the others in requesting this option. I think it's useful.

plobby
Normal user
Normal user
Posts: 115
Joined: 2008-01-29 07:04

Re: Different retry times for smtp delivery

Post by plobby » 2009-01-30 02:44

I would really like this option as well -- also because I do backup MX for a few domains.

User avatar
Rainer
Normal user
Normal user
Posts: 166
Joined: 2007-06-21 13:40
Location: Zweibrücken - Germany

Re: Different retry times for smtp delivery

Post by Rainer » 2009-04-01 08:19

Hello and a happy 1st April :lol:

My retry time in SMTP (minutes between every retry) is 3 minutes.
The reason for this short retry time is the using of greylisting on the destination-systems.
Many providers - me too - are using this great feature to block spam.
The most accept emails after the first try after 3, 5 or 6 minutes.
Our customers need a quick sending and a longer retry time is not possible.

Sometimes domains are not accessible and my log file is many MB.
It looks like this:

"SMTPC" 2676 29568 "2009-03-31 00:05:27.290" "212.227.15.169" "RECEIVED: 220 mx-b.kundenserver.de (mxeu5) Welcome to Nemesis ESMTP server"
"SMTPC" 2676 29568 "2009-03-31 00:05:27.290" "212.227.15.169" "SENT: HELO mail.milestec.de"
"SMTPC" 2676 29568 "2009-03-31 00:05:27.305" "212.227.15.169" "RECEIVED: 250 mxeu5.kundenserver.de"
"SMTPC" 2676 29568 "2009-03-31 00:05:27.305" "212.227.15.169" "SENT: MAIL FROM:<KeineAntwort@MyDomain.de>"
"SMTPC" 2676 29568 "2009-03-31 00:05:27.305" "212.227.15.169" "RECEIVED: 250 mail from: <KeineAntwort@MyDomain.de> ok"
"SMTPC" 2676 29568 "2009-03-31 00:05:27.305" "212.227.15.169" "SENT: RCPT TO:<TheDestination@Somewhere.de>"
"SMTPC" 2676 29568 "2009-03-31 00:05:28.305" "212.227.15.169" "RECEIVED: 451 Requested action aborted: local error in processing (code: 11)"
"SMTPC" 2676 29568 "2009-03-31 00:05:28.305" "212.227.15.169" "SENT: QUIT"
"SMTPC" 2676 29568 "2009-03-31 00:05:28.305" "212.227.15.169" "RECEIVED: 221 mx-b.kundenserver.de Bye"
"SMTPC" 2768 29569 "2009-03-31 00:05:28.321" "212.227.15.186" "RECEIVED: 220 mx-b.kundenserver.de (mxeu0) Welcome to Nemesis ESMTP server"
"SMTPC" 2768 29569 "2009-03-31 00:05:28.321" "212.227.15.186" "SENT: HELO mail.milestec.de"
"SMTPC" 2768 29569 "2009-03-31 00:05:28.321" "212.227.15.186" "RECEIVED: 250 mxeu0.kundenserver.de"
"SMTPC" 2768 29569 "2009-03-31 00:05:28.321" "212.227.15.186" "SENT: MAIL FROM:<KeineAntwort@MyDomain.de>"
"SMTPC" 2768 29569 "2009-03-31 00:05:28.321" "212.227.15.186" "RECEIVED: 250 mail from: <KeineAntwort@MyDomain.de> ok"
"SMTPC" 2768 29569 "2009-03-31 00:05:28.321" "212.227.15.186" "SENT: RCPT TO:<TheDestination@Somewhere.de>"
"SMTPC" 2768 29569 "2009-03-31 00:05:29.337" "212.227.15.186" "RECEIVED: 451 Requested action aborted: local error in processing (code: 11)"
"SMTPC" 2768 29569 "2009-03-31 00:05:29.337" "212.227.15.186" "SENT: QUIT"
"SMTPC" 2768 29569 "2009-03-31 00:05:29.337" "212.227.15.186" "RECEIVED: 221 mx-b.kundenserver.de Bye"
"SMTPC" 2768 29570 "2009-03-31 00:05:29.337" "212.227.15.134" "RECEIVED: 220 mx-b.kundenserver.de (mxeu0) Welcome to Nemesis ESMTP server"
"SMTPC" 2768 29570 "2009-03-31 00:05:29.337" "212.227.15.134" "SENT: HELO mail.milestec.de"
"SMTPC" 2768 29570 "2009-03-31 00:05:29.352" "212.227.15.134" "RECEIVED: 250 mxeu0.kundenserver.de"
"SMTPC" 2768 29570 "2009-03-31 00:05:29.352" "212.227.15.134" "SENT: MAIL FROM:<KeineAntwort@MyDomain.de>"
"SMTPC" 2768 29570 "2009-03-31 00:05:29.352" "212.227.15.134" "RECEIVED: 250 mail from: <KeineAntwort@MyDomain.de> ok"
"SMTPC" 2768 29570 "2009-03-31 00:05:29.352" "212.227.15.134" "SENT: RCPT TO:<TheDestination@Somewhere.de>"
"SMTPC" 2768 29570 "2009-03-31 00:05:30.368" "212.227.15.134" "RECEIVED: 451 Requested action aborted: local error in processing (code: 11)"
"SMTPC" 2768 29570 "2009-03-31 00:05:30.368" "212.227.15.134" "SENT: QUIT"
"SMTPC" 2768 29570 "2009-03-31 00:05:30.368" "212.227.15.134" "RECEIVED: 221 mx-b.kundenserver.de Bye"
"SMTPC" 2768 29571 "2009-03-31 00:05:30.368" "212.227.15.150" "RECEIVED: 220 mx-b.kundenserver.de (mxeu5) Welcome to Nemesis ESMTP server"
"SMTPC" 2768 29571 "2009-03-31 00:05:30.368" "212.227.15.150" "SENT: HELO mail.milestec.de"
"SMTPC" 2768 29571 "2009-03-31 00:05:30.384" "212.227.15.150" "RECEIVED: 250 mxeu5.kundenserver.de"
"SMTPC" 2768 29571 "2009-03-31 00:05:30.384" "212.227.15.150" "SENT: MAIL FROM:<KeineAntwort@MyDomain.de>"
"SMTPC" 2768 29571 "2009-03-31 00:05:30.384" "212.227.15.150" "RECEIVED: 250 mail from: <KeineAntwort@MyDomain.de> ok"
"SMTPC" 2768 29571 "2009-03-31 00:05:30.384" "212.227.15.150" "SENT: RCPT TO:<TheDestination@Somewhere.de>"
"SMTPC" 2768 29571 "2009-03-31 00:05:31.384" "212.227.15.150" "RECEIVED: 451 Requested action aborted: local error in processing (code: 11)"
"SMTPC" 2768 29571 "2009-03-31 00:05:31.384" "212.227.15.150" "SENT: QUIT"
"SMTPC" 2768 29571 "2009-03-31 00:05:31.384" "212.227.15.150" "RECEIVED: 221 mx-b.kundenserver.de Bye"
"SMTPC" 2768 29572 "2009-03-31 00:05:31.399" "212.227.15.134" "RECEIVED: 220 mx-b.kundenserver.de (mxeu0) Welcome to Nemesis ESMTP server"
"SMTPC" 2768 29572 "2009-03-31 00:05:31.399" "212.227.15.134" "SENT: HELO mail.milestec.de"
"SMTPC" 2768 29572 "2009-03-31 00:05:31.399" "212.227.15.134" "RECEIVED: 250 mxeu0.kundenserver.de"
"SMTPC" 2768 29572 "2009-03-31 00:05:31.399" "212.227.15.134" "SENT: MAIL FROM:<KeineAntwort@MyDomain.de>"
"SMTPC" 2768 29572 "2009-03-31 00:05:31.399" "212.227.15.134" "RECEIVED: 250 mail from: <KeineAntwort@MyDomain.de> ok"
"SMTPC" 2768 29572 "2009-03-31 00:05:31.399" "212.227.15.134" "SENT: RCPT TO:<TheDestination@Somewhere.de>"
"SMTPC" 2768 29572 "2009-03-31 00:05:32.415" "212.227.15.134" "RECEIVED: 451 Requested action aborted: local error in processing (code: 11)"
"SMTPC" 2768 29572 "2009-03-31 00:05:32.415" "212.227.15.134" "SENT: QUIT"
"SMTPC" 2768 29572 "2009-03-31 00:05:32.415" "212.227.15.134" "RECEIVED: 221 mx-b.kundenserver.de Bye"
"SMTPC" 2768 29573 "2009-03-31 00:05:32.415" "212.227.15.150" "RECEIVED: 220 mx-b.kundenserver.de (mxeu1) Welcome to Nemesis ESMTP server"
"SMTPC" 2768 29573 "2009-03-31 00:05:32.415" "212.227.15.150" "SENT: HELO mail.milestec.de"
"SMTPC" 2768 29573 "2009-03-31 00:05:32.430" "212.227.15.150" "RECEIVED: 250 mxeu1.kundenserver.de"
"SMTPC" 2768 29573 "2009-03-31 00:05:32.430" "212.227.15.150" "SENT: MAIL FROM:<KeineAntwort@MyDomain.de>"
"SMTPC" 2768 29573 "2009-03-31 00:05:32.430" "212.227.15.150" "RECEIVED: 250 mail from: <KeineAntwort@MyDomain.de> ok"
"SMTPC" 2768 29573 "2009-03-31 00:05:32.430" "212.227.15.150" "SENT: RCPT TO:<TheDestination@Somewhere.de>"
"SMTPC" 2768 29573 "2009-03-31 00:05:33.430" "212.227.15.150" "RECEIVED: 451 Requested action aborted: local error in processing (code: 11)"
"SMTPC" 2768 29573 "2009-03-31 00:05:33.430" "212.227.15.150" "SENT: QUIT"
"SMTPC" 2768 29573 "2009-03-31 00:05:33.446" "212.227.15.150" "RECEIVED: 221 mx-b.kundenserver.de Bye"
"SMTPC" 2768 29574 "2009-03-31 00:05:33.446" "212.227.15.169" "RECEIVED: 220 mx-b.kundenserver.de (mxeu22) Welcome to Nemesis ESMTP server"
"SMTPC" 2768 29574 "2009-03-31 00:05:33.446" "212.227.15.169" "SENT: HELO mail.milestec.de"
"SMTPC" 2768 29574 "2009-03-31 00:05:33.446" "212.227.15.169" "RECEIVED: 250 mxeu22.kundenserver.de"
"SMTPC" 2768 29574 "2009-03-31 00:05:33.446" "212.227.15.169" "SENT: MAIL FROM:<KeineAntwort@MyDomain.de>"
"SMTPC" 2768 29574 "2009-03-31 00:05:33.477" "212.227.15.169" "RECEIVED: 250 mail from: <KeineAntwort@MyDomain.de> ok"
"SMTPC" 2768 29574 "2009-03-31 00:05:33.477" "212.227.15.169" "SENT: RCPT TO:<TheDestination@Somewhere.de>"
"SMTPC" 2768 29574 "2009-03-31 00:05:34.477" "212.227.15.169" "RECEIVED: 451 Requested action aborted: local error in processing (code: 11)"
"SMTPC" 2768 29574 "2009-03-31 00:05:34.477" "212.227.15.169" "SENT: QUIT"
"SMTPC" 2768 29574 "2009-03-31 00:05:34.477" "212.227.15.169" "RECEIVED: 221 mx-b.kundenserver.de Bye"
"SMTPC" 2712 29575 "2009-03-31 00:05:34.509" "212.227.15.186" "RECEIVED: 220 mx-b.kundenserver.de (mxeu3) Welcome to Nemesis ESMTP server"
"SMTPC" 2712 29575 "2009-03-31 00:05:34.509" "212.227.15.186" "SENT: HELO mail.milestec.de"
"SMTPC" 2712 29575 "2009-03-31 00:05:34.509" "212.227.15.186" "RECEIVED: 250 mxeu3.kundenserver.de"
"SMTPC" 2712 29575 "2009-03-31 00:05:34.509" "212.227.15.186" "SENT: MAIL FROM:<KeineAntwort@MyDomain.de>"
"SMTPC" 2712 29575 "2009-03-31 00:05:34.509" "212.227.15.186" "RECEIVED: 250 mail from: <KeineAntwort@MyDomain.de> ok"
"SMTPC" 2712 29575 "2009-03-31 00:05:34.509" "212.227.15.186" "SENT: RCPT TO:<TheDestination@Somewhere.de>"
"SMTPC" 2712 29575 "2009-03-31 00:05:35.509" "212.227.15.186" "RECEIVED: 451 Requested action aborted: local error in processing (code: 11)"
"SMTPC" 2712 29575 "2009-03-31 00:05:35.509" "212.227.15.186" "SENT: QUIT"
"SMTPC" 2712 29575 "2009-03-31 00:05:35.524" "212.227.15.186" "RECEIVED: 221 mx-b.kundenserver.de Bye"

The feature request is a really needed feature and i hope it will be released in the next future.
Is it possible to bypass problems like this?

My wish for this feature; a input-field like this: 5|3;20|30;20|180
This means: 5 retries with 3 minutes; 20 retries with 30 minutes; and 20 retries with 180 minutes

With this input field it's easy to create a array sperated by the ( | ) pipe-character.


Kind regards from Germany :)

Rainer :shock:
Rainer Noa

vangoga
New user
New user
Posts: 1
Joined: 2009-09-17 12:49

Re: Different retry times for smtp delivery

Post by vangoga » 2009-09-17 12:54

I think this feature is "MUST BE".

I could implement it if i had a source code :D

User avatar
Rainer
Normal user
Normal user
Posts: 166
Joined: 2007-06-21 13:40
Location: Zweibrücken - Germany

Re: Different retry times for smtp delivery

Post by Rainer » 2009-09-17 13:51

Hello vangoga, if you activated greylisting, so you want to prevent the recipient is waiting long time for your messages.

My setting for 'minutes between every retry' is 10.
If you want to try for 3 days, you must set the setting 'number of retries' to 432 (3 days * 24 hours * 60 minutes = 4320 / 10 = 432 number of retries)!

This is a really silly setting; but there is no alternative.

Better is a setting like my posting before :)

Kind regards :)
Rainer Noa

^DooM^
Site Admin
Posts: 13861
Joined: 2005-07-29 16:18
Location: UK

Re: Different retry times for smtp delivery

Post by ^DooM^ » 2009-09-17 14:09

vangoga wrote:I think this feature is "MUST BE".

I could implement it if i had a source code :D
You can download the V4 source code and alter that to your hearts content.
If at first you don't succeed, bomb disposal probably isn't for you! ヅ

Bill48105
Developer
Developer
Posts: 6189
Joined: 2010-04-24 23:16
Location: Michigan, USA

Re: Different retry times for smtp delivery

Post by Bill48105 » 2010-05-14 05:09

Got a wild hair, downloaded 4.4.4 source, got it setup & compiled successfully. (WOW a lot has changed since that version! Nice work Martin!)

In looking at & playing with the source (assuming things are roughly the same with current version vs that old open source one) to me (as a lay coder not to be confused with lame coder but might be that too lol) it looks like in PersistentMessage.cpp in PersistentMessage::AddObject there is a sSQL.Format call with:
"values (%d, %I64d, '%s', %d, '%s', '', %d, %d, %d, %I64d, %d, %d, '%s', %d, %d, %d, 0, '1901-01-01')". I assume '1901-01-01' being the default date in the past to be used in the messagenexttrytime to ensure at least 1 delivery attempt with no delay, so essentially immediately or right away vs being queued into the future.

To me it seems that value could instead be replaced with current date/time + a small random value in seconds (hopefully user definable range but 0-30 might be good start) in format of 2010-05-13 10:54:38 that is used in the hm_messages table to ensure messages are staggered during heavy load & new messages have a fighting chance to get delivered while prior ones to numerous recipients or to large distribution lists are busy tying up the queue. (This part was more about the randomize retry post elsewhere than this particular post but figured they go together at least somewhat since they have to do with managing message tries in the queue and ties into below)

As far as this retry times post, the next function is PersistentMessage::SetNextTryTime & looking at that a similar thing should be possible & I'd love to see at least an option to set initial retry delay then subsequent or even a retry time & a 'factor' value so you use the formula: next_retry = retry_try * retry_delay & retry_factor so for example if you had delay of 30 minutes & factor of 0.5 you'd have
1st retry after current time + 15 minutes
2nd retry after 30 more minutes
3rd retry after 45 more minutes
etc until max retries is hit.

This would make it so each retry was staggered further out with only need for 1 additional setting.

A hybrid method would be to combine the random idea above with the retry factor. With it you'd have 2 new settings, retry factor min & max. So if factor min was 0.2 & max was 0.8 on each retry the next delay would be calculated with same formula but with random factor between those 2 values causing not only a growth in the delay but also a better random staggering of the delivery of messages which would help a lot under heavy load to ensure new messages get chance for delivery vs existing ones hogging the queue.

Btw, to help make the retries more understandable in a visual way a simple table could be shown based on the values (on the delivery of email screen).

A super hybrid version of the above would be to control based on if it's local vs external delivery or even normal email vs auto reply or distribution list but didn't want to make it any more complicated. :D
Bill
hMailServer build LIVE on my servers: 5.4-B2014050402
#hmailserver on FreeNode IRC https://webchat.freenode.net/?channels=#hmailserver
*** ABSENT FROM hMail! Those in IRC know how to find me if urgent. ***

Bill48105
Developer
Developer
Posts: 6189
Joined: 2010-04-24 23:16
Location: Michigan, USA

Re: Different retry times for smtp delivery

Post by Bill48105 » 2010-11-02 06:43

FYI this is sort of done in the 5.4 alpha martin recently released but for now is in test phase so requires INI setting to enable. (Which means not in the GUI admin at this time..)

I added a new feature called QuickRetry which tells hmail to retry the 1st X times at a quicker pace then resume normal delivery schedule. This allows for the normal retries & delay between to be set higher than what is possible now but have messages not get stuck too long due to greylisting or temp server-busy failures.

For example, with [Options] QuickRetries=3 & QuickRetriesMinutes=7 but default tries set to 25 and default delay set to 90 minutes the retry pattern would be:
Initial - Immediate
1st - 7 minutes later
2nd - 7 minutes later
3rd - 7 minutes later
4th - 90 minutes later
5th - 90 minutes later
etc

So perhaps not exactly what was asked for in the original post but certainly along the same lines.. And with the changes made it shouldn't be too hard to allow another step or 2 if desired such as QuickRetriesFactor=1 which tells hmail to multiply the try # x the retry minutes so 7, 14, 21.. Obviously with that one would need to be careful not to set retries too high or delay could get huge. :D (To be clear the Factor example was just that, an example. It's not actually in the code at this point but the other quickretries stuff above is.)

Here is a link to 5.4 Alpha: (Keep in mind it has bugs & should only be used in test environment at this time.. Hopefully we can get enough feedback to get a beta out before too long that should be considered more stable.)
http://www.hmailserver.com/forum/viewto ... 10&t=19409
Bill
hMailServer build LIVE on my servers: 5.4-B2014050402
#hmailserver on FreeNode IRC https://webchat.freenode.net/?channels=#hmailserver
*** ABSENT FROM hMail! Those in IRC know how to find me if urgent. ***

Khurram
Normal user
Normal user
Posts: 38
Joined: 2007-12-02 09:21

Re: Different retry times for smtp delivery

Post by Khurram » 2011-04-05 19:42

A flexible delivery/retry schedule would be a welcome feature but with an additional feature: an option to send a "warning email" after a set number of tries to indicate that the email has not yet been delivered.

rjk
Normal user
Normal user
Posts: 248
Joined: 2010-03-30 19:30
Location: uʍop ǝpısdn

Re: Different retry times for smtp delivery

Post by rjk » 2011-04-05 21:42

Khurram wrote:A flexible delivery/retry schedule would be a welcome feature but with an additional feature: an option to send a "warning email" after a set number of tries to indicate that the email has not yet been delivered.
Yes I know of a new mail servers that do this. After x retries, send a warning, after z retries, cancel sending and bounce the message. This would be a useful addition to this feature request.
hMailServer 5.5.2-B2129 on Server 2008 R2 VM
MySQL 5.5.25, IIS 7.5, PHP 5.6.2 via FastCGI, RoundCube 1.0.3
XenServer 6.0 on HP DL380 G5 32GB RAM

Bill48105
Developer
Developer
Posts: 6189
Joined: 2010-04-24 23:16
Location: Michigan, USA

Re: Different retry times for smtp delivery

Post by Bill48105 » 2011-04-12 01:12

Yeah was on my todo/wish list since it is something I miss from my old mail server. The issue was that many people hated them so something almost trivial to add if server-wide turns into something not so trivial if it requires per domain/user control.
Bill
hMailServer build LIVE on my servers: 5.4-B2014050402
#hmailserver on FreeNode IRC https://webchat.freenode.net/?channels=#hmailserver
*** ABSENT FROM hMail! Those in IRC know how to find me if urgent. ***

Mazufa
New user
New user
Posts: 15
Joined: 2019-09-01 20:20
Location: Finland

Re: Different retry times for smtp delivery [90%]

Post by Mazufa » 2019-09-11 14:41

Hello

Is this feature still present in the hmailserver email server program?


I myself also hMailServer e-mail server, and I have set up their own e-mail server hMailServer VPS server.

Where can I configure this change? I would like my hmailserver SMTP server to try to resend the email every 30 minutes unless the first upload attempt is successful. I want the hmailserver to retry delivery every 3 hours every 30 minutes.

I would be really grateful if anyone could help me out where I can do this configuration I want?

Thank you! :)

User avatar
RvdH
Senior user
Senior user
Posts: 797
Joined: 2008-06-27 14:42
Location: Netherlands

Re: Different retry times for smtp delivery [90%]

Post by RvdH » 2019-09-11 15:07

CIDR to RegEx: d-fault.nl/CIDRtoRegEx
DNS Lookup: d-fault.nl/DNSTools
DNSBL Lookup: d-fault.nl/DNSBLLookup
GEOIP Lookup: d-fault.nl/GeoipLookup

Mazufa
New user
New user
Posts: 15
Joined: 2019-09-01 20:20
Location: Finland

Re: Different retry times for smtp delivery [90%]

Post by Mazufa » 2019-09-11 15:31

I have a little understanding of England and so it is a bit difficult to understand everything but I try hard.

What is this INI file, where is this change made, and where is this ini file located?
Apparently the values are changed using notepad ++, for example? I just need to know exactly where this ini file is located and which ini file to be sure I can handle the correct file. I can speak a little English but I try hard to understand. I'm currently studying English for Wordrive.

Next fall I will also start studying Information and Communication Technology! :)

Mazufa
New user
New user
Posts: 15
Joined: 2019-09-01 20:20
Location: Finland

Re: Different retry times for smtp delivery [90%]

Post by Mazufa » 2019-09-11 17:12

So do I just change these two settings that are shown in this screenshot of me? So I look for the ini.file and change these two values for example notepad ++?

I want my hmailserver email server to try to resend the message after the first failed delivery attempt for 30mins time and 2 = min


Do 30 = 30min and 2 = 2min mean?



Sorry because I have to ask specific questions due to poor language skills. English when no one learns right away.


Image

Mazufa
New user
New user
Posts: 15
Joined: 2019-09-01 20:20
Location: Finland

Re: Different retry times for smtp delivery [90%]

Post by Mazufa » 2019-09-11 19:48

I have now found the hMailServer BIN folder INI.file.

So do I need to add these lines below to this ini file and add the and I am add the values ​​I want? You confirm this for me, or let me know if I'm wrong? Thank you. After that, I dare to make a change.

Is 120 = 120min and 20 = 20min?

QuickRetries=3
QuickRetriesMinutes=7




Thank you

User avatar
mattg
Moderator
Moderator
Posts: 20026
Joined: 2007-06-14 05:12
Location: 'The Outback' Australia

Re: Different retry times for smtp delivery [90%]

Post by mattg » 2019-09-12 00:09

Mazufa wrote:
2019-09-11 19:48
I have now found the hMailServer BIN folder INI.file.

So do I need to add these lines below to this ini file and add the
Yes
Under a heading named

[settings]

If that heading isn't there you need to add it, as well as the settings you mention. This is from my hmailserver.ini file

Code: Select all

QuickRetries=10

QuickRetriesMinutes=7
; Defines # of minutes to delay for each retry if QuickRetries is enabled otherwise normal delivery schedule
; is used
; Defaults to 6 if QuickRetries is enabled otherwise ignored

QueueRandomnessMinutes=3
; This key defines how many minutes to use for 'QuickRetries' that over-rides the default retry schedule.
; This does not apply to NEW messages as they are still queued for immediate delivery as before.
; This defaults to 0 or disabled

MXTriesFactor=3
; This key defines a multiplier to determine how many MX/A server results to try per retry.
; For example: If set to 2 & the recipient has 11 servers, on 1st try, 1 x MXTriesFactor or 2 are tried.
; On 2nd try, 2 x MXTriesFactor or 4 are tried. On 3rd 6 are tried & so on. Eventually all 11
; would be tried if the message was not successively delivered enough times.
; This defaults to disabled if not defined

Mazufa wrote:
2019-09-11 19:48
Is 120 = 120min and 20 = 20min?
Yes


You will need to restart the machine with hMailserver on it for this to take effect
Also note that this is not official code authorised by Martin and may be removed in a later version
Just 'cause I link to a page and say little else doesn't mean I am not being nice.
https://www.hmailserver.com/documentation

Mazufa
New user
New user
Posts: 15
Joined: 2019-09-01 20:20
Location: Finland

Re: Different retry times for smtp delivery [90%]

Post by Mazufa » 2019-09-13 17:34

mattg wrote:
2019-09-12 00:09
Mazufa wrote:
2019-09-11 19:48
I have now found the hMailServer BIN folder INI.file.

So do I need to add these lines below to this ini file and add the
Yes
Under a heading named

[settings]

If that heading isn't there you need to add it, as well as the settings you mention. This is from my hmailserver.ini file

Code: Select all

QuickRetries=10

QuickRetriesMinutes=7
; Defines # of minutes to delay for each retry if QuickRetries is enabled otherwise normal delivery schedule
; is used
; Defaults to 6 if QuickRetries is enabled otherwise ignored

QueueRandomnessMinutes=3
; This key defines how many minutes to use for 'QuickRetries' that over-rides the default retry schedule.
; This does not apply to NEW messages as they are still queued for immediate delivery as before.
; This defaults to 0 or disabled

MXTriesFactor=3
; This key defines a multiplier to determine how many MX/A server results to try per retry.
; For example: If set to 2 & the recipient has 11 servers, on 1st try, 1 x MXTriesFactor or 2 are tried.
; On 2nd try, 2 x MXTriesFactor or 4 are tried. On 3rd 6 are tried & so on. Eventually all 11
; would be tried if the message was not successively delivered enough times.
; This defaults to disabled if not defined

Mazufa wrote:
2019-09-11 19:48
Is 120 = 120min and 20 = 20min?
Yes


You will need to restart the machine with hMailserver on it for this to take effect
Also note that this is not official code authorised by Martin and may be removed in a later version





I really appreciate you helping me :)


So can I just open the hmailserver program's INI file in the BIN folder in Notepad ++ and add the code you provided to my INI.file?

Only then do I change those number values to my liking? I want the hmailserver to try to send a message after the first failed attempt For 5 hours time every 10 minutes . So I put 5h = 300 and 10 = 10min? So, can I copy the your code of the INI file you sent to me and change it only to the values I want for the my INI.file?

What is this QueueRandomnessMinutes? What does this mean? Do I have to use this? Can you also explain to me this purpose?

Thank you

User avatar
mattg
Moderator
Moderator
Posts: 20026
Joined: 2007-06-14 05:12
Location: 'The Outback' Australia

Re: Different retry times for smtp delivery [90%]

Post by mattg » 2019-09-13 23:07

Mazufa wrote:
2019-09-13 17:34
So can I just open the hmailserver program's INI file in the BIN folder in Notepad ++ and add the code you provided to my INI.file?
Yes

Then restart the machine with hMailserver on it to take effect
Mazufa wrote:
2019-09-13 17:34
Only then do I change those number values to my liking? I want the hmailserver to try to send a message after the first failed attempt For 5 hours time every 10 minutes . So I put 5h = 300 and 10 = 10min? So, can I copy the your code of the INI file you sent to me and change it only to the values I want for the my INI.file?
If that is all that you want to do, use the SMTP resend settings in the admin GUI

If you want a essentially a two step process with different delivery times than you can ALSO use this ini setting

Mazufa wrote:
2019-09-13 17:34
What is this QueueRandomnessMinutes? What does this mean? Do I have to use this? Can you also explain to me this purpose?
Did you read the comments in the settings I posted - they are fairly self explanatrory.

This is about making the timing between sending random, just to NOT be predictable. Predicable can be seen as sending spam on some systems.
Just 'cause I link to a page and say little else doesn't mean I am not being nice.
https://www.hmailserver.com/documentation

Mazufa
New user
New user
Posts: 15
Joined: 2019-09-01 20:20
Location: Finland

Re: Different retry times for smtp delivery [90%]

Post by Mazufa » 2019-09-14 00:26

QuickRetries = I want to try resending my failed message for one day. So what's the right setting for me?

QuickRetriesMinutes =10 (Duration of business again?)

QueueRandomnessMinutes=8


MXTriesFactor =5 I didn't understand this is. However, is this somehow related to an error in the MX record from the recipient server? I have to use a lot of google translator right now, and I think there has been a translation error. However, I will try my best to understand. I'm not really stupid but google translator is not always so good: D



What do my settings look like to you ?.


So I want to retry sending a failed message for one day. Can you tell me what is the correct value for my case in QuickRetries?

QuickRetriesMinutes # which would be the right value for this because I want to retry sending the message for one day. However, this setting determines the length of time between the companies. Could I also help here that this is right with the value of QuickRetries I want.




I am now thanks to your recent message I think that fairly well understood this. Since my English is still poor at the moment and I have to use Google translator which is not always very good at translations, this makes it harder for me than usual. I hope you understand me on this.

Thanks to you I am now much wiser :)

User avatar
mattg
Moderator
Moderator
Posts: 20026
Joined: 2007-06-14 05:12
Location: 'The Outback' Australia

Re: Different retry times for smtp delivery [90%]

Post by mattg » 2019-09-14 05:55

What is your native language?
Try in that language if you like, we have many languages used here (I only speak English though).


Admin GUI >> Settings >> Protocols >> SMTP >> Delivery of email

Number of retries = 142
Minutes between retries = 10


That will try for one day
You won't need to use the hMailserver.ini settings at all - please remove these new settings from your hMailserver.ini
and then restart the machine with hMailserver installed on it
Just 'cause I link to a page and say little else doesn't mean I am not being nice.
https://www.hmailserver.com/documentation

Mazufa
New user
New user
Posts: 15
Joined: 2019-09-01 20:20
Location: Finland

Re: Different retry times for smtp delivery [90%]

Post by Mazufa » 2019-09-14 10:50

Hello

I am Finnish, and my mother tongue is, therefore, Finland.

Sure enough that's what I wanted to do originally was it that I want to try to re-broadcast one day every 10minuutin. So I do not need to do this with the INI.file settings but can I do it with the hmailserver localhost settings?


I already have hmailserver installed and it works perfectly and email sending and receiving works great.

However, I want to make this change so that the hmailserver will try to resend the message one for one day and every ten minutes. Since a few times my message has not been delivered to the recipient and then I have received a return message from the SMTP server that the message was not delivered.
I want to retry sending a message in case the recipient's server has experienced a temporary malfunction or has been down.

Mazufa
New user
New user
Posts: 15
Joined: 2019-09-01 20:20
Location: Finland

Re: Different retry times for smtp delivery [90%]

Post by Mazufa » 2019-09-14 13:28

But yes, that two-step method would be better. Because then there would be no risk that the recipient's email server would think of me as a spammer. So I'm going to use that two-step method, which is defined by editing the INI file.

QuickRetries = 142

QuickRetriesMinutes = 10

QueueRandomnessMinutes = 8


MXTriesFactor = 5


I have thought about these settings ini.tiedostoon. Then, I am satisfied. The two-step method is better because there is no risk that the recipient's email server would think of me as a spammer. I've also had this problem a few times.


I think these are OK settings for me. I read the text in your code field that you put me in your own INI file settings. It clarified me and I think I understood this.

What do my settings look like to you? So now I just add these to the INI file in the hmailserver BIN folder and save and reboot?

I probably want to back up the original INI file. I don't think there will be any problems.


I also change the settings in the protocol-SMTP section to their original settings. Is the number of Retries original is = 6 and minutes between retry = 7?



I am now in my opinion understood this and the two-step method is what I'm hakenust. The settings you set for me yesterday clarified me because you had written what that setting in the INI file means. I think that I understand correctly.

I am about to put in this message settings on my INI.tiedostooni because they are good in my opinion. Do you think this is OK?

User avatar
jimimaseye
Moderator
Moderator
Posts: 8094
Joined: 2011-09-08 17:48

Re: Different retry times for smtp delivery [90%]

Post by jimimaseye » 2019-09-14 18:21

Yes.

Then restart service:

Net stop hmailserver

Net start hmailserver

Then run this and post the results: https://www.hmailserver.com/forum/viewt ... 20&t=30914 so we check for you.
HMS 5.6.6 B2383 on Win Server 2008 R2 Foundation, + 5.6.7-B2415 on test.
SpamassassinForWindows 3.4.0 spamd service
AV: Clamwin + Clamd service + sanesecurity defs : https://www.hmailserver.com/forum/viewtopic.php?f=21&t=26829

Mazufa
New user
New user
Posts: 15
Joined: 2019-09-01 20:20
Location: Finland

Re: Different retry times for smtp delivery [90%]

Post by Mazufa » 2019-09-14 19:21

I would now like to hear your opinion on these my INI settings? Are these OK now?

My intention was that I now have a QuigRetries setting of 100 and QuickRetriesMinutes = 15, so I want a 15min break between attempts again.


I think these two-step settings are good for me now because I want to retry shipping with two-step technology for about one day.

Tell me what you think about this? I think I understood all the settings unless there was a translation error due to Google Translate. However, I tried my best.

Now I want to hear your views on my settings to keep me happy :) I can also get you diagnostic information on VBS Scripot if you want to?

Hopefully, with these settings, my messages will no longer be rejected because the recipient's email server would think my messages are spam. I hope these settings now help because there have been problems with this. My messages have been rejected a few times because they were thought to be spam.
Last edited by mattg on 2019-09-15 03:48, edited 1 time in total.
Reason: images removed

Mazufa
New user
New user
Posts: 15
Joined: 2019-09-01 20:20
Location: Finland

Re: Different retry times for smtp delivery [90%]

Post by Mazufa » 2019-09-14 20:00

Here are the results of the HMSSettingsDiagnostics test. Please also note my previous post in this thread which has a picture of my settings that I added to the INI file.




HMSDiagnostic_201909141046.zip
(2.49 KiB) Downloaded 1 time

User avatar
mattg
Moderator
Moderator
Posts: 20026
Joined: 2007-06-14 05:12
Location: 'The Outback' Australia

Re: Different retry times for smtp delivery [90%]

Post by mattg » 2019-09-15 01:50

Mazufa wrote:
2019-09-14 13:28
The two-step method is better because there is no risk that the recipient's email server would think of me as a spammer. I've also had this problem a few times.
Using the two step method does not stop other servers seeing you as a spammer.

There are many reasons why others see you as a spammer, including if you send unwanted mass email.

Currently your settings show 50 retries at 30 minute intervals. This is 25 Hours, so your mail will be retied for a day.

If mail is being rejected before that, then the recipient server has REJECTED the mail, and no amount of re-sending will get your mail delivered. You shouls check with the recipient server admin why they are rejecting your mail.

You may still be on blacklists...
Just 'cause I link to a page and say little else doesn't mean I am not being nice.
https://www.hmailserver.com/documentation

Mazufa
New user
New user
Posts: 15
Joined: 2019-09-01 20:20
Location: Finland

Re: Different retry times for smtp delivery [90%]

Post by Mazufa » 2019-09-15 02:07

I changed the QuicgRetries setting so I took a new picture for you and a new HMSSettingsDiagnostic file.

Just look at these in my INI.file settings and import the diagnostics result file and tell me is everything ok? :) I also want to hear your opinion on these settings. This is what I was trying to achieve this day and so I changed the QuickRetries setting to 120.

I hope these two-step re-delivery company settings are also useful in the sense that some recipients no longer think my messages are spam. I have had three times that the message was not delivered because it was rejected by the recipient because it was considered spam. Now that I've set QueueRandomnessMinutes Regulation 5 so the recipient does not always know in advance that at the re-send should be.

I did not mean that this would correct the spamming in all cases. But I argue that these new INI regulations can help in some cases.

I have removed my server's IP address, all as blacklists. I have received some paluuviesteissa also link through which the removal from the blacklist has been able to do some sight seeing. rDNS is also okay because i did a test a week ago and found that it was wrong then and fixed it.


I donated Martin`s for hMailServer project because already I have been satisfied during the short period of use 1,5week, I have hMailServer e-mail program. I would love to support such a project. I have now had 1.5 weeks of hMailserver mail server software enabled and it has worked fine so far.


I think my SSL / TLS configuration might have something minor wrong when I was looking at the HMSSettingsDiagnostic result file. Could you also take a look and do you think the SSL settings are OK or is there something wrong with them? I think it might be. But SSL, however, has acted and Thunderbird does not have any of that when I'm huomattanut hMailServer email server connected.



HMSDiagnosticTEST2.zip
(2.5 KiB) Not downloaded yet
Last edited by mattg on 2019-09-15 03:48, edited 1 time in total.
Reason: removed image as it contains passwords

User avatar
mattg
Moderator
Moderator
Posts: 20026
Joined: 2007-06-14 05:12
Location: 'The Outback' Australia

Re: Different retry times for smtp delivery [90%]

Post by mattg » 2019-09-15 04:09

I have removed the images from this thread as they CLEARLY show your passwords

You should remove the images from where they are stored on the internet, and change your passwords
Just 'cause I link to a page and say little else doesn't mean I am not being nice.
https://www.hmailserver.com/documentation

Mazufa
New user
New user
Posts: 15
Joined: 2019-09-01 20:20
Location: Finland

Re: Different retry times for smtp delivery [90%]

Post by Mazufa » 2019-09-15 11:46

In my opinion, the photos did not have my correct password.

Or Did you mean hMailserver localhost password?



I now took a new picture of my hMailserver INI file settings that I configured yesterday. What do you think of my settings? Do you think they are good and look right and reasonable?

My intention was that the value of QuickRetries would be 120 because I wanted to try this two-step re-delivery for one day.


I also attach the results of the HMSSettingsDiagnostic test to this post. In my opinion, my SSL / TLS configuration might have something wrong with the test. Could you please take a look at the results of my diagnostic test and tell me if there is something wrong with my SSL / TLS configuration? Are all the other things okay?
HMSDiagnosticTEST2.zip



Image
Attachments
HMSDiagnosticTEST2.zip
(2.5 KiB) Downloaded 2 times

User avatar
mattg
Moderator
Moderator
Posts: 20026
Joined: 2007-06-14 05:12
Location: 'The Outback' Australia

Re: Different retry times for smtp delivery [90%]

Post by mattg » 2019-09-15 12:56

INI file settings look fine

Settings as per attachment look OK
Just 'cause I link to a page and say little else doesn't mean I am not being nice.
https://www.hmailserver.com/documentation

Mazufa
New user
New user
Posts: 15
Joined: 2019-09-01 20:20
Location: Finland

Re: Different retry times for smtp delivery [90%]

Post by Mazufa » 2019-09-15 13:54

Can you confirm to me that the GuickRetries = 120 setting is such that the two step re-delivery company is now one day long? GuickRetriesMinutes = 15 is every 15 minutes. GuicRandomness minutes = 5, ie random transmission on first attempt 5minutes on next 10 and so on?



Nice to hear that my INI.file settings are OK! :)

I realized that my HMSSettingsDiagnostic results are OK too and there is nothing wrong with them. So the summary is that everything is OK? :)

User avatar
jimimaseye
Moderator
Moderator
Posts: 8094
Joined: 2011-09-08 17:48

Re: Different retry times for smtp delivery [90%]

Post by jimimaseye » 2019-09-15 19:33

INI file should read

[settings]

(not [options])

[Entered by mobile. Excuse my spelling.]
HMS 5.6.6 B2383 on Win Server 2008 R2 Foundation, + 5.6.7-B2415 on test.
SpamassassinForWindows 3.4.0 spamd service
AV: Clamwin + Clamd service + sanesecurity defs : https://www.hmailserver.com/forum/viewtopic.php?f=21&t=26829

Mazufa
New user
New user
Posts: 15
Joined: 2019-09-01 20:20
Location: Finland

Re: Different retry times for smtp delivery [90%]

Post by Mazufa » 2019-09-15 21:51

Thanks for the note! :) I've now corrected that error you mentioned, and now everything should be fine.

Isn't QuickRetries = 120 the approximate day for which this two-phase resubmission is attempted?


Do you think I can keep the SMTP Protocol setting right where it is now or should I change it back to the original? So 6 and 7? Or is it OK the way it is now?





Image





Image

Mazufa
New user
New user
Posts: 15
Joined: 2019-09-01 20:20
Location: Finland

Re: Different retry times for smtp delivery [90%]

Post by Mazufa » 2019-09-18 19:50

Apparently this is OK and QuickRetries = 120 so one day time?

User avatar
mattg
Moderator
Moderator
Posts: 20026
Joined: 2007-06-14 05:12
Location: 'The Outback' Australia

Re: Different retry times for smtp delivery [90%]

Post by mattg » 2019-09-18 23:50

120 minutes = 2 hours
Just 'cause I link to a page and say little else doesn't mean I am not being nice.
https://www.hmailserver.com/documentation

Post Reply