Mailman https ??

I recently changed the webmail.mydomain.com from http 80 to https, ever since then mailman email notifications comes to me for approval as http not https.. i added https to the address and it will open but i cannot submit any changes .. for example: "this is how I receive it now"
s list administrator, your authorization is requested for the
following mailing list posting:
List: [email protected]
From: [email protected]
Subject: Fwd: [PBX] Voicemail 1 in mailbox 258 from 4163644499 on Wednesday, September 08, 2010 at 09:01:34 AM
Reason: Post by non-member to a members-only list
+At your convenience, visit:+
+http://odmaster.mydomain.com/mailman/admindb/group+
+to approve or deny the request.+
but the link above doesn't open when i click on it.. i have to change it to https.. which is fine.. but when i click on Approve pr Deny and submit changes .. Safari shows me a msg that Safari could not connect to the Server and it goes back to http not https..
is there away to fix this .. cause I got lots of msgs that I need to approve
Thanks.

I have this mailman problem as well, but I think it's a bug in Mailman, because the moderation site uses a hardcoded http:// link for the from that is sent via POST.
My workaround is to use Safari and the Webdeveloper mode that enables me to change the form link into https:// and then the form works just fine. Other forms work well, as they only use relative links.
I just tried Boddies suggestion, but as I'm already having a redirect, I cannot store mailman specific paths. This is the current Redirect I have in the Sites Alias Settings:
Type: RedirectMatch
Pattern: (.*)
Path: https://myserver.com$1
It works really fine, just except for this one mailman moderation page. So my guess is, that the apache redirect has some troubles redirecting POST requests
Any suggestion would be greatly appreciated!
(And I already filed a bug, but haven't heard from anyone so far).
Regard,
Michael

Similar Messages

Address error. CrystalEnterprise.Smtp: SMTP_E_MAILBOX_UNAVAILABLE_2(550)

Hi,
Due to problems with the Report Server, I had to reinstall the Crystal Reports Server XI. I had copied previous job description into word before reinstalling. When I was rescheduling reports I keep getting address errors.
I noticed that the description is different compared to the previous installation. In the previous installation, I had the description "Mail the instance to 'xxx#xxx.com.au', 'bbb#xxx.com.au' with a subject of '%SI_NAME%'.
In the new installation, the description is "Mail the instance to "[xxx#xxx.com.au, bbb#xxx.com.au]" with a subject of '%SI_NAME%'. It seems that the new installation added square brackets around the emails I entered, which was "xxx#xxx.com.au; bbb#xxx.com.au" (without quotes).
How can I get Crystal reports server to recognise the email properly?
PS: the at symbol is replaced with "#" due to limitations of adding email addresses.
regards
Frank Neo

Hi Kyle,
I would suggest testing on the Job Server machine by using telnet to see if you can email externally from the command prompt. Below is a link of how to use mailman:
http://www.yuki-onna.co.uk/email/smtp.html
Are you able to schedule the report externally without an attachment? I would also suggest speaking to your Exchange Server administrator. There may be logs or restrictions for outgoing emails set on the mail server.
Regards,
Wallie

Is it possible to email outside of organization?

Hi,
Is it possible to email crystal reports (in excel spreadsheets)
to email accounts outside of the organization. I have no problem scheduling reports to internal email addresses, but everytime I schedule a report to an outside email the report fails with an error of:
address error. CrystalEnterprise.Smtp: SMTP_E_MAILBOX_UNAVAILABLE_2(550)
We are using crystal server XI release 2.
Any suggestions or comments would be appreciated.
Regards
Kyle

Hi Kyle,
I would suggest testing on the Job Server machine by using telnet to see if you can email externally from the command prompt. Below is a link of how to use mailman:
http://www.yuki-onna.co.uk/email/smtp.html
Are you able to schedule the report externally without an attachment? I would also suggest speaking to your Exchange Server administrator. There may be logs or restrictions for outgoing emails set on the mail server.
Regards,
Wallie

Mailman vs. https?

On a 10.5.2 server, the web server has SSL enabled, and thus only answers on port 443.
Then, mailman mailing lists were enabled, and the initial mailing list (Mailman) was created.
The initial welcome messages (and subsequent welcome messages) contained:
Welcome to the [email protected] mailing list!
To post to this list, send your email to:
[email protected]
General information about the mailing list is at:
http://redacted.example.com/mailman/listinfo/mailman
If you ever want to unsubscribe or change your options (eg, switch to
or from digest mode, change your password, etc.), visit your
subscription page at:
http://redacted.example.com/mailman/options/mailman/bob%40redacted.example.com
The problem: those are all http:// URLs, which don't exist. Manually changing the
prefix to https:// gives access to the pages. But all the links on those pages are also
incorrectly http:// as well. Making the mailman web UI un-usable.
Is there a fix?

Something of a fix is in the Mailman FAQ at
http://www.python.org/cgi-bin/faqw-mm.py?req=show&file=faq04.027.htp
By editing mm_cfg.py and running "withlist" as described there, mailing lists
subsequently created have proper Welcome messages, and the links on their
Web pages are all good https:// URLS.
However, existing lists still have bad http:// URLS on their web pages. Unfortunately
that includes the original Mailman list, and its Web UI pages. Anyone know how
to fix those up as well?

10.6.2 Mail Server turn on SSL, mailman still points to non ssl (http)

Hi!
Running osx 10.6.2 server on an x-serve dual quad core intel processors.
Services running:
DNS
MAIL
OD
Web
Mail server is on DMZ zone of our firewall.
I became a little paranoid after original configuration of this server, and enabled SSL for my web services by going to Web in server admin and then "sites" then tab "security" and checked off "enable secure socket layer (SSL)"
SSL is working fine for me and my employees. When trying to respond to a Moderator request for mailman, the moderator e-mails send me links that point to http: address's. I can get around this by inserting a "s" into the copied ad pasted address, however when it comes to the point of "submit data" button on moderator interface after as example saying i want to reject an email, I am redirected to a non https site and never goes anywhere. I called Apple support and was told that I would have to pay them to fix this even though I have an extended warranty.
Does anybody know how I can resolve this?
thanks!

I think I see the problem: softpac2000 assumed you were serving both secure and insecure versions of your site, so all that was needed was a redirect from the /mailman/ section of the insecure site to its equivalent on the sercure site. From your description above, you're only serving over SSL -- no insecure version of the site, so nothing to redirect from. Here's a modified version of his instructions that'll create an insecure version of the site, that just redirects to the same page on the secure version:
1. Open Server Admin
2. Click on the Web Service on the left pane
3. Click on Sites icon on the top right pane
(At this point, you should see only one site listed, with a port number of 443; if this is not correct, I've misunderstood your setup and you should not follow the rest of these instructions.)
4. Click the "+" button under the site list to add a new virtual site
5. Set the new site's hostname and IP Address to match the old (secure) site, but leave the Port number at 80
6. Put something descriptive in the Host Description field
7. Click on the Aliases tab on the bottom right pane
8. Under URL Aliases and Redirects, delete all of the existing aliases by selecting them (one at a time), then clicking "-" underneath
9. Under URL Aliases and Redirects click on the + sign
10. Select "RedirectMatch" on the Type drop down menu
11. Type "(.*)$" without the quotes on the Pattern text box
12. Type "https://yourdomain.com$1" on the Path text box. Don't forget to replace yourdomain.com with your actual domain name
13. Click on Save button on the bottom right

Https mailman issue

I have my mailman configured, it emails me when a moderator request is needed. I have recently moved my www to https, and now mailman emails me the links with http, I can manually add the s, but I didn't know if it was in a config I am missing?
I didn't think the url fix would work, because the domain isn't changing.
Any ideas?
Thanks,
JL

For anyone that wants secure mailman.
cd /usr/share/mailman/Mailman
pico mm_cfg.py
add the following line
DEFAULTURLPATTERN = 'https://%s/mailman/'
save the file
at prompt cd ..
cd bin
./withlist -l -a -r fix_url
Should scroll through your lists.
From the mailman admin it will use the ssl.
Hope this helps someone.
JL
Xserve G5 Mac OS X (10.4.8)

Mailman - trouble creating a second list at an existing virtual host

I have a Virtual Alias error problem ...
I have a Mailman list working (for months) ... *discuss at lists.MLDfamily.org*. I've just created a new list ... *discuss-adults at lists.MLDfamily.org*. The web interface works fine for the new list and it shows lists.MLDfamily.org as its host_name.
+http://lists.mldfamily.org/mailman/admin/discuss-adults+
Both lists show up when I run the following command:
/usr/share/mailman/bin/list_lists -V lists.MLDfamily.org
But deliveries to the Postfix mail server nets me this error on my local server (i.e. the email is making it fine to my server):
Nov 28 11:44:11 darcee postfix/smtpd[11450]: NOQUEUE: reject: RCPT from mail-pv0-f170.google.com[74.125.83.170]: 550 5.1.1 <[email protected]>: *Recipient address rejected: User unknown in virtual alias table*; from=<[email protected]> to=<[email protected]> proto=ESMTP helo=<mail-pv0-f170.google.com>
Deliveries to the initial discuss list at this virtual domain continue to work but discuss-adults give the virtual alias table error.
What do I need to do to get this new list into the virtual domain table? I am thinking I am overlooking the obvious - your help is appreciated.
Thanks in advance, Dean
FWIW, this is the process I used to create the list:
(did not need to create the virtual domain since it already existed)
Stopped the mail server using server admin
sudo /usr/share/mailman/bin/rmlist -a discuss-adults +(to remove all residual old list stuff)+
sudo /usr/share/mailman/bin/newlist discuss-adults
sudo /usr/share/mailman/bin/list_lists +new list showed up+
sudo /usr/share/mailman/bin/list_lists -V lists.MLDfamily.org +new list did not show up+
sudo /usr/share/mailman/bin/withlist -l -r fix_url discuss-adults -u lists.MLDfamily.org
sudo /usr/share/mailman/bin/list_lists -V lists.MLDfamily.org +new list now shows up at the proper virtual domain+
sudo /usr/share/mailman/bin/genaliases
sudo postfix reload +failed since mail server was stopped+
started mail server using server admin
To confirm the updates of the virtual alias table I did the following:
ls -l /var/mailman/data +aliases, aliases.db, virtual-mailman, & virtual-mailman.db all were time stamped the last few minutes+
Looking inside aliases and virtual-mailman conformed the proper entries. Aliases and virtual-mailman both contained the following stanzas (in addition to others):
~~
+# STANZA START: discuss+
+# CREATED: Sun Nov 28 11:39:09 2010+
+discuss: "|/usr/share/mailman/mail/mailman post discuss"+
+discuss-admin: "|/usr/share/mailman/mail/mailman admin discuss"+
+discuss-bounces: "|/usr/share/mailman/mail/mailman bounces discuss"+
+discuss-confirm: "|/usr/share/mailman/mail/mailman confirm discuss"+
+discuss-join: "|/usr/share/mailman/mail/mailman join discuss"+
+discuss-leave: "|/usr/share/mailman/mail/mailman leave discuss"+
+discuss-owner: "|/usr/share/mailman/mail/mailman owner discuss"+
+discuss-request: "|/usr/share/mailman/mail/mailman request discuss"+
+discuss-subscribe: "|/usr/share/mailman/mail/mailman subscribe discuss"+
+discuss-unsubscribe: "|/usr/share/mailman/mail/mailman unsubscribe discuss"+
+# STANZA END: discuss+
~~
+# STANZA START: discuss-adults+
+# CREATED: Sun Nov 28 11:39:10 2010+
+discuss-adults: "|/usr/share/mailman/mail/mailman post discuss-adults"+
+discuss-adults-admin: "|/usr/share/mailman/mail/mailman admin discuss-adults"+
+discuss-adults-bounces: "|/usr/share/mailman/mail/mailman bounces discuss-adults"+
+discuss-adults-confirm: "|/usr/share/mailman/mail/mailman confirm discuss-adults"+
+discuss-adults-join: "|/usr/share/mailman/mail/mailman join discuss-adults"+
+discuss-adults-leave: "|/usr/share/mailman/mail/mailman leave discuss-adults"+
+discuss-adults-owner: "|/usr/share/mailman/mail/mailman owner discuss-adults"+
+discuss-adults-request: "|/usr/share/mailman/mail/mailman request discuss-adults"+
+discuss-adults-subscribe: "|/usr/share/mailman/mail/mailman subscribe discuss-adults"+
+discuss-adults-unsubscribe: "|/usr/share/mailman/mail/mailman unsubscribe discuss-adults"+
+# STANZA END: discuss-adults+

The solution came from Mark Shapiro in another forum. In short - always use lower case.
ds
+It should happen automatically. I suspect it didn't in your case+
+because of certain case-sensitivities which are really bugs. If you+
+make all your domain names in mm_cfg.py, i.e. DEFAULTURLHOST,+
+DEFAULTEMAILHOST, additional domains in add_virtualhost() and+
+domains in POSTFIXSTYLE_VIRTUALDOMAINS, all lower case and use all+
+lower case in -u options to newlist or fix_url. Everything should work.+
+The underlying bug is that domains in add_virtualhost() directives are+
+lower-cased by Mailman but are matched case-sensitively to+
+POSTFIXSTYLE_VIRTUALDOMAINS so if the POSTFIXSTYLE_VIRTUALDOMAINS+
+domains are mixed or upper case, they don't match.+
+If you make everything lower case and run fix_url with a lower case -u+
+domain and then run genaliases, you should be OK.+

Configuring host name in mailman

I'm trying to reconfigure the DEFAULTEMAILHOST and DEFAULTURLHOST in my mm_cfg.py and default.py files in Mailman (I'm repurposing my server to be a dedicated mail server, have another one for web services), but as soon as I restart Mailman the configurations revert to the previous settings.
Where is Mailman drawing this old data from so that I can change it permanently?
TIA,
Marshall

Yes, that was a bit strange taking the time to post that you'd solved it but not posting the solution
I found that I had to do two things. The first was remove mm_cfg.pyc which is a compiled version of mm_cfg.py. That forces python to recompile the file and creates a new mm_cfg.pyc with the values you specific in mm_cfg.py.
Then, as is 'half pointed out' in Defaults.py to change the already generated html for each list's interface you have to run:
$cd /usr/share/mailman/bin
$sudo ./withlist -l -r fix_url <listname>
(replacing <listname> with the name of each of your lists).
Once I did those two things the urls in the HTML interface changed. I did this to move the mailman interface to port 443, because I am using a ReverseProxy on the main site. I tried ProxyPass /mailman/ ! to ensure that the mailman URLs didn't get passed to the Proxy, but that was re-written by Server Admin when I changed the Proxy configuration. So I created a separate site on <servername:443> to handle Mailman.
I had to add
DEFAULTURLPATTERN = 'https://%s/mailman/'
PUBLICARCHIVEURL = 'https://%(hostname)s/pipermail/%(listname)s'
to mm_cfg.py to ensure that it used port 443.
hth,
James

Mailman + Postfix - User unknown

Hi all, I'm having some trouble installing mailman (who doesn't?) right now.
I tried everything. I followed EXACTLY what is said on our wiki (https://wiki.archlinux.org/index.php/Mailman) but still it's not working.
Actually the only thing that is not working is 'sending an email to the mailing list'. And this is quite important for a mailing list, I guess.
After spending hours trying, here is my current status:
I created a mailing list called pynochio, with [email protected] as the mailing list address.
Postfix reads my /var/lib/mailman/data/virtual-mailman file and applies the mapping. I'm sure about that because I changed the content of virtual-mailman (and then hashed it using postmap command) and the email postfix was trying to authenticate changed. (so there is no permission issue from this side)
But then postfix concludes that the user doesn't exist. Here are fresh logs from journalctl, just for you:
Mar 20 19:59:53 ks3100290 postfix/qmgr[26527]: 128382077C: from=<[email protected]>, size=1775, nrcpt=2 (queue active)
Mar 20 19:59:53 ks3100290 postfix/trivial-rewrite[26562]: warning: do not list domain too.gy in BOTH mydestination and virtual_mailbox_domains
Mar 20 19:59:53 ks3100290 postfix/trivial-rewrite[26562]: warning: do not list domain too.gy in BOTH mydestination and virtual_mailbox_domains
Mar 20 19:59:53 ks3100290 postfix/virtual[26567]: 128382077C: to=<[email protected]>, relay=virtual, delay=0.74, delays=0.65/0.03/0/0.07, dsn=5.1.1, status=bounced (unknown user: "[email protected]")
Mar 20 19:59:53 ks3100290 postfix/virtual[26567]: 128382077C: to=<[email protected]>, relay=virtual, delay=0.78, delays=0.65/0.03/0/0.1, dsn=2.0.0, status=sent (delivered to maildir)
This warning appears because in the tutorial we are said to put `too.gy` (our domain) in mydestination and because in my postfix database inside the `domain` table, `too.gy` is said to be virtual (transport=virtual). I don't know if it should be that way.
My problem is that I don't really know how postfix and mailman are supposed to communicate. Postfix is supposed to let mailman handle things since [email protected] is a list address but it doesn't.
I read some tutorials (on other distribs) and they are using lists.too.gy domain for their lists address (it seems easier) but it looks like there's a better way to do it and in the archlinux mailman documentation, we are not using such subdomain for our lists. So I want to do it the right, archlinux way.
There is `postfix_to_mailman.py` transport script thing but I read it's a bad practice...
Here is the output of `postconf -n` (which respects the mailman tutorial, once again):
alias_database = $alias_maps
alias_maps = hash:/etc/postfix/aliases, hash:/var/lib/mailman/data/aliases
broken_sasl_auth_clients = yes
command_directory = /usr/bin
config_directory = /etc/postfix
daemon_directory = /usr/lib/postfix
data_directory = /var/lib/postfix
debug_peer_level = 2
debugger_command = PATH=/bin:/usr/bin:/usr/local/bin:/usr/X11R6/bin ddd $daemon_directory/$process_name $process_id & sleep 5
html_directory = no
inet_protocols = ipv4
local_recipient_maps = $alias_maps
local_transport = virtual
mail_owner = postfix
mailq_path = /usr/bin/mailq
manpage_directory = /usr/share/man
mydestination = localhost, too.gy
mydomain = too.gy
myhostname = mail.too.gy
mynetworks_style = host
myorigin = $mydomain
newaliases_path = /usr/bin/newaliases
queue_directory = /var/spool/postfix
readme_directory = /usr/share/doc/postfix
recipient_delimiter = +
relay_recipient_maps = hash:/var/lib/mailman/data/virtual-mailman
sample_directory = /etc/postfix/sample
sendmail_path = /usr/bin/sendmail
setgid_group = postdrop
smtpd_recipient_restrictions = permit_mynetworks, permit_sasl_authenticated, reject_unauth_destination
smtpd_relay_restrictions = permit_mynetworks, permit_sasl_authenticated, reject_unauth_destination
smtpd_sasl_auth_enable = yes
smtpd_sasl_local_domain = $mydomain
smtpd_sasl_path = /var/run/dovecot/auth-client
smtpd_sasl_security_options = noanonymous
smtpd_sasl_tls_security_options = $smtpd_sasl_security_options
smtpd_sasl_type = dovecot
smtpd_tls_auth_only = yes
smtpd_tls_cert_file = /etc/ssl/private/server.crt
smtpd_tls_key_file = /etc/ssl/private/server.key
smtpd_tls_loglevel = 1
transport_maps = hash:/etc/postfix/transport
unknown_local_recipient_reject_code = 550
virtual_alias_maps = hash:/etc/postfix/virtual, proxy:mysql:/etc/postfix/virtual_alias_maps.cf, hash:/var/lib/mailman/data/virtual-mailman
virtual_gid_maps = static:5000
virtual_mailbox_base = /home/vmail
virtual_mailbox_domains = proxy:mysql:/etc/postfix/virtual_domains_maps.cf
virtual_mailbox_limit = 512000000
virtual_mailbox_maps = proxy:mysql:/etc/postfix/virtual_mailbox_maps.cf
virtual_minimum_uid = 5000
virtual_transport = virtual
virtual_uid_maps = static:5000
Any help appreciated. I'm on it since 10 hours, I don't want to kill myself.
EDIT: Forgot my `/etc/mailman/mm_cfg.py` >
# -*- python -*-
from Defaults import *
DEFAULT_URL_HOST = 'lists.too.gy'
DEFAULT_EMAIL_HOST = 'too.gy'
MTA = 'Postfix'
VIRTUAL_HOSTS.clear()
add_virtualhost(DEFAULT_URL_HOST, DEFAULT_EMAIL_HOST)
POSTFIX_STYLE_VIRTUAL_DOMAINS = ['too.gy']
DEFAULT_URL_PATTERN = 'http://%s/'
PUBLIC_ARCHIVE_URL = 'http://%(hostname)s/archives/%(listname)s'
MAILMAN_SITE_LIST = 'mailman'
Last edited by toogy (2014-03-20 19:23:23)

AlanNYC wrote:
If I turn off local recipient checking, will I actually get my mail?
Yes, all email properly addressed should be delivered to you without problems.
The line only affects improperly addressed email, in this case allowing them to be accepted instead of rejected.
Since you are running Spamassassin and an IMAP server, I suggest also using the line
luser=[email protected]
which will send all improperly addressed mail to the address specified by "[email protected]". This is what I meant by "catch-all" address.
If you find postfix giving you problems after adding the lines, simply delete them or comment them out by adding a hash mark to the front of the line, e.g.
#localrecipientmaps =
Alternatively, you can simply make no changes and allow the log messages to accumulate. The messages mean that postfix is doing its job by rejecting email addressed to users that don't exist. The above steps allow you to receive mail addressed to [email protected], where "anything" is any string allowed in an email address.
I assume you're testing your changes using a separate email account, but in case you're not: sign up for a free email account with any of a number of free email services (Gmail, Yahoo) and test your postfix install as you make changes using the free account.

Steps in migrating Web and mailman from one server to another

I am minimally skilled so am taking this slowly
I currently have a server set to manage several websites all on the same IP forwarded from a DSL modem. Also Mailman provides list distribution for several of the websites. That box also serves as a primary DNS within my subnet behind the modem. My question is what services to I transfer first to make sure I have it right. Shooting from the hip, I would say I do it in this order:
~ Set up the multiple web sites on the new server.
~ Set up mail services on the new server
~ Set up the mailman services on the new server.
~ Change the port forwarding on the modem from the old box to the new one so the outside world now gets sent to the new server
~ Change DNS services for the intranet
Does this sequence make sense or am I missing something?

Actually, I migrated using a process in this thread:
http://discussions.apple.com/message.jspa?messageID=6390958#6390958
and it worked very well. Had to do a lot of clean-up to get Apache to work correctly but now it does.

Mailman cannot create new list

In OS X Server 10.4.x, for some reason creating a new list for an existing virtual domain results in "Error: Unknown virtual host: <domain>".
This domain exists and existing lists can be updated, but the creation new list fails. This virtual domain was setup after following the steps indicated in this thread
http://discussions.apple.com/thread.jspa?messageID=659014
Have gone the step for mailman genaliases and postfix reload.
Still the error. Any help in fixing the problem is much appreciated.
XServe G4 Mac OS X (10.4.4)

Are you adding the list via SA or the web interface?

Mailman in OS X Server (10.8)?

What happened to Mailman and how can I get it's functionality back into OS X Server?

Mailman has been removed, but it's possible to get it back. Check out this guide:
http://www.livetime.com/mountain-lion-mailman-mailing-list/

Mailman destroys html-emails

hello,
my mailman service doesn't operate correctly.
if i send an email with html-code, mailman try to put all this code in one line. is this line too ends, mailman makes a break and starts a new line. here it divides words and code like this:
"hello, i have an ques
tion"
or
"img src='http://www.na
me.de/img.gif'"
the first example works, the email is ok. but the second example dosn't work. first mailmain divides the code and put it together like this:
img src='http://www.na%20me.de/img.gif'
this image will not be displayed at the emailclient.
can you help me, that this not happend?
regards,
Oliver

Whatever you were trying to post is not readable.
Anyway, log into your mailman admin interface (yourdomain.tld/mailman/admin), pick your list and check the "Content filtering" settings.
Alternatively, Google is your friend.
See for example:
http://www.python.org/cgi-bin/faqw-mm.py?req=show&file=faq04.039.htp

Group Mail, Mailman and archives

Im confused. I have a mailman list I want to migrate to Leopard Server. Id like to let the listers have a wiki. Ive set up the group, and the wiki and I see it. (i have other problems with that but ignoring them for the minute)
Will poste to my mailman list be the mail archive?
If so can I migrate my old archive somewhere to make sure the old data is still searchable.
Or, is a mailman list completely separate from a group mailing list.
Like I said. Im confused.
If this is all explained somewhere please point me. Ive looked for doc and searched - probably not enough.
thanks
Angus

Hi
"It seems that group mail introduced in previous Snow Leopard Server, it's gone. There is mailman, but I don't need a mailing list , just a simple mail grooup functionality. It's impossible to do in Lion Server?"
Actually Group e-mailing was available in previous versions of the Server. It's not impossible to do in Lion Server either. It's just not obvious if you want to use the interface. There's not much documentation regarding this either.
These two threads (you could have searched this for yourself) should have the information you need:
https://discussions.apple.com/thread/3518290?start=0&tstart=0
https://discussions.apple.com/thread/3229060?start=0&tstart=0
There's also a way of doing this using WorkGroup Manager's Info Tab.
You should get into the habit of using the command line on OS X Server - the Terminal application in /Applications/Utilities - as this is the most effective way for you to get what you want, especially with the Mail Service.
The other Server Administration applications (which you may not be aware of?) are available for free download here:
http://support.apple.com/kb/DL1488
You will need Server Admin to initially configure the Mail Service properly. As ever remember to set up DNS Services correctly as everything you want or may want will depend on it.
HTH?
Tony

Another Mailman and virtual domains problem... mailbox does not exist

Hi,
this is yet another thread about virtual domain mailinglist with mailman.
To sum up:
- OpenDirectory account "[email protected]" -> mail delivered
- Deleting this account and creating a mailing-list "test11", opening the admin interface to change the host "server.domain.com" (which is the primary host of the machine, so each mailinglist is created with this host) and replacing it with "virtualdomain.com"
- sending an email to "[email protected]" -> following error:
Jan 18 14:12:23 server postfix/qmgr[74872]: 698E5BF735: from=<[email protected]>, size=691, nrcpt=1 (queue active)
Jan 18 14:12:23 server postfix/pipe[74882]: 698E5BF735: to=<[email protected]>, orig_to=<[email protected]>, relay=cyrus, delay=0.28, delays=0.14/0.01/0/0.13, dsn=5.6.0, status=bounced (data format error. Command output: test11: Mailbox does not exist )
- adding back the OD account "[email protected]" -> mail delivered to inbox (not to mailing-list recipients)
- now if i delete the mailinglist in Server Admin then send an email to "[email protected]" -> following error (seems obvious):
Jan 18 13:18:49 server postfix/lmtp[74275]: A9B7CBF45F: to=<[email protected]>, relay=server.domain.com[/var/imap/socket/lmtp], delay=0.16, delays=0.13/0/0/0.03, dsn=5.1.1, status=bounced (host server.domain.com[/var/imap/socket/lmtp] said: 550-Mailbox unknown. Either there is no mailbox associated with this 550-name or you do not have authorization to see it. 550 5.1.1 User unknown (in reply to RCPT TO command))
IOW, it looks like somehow the mailinglist aliases are being lost somewhere.
Postfix forgets to delivers the incomming mails to Mailman, doesn't it? According to lots of forum searchs it could be forced by using one of those two commands:
sudo /usr/sbin/postalias
sudo /usr/sbin/postmap
Unfortunately I dont know how they work precisely and can't find X.5 accurate information so I hope you can guide me through this step.
Also I don't know how to track the incomming mails at the moment they are dispatched to either an OD account (so it's delivered or generates the 550 error) or a Mailman list (so it's looking for aliases and so on).
Any help will be appreciated.
Config:
- in /etc/postfix/main.cf
virtual_transport = lmtp:unix:/var/imap/socket/lmtp
virtualmailboxdomains = hash:/etc/postfix/virtual_domains
alias_maps = hash:/etc/aliases,hash:/var/mailman/data/virtual-mailman
virtualaliasmaps = hash:/etc/aliases,hash:/var/mailman/data/virtual-mailman
- in /etc/postfix/virtual_domains
virtualdomain.com allow
- in /var/mailman/data/virtual-mailman
# LOOP ADDRESSES START
[email protected] mailman-loop
# LOOP ADDRESSES END
# STANZA START: test11
# CREATED: Sun Jan 18 13:55:03 2009
[email protected] test11
[email protected] test11-admin
[email protected] test11-bounces
[email protected] test11-confirm
[email protected] test11-join
[email protected] test11-leave
[email protected] test11-owner
[email protected] test11-request
[email protected] test11-subscribe
[email protected] test11-unsubscribe
# STANZA END: test11
- in /var/mailman/data/aliases
# The ultimate loop stopper address
mailman-loop: /private/var/mailman/data/owner-bounces.mbox
# STANZA START: mailman
# CREATED: Sun Jan 18 14:11:53 2009
mailman: "|/usr/share/mailman/mail/mailman post mailman"
mailman-admin: "|/usr/share/mailman/mail/mailman admin mailman"
mailman-bounces: "|/usr/share/mailman/mail/mailman bounces mailman"
mailman-confirm: "|/usr/share/mailman/mail/mailman confirm mailman"
mailman-join: "|/usr/share/mailman/mail/mailman join mailman"
mailman-leave: "|/usr/share/mailman/mail/mailman leave mailman"
mailman-owner: "|/usr/share/mailman/mail/mailman owner mailman"
mailman-request: "|/usr/share/mailman/mail/mailman request mailman"
mailman-subscribe: "|/usr/share/mailman/mail/mailman subscribe mailman"
mailman-unsubscribe: "|/usr/share/mailman/mail/mailman unsubscribe mailman"
# STANZA END: mailman
# STANZA START: test11
# CREATED: Sun Jan 18 14:11:53 2009
test11: "|/usr/share/mailman/mail/mailman post test11"
test11-admin: "|/usr/share/mailman/mail/mailman admin test11"
test11-bounces: "|/usr/share/mailman/mail/mailman bounces test11"
test11-confirm: "|/usr/share/mailman/mail/mailman confirm test11"
test11-join: "|/usr/share/mailman/mail/mailman join test11"
test11-leave: "|/usr/share/mailman/mail/mailman leave test11"
test11-owner: "|/usr/share/mailman/mail/mailman owner test11"
test11-request: "|/usr/share/mailman/mail/mailman request test11"
test11-subscribe: "|/usr/share/mailman/mail/mailman subscribe test11"
test11-unsubscribe: "|/usr/share/mailman/mail/mailman unsubscribe test11"
# STANZA END: test11
- in /usr/share/mailman/Mailman/mm_cfg.py
MTA = 'Postfix'
POSTFIXSTYLE_VIRTUALDOMAINS = ['virtualdomain.com','mail.virtualdomain.com']
add_virtualhost('virtualdomain.com', 'mail.virtualdomain.com')

I've finaly solved the problem by myself, mixing postfix-style aliases.
Since it's quite long I wrote a tutorial, it's here:
http://spip.ashorlivs.net/notepad/os-x/article/virtual-host-mailman-w-os-x-serve r
Hope it can help someone else.
Regards,
g.
Message was edited by: ashorlivs

Mailman https ??

Similar Messages

Maybe you are looking for