Author Topic: Avast checks one outgoing email but not another  (Read 5828 times)

0 Members and 1 Guest are viewing this topic.

Offline bob3160

  • Avast Überevangelist
  • Probably Bot
  • *****
  • Posts: 45153
  • 61 Years of Happiness
    • bob3160 Protecting Yourself, Your Computer and, Your Identity
Re: Avast checks one outgoing email but not another
« Reply #15 on: June 18, 2016, 10:15:47 PM »
Sorry, I don't follow your point ??? 587 works so what's the problem with using it?
Why are you insisting on using something that's not working ???
Free avast! Security Seminar: http://bit.ly/2N1eaR2  -  Important: http://www.organdonor.gov/ -- My Web Site: http://bob3160.strikingly.com/ - Win 10 Pro v20H2 64bit, 24 Gig Ram, 1TB SSD, AvastOmni 20.7.xxx, How to Successfully Install Avast http://goo.gl/VLXdeRepair & Clean Install https://goo.gl/t7aJGq

Offline Pondus

  • Probably Bot
  • ****
  • Posts: 36991
Re: Avast checks one outgoing email but not another
« Reply #16 on: June 18, 2016, 10:30:03 PM »
Quote
Port 2525 and others may be used by some individual providers, but have never been officially supported.
this may be why   ;)   https://en.wikipedia.org/wiki/Simple_Mail_Transfer_Protocol





Quote
Port is sometimes unofficially used as an alternate to port 25 SMTP (Simple Mail Transfer Protocol). This is useful as a dedicated port for VPN clients or for those who cannot directly send mail to a mail server outside of their ISP's network because of an ISP blocking port 25.
http://www.speedguide.net/port.php?port=2525




« Last Edit: June 18, 2016, 10:36:07 PM by Pondus »

Offline glnz

  • Sr. Member
  • ****
  • Posts: 300
Re: Avast checks one outgoing email but not another
« Reply #17 on: June 19, 2016, 01:03:09 AM »
Bob, Pondus and Snake - I don't get your willingness to excuse Avast here.

The two links you provide indicate that (a) 2525 is actually used by email companies and (b) it could be used by trojans.  Sorry, but this is exactly why Avast should scan my outgoing emails on port 2525 if I add ,2525 to the SMTP field in the redirect list (pictured in my first post above).  But that does not work.

Why are you so fast to let Avast off the hook?  Avast should be working exactly as I say.
Various Dell Optiplexes running XP Pro SP3 32-bit, Win 7 Pro SP1 64-bit and Win 10 Pro 64-bit.  Firefox with security add-ons.

Offline lakrsrool

  • Advanced Poster
  • **
  • Posts: 712
  • Get the Picture !
Re: Avast checks one outgoing email but not another
« Reply #18 on: June 19, 2016, 02:11:12 AM »
Port 2525 which by the way mirrors Port 587 is sometimes recommended by Email Clients as an alternative to Port 25 in the event Port 25 is blocked (which is not that uncommon due to inherent vulnerabilities).  Fact is Port 2525 is not endorsed by either the IETF or IANA so I would personally recommend using Port 587 which does get scanned by Avast as we know.  Ports 25 and the alternate Port 2525 are generally only recommended when either 587 and/or 465 cannot be used for SMTP protocol depending upon the encryption protocol used. Why Port 2525 is recommended by your Email Client and/or why Avast does not scan Port 2525 I have no idea, but Port 587 is widely recommended for SMTP protocol so I'd simply go with this SMTP protocol Port that works.

A little background; back around 1981 Port 25 was established as the default transmission channel for Internet email as a proposal by USC to the IETF and  is still used today as a means of transmitting between mail servers. Around 1999 the RFC proposed a concept that involved a split message transmission relay that was determined by the RFC to occur over Port 587 to ensure a higher level of security that in turn would not interfere with relay message traffic over Port 25.  Later the IANA registered Port 465 for SMTPS traffic in order to provide a Port for the SMTP protocol using SSL and later the increasingly secure TLS encryption.  Currently SSL/TLS is generally recommended for Port 465 on the other hand Port 587 is recommended for the more recent protocol command STARTTLS.  The STARTTLS command protocol allows SMTP servers to determine whether or not destination Servers support TLS encryption and if they do then the sending Server will upgrade the connection to the STARTTLS SMTP command protocol.

Bottom line: Port 25 and the more recent alternative 2525 Port does continue to primarily be used for SMTP relaying (FYI; SMTP is the transmittal relaying of Email between Servers).  However that said, currently in most cases SMTP clients should not use these Ports in my opinion and the fact is Port 25 is very often blocked by ISP and cloud hosting providers (which is why we have the alternate Port 2525) in order to try and curb SPAM that can occur between compromised Servers.  So unless you happen to be managing a Mail Server it is generally highly recommend to avoid using Port 25 (or in my view 2525 as well). Port 587 is the default mail submission port and should always be the Port used to route Email by a proper Mail Server when possible, that is unless you're explicitly blocked by your upstream network or hosting provider. Port 587, coupled with TLS encryption, will ensure that email is submitted securely and follows IETF guidelines. Port 465 is generally used for legacy systems that are only capable of using this connection method therefore Port 465 is typically used in the event your application demands it.  In regards to Port 2525 discussed here in this topic, which as I said mirrors Port 587, yes it does support TLS encryption and is generally not blocked to the extent that Port 25 tends to be but as I said before is not currently endorsed by either the IETF or IANA. Because 2525 happens to be a non-traditionally high port number it is generally not blocked by ISPs and Cloud Hosting providers but nevertheless in my opinion should only be used in the event the other Ports previously mentioned happen to have connectivity issues.
Processor: i3 2.53 GHz 4 GIG RAM, OS: WIN 7, Connection: High Speed, Virus/Malware Protection: Avast-2015, SpywareBlaster, Windows Firewall & Defender. Email: Outlook 2010 w/ POP Peeper Email Notifiers.

Offline bob3160

  • Avast Überevangelist
  • Probably Bot
  • *****
  • Posts: 45153
  • 61 Years of Happiness
    • bob3160 Protecting Yourself, Your Computer and, Your Identity
Re: Avast checks one outgoing email but not another
« Reply #19 on: June 19, 2016, 12:23:20 PM »
Bob, Pondus and Snake - I don't get your willingness to excuse Avast here.

The two links you provide indicate that (a) 2525 is actually used by email companies and (b) it could be used by trojans.  Sorry, but this is exactly why Avast should scan my outgoing emails on port 2525 if I add ,2525 to the SMTP field in the redirect list (pictured in my first post above).  But that does not work.

Why are you so fast to let Avast off the hook?  Avast should be working exactly as I say.
Why are you so insistent on using a port that is dangerous (2525) when a safe alternative (587 is available and works ???
Free avast! Security Seminar: http://bit.ly/2N1eaR2  -  Important: http://www.organdonor.gov/ -- My Web Site: http://bob3160.strikingly.com/ - Win 10 Pro v20H2 64bit, 24 Gig Ram, 1TB SSD, AvastOmni 20.7.xxx, How to Successfully Install Avast http://goo.gl/VLXdeRepair & Clean Install https://goo.gl/t7aJGq

Offline Pondus

  • Probably Bot
  • ****
  • Posts: 36991
Re: Avast checks one outgoing email but not another
« Reply #20 on: June 19, 2016, 12:35:24 PM »
Quote
Bob, Pondus and Snake - I don't get your willingness to excuse Avast here.
We are not, we just give you the info found online, and try to explain why avast dont scan

As the info found say port 2525 is not "never been officially supported"  this may be the reson why avast dont scan outgoing mail sendt true that port, maybe it will be supported in a later version

If we are correct or not only somone from avast team can tell ... i will see if i can get somone to comment


« Last Edit: June 19, 2016, 12:37:17 PM by Pondus »

Offline lukor

  • Avast team
  • Super Poster
  • *
  • Posts: 1879
    • AVAST Software
Re: Avast checks one outgoing email but not another
« Reply #21 on: June 20, 2016, 12:48:25 AM »
Hi, does entering 2525 only works for the mail client/account running on port 2525?
Thanks. Lukas.

Offline glnz

  • Sr. Member
  • ****
  • Posts: 300
Re: Avast checks one outgoing email but not another
« Reply #22 on: June 20, 2016, 02:10:53 AM »
Lukas - If I add
    ,2525
to my redirect listings for SMTP (not SSL), all my email connections stop.  Email does not work any more.  Outlook Express gives me error messages.
Various Dell Optiplexes running XP Pro SP3 32-bit, Win 7 Pro SP1 64-bit and Win 10 Pro 64-bit.  Firefox with security add-ons.

Offline lakrsrool

  • Advanced Poster
  • **
  • Posts: 712
  • Get the Picture !
Re: Avast checks one outgoing email but not another
« Reply #23 on: June 20, 2016, 04:02:39 AM »
glnz, Since Port 2525 does support TLS encryption, have you tried using the Port with TLS  protocol enabled to see if this makes a difference?
Processor: i3 2.53 GHz 4 GIG RAM, OS: WIN 7, Connection: High Speed, Virus/Malware Protection: Avast-2015, SpywareBlaster, Windows Firewall & Defender. Email: Outlook 2010 w/ POP Peeper Email Notifiers.

Offline glnz

  • Sr. Member
  • ****
  • Posts: 300
Re: Avast checks one outgoing email but not another
« Reply #24 on: June 20, 2016, 04:05:29 AM »
laksrool - that email ISP does NOT use SSL with our account.  But they DID ask us to use 2525.
Various Dell Optiplexes running XP Pro SP3 32-bit, Win 7 Pro SP1 64-bit and Win 10 Pro 64-bit.  Firefox with security add-ons.

Offline vojtech

  • Avast team
  • Advanced Poster
  • *
  • Posts: 939
    • ALWIL Software
Re: Avast checks one outgoing email but not another
« Reply #25 on: June 20, 2016, 03:02:18 PM »
You can look to the log file 'C:\ProgramData\AVAST Software\Avast\log\Mail.log' for errors when the port is added and sending fails.

Offline glnz

  • Sr. Member
  • ****
  • Posts: 300
Re: Avast checks one outgoing email but not another
« Reply #26 on: June 20, 2016, 03:09:27 PM »
vojtech - lots of work.  Also, mail.log is in Application Data, not where you said.  Also, I cannot open it because it is in use.

Maybe next weekend - not now.
Various Dell Optiplexes running XP Pro SP3 32-bit, Win 7 Pro SP1 64-bit and Win 10 Pro 64-bit.  Firefox with security add-ons.

Offline Pondus

  • Probably Bot
  • ****
  • Posts: 36991
Re: Avast checks one outgoing email but not another
« Reply #27 on: June 20, 2016, 03:32:53 PM »
Quote
Also, I cannot open it because it is in use.
Close mail client and try again


Offline glnz

  • Sr. Member
  • ****
  • Posts: 300
Re: Avast checks one outgoing email but not another
« Reply #28 on: June 20, 2016, 03:44:00 PM »
Pondus - no, does not work.  Still locked.  And I rebooted and tried again - still locked - before turning OE back on.

This weekend maybe.
Various Dell Optiplexes running XP Pro SP3 32-bit, Win 7 Pro SP1 64-bit and Win 10 Pro 64-bit.  Firefox with security add-ons.

Offline DavidR

  • Avast Überevangelist
  • Certainly Bot
  • *****
  • Posts: 84792
  • No support PMs thanks
Re: Avast checks one outgoing email but not another
« Reply #29 on: June 20, 2016, 03:53:01 PM »
<snip>
Also, mail.log is in Application Data, not where you said. 

Also, I cannot open it because it is in use.
<snip>

Yes it is in winXP, the location given is for Vista, Win7 and later.

How are you trying to open the mail.log file (notepad or other text editor) ?

Pondus - no, does not work.  Still locked.  And I rebooted and tried again - still locked - before turning OE back on.
<snip>

You could or rather should disable the Mail Shield that would be the only thing accessing the mail.log, not your email client.
Windows 10 Home 2004 64bit/ Acer Aspire F15/ Intel Core i5 7200U 2.5GHz, 8GB DDR4 memory, 256GB SSD, 1TB HDD/ avast! free 21.3.2459 (build 21.3.6164.561) UI 1.0.609/ Firefox, uBlock Origin, uMatrix/ MailWasher Pro/ Avast! Mobile Security