[Mailman-Users] Re: "Error: Unknown virtual host" trying to create new list from web UI

[Mark Sapiro]

On 7/29/20 10:24 PM, Sean McBride wrote:
> 
> After reading the comments in that file and FAQ 4.29, I *think* the correct 
> solution is to append the following 5 lines to my mm_cfg.py:
> 
> DEFAULT_EMAIL_HOST = 'rogue-research.com'
> DEFAULT_URL_HOST = 'mail.rogue-research.com'
> DEFAULT_URL_PATTERN = 'https://%s/mailman/'
> VIRTUAL_HOSTS.clear()
> add_virtualhost(DEFAULT_URL_HOST, DEFAULT_EMAIL_HOST)
> 
> Is that correct?

Yes, that looks good.

-- 
Mark Sapiro The highway is for gamblers,
San Francisco Bay Area, Californiabetter use your sense - B. Dylan
--
Mailman-Users mailing list -- mailman-users@python.org
To unsubscribe send an email to mailman-users-le...@python.org
https://mail.python.org/mailman3/lists/mailman-users.python.org/
Mailman FAQ: http://wiki.list.org/x/AgA3
Security Policy: http://wiki.list.org/x/QIA9
Searchable Archives: https://www.mail-archive.com/mailman-users@python.org/
https://mail.python.org/archives/list/mailman-users@python.org/

[Mailman-Users] "Error: Unknown virtual host" trying to create new list from web UI

[Sean McBride]

Hi all,

I'm running mailman 2.1.x.  I haven't had need to create a new list in years, 
but now I need to.  Trying to do so from the web UI here:
 

results in:
 "Error: Unknown virtual host: mail.rogue-research.com".

After searching for this, I now have a partial understanding of the problem.

In my Defaults.py I see:

DEFAULT_EMAIL_HOST = 'foo.rogue-research.com'
DEFAULT_URL_HOST = 'foo.rogue-research.com'
DEFAULT_URL_PATTERN = 'http://%s/mailman/'

foo is the real hostname of the machine. I guess that's how it ended up there? 
After reading the comments in that file and FAQ 4.29, I *think* the correct 
solution is to append the following 5 lines to my mm_cfg.py:

DEFAULT_EMAIL_HOST = 'rogue-research.com'
DEFAULT_URL_HOST = 'mail.rogue-research.com'
DEFAULT_URL_PATTERN = 'https://%s/mailman/'
VIRTUAL_HOSTS.clear()
add_virtualhost(DEFAULT_URL_HOST, DEFAULT_EMAIL_HOST)

Is that correct?

Many thanks,

Sean

--
Mailman-Users mailing list -- mailman-users@python.org
To unsubscribe send an email to mailman-users-le...@python.org
https://mail.python.org/mailman3/lists/mailman-users.python.org/
Mailman FAQ: http://wiki.list.org/x/AgA3
Security Policy: http://wiki.list.org/x/QIA9
Searchable Archives: https://www.mail-archive.com/mailman-users@python.org/
https://mail.python.org/archives/list/mailman-users@python.org/

[Mailman-Users] Re: Very strange issue With Mailman + Exchange(?)

[Bruce Johnson]

> On Apr 27, 2020, at 11:21 AM, Bruce Johnson  
> wrote:
> 
> I am not sure how to figure this out.
> 
> Lengthy explanation:
> 
> Internally in our Exchange server, that address is a distribution group whose 
> only member is the actual @lists.pharmacy.arizona.edu, because the 
> Mailman server is not our mail server. (we have a mildly complicated setup: 
> hybrid OnPrem and O365 exchange + Barracuda spam appliance in front of all of 
> it, which is our actual SMTP server.  
> 
> Outgoing email from the list server bypasses Exchange and is sent directly to 
> the Barracuda SMTP server.
> 
> For two users and ONLY these two users, somewhere between them and mailman 
> and back, the Mailman list is being expanded to put all the members of the 
> list on the CC line. It then gets held for approval with a ’too many 
> addresses’ message.

Just posting this for the record  in case any other person is unlucky enough to 
run into this…it turns out that the culprit in this case was the Zoom Outlook 
plug-in, when dealing with changing, deleting or adding to existing scheduled 
meeting instances (for instance biweekly faculty meetings were originally 
scheduled and sent as outlook invites to the mailman list. I finally caught how 
this was happening when another one of our people ran into it and noticed it 
only happened to the messages that had to do with Zoom meetings. 

I do not know the full details of the issue yet, but I'm guessing that Zoom 
tried to be oh-so-clever, went back to THEIR servers, retrieved and appended 
the email addresses for the people who had logged into the meetings associated 
with that Exchange event record in the past. Altering or deleting a simple 
calendar event in Exchange does not do this, so it’s not anything on the 
Exchange side of things.  

There appears to be no way of changing this on a quick perusal of the settings 
and Zoom is retiring the outlook plugin for a different architecture built into 
O365, I do not know yet if it continues the bug, but I'm sure I’ll find out as 
our entire campus is heavily invested in both Outlook and Zoom especially this 
fall.

-- 
Bruce Johnson
University of Arizona
College of Pharmacy
Information Technology Group

Institutions do not have opinions, merely customs


--
Mailman-Users mailing list -- mailman-users@python.org
To unsubscribe send an email to mailman-users-le...@python.org
https://mail.python.org/mailman3/lists/mailman-users.python.org/
Mailman FAQ: http://wiki.list.org/x/AgA3
Security Policy: http://wiki.list.org/x/QIA9
Searchable Archives: https://www.mail-archive.com/mailman-users@python.org/
https://mail.python.org/archives/list/mailman-users@python.org/