Need help with ISPConfig Mail and Squirrelmail

[m.xander]

Originally Posted by cbj4074

Next up, mail client configuration settings. (I wish I had seen that screenshot sooner, but that's okay.)

Have you tried any mail client other than Evolution, or tried from any location on the Internet other than your current location?



Many ISPs block outgoing traffic on port 25, so you'll never be able to send mail using that port. (The logic, while flawed, is that less SPAM will come from compromised PCs if they block port 25.)

Try using port 587 for your SMTP connection. (This is the same port you will use even with STARTTLS enabled.)

If you are using SSL for some reason (instead of STARTTLS), try port 465.

I've tried Kmail & Thunderbird with no success... (both of these wouldn't even complete the mail account setup because of an authentication problem with the server.) - tried TLS on port 25 and 587
From Gmail website, I was able to add a third party address 'admin@urbancampsite.com'
selected option to use urbancampsite.com's SMTP server with TLS on port 25
I was able to send an email from admin@urbancampsite.com from Gmail website and then recieved it in evolution...
note - while setting up third party address in Gmail also tried port 587 which didn.t work.

[cbj4074]

Does this same issue occur when you create another email user from within the ISPConfig interface? Say, test@urbancampsite.com?

It's interesting that you were able to send mail from a Gmail account via the SMTP server in question without issue.

[m.xander]

Originally Posted by cbj4074

Does this same issue occur when you create another email user from within the ISPConfig interface? Say, test@urbancampsite.com?

It's interesting that you were able to send mail from a Gmail account via the SMTP server in question without issue.

I've added a new mailbox for test@urbancampsite.com - same results as previous attempts...
See this screenshot of evolution account setup...
On the recieving email tab there is 'Authentication type' -> 'check for supported types' button, which successfully queries the server - then on the 'sending email' tab - > 'check for supported types' returns the error in the screenshot...?




While we're going through the mail configuration, is it important at this stage that I'd like the webmail domain to be 'mail.urbancampsite.com' ...
Would it be appropriate to make a sub-domain 'mail.urbancampsite.com' and just for uniformity make 'mail.urbancampsite.com' the IMAP server and the SMTP server instead of 'urbancampsite.com' as they are now...
Can you clarify something for me... about sub-domains, once I own and host a domain I can create as many sub-domains of that domain as needed..? and registration of sub-domains is not required as they are resolved via their parent domain..?

Thanks...
Mike.

[cbj4074]

Okay, let's try this.

Please "tail" (follow) the mail log and copy only the messages that occur at the precise moment when you get the above-pictured error message. To tail:

tail -f -n 30 /var/log/mail.log

As for the Evolution configuration, is pressing that "Check for supported types" button a requirement? If not, can you just ignore it?

I use Thunderbird and it can't pass that step automatically, either (I'm not sure why), but when I tell it which authentication mechanism to use, explicitly, it works fine.

Regarding the mail subdomains, it is a standard convention to use mail.example.com for POP/IMAP/SMTP, but there's no technical reason for which you can't forego convention and use that domain for webmail instead. (The convention for webmail is usually webmail.domain.com.)

Truth be told, all of those domains are likely to resolve to the same IP address, so it wouldn't matter which one you actually used.

And yes, that's correct: you can create as many subdomains as you like once you control the TLD (top-level domain).

[m.xander]

Jan  4 14:00:01 25612-21212 postfix/pickup[25658]: 262D2C760867: uid=103 from=<smmsp>
Jan  4 14:00:01 25612-21212 postfix/cleanup[26183]: 262D2C760867: message-id=<20120104030001.262D2C760867@25612-21212.vps.digitalpacific.com.au>
Jan  4 14:00:01 25612-21212 pop3d: Connection, ip=[::ffff:127.0.0.1]
Jan  4 14:00:01 25612-21212 pop3d: Disconnected, ip=[::ffff:127.0.0.1]
Jan  4 14:00:01 25612-21212 imapd: Connection, ip=[::ffff:127.0.0.1]
Jan  4 14:00:01 25612-21212 imapd: Disconnected, ip=[::ffff:127.0.0.1], time=0
Jan  4 14:00:01 25612-21212 postfix/smtpd[26201]: connect from localhost.localdomain[127.0.0.1]
Jan  4 14:00:01 25612-21212 postfix/smtpd[26201]: lost connection after CONNECT from localhost.localdomain[127.0.0.1]
Jan  4 14:00:01 25612-21212 postfix/smtpd[26201]: disconnect from localhost.localdomain[127.0.0.1]
Jan  4 14:00:01 25612-21212 postfix/qmgr[32715]: 262D2C760867: from=<smmsp@25612-21212.vps.digitalpacific.com.au>, size=779, nrcpt=1 (queue active)
Jan  4 14:00:01 25612-21212 postfix/smtpd[26219]: connect from localhost.localdomain[127.0.0.1]
Jan  4 14:00:01 25612-21212 postfix/smtpd[26219]: 79E42C760865: client=localhost.localdomain[127.0.0.1]
Jan  4 14:00:01 25612-21212 postfix/cleanup[26183]: 79E42C760865: message-id=<20120104030001.262D2C760867@25612-21212.vps.digitalpacific.com.au>
Jan  4 14:00:01 25612-21212 postfix/smtpd[26219]: disconnect from localhost.localdomain[127.0.0.1]
Jan  4 14:00:01 25612-21212 postfix/qmgr[32715]: 79E42C760865: from=<smmsp@25612-21212.vps.digitalpacific.com.au>, size=1371, nrcpt=1 (queue active)
Jan  4 14:00:01 25612-21212 amavis[9592]: (09592-13) Passed CLEAN, <smmsp@25612-21212.vps.digitalpacific.com.au> -> <root@25612-21212.vps.digitalpacific.com.au>, Message-ID: <20120104030001.262D2C760867@25612-21212.vps.digitalpacific.com.au>, mail_id: CDAT0vRb0Xno, Hits: 1.178, size: 779, queued_as: 79E42C760865, 424 ms
Jan  4 14:00:01 25612-21212 postfix/smtp[26206]: 262D2C760867: to=<root@25612-21212.vps.digitalpacific.com.au>, orig_to=<root>, relay=127.0.0.1[127.0.0.1]:10024, delay=0.55, delays=0.11/0.01/0/0.43, dsn=2.0.0, status=sent (250 2.0.0 Ok, id=09592-13, from MTA([127.0.0.1]:10025): 250 2.0.0 Ok: queued as 79E42C760865)
Jan  4 14:00:01 25612-21212 postfix/qmgr[32715]: 262D2C760867: removed
Jan  4 14:00:01 25612-21212 postfix/smtp[26220]: 79E42C760865: to=<root@25612-21212.vps.digitalpacific.com.au>, relay=none, delay=0.16, delays=0.15/0.01/0/0, dsn=5.4.4, status=bounced (Host or domain name not found. Name service error for name=25612-21212.vps.digitalpacific.com.au type=A: Host not found)
Jan  4 14:00:01 25612-21212 postfix/cleanup[26183]: A9C10C76086A: message-id=<20120104030001.A9C10C76086A@25612-21212.vps.digitalpacific.com.au>

note - at the time of 'the perfect server' install I did not have urbancampsite.com on the server. so...
in step 12 of the perfect server "Install Postfix, Courier, Saslauthd, MySQL, rkhunter, binutils" it requires
System mail name: <-- server1.example.com
for which I entered 25612-21212.vps.digitalpacific.com.au as at the time I just used this but it is the VPS container.
then in step 21 Install ISPConfig
Full qualified hostname (FQDN) of the server, eg server1.domain.tld [server1.example.com]: <-- ENTER

Was it correct to use 25612-21212.vps.digitalpacific.com.au at those steps?

[cbj4074]

Was it correct to use 25612-21212.vps.digitalpacific.com.au at those steps?

Yes, that's fine, in fact it is preferable. I always leave the hosting-provider-assigned hostname as the primary hostname, in case anything unexpected should happen with the vanity domain's DNS records.

Okay, I think I see the problem here. Tempted to "LOL"...

As I mentioned in a previous post, Postfix will complain if a given domain is used for both myhostname and mydestination in Postfix's main.cf. Now that you have removed the VPS hostname from the mydestination directive, you need to add the mail domain 25612-21212.vps.digitalpacific.com.au via the ISPConfig interface and create a mailbox or a catch-all for it.

The part I failed to realize is that you are attempting to send mail to @25612-21212.vps.digitalpacific.com.au, and not @urbancampsite.com, as evidenced by this excerpt from your log file:

to=<root@25612-21212.vps.digitalpacific.com.au>

To be clear, I think you had two different problems that were "stacking-up". We resolved one of them, but then you changed the test-case (not your fault), which made the second problem harder to spot.

Try making the above change and then report back when you have a chance.

[m.xander]

Originally Posted by cbj4074

Yes, that's fine, in fact it is preferable. I always leave the hosting-provider-assigned hostname as the primary hostname, in case anything unexpected should happen with the vanity domain's DNS records.

Okay, I think I see the problem here. Tempted to "LOL"...

As I mentioned in a previous post, Postfix will complain if a given domain is used for both myhostname and mydestination in Postfix's main.cf. Now that you have removed the VPS hostname from the mydestination directive, you need to add the mail domain 25612-21212.vps.digitalpacific.com.au via the ISPConfig interface and create a mailbox or a catch-all for it.

The part I failed to realize is that you are attempting to send mail to @25612-21212.vps.digitalpacific.com.au, and not @urbancampsite.com, as evidenced by this excerpt from your log file:

to=<root@25612-21212.vps.digitalpacific.com.au>

To be clear, I think you had two different problems that were "stacking-up". We resolved one of them, but then you changed the test-case (not your fault), which made the second problem harder to spot.

Try making the above change and then report back when you have a chance.

OK... In ISPConfig I've made a new domain 25612-21212.vps.digitalpacific.com.au and then in Email added a new mailbox root@25612-21212.vps.digitalpacific.com.au

then tried sending from test@urbancampsite.com and repeated the tail command...

root@25612-21212:~# tail -f -n 30 /var/log/mail.log
Jan  5 13:15:01 25612-21212 postfix/smtpd[7945]: connect from localhost.localdomain[127.0.0.1]
Jan  5 13:15:01 25612-21212 postfix/smtpd[7945]: lost connection after CONNECT from localhost.localdomain[127.0.0.1]
Jan  5 13:15:01 25612-21212 postfix/smtpd[7945]: disconnect from localhost.localdomain[127.0.0.1]
Jan  5 13:20:02 25612-21212 postfix/pickup[5411]: 061A9C76097F: uid=103 from=<smmsp>
Jan  5 13:20:02 25612-21212 pop3d: Connection, ip=[::ffff:127.0.0.1]
Jan  5 13:20:02 25612-21212 pop3d: Disconnected, ip=[::ffff:127.0.0.1]
Jan  5 13:20:02 25612-21212 imapd: Connection, ip=[::ffff:127.0.0.1]
Jan  5 13:20:02 25612-21212 imapd: Disconnected, ip=[::ffff:127.0.0.1], time=0
Jan  5 13:20:02 25612-21212 postfix/cleanup[8036]: 061A9C76097F: message-id=<20120105022002.061A9C76097F@25612-21212.vps.digitalpacific.com.au>
Jan  5 13:20:02 25612-21212 postfix/qmgr[31819]: 061A9C76097F: from=<smmsp@25612-21212.vps.digitalpacific.com.au>, size=779, nrcpt=1 (queue active)
Jan  5 13:20:02 25612-21212 postfix/smtpd[8046]: connect from localhost.localdomain[127.0.0.1]
Jan  5 13:20:02 25612-21212 postfix/smtpd[8046]: lost connection after CONNECT from localhost.localdomain[127.0.0.1]
Jan  5 13:20:02 25612-21212 postfix/smtpd[8046]: disconnect from localhost.localdomain[127.0.0.1]
Jan  5 13:20:02 25612-21212 postfix/smtpd[8072]: connect from localhost.localdomain[127.0.0.1]
Jan  5 13:20:02 25612-21212 postfix/smtpd[8072]: 728ADC760869: client=localhost.localdomain[127.0.0.1]
Jan  5 13:20:02 25612-21212 postfix/cleanup[8036]: 728ADC760869: message-id=<20120105022002.061A9C76097F@25612-21212.vps.digitalpacific.com.au>
Jan  5 13:20:02 25612-21212 postfix/smtpd[8072]: disconnect from localhost.localdomain[127.0.0.1]
Jan  5 13:20:02 25612-21212 postfix/qmgr[31819]: 728ADC760869: from=<smmsp@25612-21212.vps.digitalpacific.com.au>, size=1587, nrcpt=1 (queue active)
Jan  5 13:20:02 25612-21212 amavis[27704]: (27704-10) Passed CLEAN, <smmsp@25612-21212.vps.digitalpacific.com.au> -> <root@25612-21212.vps.digitalpacific.com.au>, Message-ID: <20120105022002.061A9C76097F@25612-21212.vps.digitalpacific.com.au>, mail_id: b1HkB84+Y2NQ, Hits: 1.178, size: 779, queued_as: 728ADC760869, 428 ms
Jan  5 13:20:02 25612-21212 postfix/smtp[8050]: 061A9C76097F: to=<root@25612-21212.vps.digitalpacific.com.au>, orig_to=<root>, relay=127.0.0.1[127.0.0.1]:10024, delay=0.49, delays=0.05/0.01/0/0.43, dsn=2.0.0, status=sent (250 2.0.0 Ok, id=27704-10, from MTA([127.0.0.1]:10025): 250 2.0.0 Ok: queued as 728ADC760869)
Jan  5 13:20:02 25612-21212 postfix/qmgr[31819]: 061A9C76097F: removed
Jan  5 13:20:02 25612-21212 postfix/pipe[8073]: 728ADC760869: to=<root@25612-21212.vps.digitalpacific.com.au>, relay=maildrop, delay=0.03, delays=0.01/0.01/0/0.01, dsn=2.0.0, status=sent (delivered via maildrop service)
Jan  5 13:20:02 25612-21212 postfix/qmgr[31819]: 728ADC760869: removed
Jan  5 13:25:01 25612-21212 pop3d: Connection, ip=[::ffff:127.0.0.1]
Jan  5 13:25:01 25612-21212 pop3d: Disconnected, ip=[::ffff:127.0.0.1]
Jan  5 13:25:01 25612-21212 imapd: Connection, ip=[::ffff:127.0.0.1]
Jan  5 13:25:01 25612-21212 imapd: Disconnected, ip=[::ffff:127.0.0.1], time=0
Jan  5 13:25:01 25612-21212 postfix/smtpd[8147]: connect from localhost.localdomain[127.0.0.1]
Jan  5 13:25:01 25612-21212 postfix/smtpd[8147]: lost connection after CONNECT from localhost.localdomain[127.0.0.1]
Jan  5 13:25:01 25612-21212 postfix/smtpd[8147]: disconnect from localhost.localdomain[127.0.0.1]

Alot of this looks like a foreign language to me... but I was expecting to see the email address test@urbancampsite.com somewhere in the output...?

Then in addition to that the test@urbancampsite.com received an email

From: Cron Daemon <root@25612-21212.vps.digitalpacific.com.au>
To: root@25612-21212.vps.digitalpacific.com.au
Subject: ***SPAM***Cron <smmsp@25612-21212> test -x /etc/init.d/sendmail && /usr/share/sendmail/sendmail cron-msp
Date: Thu, 5 Jan 2012 06:00:02 +1100 (EST) (05/01/12 05:00:02)
Message:
/usr/share/sendmail/sendmail: line 880: /usr/sbin/sendmail-msp: No such file or directory

???

[m.xander]

Also evolution still failed to send an email from test@urbancampsite.com

error message
"The reported error was "Could not connect to urbancampsite.com: Connection refused"."

[imjsa]

some ISP don't allow loopback or whatever they call it to access your own ip even if it has a domain name...
try using the LAN ip address as the server name... instead of your chosen server name...

[imjsa]

also, I have had issues with inexpensive routers to where communication between wireless computers and hard wired cat5 cable computers didn't communicate with each other...