Hello,

i have iredmail Pro installed on my sever and it is working fine but i have issue in mailing lists which is any one can send to this lists even if he is not listed on members or moderators or in the domain, i am sure that i selected moderators only can send to this lists but unfortunately any one of the world can send to this lists, please advice

Regards

Hi Zhang,

We are facing issues with the mailing list for users. Assume there is a mailing list like "abc-ops@mail.xxx.com" which has users added to it. Alais name for the domain is defined as "abc-ops@xxx.com". Now on adding a new user to this mailing list, removes one or many user's  randomly from the existing list.

Note: I am able to view all the user's through the UI. Whereas while execuing the below commands user's are missing

For eg..,

On executing the below command (Using actual domain name) all the users (including the newly added one) is listed.

for cf in $(ls *.cf); do echo $cf; postmap -q abc-ops@mail.xxx.com  ldap:./${cf}; done

If we run the below command (using alias name), few existing users are missing in the list

for cf in $(ls *.cf); do echo $cf; postmap -q abc-ops@xxx.com  ldap:./${cf}; done

Note: We also re-created the mailing list & re-enabled the alias name for the domain mail.xxx.com

Thanks
Soundarajan

Nothing. Just make sure you have only one iRedAdmin-Pro running.

Glad to hear that :-)

What should I do to update the license?

Nothing. Just make sure you have only one iRedAdmin-Pro running.

best regards,
Alessio Gattei

==== Required information ====
- iRedMail version: 0.8.4 (First installed version 0.7.4)
- Store mail accounts in which backend (LDAP/MySQL/PGSQL): iRedAdmin-Pro v1.6.0 MySql (First version 1.4.0)
- Linux/BSD distribution name and version: CentOS 6.2 x64
- Related log if you're reporting an issue:
====

I discovered that BOTH when attempting to send mail via the roundcube web interface and via a mail client using the iredmail installation as the smtp server (and the destination email is a hosted email domain), greylisting takes place.

This is unexpected.

Greylisting is configured to be bypassed for authenticated users and all clients listed in Postfix "mynetworks". Please show us output of command "postconf -n" here for troubleshooting.

====

I discovered that BOTH when attempting to send mail via the roundcube web interface and via a mail client using the iredmail installation as the smtp server (and the destination email is a hosted email domain), greylisting takes place. Which, of course, errors out the web client and the mail client.

I fixed the web client by adding 127.0.0.1 as a whitelisted IP to the greylist config in the cluebringer web interface.

But, users with smtp clients, this is a problem. The correct answer would be that if the smtp sender is an authenticated user, there should be no greylisting (regardless of the IP of the smtp client). Otherwise, we want to greylist.

So, how would I configure this?

thanks.

Anything I need to add other than the domain to the %intermal_domains group? Looks like, also, %internal_ips is defaulted to 10.0.0.0/8 .

With the upcoming release, you should remove your alias domain first, then re-add it. so that iRedAdmin-Pro can add missing data/metadata for alias domain.

If I send mail to user@aliasdomain, no greylisting happens -- nothing at all w.r.t. greylisting in the log file. Mail is still delivered (which is a good way to fail) to the user@targetdomain

If I send mail to user@realdomain, greylisting happens.

I'm wondering if iRedAdmin Pro didn't configure something correctly for greylisting with the new alias domain. I connected directly to the cluebringer web interface and don't see anything for the alias domain in there.

thanks.

==== Required information ====
- iRedMail version: 0.8.4
- Store mail accounts in which backend (LDAP/MySQL/PGSQL): PGSQL
- Linux/BSD distribution name and version: RHEL6/64
- Related log if you're reporting an issue:
====

In a new installation I notice that if any spammer, fake "MAIL FROM:" command to a valid alias domain account it can relay mail without been authenticated.

A valid reject if try to relay with a domain account:
**************************************************************
Resolving hostname...
Connecting...
SMTP -> FROM SERVER:
220 mail01.domain.tld (Postfix). All Spam Is Reported. ESMTP
SMTP -> FROM SERVER:
250-mail01.domain.tld
250-PIPELINING
250-SIZE 15728640
250-ETRN
250-STARTTLS
250-AUTH PLAIN LOGIN
250-AUTH=PLAIN LOGIN
250-ENHANCEDSTATUSCODES
250-8BITMIME
250 DSN
MAIL FROM: postmaster@domain.tld
SMTP -> FROM SERVER:
250 2.1.0 Ok
RCPT TO: postmaster@domain.tld
SMTP -> FROM SERVER:
553 5.7.1 : Sender address rejected: not logged in
SMTP -> ERROR: RCPT not accepted from server: 553 5.7.1 : Sender address rejected: not logged in

Message sending failed.                                                #################   PERFECT... It's ok
**************************************************************

The problem when spammer use an alias domain in MAIL FROM: command
************************************************************
Resolving hostname...
Connecting...
SMTP -> FROM SERVER:
220 mail01.domain.tld (Postfix). All Spam Is Reported. ESMTP
SMTP -> FROM SERVER:
250-mail01.domain.tld
250-PIPELINING
250-SIZE 15728640
250-ETRN
250-STARTTLS
250-AUTH PLAIN LOGIN
250-AUTH=PLAIN LOGIN
250-ENHANCEDSTATUSCODES
250-8BITMIME
250 DSN
MAIL FROM: any_valid_user@domain-alias.tld
SMTP -> FROM SERVER:
250 2.1.0 Ok
RCPT TO: another_valid_user@domain.tld      # Or domain-alias.tld
SMTP -> FROM SERVER:
250 2.1.5 Ok
Sending Mail Message Body...
SMTP -> FROM SERVER:
354 End data with .
SMTP -> FROM SERVER:
250 2.0.0 Ok: queued as A897B1340DBD
Message completed successfully.                                             #################   Houston, we've had a problem!!!
************************************************************

Hello,
based on your experience it is safe to implement spam scan from UCEprotect?
http://www.uceprotect.net/en/index.php?m=6&s=11
and backscatter scan from BackScatterer?
http://www.backscatterer.org/index.php?target=usage

Or you suggest to use other antispam list provider?