Outbound SMTP mail question

[Nev]

Hi all,

Is it as I perceive for my users that when a message is partially sent that it becomes mis queued.

Wingate 6.0.3 / Win XP Pro.

The situation is brought about by users disabling / powering off after delivering larger eMails to Wingate's eMail server.

This is a difficulty is for home user's to understand that even though the progress bar has gone from their client program that the message is still only partially sent.

Next power on / dial up the message will be moved to dead after the default 20 tries.

I assume here that the ID of the message is rejected by the host [ISP] or that due to size limitations only messages '< so many Kb' will be allowed traffic.

The reason I suspect that, is one client now cannot send me the SMTP server log [120Kb] but can send minor messages around 10/20Kb ok.

This issue seems to clear after say 24H [when perhaps the ISP lifts a ban on outbound traffic for their client] and nothing more is an issue for a while.

Applying SMTP authentication doesn't seem to ease the problem, however choosing another remote gateway can, if the user has access and the ability to modify Wingate's eMail server to point traffic that way.

So am I correct that some ISP's may temporarily restrict Port 25 traffic and the scenario above will fall in that loop?

I can understand this for DSL/cable type connections where the pc has been hijacked and is acting as a spam zOmbie, unlike the above which are slow dial in type connections.

Thanks!

Nev.

[adrien]

Hi Nev

When WinGate comes back up, it should simply retry any messages sitting in its outbound queue, so it would be interesting to see the debug log of the SMTP server when this happens, to see if the ISP's server rejects it at the MAIL FROM:<> SIZE=xxxx stage, or whether the mail is delivered and rejected after delivery (would be unusual).

if the ISP is being quite draconian, if they still allow outbound port 25, perhaps the client would be better to try direct delivery first, then fail over to the ISP's server.

Adrien

[Nev]

Hi Nev

When WinGate comes back up, it should simply retry any messages sitting in its outbound queue, so it would be interesting to see the debug log of the SMTP server when this happens, to see if the ISP's server rejects it at the MAIL FROM:<> SIZE=xxxx stage, or whether the mail is delivered and rejected after delivery (would be unusual).

if the ISP is being quite draconian, if they still allow outbound port 25, perhaps the client would be better to try direct delivery first, then fail over to the ISP's server.

Adrien

G'day Adrien,

As usual it is nothing to do with Wingate but from the log basically [as I thought] service outages or congestion could be a polite excuse for the host!

10/19/04 18:33:07 127.0.0.2 <system> 0000000105 Traffic 259969 134 0 0 492s
10/19/04 18:33:07 127.0.0.2 <system> 0000000106 Traffic 254135 134 0 0 492s
10/19/04 18:33:07 127.0.0.2 <system> 0000000106 Terminated exit code 4294967295
10/19/04 18:33:07 127.0.0.2 <system> 0000000105 Terminated exit code 4294967295
10/19/04 19:12:53 Service started successfully
10/19/04 19:12:53 Debug: Build DomainList took 15 milliseconds
10/19/04 19:13:07 127.0.0.2 <system> 0000000004 Error: Delivery for domain bigpond.com failed - unable to lookup MX or A record
10/19/04 19:13:09 127.0.0.2 <system> 0000000004 Traffic 0 0 0 0 3s
10/19/04 19:13:09 127.0.0.2 <system> 0000000004 Terminated exit code 0
10/19/04 19:13:11 Service stopped
10/19/04 19:30:00 Service started successfully
10/19/04 19:30:00 Debug: Build DomainList took 16 milliseconds
10/19/04 19:30:00 Error: Orphaned message file 0000000191.msg moved to dead
10/19/04 19:30:00 Error: Orphaned message file 0000000192.msg moved to dead
10/19/04 19:30:00 Error: Orphaned message file 0000000193.msg moved to dead
10/19/04 19:30:00 Error: Orphaned message file 0000000194.msg moved to dead
10/19/04 19:30:00 Error: Orphaned message file 0000000195.msg moved to dead
10/19/04 19:30:00 Error: Orphaned message file 0000000196.msg moved to dead
10/19/04 19:30:00 Error: Orphaned message file 0000000197.msg moved to dead
10/19/04 19:30:00 Error: Orphaned message file 0000000198.msg moved to dead
10/19/04 19:30:00 Error: Orphaned message file 0000000199.msg moved to dead
10/19/04 19:30:00 Error: Orphaned message file 0000000200.msg moved to dead
10/19/04 19:30:00 Error: Orphaned message file 0000000201.msg moved to dead

Many thanks!

Nev.