Failure in Email alerts test

Test was not concluded in Email alerts test.
I configured properly necessary requirements for Email alerts as below, I think.
Then pushed Test button, but the test process was freezed.
After several trials, I changed “From part” sk-laptop to my email address, but result was same, same failures repeated.
Please advise proper procedures.

Recipient: My email address
SMTP settings :
Server address : smtpa.home.ne.jp
Port : 465 (for SSL)
From : sk-laptop
Server authentication
: User name: sekko
: Password: ********

OS : Ubuntu 9.04 / virtualize on Mac OSX by VitualBox v.2.2.2
Package : avast4workstation_1.3.0-2_i386

hallo,
just try to specify some local port, and run netcat (nc) there in a listening mode (or real local smtp server) - you can easily check, whether the connection attempt was made, and what authentication was used.

regards,
pc

Hi, pc
I changed SMTP setting from smtpa (port 465) to smtp (port 25).
Test was successful in above condition, but still I have trouble in smtpa (port 465).

I have just tried the latest build that you introduced today, but trouble is lasting.

hallo, looks like some problem in SSL authentication, please have a look into SMTP server, why the connection attempt was refused.

regards,
pc

Thank you, zilog,
I found a discrepancy between the SSL authentications, I will check ISP (JCOM) tomorrow.
Current SMTP settings “Test was successful” are ;

  • On Avast Email alerts window
    Server address : smtp.jcom.home.ne.jp
    Port : 25

  • On Thundrbird
    Server address : smtpa.home.ne.jp (authentication is made on)
    Port : 465

Hi, zilog
I had long discussion with JCOM (ISP), this morning.
JCOM said they have been managed SMTP and SMTPa server long long time, and both servers are normally operated.
JCOM advised me, pls ask you if there is unexpected problem in Avast smtp settings area, does your Email alerts system support port 465?

I don’t know the scheme of access into external smtp(a) server from the Avast Email Alerts.

Regards, Sekko

Hallo, it’s not about port, but about authentication style. You can run any service on any port (at least as root:), it, in the unshot, just a number.

Just use: tcpdump -n -p -e -X -s 1500 tcp and port 465
and then, detect a virus (eicar.org’s testfile).

the packet dump will reveal all (rather than people at the provider’s side:).

regards,
pc

Hi, zilog
Sorry I don’t understand your suggestions, please teach me terminal manipulations.
Regards, Sekko

option #2 is to use something GUI-endowed, for example Ethereal :). under the hood, it’s tcpdump/libpcap machinery anyway :).

regards,
pc

If youre using email, do you know about dgtestsmtp ? Run it with one email address on the command line to test your SMTP settings. If you receive the email, your globals.xml SMTP settings are set up correctly.

Quite useful link, thanks :).
pc